Hello List,
we have been trying the flicker0.7 (http://sourceforge.net/p/flickertcb/wiki/Home/) on 32 bit windows 7. after successful execution of the flicker we get the following exception after random time. At first it seemed to a harddisk related issue, but then we confirmed that this happens only after the flicker execution. In short what flicker does is pause the os and then executes in TXT environment and upon exit restores the os. It also builds the
page tables to be used on TXT exit for restoration of the os.
Any clues on how to debug this issue.
*** Inpage error in C:\Windows\System32\svchost.exe -k WerSvcGroup:
The instruction at 77C255C0 referenced memory at 6FD11000.
This failed because of error c0000185.
This means that the I/O device reported an I/O error. Check your hardware. *** enter .exr 0020EE7C for the exception record
*** enter .cxr 0020EE9C for the context
*** then kb to get the faulting stack
Break instruction exception - code 80000003 (first chance)
Another observation is that service “WerSvcGroup” where inpage error occurs keeps on changing after each execution.
-Sandeep
The drive that contains the boot volume is failing I/Os after you come back
from whatever it is that this code is doing. Between having no idea what
this software does and not having a clearer description of the problem I
don’t think anyone is going to be able to help you.
The standard AHCI controller driver in Windows 7 (msahci) is available in
source form in the Windows 7 Driver Kit. You may want to build your own
version and see if you can reproduce the problem. It’s not a given that this
will help you and I would plan for this problem to be a major time sink
(especially without intimate knowledge of flicker and Windows).
Good luck!
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@windbg…
Hello List,
we have been trying the flicker0.7
(http://sourceforge.net/p/flickertcb/wiki/Home/) on 32 bit windows 7. after
successful execution of the flicker we get the following exception after
random time. At first it seemed to a harddisk related issue, but then we
confirmed that this happens only after the flicker execution. In short what
flicker does is pause the os and then executes in TXT environment and upon
exit restores the os. It also builds the
page tables to be used on TXT exit for restoration of the os.
Any clues on how to debug this issue.
*** Inpage error in C:\Windows\System32\svchost.exe -k WerSvcGroup:
The instruction at 77C255C0 referenced memory at 6FD11000.
This failed because of error c0000185.
This means that the I/O device reported an I/O error. Check your hardware.
*** enter .exr 0020EE7C for the exception record
*** enter .cxr 0020EE9C for the context
*** then kb to get the faulting stack
Break instruction exception - code 80000003 (first chance)
Another observation is that service “WerSvcGroup” where inpage error occurs
keeps on changing after each execution.
-Sandeep