BSOD after standby

Hi everyone,

I'm having problems with my DELL M4500 which presents me with a nice BSOD every time it comes back from standby. This is a Windows 10 64bit system. The BSOD typicall says CRITICAL_PROCESS_DIED (although I've already seen the odd MEMORY_MANAGEMENT as well), and to my dismay, it doesn't leave a proper dump: Coming from standby, the screen typically freezes for 30+ seconds (in most cases on the splash screen, although sometimes I just get a black screen and sometimes I actually get to see my desktop before the crash). The BSOD claims it's gathering information, but it actually doesn't get beyond 0% and then reboots quickly.

Be that as it may - I'm pretty sure my NVIDIA Quadro FX 880M is to blame, or rather its drivers. Although there's one thing I don't understand: I can't actually test if the same problem occurs because, with the NVIDIA driver uninstalled, I don't even *have* a standby mode - only hibernation. (No idea what the graphics driver has to do with standby mode - is this normal?)

I've followed the following instructions here:
BSOD, Nvidia driver crashes after waking from sleep - Windows 10 Forums

...but with no luck, I really only reinstalled the latest graphics driver now with none of the other deadweight, but the problem still occurs.

So what's the solution - simply disable standby mode?

If so, I can live without standby, no problem. What I can't live with is the crashes, because they've already cost me quite some data. So if I do avoid standby, I want to make sure that the problem is squashed and doesn't start haunting me via some other "feature". Thanks!

Please read BSOD Posting Instructions & How to upload files so we may be able to figure out why no dump is being created.

It seems the crashes aren't even logged, lets try a few things.

Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial.
Please search "services.msc" (without quotes) by pressing Windows key + r and press enter, search for the Windows Error Reporting Service and make sure it is set to manual.
Please make sure that the pagefile is handled by the system to ensure it is large enough Virtual Memory Paging File - Change

If all that is done and set properly lets see if we can try to force a crash, but not manually

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

If you would like help for your other laptop, please create a new thread for it so we don't get confused :)

Partly good to hear, disable driver verifier by resetting the settings and see how it goes :)

Driver verifier is a diagnostic tool, that it couldn't find drivers means no driver has violated the settings that driver verifier checked for :)

Whyfly said:

(As for the E4200 the symptoms are identical, and running drive verifier didn't change anything.)

In most cases the causes are different which is another reason to start another thread for a different system.