Home > Bsod On > BSOD On Shutdown "DRIVER_POWER_STATE_FAILURE"

BSOD On Shutdown "DRIVER_POWER_STATE_FAILURE"

I would caution you about continued use of Alcohol 120 and McAfee. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Any suggestion for us? It has been Windows 7 compliant for some time (since the Beta/RC -- I've been loving 7 for some time). his comment is here

Register now! Attached Files TSF_Vista_Support.zip (1.56 MB, 263 views) Remove Advertisements Sponsored Links TechSupportForum.com Advertisement 04-04-2010, 10:24 PM #2 jcgriff2 Team Manager, Microsoft SupportBSOD Kernel Dump Expert Join BSOD BUGCHECK SUMMARY Code: Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Apr 4 08:21:51.643 2010 (GMT-4) System Uptime: 0 days 8:38:51.678 BugCheck 9F, {4, 258, fffffa80039f5b60, fffff80000b9c4d0} Probably caused by : This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. https://social.technet.microsoft.com/Forums/en-US/197f1783-b089-4c74-aec1-94c096d667d5/help-bsod-driverpowerstatefailure-9f-on-shutdown-win7?forum=w7itprogeneral

You get to the command prompt exactly the same way as you get to control panel. MEMTEST+ shows no memory errors 6. I initially attributed this effect to Google Chrome (a known issue for some users) and uninstalled it but the problem still comes back from time to time. Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7.

I went through and cleaned up the drivers the afternoon after we last talked (the 5th). Question #3: I have not had the machine apart since last (2011) summer when I installed a new HD, and although I picked out dust from the fans and cooling-tubes, I The time now is 08:16 PM. -- Mobile_Default -- TSF - v2.0 -- TSF - v1.0 Contact Us - Tech Support Forum - Site Map - Community Rules - Terms of Password Site Map Posting Help Register Rules Today's Posts Search Site Map Home Forum Rules Members List Contact Us Community Links Pictures & Albums Members List Search Forums Show Threads

Problem: Upon shutdown, Windows 7 will say shutting down for about 8 minutes and then blue screen. BSOD Help and Support Unexpected Shutdown DRIVER_POWER_STATE_FAILURE 0x0000009fNew system Win7 x64. After uninstalling the old and restarting, my computer froze at the Finish screen. http://www.eightforums.com/bsod-crashes-debugging/14404-bsod-shutdown-driver_power_state_failure.html It was only at that point I googled the model of the GPU to discover it was fitted to laptops !

It seems to... The cause was Asmedia 104x USB 3.0 controller. May be F10 r F12 want to be pressed for recovery while system gets on Post ur Laptop model and its Brand Reports: · Posted 5 years ago Top keshu This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Hmm, strange, I ran Vista for a couple of years along with McAfee and Alcohol 120% with no issues at all. Back to top #12 pcar pcar Topic Starter Members 55 posts OFFLINE Gender:Male Local time:09:16 PM Posted 03 June 2012 - 12:55 PM External mouse results: 1. On Wed 05/10/2011 10:18:24 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\100511-23072-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8003072A10, 0xFFFFF80000BA2748, 0xFFFFFA8003682480) Error: Reports: · Posted 5 years ago Top DIGGY416 Posts: 9 This post has been reported.

Same goes for updating Intel RST. http://servergeek.net/bsod-on/bsod-on-wake-up-bugcheck-7f.html Clean after that 3. BlueScreenView Reports on the four drivers listed above: ntoskrnl.exe ================================================== Dump File : 053012-17487-01.dmp Crash Time : 5/30/2012 7:10:33 PM Bug Check String : DRIVER_POWER_STATE_FAILURE Bug Check Code : 0x1000009f Parameter To answer your question regarding MSE, the answer is NO - I do not promote MSE simply because of MVP status.

Glad to hear of 5+ day BSOD-free status and certainly hope it continues. BSOD Crashes and Debugging Driver_power_state_failure bsodSo, I'm in need of help. The crash took place in the Windows kernel. weblink Several functions may not work.

BSOD Help and Support Often occurring 0x0000009f DRIVER_POWER_STATE_FAILURE- Gateway ZX4931 computer with touchscreen installed. - 3gig RAM - Pentium Dual Core E5800 - Intel G45/G43 Express Chipset - 64bit Windows 7 If so remove the USB Mouse prior to shutdown, and see if the bsod's stop. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Register Windows 7 Forum Forum Windows 8 Forums BSOD Crashes and Debugging BSOD on shutdown.

Reported by component: Processor Core Error Source: 3 Error Type: 10 Processor ID: 1 The details view of this entry contains further information. or you risk diminished security and all sorts of problems such as the one you are experiencing.Uninstall AdAware (this could be a nightmare to get rid of ... ) and ESET, Thanks for any assistance. I have seen both Alcohol 120 and Daemon Tools common driver sptd.sys named as the probable cause of BSODs going back to Vista. > It now continues in Windows 7.

I do run Windows Defender (nice that they sneak it in to run all the time in Vista and 7 ;)) and looked into MSE. On Thu 06/10/2011 1:02:54 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\100611-26442-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA8003057A10, 0xFFFFF80000BA2748, 0xFFFFFA8004C4B740) Error: Error: (05/31/2012 11:51:32 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE) Description: A fatal hardware error has occurred. check over here Error: (05/31/2012 11:51:32 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE) Description: A fatal hardware error has occurred.

Insert your Windows installation disc and restart your computer. 2. Any and all help is greatly appreciated. No viable info on this driver. Here's my dumpfile.

I thought I had all of the information in my initial post. I still have the .exe that installed the driver. The crash took place in the Windows kernel. AustrAlienGoogle is my friend.

Reported by component: Processor Core Error Source: 3 Error Type: 10 Processor ID: 1 The details view of this entry contains further information. SF Debug files are attached. Todays BlueScreenView reports have ntoskrnl.exe and athrx.sys. Back to top #9 cryptodan cryptodan Bleepin Madman Members 21,868 posts OFFLINE Gender:Male Location:Catonsville, Md Local time:03:16 AM Posted 02 June 2012 - 09:36 PM There will not be any

But ESET was an application I installed and ran after these troubles started. Module Path: C:\Windows\system32\athExt.dll Error Code: 126 Error: (05/31/2012 11:51:22 AM) (Source: BugCheck) (User: ) Description: 0x00000124 (0x0000000000000000, 0xfffffa800263c8f8, 0x0000000000000000, 0x0000000000000000)C:\Windows\Minidump\053112-16645-01.dmp053112-16645-01 Error: (05/31/2012 08:27:52 AM) (Source: Microsoft-Windows-WHEA-Logger) (User: LOCAL SERVICE) Description: A Isn't that the way it goes, haha! Reported by component: Processor Core Error Source: 3 Error Type: 9 Processor ID: 1 The details view of this entry contains further information.

what do i do to fix this? :( Reports: · Posted 5 years ago Top babinlonston Posts: 177 This post has been reported. because its windows 7 i just usually reinstall windows to factory settings but at this time i dont have a back up CD either or a data CD i just back Go to the company website and updated driver. Read the topic general suggestions for troubleshooting system crashes for more information.