DRIVER_POWER_STATE_FAILURE on shutdown

HP600

New member
Local time
10:04 PM
Messages
7
We've got this problem with some HP desktops that, from time to time, won't detect anything connected to the USB ports. It's very confusing, because it happens in a apparent random fashion. The machines are brand new HP ProDesk 600 TWR.

I feel it's a driver problem, and my mates think the trouble comes from cloning. The supplier thinks the problem comes from the special POS keyboards we use.

Anyway, the fact is that, when it happens, you can't press CTRL+ALT+DEL to enter Windows, as one of the non detected hard is the keyboard, so we press the button to turn the computer off, and it takes ages until decides to BSOD with a DRIVER_POWER_STATE_FAILURE.

Any ideas?
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64
Code:
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80036ad660, fffff8000473e3d0}

*** WARNING: Unable to verify timestamp for RTL8192cu.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.sys
Implicit thread is now fffffa80`036ad660
*** 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][COLOR="red"]RTL8192cu.sys[/COLOR][/B] ( RTL8192cu+1b2a7 )

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

0: kd> lmvm rtl8192cu
start             end                 module name
fffff880`058d8000 fffff880`059ea000   RTL8192cu T (no symbols)           
    Loaded symbol image file:[B][COLOR="red"] RTL8192cu.sys[/COLOR][/B]
    Image path: \SystemRoot\system32\DRIVERS\RTL8192cu.sys
    Image name: RTL8192cu.sys
    Timestamp:        Tue [B][COLOR="Red"]Jun 15[/COLOR][/B] 19:27:44 [B][COLOR="red"]2010[/COLOR][/B] (4C174E98)
    CheckSum:         000BFA37
    ImageSize:        00112000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
The problem appears to lie with the outdated Realtek wireless driver.....update it here:
Realtek
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Golden Mk. I.4
OS
Windows 10 Pro x64 ; Xubuntu x64
CPU
Intel i7 860 @ 2.80 GHz O/C'ed to 4.0GHz
Motherboard
Gigabyte P55A-UD3R Rev.1. Award BIOS F13
Memory
16GB Corsair Vengance DDR3 @ 661 MHz Dual Channel (9-9-9-24)
Graphics Card(s)
EVGA NVidia GTX 560 1024MB
Sound Card
Realtek Integrated
Monitor(s) Displays
Dual Samsung SyncMaster 2494HS
Screen Resolution
1920*1080 and 1920*1080
Hard Drives
1*Samsung 840 EVO 120GB SSD;
1*OCZ Vertex 2 60GB SSD;
2*Samsung F3 SpinPoint 1TB in RAID0;
1*Samsung F1 SpinPoint 1TB;
2*Western Digital 1TB External USB 3.0
1*Western Digital 500GB External USB 3.0
1*Seagate 500GB External USB 2.0
PSU
Thermaltake ToughPower QFan 750W
Case
Thermaltake Element S VK60001W2Z
Cooling
Corsair H60 Water Cooling, 2*230mm and 2*80mm case fans
Keyboard
Logitech G110
Mouse
Logitech MX518
Ok, so the good news are that you have detected succesfully the problematic realtek wifi my friend felt was the problem, but the (very) bad are that this is the only computer out of a group with this problem AND a realtek usb wifi.

At least now thanks to your post... are you a bot? ... I'm downloading the win 7 sdk so I can learn to check by myself other core dumps with windbg.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Golden Mk. I.4
OS
Windows 10 Pro x64 ; Xubuntu x64
CPU
Intel i7 860 @ 2.80 GHz O/C'ed to 4.0GHz
Motherboard
Gigabyte P55A-UD3R Rev.1. Award BIOS F13
Memory
16GB Corsair Vengance DDR3 @ 661 MHz Dual Channel (9-9-9-24)
Graphics Card(s)
EVGA NVidia GTX 560 1024MB
Sound Card
Realtek Integrated
Monitor(s) Displays
Dual Samsung SyncMaster 2494HS
Screen Resolution
1920*1080 and 1920*1080
Hard Drives
1*Samsung 840 EVO 120GB SSD;
1*OCZ Vertex 2 60GB SSD;
2*Samsung F3 SpinPoint 1TB in RAID0;
1*Samsung F1 SpinPoint 1TB;
2*Western Digital 1TB External USB 3.0
1*Western Digital 500GB External USB 3.0
1*Seagate 500GB External USB 2.0
PSU
Thermaltake ToughPower QFan 750W
Case
Thermaltake Element S VK60001W2Z
Cooling
Corsair H60 Water Cooling, 2*230mm and 2*80mm case fans
Keyboard
Logitech G110
Mouse
Logitech MX518
So I'm trying to do it myself but my windbg comes to a "different" solution. Off course I understand it was a memory corruption from the realtek driver, but, how can I get it to say it as clear as yours?

--

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\121514-3744-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00213022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`013175f2?
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325c890
Debug session time: Mon Dec 15 11:44:31.643 2014 (UTC + 1:00)
System Uptime: 0 days 0:33:29.954
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80036ad660, fffff8000473e3d0}
Unable to load image \SystemRoot\system32\DRIVERS\RTL8192cu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8192cu.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.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 : memory_corruption
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64
Just format the text
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Golden Mk. I.4
OS
Windows 10 Pro x64 ; Xubuntu x64
CPU
Intel i7 860 @ 2.80 GHz O/C'ed to 4.0GHz
Motherboard
Gigabyte P55A-UD3R Rev.1. Award BIOS F13
Memory
16GB Corsair Vengance DDR3 @ 661 MHz Dual Channel (9-9-9-24)
Graphics Card(s)
EVGA NVidia GTX 560 1024MB
Sound Card
Realtek Integrated
Monitor(s) Displays
Dual Samsung SyncMaster 2494HS
Screen Resolution
1920*1080 and 1920*1080
Hard Drives
1*Samsung 840 EVO 120GB SSD;
1*OCZ Vertex 2 60GB SSD;
2*Samsung F3 SpinPoint 1TB in RAID0;
1*Samsung F1 SpinPoint 1TB;
2*Western Digital 1TB External USB 3.0
1*Western Digital 500GB External USB 3.0
1*Seagate 500GB External USB 2.0
PSU
Thermaltake ToughPower QFan 750W
Case
Thermaltake Element S VK60001W2Z
Cooling
Corsair H60 Water Cooling, 2*230mm and 2*80mm case fans
Keyboard
Logitech G110
Mouse
Logitech MX518
Please excuse me but I can't understand what do you mean with format the text. Do you mean is better to put the output from winddbg in a attached .txt instead of dumping it in post? Or there's really an option in windbg called "Format the text"? Or what?

Anyway, I always get memory corruption, here's the minidump from another identical machine with the same problem.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Golden Mk. I.4
OS
Windows 10 Pro x64 ; Xubuntu x64
CPU
Intel i7 860 @ 2.80 GHz O/C'ed to 4.0GHz
Motherboard
Gigabyte P55A-UD3R Rev.1. Award BIOS F13
Memory
16GB Corsair Vengance DDR3 @ 661 MHz Dual Channel (9-9-9-24)
Graphics Card(s)
EVGA NVidia GTX 560 1024MB
Sound Card
Realtek Integrated
Monitor(s) Displays
Dual Samsung SyncMaster 2494HS
Screen Resolution
1920*1080 and 1920*1080
Hard Drives
1*Samsung 840 EVO 120GB SSD;
1*OCZ Vertex 2 60GB SSD;
2*Samsung F3 SpinPoint 1TB in RAID0;
1*Samsung F1 SpinPoint 1TB;
2*Western Digital 1TB External USB 3.0
1*Western Digital 500GB External USB 3.0
1*Seagate 500GB External USB 2.0
PSU
Thermaltake ToughPower QFan 750W
Case
Thermaltake Element S VK60001W2Z
Cooling
Corsair H60 Water Cooling, 2*230mm and 2*80mm case fans
Keyboard
Logitech G110
Mouse
Logitech MX518
Ok, so here's the output from the minidumps from two identical computer with the same problem, first is the one with realtek, the second doesn't have a realtek wifi but has the same problem:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\121514-3744-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00213022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`013175f2?
Symbol search path is: SRV*C:\WINDOWS\Symbols*[URL="http://msdl.microsoft.com/download/symbols"][U][COLOR=#000080]http://msdl.microsoft.com/download/symbols[/COLOR][/U][/URL]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325c890
Debug session time: Mon Dec 15 11:44:31.643 2014 (UTC + 1:00)
System Uptime: 0 days 0:33:29.954
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80036ad660, fffff8000473e3d0}
Unable to load image \SystemRoot\system32\DRIVERS\RTL8192cu.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8192cu.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.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 : memory_corruption

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Servidor\Desktop\hoss\121514-4960-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0020b342?
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02ea4890
Debug session time: Mon Dec 15 17:21:52.377 2014 (UTC + 1:00)
System Uptime: 0 days 1:15:26.361
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa80036ad040, fffff80000b9c3d0}
Unable to load image \SystemRoot\system32\drivers\usbfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.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 : memory_corruption
Followup: memory_corruption

I always get memory_corruption instead of the culprit.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64
My algorithm has computed that the USB driver is the issue.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Golden Mk. I.4
OS
Windows 10 Pro x64 ; Xubuntu x64
CPU
Intel i7 860 @ 2.80 GHz O/C'ed to 4.0GHz
Motherboard
Gigabyte P55A-UD3R Rev.1. Award BIOS F13
Memory
16GB Corsair Vengance DDR3 @ 661 MHz Dual Channel (9-9-9-24)
Graphics Card(s)
EVGA NVidia GTX 560 1024MB
Sound Card
Realtek Integrated
Monitor(s) Displays
Dual Samsung SyncMaster 2494HS
Screen Resolution
1920*1080 and 1920*1080
Hard Drives
1*Samsung 840 EVO 120GB SSD;
1*OCZ Vertex 2 60GB SSD;
2*Samsung F3 SpinPoint 1TB in RAID0;
1*Samsung F1 SpinPoint 1TB;
2*Western Digital 1TB External USB 3.0
1*Western Digital 500GB External USB 3.0
1*Seagate 500GB External USB 2.0
PSU
Thermaltake ToughPower QFan 750W
Case
Thermaltake Element S VK60001W2Z
Cooling
Corsair H60 Water Cooling, 2*230mm and 2*80mm case fans
Keyboard
Logitech G110
Mouse
Logitech MX518
Were these machines originally shipped with Win8? The HP site seems to imply that.

These are brand new machines ... please elaborate on the cloning reference.

Are all machines experiencing the issue HP ProDesk 600 TWR. Are they configured differently (hardware).

Golden bot identified drivers on two machines from the dumps - have you updated those drivers? Did that solve the issue on those machines?

Check for driver updates on any affected machine - Windows Updates offers hardware driver updates in Optional Updates. Install any that are offered.
What POS system are you using? I'm not certain that is causing the issues, but more information is better.

How many machines are affected? If it's only a few, it might be best to wait for a BSOD, identify the driver and update as needed. If it's 10 or more ... it might be better to start clean on all machines following the Clean re-install tutorial.

Back to Golden bot!

Bill
.
 
Last edited:

My Computer

Computer type
Laptop
Computer Manufacturer/Model Number
HP Pavilion dv6-6c10us
OS
x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
CPU
AMD A6-3420M APU with Radeon(tm) HD Graphics
Motherboard
Hewlett-Packard 1805
Memory
6.00 GB
Graphics Card(s)
AMD Radeon(TM) HD 6520G
Sound Card
(1) AMD High Definition Audio Device (2) IDT High Definiti
Monitor(s) Displays
HP W2072a 20" LCD (1600 x 900) @ 60 Hz
Screen Resolution
1366 x 768 x 32 bits (4294967296 colors) @ 60 Hz
Hard Drives
ST640LM0 00 HM641JI SATA Disk Device
Keyboard
Logitech k520 wireless KB
Mouse
Logitech m320 wireless mouse (bundled with KB)
Internet Speed
15/5 | 54 MB Wireless 'n'
Antivirus
Realtime: Defender or Avast | On-demand: Malwarebytes, ESET
Browser
IE 11 on Win8, IE 10 on win 7
Other Info
Media: [Gimp, Audacity, VLC] || Comm: [WEmail 2012, Skype] || Productivity: [OpenOffice,| Textpad] || Utils: [Sysinternals, cCleaner, Speccy, Defraggler]
Something has eaten my last reply, so I'll retype it:

* HP 600 TOWER, Win 7 from factory, supposedly all driver and bios updated, sometimes ten times in a row, sometimes can take months between errors, won't detect anything connected by USB and when we press the button to turn it off, will die after a while with an DRIVER_POWER_STATE_FAILURE . Hard to tell how much machines, i'd say in the tens.

* Now in the proccess to replicate it with a machine under my control without success, so I can talk to HP.

* First we formated them, then when the problem arised, we used the Win 7 that came with them as a basis for a Acronis True Image.

* POS keyboards are Cherry and no-brand. Also hand held Honeywell scanners.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64
Thanks for the update. I'm not sure what bullet #2 implies - are you working with HP on the issue?

If HP provides any useful support, please update your thread with what you find out even if it doesn't help solve the issue, but especially if HP does provide the solution.
 

My Computer

Computer type
Laptop
Computer Manufacturer/Model Number
HP Pavilion dv6-6c10us
OS
x64 (6.3.9600) Win8.1 Pro & soon dual boot x64 (6.1.7601) Win7_SP1 HomePrem
CPU
AMD A6-3420M APU with Radeon(tm) HD Graphics
Motherboard
Hewlett-Packard 1805
Memory
6.00 GB
Graphics Card(s)
AMD Radeon(TM) HD 6520G
Sound Card
(1) AMD High Definition Audio Device (2) IDT High Definiti
Monitor(s) Displays
HP W2072a 20" LCD (1600 x 900) @ 60 Hz
Screen Resolution
1366 x 768 x 32 bits (4294967296 colors) @ 60 Hz
Hard Drives
ST640LM0 00 HM641JI SATA Disk Device
Keyboard
Logitech k520 wireless KB
Mouse
Logitech m320 wireless mouse (bundled with KB)
Internet Speed
15/5 | 54 MB Wireless 'n'
Antivirus
Realtime: Defender or Avast | On-demand: Malwarebytes, ESET
Browser
IE 11 on Win8, IE 10 on win 7
Other Info
Media: [Gimp, Audacity, VLC] || Comm: [WEmail 2012, Skype] || Productivity: [OpenOffice,| Textpad] || Utils: [Sysinternals, cCleaner, Speccy, Defraggler]
I didn't even remember I had an account at this forum... just for an update, I'll tell you we never knew what caused the problem.

What we did is to just change randomly the "faulty" hardware to customers. The most we had from HP was a "thank you, we can see is our fault but we have no idea of what the problem is" when we sent them hardware samples to the national HP headquarters (keyboards and bar code scaners) to test. Not very happy with them.

In retrospective I feel it's obvious the HP motherboards randomly don't send enough current to start some power hungry devices... another way to almost always correct the problem was to connect the usb hardware to an usb hub and the usb to the HP computers. And it didn't matter if it was a powered 20 bucks hub or an un powered free publicity hub.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Pro x64
Back
Top