BSOD Driver_Power_State_Failure on Dell XPS 15 L502x

TheStormyOne · 11 Jul 2012

I have been getting BSOD's from Driver_Power_State_Failure over the past couple of days.
More often than not it occurs when browsing (particularly youtube). The system will hang and sometimes recover (loading what I was trying to load) but if not I get the BSOD with the error above. Strangely it doesn't seem to happen whenever I am playing games, even online ones. My specs are below and I have attached the 2 files asked of me in the attachments.
Thanks for any and all help.

Specs:
Dell xps 15 L502x
Windows 7 Home Premium x64 (Already on the laptop and unchanged)
Intel Core i5- 2410m 2.30ghz with Intel HD Graphics 3000
Ram- 8gb
HDD- 500gb
Nvidia geforce 525m

usasma · 11 Jul 2012

MSINFO32 is corrupted. Please do the following:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Memory dump blames your nVidia drivers. Please do the following:
- Download a fresh copy of the video drivers from the Dell website
- Uninstall the current video drivers
- Install the freshly downloaded video drivers
- monitor for further BSOD's

There's a copy protection program on your system that dates from 2004 (the driver lirsgt.sys is the one from 2004). It's probably not compatible with Windows 7 and must be uninstalled. It may have been when you installed an older movie or viewer on your system.

I can't tell for sure, but if you have more than one antivirus or firewall installed - please remove all but one.

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


Accelern.sys    Mon Dec 13 12:33:51 2010 (4D0658FF)
CtClsFlt.sys    Wed Jan 19 22:20:46 2011 (4D37AA0E)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
IntcDAud.sys    Fri Oct 15 04:28:17 2010 (4CB810A1)
Mbm3CBus.sys    Tue Apr 27 09:11:43 2010 (4BD6E28F)
Mbm3DevMt.sys   Tue Apr 27 09:25:58 2010 (4BD6E5E6)
Mbm3Mdm.sys     Tue Apr 27 09:19:00 2010 (4BD6E444)
Mbm3cm.sys      Tue Apr 27 09:25:36 2010 (4BD6E5D0)
Mbm3mdfl.sys    Tue Apr 27 09:18:39 2010 (4BD6E42F)
Mbm3wh.sys      Tue Apr 27 09:11:23 2010 (4BD6E27B)
NETwNs64.sys    Tue Dec 21 12:08:43 2010 (4D10DF1B)
PxHlpa64.sys    Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RTKVHD64.sys    Fri Feb 18 04:55:19 2011 (4D5E4207)
Rt64win7.sys    Wed Apr 11 12:29:16 2012 (4F85B15C)
RzSynapse.sys   Wed Dec 15 05:32:19 2010 (4D089933)
SASDIFSV64.SYS  Thu Jul 21 19:03:00 2011 (4E28B024)
SASKUTIL64.SYS  Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SMCLIB.SYS      Mon Jul 13 20:00:35 2009 (4A5BCAA3)
SynTP.sys       Thu Mar 31 21:30:00 2011 (4D952A98)
TurboB.sys      Mon Nov 29 18:02:31 2010 (4CF43107)
WDKMD.sys       Fri Nov 26 07:02:08 2010 (4CEFA1C0)
WwanUsbMp64.sys Fri Jul 30 08:41:15 2010 (4C52C86B)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswFsBlk.SYS    Tue Jul 03 12:13:12 2012 (4FF31A18)
aswMonFlt.sys   Tue Jul 03 12:13:24 2012 (4FF31A24)
aswSP.SYS       Tue Jul 03 12:14:23 2012 (4FF31A5F)
aswSnx.SYS      Tue Jul 03 12:14:27 2012 (4FF31A63)
aswTdi.SYS      Tue Jul 03 12:13:33 2012 (4FF31A2D)
aswrdr2.sys     Tue Jul 03 12:13:43 2012 (4FF31A37)
atksgt.sys      Mon Oct 20 03:50:38 2008 (48FC384E)
d554scard.sys   Thu Jun 24 04:52:11 2010 (4C231CBB)
dump_iaStor.sys Wed Jan 12 20:50:12 2011 (4D2E5A54)
iaStor.sys      Wed Jan 12 20:50:12 2011 (4D2E5A54)
igdkmd64.sys    Fri Mar 25 21:17:43 2011 (4D8D3EB7)
lirsgt.sys      Sat Mar 06 14:53:01 2004 (404A2C1D)
nusb3hub.sys    Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys    Thu Feb 10 00:52:33 2011 (4D537D21)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
nvkflt.sys      Wed Feb 29 13:05:52 2012 (4F4E6900)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
nvpciflt.sys    Wed Feb 29 13:05:34 2012 (4F4E68EE)
qicflt.sys      Thu Jul 01 21:46:34 2010 (4C2D44FA)
scfilter.sys    Sat Nov 20 05:09:59 2010 (4CE79E77)
stdcfltn.sys    Fri Aug 20 14:05:01 2010 (4C6EC3CD)
wwuss64.sys     Thu Nov 19 03:42:55 2009 (4B05050F)
wwussf64.sys    Thu Nov 19 03:42:54 2009 (4B05050E)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-22479-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 12:02:22.946 2012 (UTC - 4:00)
System Uptime: 0 days 1:28:21.194
BugCheck 9F, {3, fffffa8007c48a10, fffff80000b9c3d8, fffffa8007400e10}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 : pci.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07c48a10 fffff800`00b9c3d8 fffffa80`07400e10
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

TheStormyOne · 11 Jul 2012

Thank you for the reply.
I got rid off the driver you suggested.
I also did what you suggested regarding the nVidia drivers.
No BSOD as yet but I will keep watching for a day or so just to make sure.
I have attached the msinfo as requested but I couldn't see how to save a .txt version.

If the BSOD's are stopped will it be safe to update my nVidia drivers? Or should I just stick to the ones on the dell page?

Thanks again

usasma · 11 Jul 2012

I considered sending you to the nVidia page for driver updates - but some laptops use specially modified drivers and can't use the standard nVidia drivers. Stay with what you have until you've been BSOD free for a couple of weeks.

Then, the test for this is to set a System Restore point and then install the nVidia drivers. If they work properly for you, then all is good. If they don't, then you use the System Restore point to go back to a good point.

This copy of MSINFO32 is corrupt also (sometimes this happens because of the different language settings - but this is the first time I've seen it happen with Great Britian English). But I just learned a trick. I drag the .nfo file onto an open Notepad window and it opens up as if it were an xml file. I'm able to check the Startups and the Program Files. It's not easy to check the Network Adapters (I'm looking for wireless USB devices), the Drives (I'm looking to see if an SSD is installed), and the WER section (I'm looking for repeating errors).

TheStormyOne · 12 Jul 2012

Nope got another BSOD this morning.
I didn't get one at all last night playing and then this morning trying to watch some youtube and it hangs. I then try to shut down and on the logging off screen it dumps.
I have included the new dump files along with the previous 2 in the zip file below.
Thanks in advance.

usasma · 12 Jul 2012

Well, it still blames your nVidia drivers. Since you've updated the drivers it's most likely either:
- another program interfering with the video
- hardware problems with your video card (to include overheating).

The first thing is to remove the older drivers. To do this:
- Create a System Repair disc (Go to Start...All Programs...Maintenance...Create a System Repair Disc)
- Create a System Restore point
- search for lirsgt.sys and rename it to lirsgt.BAD (probably in C:\Windows\System32\drivers)
- search for atksgt.sys and rename it to atksgt.BAD (probably in C:\Windows\System32\drivers)
- reboot and see if that fixes the BSOD's
NOTE: If the system won't boot, boot from the System Repair disc and use System Restore to restore the system. If it still won't boot, then use the Command Prompt to un-rename the files that you renamed above.

Next, update all of the Dell networking drivers (LAN, WLAN, WiMAX, Bluetooth, etc)

If this doesn't stop the BSOD's, then try running Driver Verifier according to these instructions: Driver Verifier Settings

While waiting for a reply, start by running the free video diagnostics listed on this page: Additional Hardware Diagnostics

If the above steps don't stop the BSOD's, please zip up and upload any new memory dumps with your next post - and we'll see what we can figure out from there.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


Accelern.sys    Mon Dec 13 12:33:51 2010 (4D0658FF)
CtClsFlt.sys    Wed Jan 19 22:20:46 2011 (4D37AA0E)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
IntcDAud.sys    Fri Oct 15 04:28:17 2010 (4CB810A1)
Mbm3CBus.sys    Tue Apr 27 09:11:43 2010 (4BD6E28F)
Mbm3DevMt.sys   Tue Apr 27 09:25:58 2010 (4BD6E5E6)
Mbm3Mdm.sys     Tue Apr 27 09:19:00 2010 (4BD6E444)
Mbm3cm.sys      Tue Apr 27 09:25:36 2010 (4BD6E5D0)
Mbm3mdfl.sys    Tue Apr 27 09:18:39 2010 (4BD6E42F)
Mbm3wh.sys      Tue Apr 27 09:11:23 2010 (4BD6E27B)
NETwNs64.sys    Tue Dec 21 12:08:43 2010 (4D10DF1B)
PxHlpa64.sys    Tue Oct 20 14:08:42 2009 (4ADDFCAA)
RTKVHD64.sys    Fri Feb 18 04:55:19 2011 (4D5E4207)
Rt64win7.sys    Wed Apr 11 12:29:16 2012 (4F85B15C)
RzSynapse.sys   Wed Dec 15 05:32:19 2010 (4D089933)
SASDIFSV64.SYS  Thu Jul 21 19:03:00 2011 (4E28B024)
SASKUTIL64.SYS  Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SMCLIB.SYS      Mon Jul 13 20:00:35 2009 (4A5BCAA3)
SynTP.sys       Thu Mar 31 21:30:00 2011 (4D952A98)
TurboB.sys      Mon Nov 29 18:02:31 2010 (4CF43107)
WDKMD.sys       Fri Nov 26 07:02:08 2010 (4CEFA1C0)
WwanUsbMp64.sys Fri Jul 30 08:41:15 2010 (4C52C86B)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswFsBlk.SYS    Tue Jul 03 12:13:12 2012 (4FF31A18)
aswMonFlt.sys   Tue Jul 03 12:13:24 2012 (4FF31A24)
aswSP.SYS       Tue Jul 03 12:14:23 2012 (4FF31A5F)
aswSnx.SYS      Tue Jul 03 12:14:27 2012 (4FF31A63)
aswTdi.SYS      Tue Jul 03 12:13:33 2012 (4FF31A2D)
aswrdr2.sys     Tue Jul 03 12:13:43 2012 (4FF31A37)
atksgt.sys      Mon Oct 20 03:50:38 2008 (48FC384E)
d554scard.sys   Thu Jun 24 04:52:11 2010 (4C231CBB)
dump_iaStor.sys Wed Jan 12 20:50:12 2011 (4D2E5A54)
iaStor.sys      Wed Jan 12 20:50:12 2011 (4D2E5A54)
igdkmd64.sys    Fri Mar 25 21:17:43 2011 (4D8D3EB7)
lirsgt.sys      Sat Mar 06 14:53:01 2004 (404A2C1D)
nusb3hub.sys    Thu Feb 10 00:52:32 2011 (4D537D20)
nusb3xhc.sys    Thu Feb 10 00:52:33 2011 (4D537D21)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
nvkflt.sys      Thu Nov 03 14:40:40 2011 (4EB2E028)
nvkflt.sys      Wed Feb 29 13:05:52 2012 (4F4E6900)
nvlddmkm.sys    Thu Nov 03 14:39:38 2011 (4EB2DFEA)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
nvpciflt.sys    Thu Nov 03 14:40:21 2011 (4EB2E015)
nvpciflt.sys    Wed Feb 29 13:05:34 2012 (4F4E68EE)
qicflt.sys      Thu Jul 01 21:46:34 2010 (4C2D44FA)
scfilter.sys    Sat Nov 20 05:09:59 2010 (4CE79E77)
stdcfltn.sys    Fri Aug 20 14:05:01 2010 (4C6EC3CD)
wwuss64.sys     Thu Nov 19 03:42:55 2009 (4B05050F)
wwussf64.sys    Thu Nov 19 03:42:54 2009 (4B05050E)

Code:


Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071112-19375-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jul 11 15:28:43.523 2012 (UTC - 4:00)
System Uptime: 0 days 2:59:06.382
BugCheck 9F, {3, fffffa80094d3a10, fffff80000b9c3d8, fffffa8006e46010}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 : pci.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`094d3a10 fffff800`00b9c3d8 fffffa80`06e46010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\071212-19219-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul 12 06:28:31.944 2012 (UTC - 4:00)
System Uptime: 0 days 1:35:36.193
BugCheck 9F, {3, fffffa80094f0a10, fffff8000491a3d8, fffffa800b292010}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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 : pci.sys
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`094f0a10 fffff800`0491a3d8 fffffa80`0b292010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

TheStormyOne · 12 Jul 2012

Right then a big check to the removal off old drivers
I essentially took the drivers off and got rid of every trace of nvidia from my system before reinstalling the dell recommended drivers.
I had already updated all the network drivers on the advice of a friend before I posted on here, so that's done.
I doubt it could be an overheating problem. Firstly I use an external fan for exactly that worry (slightly paranoid due to a past laptop meltdown) and it performs brilliantly in a high stress game environment. So hopefully it's not that.
Fingers crossed and thanks very much.

TheStormyOne · 12 Jul 2012

Got another BSOD I will look at the two things you suggested in the previous comment but in the mean time here are the new dump files. It definitely doesn't seem to be BSODing as much but the hangs seem to be as frequent.

I had a peek at them myself and this one seem to be a little different from the previous ones. Although I only compared numbers that mean little to me so I could be wrong.

As a last resort would returning the system to factory settings stop the problem? I am willing to do so and have just finished backing up all of my personal documents just in case it comes to that.

Thanks again.

usasma · 12 Jul 2012

If you return the system to factory settings you'll be accomplishing several things at once. The drawback is that you might not fix the problem.

Basically there are 3 different issues that can cause this problem:
- 3rd party drivers
- hardware problems
- Windows problems

Reinstalling Windows will "fix" most Windows problems.
If you don't install 3rd party programs, then there will be minimal issues due to 3rd party drivers (things like the display, storage, chipset, etc drivers)
Which leaves you with primarily hardware issues as a cause (and if there aren't hardware issues, then the chances are that it'll work just fine) Remember that one of the possibilities here is a hardware problem with your video card.

BUT...the issue is that you have to ensure that Windows is updated AND that you've got the latest 3rd party drivers for the internal components that require them.

If you want a clean install, please follow this suggested procedure:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.
NOTE: Disconnect any additional hard drives (internal and external) that you may have installed. This may break any multi-boot setups that you have, so be prepared to conduct recovery operations on them once you're done. Don't forget that, if this is due to an infection, the additional hard drives may be infected also.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).

3. Use one of these free utilities to wipe the hard drive clean:
DBAN ( DBAN Download | Darik's Boot And Nuke )
KillDisk ( Freeware Download Active@ KillDisk ).
This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

5. Visit Windows Update and get all updates

6. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

7. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center

8. Visit Windows Update and get any other available updates

9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009/2010 is OK. Updates are available at the Asus support website.

CAVEAT: If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys). Update this driver immediately!!!

TheStormyOne · 13 Jul 2012

Two quick questions.
By Recovery disk do you mean the same one I made for the Driver Verifier step in one of your previous comments? Or something different?
And is this pretty much my last option at this point? Or did that new dump file I posted show up anything different?
Thanks again