Another crash on enering StandBy

[Guest]

The system crashes consistently trying to enter StandBy mode.

Microsoft Online Crash Analysis tells "Error Caused by a Device Driver".
However it does not mention which driver is that.

I built the whole system from scratch using the most recent drivers
available.
How do I know what piece of hardware/its driver to troubleshoot?

Any help is greatly appreciated.

BCCode=8086
BCP1=00000000
BCP2=00000000
BCP3=00000000
BCP4=00000000
OSVer=5_1_2600
SP=2_0
Product=256_1

 

[Joshua Smith [MSFT]]

Hi Govis,

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft

 

[Guest]

Hi Joshua,

Thank you for such great instructions.
Unfortunately the box does not seem to come up after crash with verifier
enabled.
It comes up when I enable verifier but as soon as I crash it never comes up
again. Even if I select a single driver to be verified. It gets stuck
somewhere past the Windows logo.

Any idea what is going on. Is there anything else I could try.
I can send you the current minidump that I have - where to?

Thanks,

Victor

 

[Joshua Smith [MSFT]]

Hi Victor,

You can try sending me some of your existing minidumps. I can see if
they have anything in them that indicates the issue. A lot of times however
what happens is some driver writes data where it wasn't supposed to. Later
another driver tries to read data from its location and since the memory
there has been over written it crashes because it can't execute what it
thinks should be code. Driver Verifier puts marks in the memory and then
checks the marks after each operation to see the point where memory is over
written. Then it can tell what module and function call was at fault.
The box I think you are referring to probably won't come up after
enabling verifier. That is if you mean the one that asks if you want to send
the crash data to Microsoft. This is normal. Verifier is a development tool.
If everyone writing a driver was sending crash reports for drivers in
development we'd get flooded. To send me the dumps you can either post
them here or email them directly to me. Just remove the online portion of my
email address.

Joshua Smith
OpenGL Test Lab
Microsoft
-----

Get Secure! www.microsoft.com/security

This posting is provided "AS IS" with no warranties, and confers no rights