DRIVER_POWER_STATE_FAILURE blue screen

[concord72]

Lenovo 410p running Win 8.1 (recently upgraded from 8, about 3 weeks ago), have gotten blue DRIVER_POWER_STATE_FAILURE screen about 4 times now, today was most recent. The last time I got it, I ran sigverif and found 2 unsigned files, which were related to my wireless printer. So i completely unistalled everything, went to the Brother site and downloaded the latest drivers and reinstalled my printer. Then i get the screen again today, run sigverif and boom, same 2 files. Names are "brtwdfe.ds" and "twmfj470dwn.ini". Both are located in "c:\windows/twain_32\brsc13a\mfj470dwn". What should I do? I've already went into Device Manager and manually updated all the printer drivers, it says they are all up to date. And I manually updated ALL my drivers when I upgraded to Win 8.1 about 3 weeks ago.

 

[johnbl]

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

 

[concord72]

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

I forgot to mention that i upgraded my BIOS about 2 weeks ago, could that have anything to do with it? I'm not too tech savy, i dont even know what BIOS is. I just went into device manager and checked all the drivers under BLUETOOTH and NETWORK ADAPTERS and they were all up to date.
I ran powercfg and got the energy report but don't really understand it too well, is there any way I could upload it here for you to take a look at?

 

[johnbl]

windows device manager will only check for driver updated to drivers that OEMs provide to microsoft. Most OEMs don't bother giving microsoft the fixed drivers. This means you have to use the OEM installer from the motherboard website or the actual OEM website. OEM used to have to pay microsoft($20k) to have their driver tested before microsoft would distribute them. Now microsoft will let the OEM test the drivers with the various Microsoft test suites(for free) but the OEM still don't bother to give microsoft the updated/fixed drivers. Bad drivers force users to buy new hardware and generates sales for the hardware manufactures.

go to the motherboard website and update the custom drivers for your machine. if you still have problems then you have to go to the OEM hardware website and get a driver update.

the BIOS update and the driver update often go hand and hand. Sometimes the OEM has to fix the BIOS to fix a bug for a hardware driver, they then make a driver update and put it on the website. You have problems, if you update the BIOS but not the driver with the matching change. (same if you update the driver but not the BIOS)

some "fixes" provided are really just disabling the feature rather than fixing the problem.
OEMs don't like to fix bugs in hardware drivers that they are not currently selling. (thye focus on new products that are about to ship or have just shipped)

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

I forgot to mention that i upgraded my BIOS about 2 weeks ago, could that have anything to do with it? I'm not too tech savy, i dont even know what BIOS is. I just went into device manager and checked all the drivers under BLUETOOTH and NETWORK ADAPTERS and they were all up to date.
I ran powercfg and got the energy report but don't really understand it too well, is there any way I could upload it here for you to take a look at?

 

[concord72]

windows device manager will only check for driver updated to drivers that OEMs provide to microsoft. Most OEMs don't bother giving microsoft the fixed drivers. This means you have to use the OEM installer from the motherboard website or the actual OEM website. OEM used to have to pay microsoft($20k) to have their driver tested before microsoft would distribute them. Now microsoft will let the OEM test the drivers with the various Microsoft test suites(for free) but the OEM still don't bother to give microsoft the updated/fixed drivers. Bad drivers force users to buy new hardware and generates sales for the hardware manufactures.

go to the motherboard website and update the custom drivers for your machine. if you still have problems then you have to go to the OEM hardware website and get a driver update.

the BIOS update and the driver update often go hand and hand. Sometimes the OEM has to fix the BIOS to fix a bug for a hardware driver, they then make a driver update and put it on the website. You have problems, if you update the BIOS but not the driver with the matching change. (same if you update the driver but not the BIOS)

some "fixes" provided are really just disabling the feature rather than fixing the problem.
OEMs don't like to fix bugs in hardware drivers that they are not currently selling. (thye focus on new products that are about to ship or have just shipped)

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

I forgot to mention that i upgraded my BIOS about 2 weeks ago, could that have anything to do with it? I'm not too tech savy, i dont even know what BIOS is. I just went into device manager and checked all the drivers under BLUETOOTH and NETWORK ADAPTERS and they were all up to date.
I ran powercfg and got the energy report but don't really understand it too well, is there any way I could upload it here for you to take a look at?

Ok, how do I find my motherboard website and how do I find the OEM hardware website? Im not that tech savvy in all honesty. After I upgraded by BIOS, i went to the support page on Lenovo's site for my laptop model and manually updated my drivers, that's all I have done.

 

[johnbl]

best to put the power config energy report and the memory .dmp file on a public cloud server so it could be downloaded.
Use something like mediafire, microsoft one drive, or any cloud storage provider and give the file public access then post a link to the file.

windows device manager will only check for driver updated to drivers that OEMs provide to microsoft. Most OEMs don't bother giving microsoft the fixed drivers. This means you have to use the OEM installer from the motherboard website or the actual OEM website. OEM used to have to pay microsoft($20k) to have their driver tested before microsoft would distribute them. Now microsoft will let the OEM test the drivers with the various Microsoft test suites(for free) but the OEM still don't bother to give microsoft the updated/fixed drivers. Bad drivers force users to buy new hardware and generates sales for the hardware manufactures.

go to the motherboard website and update the custom drivers for your machine. if you still have problems then you have to go to the OEM hardware website and get a driver update.

the BIOS update and the driver update often go hand and hand. Sometimes the OEM has to fix the BIOS to fix a bug for a hardware driver, they then make a driver update and put it on the website. You have problems, if you update the BIOS but not the driver with the matching change. (same if you update the driver but not the BIOS)

some "fixes" provided are really just disabling the feature rather than fixing the problem.
OEMs don't like to fix bugs in hardware drivers that they are not currently selling. (thye focus on new products that are about to ship or have just shipped)

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

I forgot to mention that i upgraded my BIOS about 2 weeks ago, could that have anything to do with it? I'm not too tech savy, i dont even know what BIOS is. I just went into device manager and checked all the drivers under BLUETOOTH and NETWORK ADAPTERS and they were all up to date.
I ran powercfg and got the energy report but don't really understand it too well, is there any way I could upload it here for you to take a look at?

Ok, how do I find my motherboard website and how do I find the OEM hardware website? Im not that tech savvy in all honesty. After I upgraded by BIOS, i went to the support page on Lenovo's site for my laptop model and manually updated my drivers, that's all I have done.

 

[concord72]

best to put the power config energy report and the memory .dmp file on a public cloud server so it could be downloaded.
Use something like mediafire, microsoft one drive, or any cloud storage provider and give the file public access then post a link to the file.

windows device manager will only check for driver updated to drivers that OEMs provide to microsoft. Most OEMs don't bother giving microsoft the fixed drivers. This means you have to use the OEM installer from the motherboard website or the actual OEM website. OEM used to have to pay microsoft($20k) to have their driver tested before microsoft would distribute them. Now microsoft will let the OEM test the drivers with the various Microsoft test suites(for free) but the OEM still don't bother to give microsoft the updated/fixed drivers. Bad drivers force users to buy new hardware and generates sales for the hardware manufactures.

go to the motherboard website and update the custom drivers for your machine. if you still have problems then you have to go to the OEM hardware website and get a driver update.

the BIOS update and the driver update often go hand and hand. Sometimes the OEM has to fix the BIOS to fix a bug for a hardware driver, they then make a driver update and put it on the website. You have problems, if you update the BIOS but not the driver with the matching change. (same if you update the driver but not the BIOS)

some "fixes" provided are really just disabling the feature rather than fixing the problem.
OEMs don't like to fix bugs in hardware drivers that they are not currently selling. (thye focus on new products that are about to ship or have just shipped)

you should not get a DRIVER_POWER_STATE_FAILURE from a wireless connected printer, and driver signing would not matter in either case.

This bugcheck would indicate windows told a hardware device to change its power state. (got to low power/sleep mode or wake up) and the driver or hardware did not respond so windows thought the device failed and called a bugcheck.

Normally, you would go to your motherboard web site and update your hardware drivers. I would start with the wireless ethernet drivers. Some of these problems require a BIOS update to fix, I would check the list of fixes for the machines bios and see if they have any power management fixes.

you can also post your memory .dmp file to a public access server on the cloud and someone can look and see if the debugger can list the device name that failed.

you can also use the powercfg.exe /energy command to help figure out what driver is failing.
just start cmd.exe as an admin then type the command and look at the report.

it is common for bluetooth devices and usb devices to have sleep issues, most of the time you just have to update them or turn off the sleep support for the device in the windows control panel device manager section for the device.

I forgot to mention that i upgraded my BIOS about 2 weeks ago, could that have anything to do with it? I'm not too tech savy, i dont even know what BIOS is. I just went into device manager and checked all the drivers under BLUETOOTH and NETWORK ADAPTERS and they were all up to date.
I ran powercfg and got the energy report but don't really understand it too well, is there any way I could upload it here for you to take a look at?

Ok, how do I find my motherboard website and how do I find the OEM hardware website? Im not that tech savvy in all honesty. After I upgraded by BIOS, i went to the support page on Lenovo's site for my laptop model and manually updated my drivers, that's all I have done.

It happened again, here are the reports: https://www.mediafire.com/?apcsb9tshc6dzbs