BSOD when coming out of sleep

rcferry · 25 Mar 2013

I ran multiple AV and rootkit scans from multiple vendors and found only a couple of suspect files (removed.)

Also updated the BIOS and the touchpad drivers (would be interested in understanding how/where you found the error from the SynTP.sys driver), but still BSOD'ing every time the system comes out of sleep and occasionally at other times.

Any other suggestions? Dell wants me to reload the OS which I am reluctant to do.

As I've made multiple changes since my original post, I have attached new dump/system files.

Thanks.

Arc · 25 Mar 2013

Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus and the touchpad driver, syntpENh
Apply > OK
Accept then restart.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

rcferry · 25 Mar 2013

Deactivated all startups except touchpad and AV drivers as suggested and turned on DV.

Another BSOD occurred within 10 minutes of reboot. New DMP and other files are attached.

Arc · 26 Mar 2013

rcferry said:

Deactivated all startups except touchpad and AV drivers as suggested and turned on DV.

Another BSOD occurred within 10 minutes of reboot. New DMP and other files are attached.

Sorry to say, but the zip you uploaded says that you have not taken any of my suggestions.

You havent disabled startup, you havent enabled Driver Verifier.

In that situation, a person assisting you remotely does not have any more option to help you ..... unfortunately.

If you mind to follow the instructions, report back with results.

rcferry · 26 Mar 2013

I confirmed that DV is active and that MSCONFIG changes are in place (see attached images.) I did, however, rerun the SF Diags utility to make sure that the current settings are reflected as the tool gave me some problems last time.

Sorry for the confusion, but thanks for the help.

Arc · 26 Mar 2013

Now startup is cleared.

If there is any further BSOD, enable driver verifier. Crash dumps are saying the DV was not enabled at all.
And unfortunately we need to see the verifier enabled crash dumps .... as the normal ones are not giving any clue to proceed

rcferry · 26 Mar 2013

That is interesting as it appears to me that DV *is* enabled. Any way to verify this other than the Verifier.exe UI?

If not, I will wait until the next BSOD and upload the dump files. Maybe they will capture some usable information.

Arc · 26 Mar 2013

rcferry said:

That is interesting as it appears to me that DV *is* enabled. Any way to verify this other than the Verifier.exe UI?

If not, I will wait until the next BSOD and upload the dump files. Maybe they will capture some usable information.

No, but seeing a crash dump it is determinable that whether DV is enabled or not. Sorry to say, but the dumps are not saying that they are occurred in a DV enabled environment.

I think what you planned is good .... take the time .... try it again if the computer crashes again.

rcferry · 26 Mar 2013

I found the /query and /querysettings CLI commands for Verifier.exe, ran them, and copied the output to the attached file.

rcferry · 26 Mar 2013

I also found this post:

"After having to mention it numerous times in threads here, I feel it best to notify others here that in addition to turning off Low Resource Simulation as instructed in the article, it's best to do the same for IRP Logging and Force Pending I/O Requests.

IRP Logging is a very beneficial debugging check for Driver Verifier that will greatly enhance finding issues in I/O on a PC. However, the logs are not retained in crashdumps; they can only be accessed during a live kernel debugging session (that means hooking your PC to the troubled PC and running Windbg through that connection)."

I reset Verifier and then re-enabled it WITHOUT IRP Logging and Force Pending I/O Requests as it seems that they will not log to the crashdump file.