Blue Screen of Death over and over

  • Thread starter Thread starter FuzzyCritter
  • Start date Start date
F

FuzzyCritter

Ok guys, for the past month BSOD has been appearing.
Finally got to read the death screen. Here's what it
says:

A problem has been detected and windows has been shut down
to prevent damage to your system.

A device driver attempting to corrupt the system has been
caught. The faulty driver currently on the Kernel stack
must be replaced with a working version.

Technical Info:

*** STOP: 0x000000c4 (0x00000081, 0x86197A98, 0x00000082, 0x00000000)

Beginning dump of physica memory
Physical dump complete
Contact your sys admin or technical support group for further assistance.

OK, now what guys. Need more info pls let me know.

John Smella
 
FuzzyCritter said:
Ok guys, for the past month BSOD has been appearing.
Finally got to read the death screen. Here's what it
says:

A problem has been detected and windows has been shut down
to prevent damage to your system.

A device driver attempting to corrupt the system has been
caught. The faulty driver currently on the Kernel stack
must be replaced with a working version.

Technical Info:

*** STOP: 0x000000c4 (0x00000081, 0x86197A98, 0x00000082, 0x00000000)

Beginning dump of physica memory
Physical dump complete
Contact your sys admin or technical support group for further assistance.

OK, now what guys. Need more info pls let me know.

John Smella
Click to expand...

It's a bad - damaged or incompatible - device driver error. What changed
in the system just before the BSOD's started?

That errror is DRIVER_VERIFIER_DETECTED_VIOLATION

So you're going to need to identify the driver before you can remove it.
The context around the error may provide clues (i.e. what exactly you were
doing at the time and what was running).

http://support.microsoft.com/?kbid=244617&sd=RMVP

You could probably also do a repair install, then reload drivers carefully.

Of course, all of this should be preceded by a backup of any and all valued
data.


HTH
-pk
 
Take the first two hex numbers there and Google them. You'll find many
articles on this. The short summary is to figure out what the last driver
you updated was, roll it back under Safe Mode, and see if it comes back up
normally. Also you may want to run the driver verification tool under safe
mode as well to identify the culprit.
 
Back
Top