Driver Power State Failure
Hi, I apologize if this is the wrong forum for this. I received a BSOD on one of our production servers today. We are running Server 2008 R2 Enterprise with SQL 2008 Enterprise. It created a Minidump file which I loaded into a minidump reader. The bug check string said "DRIVER_POWER_STATE_FAILURE" and that the cause was ntoskrnl.exe. To be honest I'm really not sure what I'm looking at. There are a lot of search results for this issue, but none for Server 2008. Also, they all seem to have an obvious cause. Like a sound or webcam driver. Any help or a push in the right direction would be welcomed. Thanks
July 19th, 2012 4:18pm

It's probably i driver issue, can you upload the minidump so we can take a look at it so we can figure out which driver causing the bsod
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 4:35pm

Thanks. How would I normally upload the file to here?
July 19th, 2012 4:40pm

You can't upload to this site, but create an account on skydrive and put it there and then put a link in this thread.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 5:48pm

I have an account on adrive instead. I just wanted to know if there was a standard/traditional way people uploaded on here. http://www.adrive.com/public/59W3HX/071912-24304-01.dmp MD5: 7ebd7f5a2c6d91768c98d5b54dd55e26 Thanks again for your help.
July 19th, 2012 5:50pm

Generally, you may update BIOS and other hardware drivers first. If it does not work, you may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Arthur Li TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 2:30am

Generally, you may update BIOS and other hardware drivers first. If it does not work, you may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Arthur Li TechNet Community Support
July 24th, 2012 2:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics