BSOD going to sleep 0x0000009f

The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD was caused by SUPERAntiSpyware, apparently; but that may not be the reason behind it.

1. You disable Driver Verifier and see if the BSOD comes back even after then or not. Let us know. Till then, dont take any action against SAS.

For the main DRIVER_POWER_STATE_FAILURE issue, do the following:

2. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

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

3. Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

4. Uninstall/Upgrade team viewer.

Report us for any further BSOD after doing these four steps.
______________________________________________________________

Code:

BugCheck 1000007E, {c0000005, 934ed503, 807867cc, 807863b0}

Probably caused by : SASKUTIL.SYS ( SASKUTIL+7503 )

Followup: MachineOwner
---------

Code:

BugCheck 9F, {3, 861974f0, 835309e0, 867f1a88}

Unable to load image \SystemRoot\system32\DRIVERS\teamviewervpn.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for teamviewervpn.sys
*** ERROR: Module load completed but symbols could not be loaded for teamviewervpn.sys
Probably caused by : ntkrpamp

Followup: MachineOwner
---------
    Image name: teamviewervpn.sys
    Timestamp:        Thu Nov 29 13:57:19 2007

DeFacto said:

Found it before i did read your answer, uninstalled SAS

I told you (and telling you again) to not take any action against SAS, if the computer does not BSOD after disabling verifier.

Install it back.

The 0x7E caused by SAS was a glitch form the part of verifier, as it is appearing till now.

i did that before i saw your reply installed it back.

Also, before there were 2 sys files of SAS: sasdiv.sys and saskutil.sys. after reinstall of SAS there is only 1 - saskutil.sys.

One more thing i forgot to tell.
I have noticed, that sometimes my touchpad losses extra options like 2 finger click = mouse right and so on. After restart of PC those functions come back. I'm not sure if it makes any effect to 9F BSOD.

The features of the touchpad are powered by OEM driver. You may search for an update to it in Lenovo's site.

Report us for any further BSOD. If you can put the computer to sleep and wake it up successfully without a BSOD for a couple of times, 0x9F is apparently cured.

The update to teamviewer did not help.

Code:

BugCheck 9F, {3, 861974f0, 8353b9e0, 86a579f0}

Unable to load image \SystemRoot\system32\DRIVERS\teamviewervpn.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for teamviewervpn.sys
*** ERROR: Module load completed but symbols could not be loaded for teamviewervpn.sys
Probably caused by : ntkrpamp

Followup: MachineOwner
---------

It did not help because there is a driver that is extremely old, which is involved in the BSOD.

Code:

    Image name: teamviewervpn.sys
    Timestamp:        Thu Nov 29 13:57:19 2007

As long as this extremely old driver will be present there, the BSODs are supposed to take place.

As you cannot uninstall TeamViewer, you may ask to the program developer how to update this driver.

Upto then nothing more can be done.