[QUESTION] Driver Verifier lock ups and no dump

P

Patrick

Sysnative Staff
Joined
Jun 7, 2012
Posts
4,618
Hey guys,

Let's say you instruct a user to enable Driver Verifier as you have belief their issue is being caused by a device driver. What should we instruct the user to do if verifier is locking up the system when it's catching the driver rather than causing a BSOD and generating a dump?

What I usually do is tell the user to perform a clean boot and add things one at a time until you catch the culprit... however, there has to be a better way... right?

Regards,

Patrick
 
Do you mean "locking" as in OP needs to do a hard-shutdown?

If so, try groups of drivers, then single drivers to try and locate the culprit, assuming Driver Verifier is in fact locking up on a driver.
 
Thanks for the reply, John. This is what the OP said:

Catched the driver again it seems, but it didn't BSOD? It just locked up for a second, and closed.
Click to expand...

&

Happend again in less than 20 minutes again, just shuts down without any BSOD and does not generate any crash report what so ever.
Click to expand...

So enabling it for one 3rd party driver at a time would be the solution to this until you find out the driver that is causing the lock up?
 
Just a thought. I'm not sure if D/V tests >1 loaded driver or not. Maybe it depends on the settings...?

Is OP's system resources heavily taxed?
 
Please explain what actually happens? I see reference to locking up, and then a reference to shutting down. What is the actual, observable behavior? I'm slightly confused, so it might make sense to see if the OP can provide more detail into the "what happens" section of information gathering. If it locks up with no BSOD, we might want to try crashing the machine via a PS/2 keyboard to see if the hardware itself is hung, or just the driver framework.
 
I asked the OP in my most recent post, I will provide info for what he/she meant when I can.
 
Okay, sorry for the late update, here is what the OP says about the lock-up / shut down:

So it starts up with no problems whatsoever, but after some time the screen quickly gets all green colored (the main color of my desktop background) with strange stripes and then simply shuts down and the computer turns on again.
I found out that, if in the "Startup and Recovery" menu I make it not automatically restart, instead of rebooting, the screen stays on that strange green colored "image". If I change the desktop image the color also changes accordingly.
Click to expand...

What should I recommend at this point?
 
Thanks, Bruce.

I had the OP run Furmark and it went ~15 mins with minimum temps and no artifacts or issues, but I will ask for the voltages.
 
If that was running during the furmark test the GPU temp is really low.

Does he have a motherboard that supports the integrated video on the cpu?
If he does have him pull the video card out and see if the same thing happens using the integrated.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top