system has recovered from a serious error

[J Lunis]

My PC has recently crashed spontaneously with a half-second (too fast to
read) BSOD. After automatic reboot I get 8-9 popups seconds apart of
'the system has recovered from a serious error.'
Eventvwr shows error code 000000c4
parameter1 00000090, parameter2 2ffddd120,
parameter3 00000000, parameter4 00000000

 

[danny3xd]

first, I would try reinstalling OS. Choose to save files so it's not
an all day afaire.

 

[danny3xd]

first, I would try reinstalling OS. Choose to save files so it's not
an all day afaire.

 

[Rock]

My PC has recently crashed spontaneously with a half-second (too fast to
read) BSOD. After automatic reboot I get 8-9 popups seconds apart of
'the system has recovered from a serious error.'
Eventvwr shows error code 000000c4
parameter1 00000090, parameter2 2ffddd120,
parameter3 00000000, parameter4 00000000
------------------------------------------
In case it matters, I have tried My Computer|Advanced|Startup and
recovery|Settings|System Failure. 'Automatically restart' is not checked
so, I think, when my PC crashes with the blue screen of death, it should
stop at the blue screen. It does not - it reboots.

See this link for some information. Looks like a driver problem:
http://aumha.org/win5/kbestop.htm
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

 

[J Lunis]

See this link for some information. Looks like a driver problem:
http://aumha.org/win5/kbestop.htm
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

Thanks, I have run verifier and, if the answer is there, I can't find
it. The MS notes on this are quite technical (IMO). Can you suggest
anywhere to look, or at least narow down where to look, in the verifier
data?

 

[J Lunis]

See this link for some information. Looks like a driver problem:
http://aumha.org/win5/kbestop.htm
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

And if I read the MSDN document correctly, the '90' in parameter1 suggests
"The driver switched stacks, and the current stack is neither a thread
stack nor a DPC stack. (Typically, the driver doing this should be on
the stack obtained by the kb debugger command.)" Whatever that means.

 

[Rock]

Thanks, I have run verifier and, if the answer is there, I can't find
it. The MS notes on this are quite technical (IMO). Can you suggest
anywhere to look, or at least narow down where to look, in the verifier
data?

Search for recent posts by David Candy. He regularly posts how to debug
this issue using verifier.