[SOLVED] BSOD randomly 0x0000009F

thermalfake · Jul 29, 2012

Hi everyone,

My friend told me about some strange things that occured few times.
His Asus notebook when lid was closed suddenly boot up from the beginning. This is random situation. I have looked into minidumps and saw all of them had one type 0x0000009F DRIVER_POWER_STATE_FAILURE. I've made some investigation and found this site http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329%28v=vs.85%29.aspx but cannot use nt!TRIAGE_9F_PNP, message was "Symbol nt!TRIAGE_9F_PNP not found".

I don't know what exactly make this things happen.
I would appreciate for any support.

writhziden · Jul 29, 2012

Software Concerns:

I would recommend that ASUS USBChargerPlus be removed from the system. Programs that allow for faster USB charging typically place the USB ports in an unnatural power state that can cause 0x9F crashes.

Code:

[COLOR=#ff0000][B]sptd.sys           Tue Aug 24 00:13:12 2010 (4C7362F8)[/B][/COLOR]

Please remove any CD/DVD virtualization software, probably Alcohol 52%, as it may use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.
Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor instead, which is free.

Analysis:

The following is for information purposes only.

Code:

**************************Sun Jul 22 12:56:51.464 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\thermalfake\072212-23571-01.dmp]
Windows 7 Kernel Version[B]7601 (Service Pack 1) MP (4 [/B] (Service Pack 1) MP (4 procs) Free x64
System Uptime:[B]0 days 6:03:37.524[/B]
BugCheck Code: [B]BugCheck 1000009F, {4, 258, fffffa8003fdc660, fffff80000b9c3d0}[/B]
*** WARNING: Unable to verify timestamp for btfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/B]
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed:[B]2294[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul  4 07:19:09.314 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\thermalfake\070412-27705-01.dmp]
Windows 7 Kernel Version[B]7601 (Service Pack 1) MP (4 [/B] (Service Pack 1) MP (4 procs) Free x64
System Uptime:[B]0 days 4:50:21.750[/B]
BugCheck Code: [B]BugCheck 1000009F, {4, 258, fffffa8003fdab50, fffff80000b9c3d0}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/B]
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed:[B]2294[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 23 11:18:52.767 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\thermalfake\062312-50981-01.dmp]
Windows 7 Kernel Version[B]7601 (Service Pack 1) MP (4 [/B] (Service Pack 1) MP (4 procs) Free x64
System Uptime:[B]0 days 4:24:56.828[/B]
BugCheck Code: [B]BugCheck 1000009F, {4, 258, fffffa8003fdab50, fffff80000b9c3d0}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/B]
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed:[B]2294[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 15 11:39:35.315 2012 (GMT-6)**************************
Loading Dump File [C:\Users\Mike\Downloads\thermalfake\061512-25272-01.dmp]
Windows 7 Kernel Version[B]7601 (Service Pack 1) MP (4 [/B] (Service Pack 1) MP (4 procs) Free x64
System Uptime:[B]0 days 4:37:37.751[/B]
BugCheck Code: [B]BugCheck 1000009F, {4, 258, fffffa8003fdc040, fffff80000ba2740}[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_MEMORY_CORRUPTION_ONE_BIT_LARGE[/B]
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed:[B]2294[/B]

3rd Party Drivers:

The following is for information purposes only. Any drivers in red should be updated.

Code:

**************************Sun Jul 22 12:56:51.464 2012 (GMT-6)**************************
hamachi.sys        Thu Feb 19 03:36:41 2009 (499D3639)
ASMMAP64.sys       Thu Jul  2 03:13:26 2009 (4A4C7A36)
intelppm.sys       Mon Jul 13 17:19:25 2009 (4A5BC0FD)
kbfiltr.sys        Mon Jul 20 03:21:42 2009 (4A643726)
sncduvc.SYS        Wed Jan 27 20:04:12 2010 (4B60FEAC)
amdxata.sys        Fri Mar 19 10:18:18 2010 (4BA3A3CA)
assd.sys           Tue Apr 27 19:41:31 2010 (4BD7924B)
btath_bus.sys      Thu Jun 24 00:17:43 2010 (4C22F887)
a37iiwg4.SYS       Sat Jul 17 04:58:04 2010 (4C418CBC)
atkwmiacpi64.sys   Sun Jul 25 23:56:49 2010 (4C4D23A1)
sptd.sys           Tue Aug 24 00:13:12 2010 (4C7362F8)
L1C62x64.sys       Tue Aug 24 03:14:01 2010 (4C738D59)
snp2uvc.sys        Tue Sep  7 03:19:37 2010 (4C8603A9)
IntcDAud.sys       Fri Oct 15 02:28:17 2010 (4CB810A1)
HECIx64.sys        Tue Oct 19 17:33:43 2010 (4CBE2AD7)
ATSwpWDF.sys       Tue Nov  2 09:09:34 2010 (4CD029AE)
iaStor.sys         Sat Nov  6 01:44:52 2010 (4CD50774)
TurboB.sys         Mon Nov 29 16:02:31 2010 (4CF43107)
AiCharger.sys      Fri Feb 25 02:41:45 2011 (4D677959)
btfilter.sys       Mon Mar  7 23:15:22 2011 (4D75C97A)
SynTP.sys          Thu Mar 31 19:30:00 2011 (4D952A98)
FLxHCIc.sys        Fri Apr  8 01:44:09 2011 (4D9EBCC9)
FLxHCIh.sys        Fri Apr  8 01:44:17 2011 (4D9EBCD1)
RTKVHD64.sys       Tue May 17 03:00:03 2011 (4DD23913)
athrx.sys          Tue Oct  4 00:49:29 2011 (4E8AAC79)
VBoxNetFlt.sys     Mon Dec 19 05:43:51 2011 (4EEF3187)
VBoxUSBMon.sys     Mon Dec 19 05:43:53 2011 (4EEF3189)
VBoxNetAdp.sys     Mon Dec 19 05:43:53 2011 (4EEF3189)
VBoxDrv.sys        Mon Dec 19 05:43:53 2011 (4EEF3189)
igdkmd64.sys       Mon Mar 19 17:31:54 2012 (4F67C1EA)
nvlddmkm.sys       Tue May 15 01:35:36 2012 (4FB20748)
nvpciflt.sys       Tue May 15 01:36:26 2012 (4FB2077A)
aswFsBlk.SYS       Tue Jul  3 10:13:12 2012 (4FF31A18)
aswMonFlt.sys      Tue Jul  3 10:13:24 2012 (4FF31A24)
aswTdi.SYS         Tue Jul  3 10:13:33 2012 (4FF31A2D)
aswrdr2.sys        Tue Jul  3 10:13:43 2012 (4FF31A37)
aswSP.SYS          Tue Jul  3 10:14:23 2012 (4FF31A5F)
aswSnx.SYS         Tue Jul  3 10:14:27 2012 (4FF31A63)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul  4 07:19:09.314 2012 (GMT-6)**************************
ai5lorce.SYS       Sat Jul 17 04:58:04 2010 (4C418CBC)
aswFsBlk.SYS       Tue Mar  6 17:01:31 2012 (4F56A55B)
aswMonFlt.sys      Tue Mar  6 17:01:51 2012 (4F56A56F)
aswTdi.SYS         Tue Mar  6 17:01:56 2012 (4F56A574)
aswrdr2.sys        Tue Mar  6 17:02:19 2012 (4F56A58B)
aswSP.SYS          Tue Mar  6 17:04:03 2012 (4F56A5F3)
aswSnx.SYS         Tue Mar  6 17:04:05 2012 (4F56A5F5)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jun 23 11:18:52.767 2012 (GMT-6)**************************
a0tafw22.SYS       Sat Jul 17 04:58:04 2010 (4C418CBC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 15 11:39:35.315 2012 (GMT-6)**************************
a7mrw6gb.SYS       Sat Jul 17 04:58:04 2010 (4C418CBC)

Recommendations:

See about removing Alcohol 52% and ASUS USBChargerPlus and determine if that resolves the issue. If not, the problem may be memory related.

If you are overclocking any hardware, please stop.
Run the boot version of Memtest86+. Let it run for at least 7-10 passes (preferably more) or until errors show up.

If you see even one error, stop the test and do the following:
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Click to expand...
1. Shut down and turn off your computer.
2. Unplug all power sources to the system: unplug the power from the outlet/surge protector or PSU (then remove the battery if it is a laptop).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing (or remove the RAM panel if it is a laptop).
5. Remove all but one memory module making sure you are grounded while doing so.
  Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
6. Replace the casing (or replace the RAM panel if it is a laptop) and put the remaining memory module(s) in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).
Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.
Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. You may want to run both Memtest86+ and the Windows Memory Diagnostics Tool overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
Check RAM compatibility:
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:
1. generate the images using the Snipping Tool,
2. go to where the images are saved,
3. right click in a blank area within the folder where the images are saved,
4. create a new folder,
5. name the folder CPUZ,
6. select all the images,
7. place the pointer over an image,
8. press and hold down the left mouse button and drag the image (all images should move with it),
9. drop the images into the CPUZ directory you created,
10. create a compressed (zipped) folder of CPUZ
11. upload the .zip file to the forums.

thermalfake · Jul 29, 2012

Thank you so much. I will inform about progression

writhziden · Jul 29, 2012

You're welcome. The latest crash also blamed a BlueTooth device. Is that device built into the system, or is it a USB dongle BlueTooth device?

If it is USB, that may also be a clue to implicating the ASUS ChargerPlus software.

Vir Gnarus · Jul 30, 2012

I concur with writhziden's diagnosis. Blasted ASUS AI Charger software has caused many people woes; not to mention so much other gimmicky software that comes with motherboards. Make sure your system is cleaned up of any software associated with your motherboard. The only things that should be left are drivers - except "USB drivers" which are unnecessary and broken.

thermalfake · Jul 31, 2012

Definitely Solved.

writhziden · Jul 31, 2012

Excellent news. Thank you for posting back. :grin1:

Vir Gnarus · Aug 1, 2012

Splendid job Writhzeden. I'm still curious about the single bit corruptions though, as that isn't usually what happens from an unscrupulous driver. Still, I wouldn't put it past AiCharger to be fouling up.

writhziden · Aug 1, 2012

Thanks. I also was questioning the corruptions. I wonder if it might be due to the power state of the USB ports causing the system hardware to enter a state either prematurely or delayed.

EDIT: Thanks Patrick. I have also often wondered what ASUS and Gigabyte developers might say if they saw our posts asking people to remove the utilities. I still half-expect someone from one of the two companies (or MSI for Afterburner?) to see one at some point and respond telling me it can't be their software.

Patrick · Aug 1, 2012

Indeed, excellent post Mike. Manufacturers really need to work on their software side on things as far as their utilities go...

With the amount of times I've told user's to uninstall mobo software / utilities, I'm surprised an Asus / Gigabyte hit squad hasn't arrived at my house! :lol:

Shintaro · Aug 1, 2012

If they did a decent job of writing the software we wouldn't need to ask people to remove it.
But I suppose that's not fair, maybe they are working in a programming sweat shop?

Those mobo utils are also high on my hit list as well. But then again so are some of the video card utils.

[SOLVED] BSOD randomly 0x0000009F

thermalfake

Member

writhziden

Administrator, .NET/UWP Developer

thermalfake

Member

writhziden

Administrator, .NET/UWP Developer

Vir Gnarus

BSOD Kernel Dump Expert

thermalfake

Member

writhziden

Administrator, .NET/UWP Developer

Vir Gnarus

BSOD Kernel Dump Expert

writhziden

Administrator, .NET/UWP Developer

Patrick

Sysnative Staff

Shintaro

Well-known member