DRIVER_POWER_STATE_FAILURE on shutdown

Slartybart · 16 Dec 2014

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
.

HP600 · 16 Dec 2014

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.

Slartybart · 18 Dec 2014

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.

HP600 · 28 Sep 2015

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.