Windows 8 and 8.1 Forums


BSOD...for driver_power_state_failure

  1. #1

    BSOD...for driver_power_state_failure


    I've been having many times of this BSOD. The screen usually stops responding and 1 minute later...it'll show windows ran into a problem and needs to restart. Please help. I neeed my laptop for work and I'll have to redo things everytime.

    Win 8
    I-7
    8gbram
    4gb Gcard nvidia 730m
    1tb toshiba HDD

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Bluetooth is disabled. Is this deliberate? If so, why?

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
    Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [S] DuplexSecure - FAQ [/S] Link broken as of 21 Jul 2012
    New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
    Alternate link: Disc-Tools.com
    Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
    Please update your video drivers from the nVidia website ( World Leader in Visual Computing Technologies | NVIDIA ).

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    NTIDrvr.sys Mon Apr 19 21:37:59 2010 (4BCD0577)
    NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology)
    http://www.carrona.org/drivers/driver.php?id=NTIDrvr.sys

    UBHelper.sys Tue Jul 6 00:19:26 2010 (4C32AECE)
    NTI CD &DVD-Maker or NTI Backup NOW! or NTI CD-Maker by NewTech Infosystems (usually in Acer Empowering Technology)
    http://www.carrona.org/drivers/driver.php?id=UBHelper.sys

    safedrv.sys Mon Oct 25 01:12:57 2010 (4CC511D9)
    Garena Update - World of Warcraft
    http://www.carrona.org/drivers/driver.php?id=safedrv.sys

    mwlPSDFilter.sys Fri Mar 25 03:12:11 2011 (4D8C404B)
    EgisTec Inc. Fingerprint Biometrics
    http://www.carrona.org/drivers/driver.php?id=mwlPSDFilter.sys

    mwlPSDNServ.sys Fri Mar 25 03:12:13 2011 (4D8C404D)
    EgisTec Inc. Fingerprint Biometrics
    http://www.carrona.org/drivers/driver.php?id=mwlPSDNServ.sys

    mwlPSDVDisk.sys Fri Mar 25 03:12:23 2011 (4D8C4057)
    EgisTec Inc. Fingerprint Biometrics
    http://www.carrona.org/drivers/driver.php?id=mwlPSDVDisk.sys

    k57nd60a.sys Wed Oct 19 16:17:36 2011 (4E9F3060)
    Broadcom NetLink Gigabit Ethernet NDIS6.x Unified Driver
    http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys




    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Apr 22 11:42:17.438 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\042213-23406-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:2 days 2:39:43.970
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, fffffa80077a6880, fffff880030067f0, fffffa800e0ec690}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80077a6880, Physical Device Object of the stack
    Arg3: fffff880030067f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800e0ec690, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  V2.14
      BIOS Release Date             02/19/2013
      Manufacturer                  Acer
      Product Name                  Aspire V3-571G
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 14:44:33.636 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041813-26578-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:1 days 6:12:55.377
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, fffffa800a07b880, fffff880009f47f0, fffffa8014ecf8a0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800a07b880, Physical Device Object of the stack
    Arg3: fffff880009f47f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa8014ecf8a0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Apr  8 20:38:43.227 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\040913-30671-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 23:44:06.110
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :pci.sys
    BugCheck 9F, {3, fffffa80093ee880, fffff880009f47e0, fffffa801264f300}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa80093ee880, Physical Device Object of the stack
    Arg3: fffff880009f47e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa801264f300, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys
    CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2395
      BIOS Version                  V2.14
      BIOS Release Date             02/19/2013
      Manufacturer                  Acer
      Product Name                  Aspire V3-571G
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Mon Apr 22 11:42:17.438 2013 (UTC - 4:00)**************************
    NTIDrvr.sys                 Mon Apr 19 21:37:59 2010 (4BCD0577)
    UBHelper.sys                Tue Jul  6 00:19:26 2010 (4C32AECE)
    safedrv.sys                 Mon Oct 25 01:12:57 2010 (4CC511D9)
    mwlPSDFilter.sys            Fri Mar 25 03:12:11 2011 (4D8C404B)
    mwlPSDNServ.sys             Fri Mar 25 03:12:13 2011 (4D8C404D)
    mwlPSDVDisk.sys             Fri Mar 25 03:12:23 2011 (4D8C4057)
    k57nd60a.sys                Wed Oct 19 16:17:36 2011 (4E9F3060)
    dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
    ccSetx64.sys                Fri May 25 15:34:57 2012 (4FBFDEE1)
    bScsiMSa.sys                Mon Jun 18 19:20:36 2012 (4FDFB7C4)
    btath_bus.sys               Thu Jun 21 01:22:17 2012 (4FE2AF89)
    b57xdmp.sys                 Mon Aug 13 13:59:00 2012 (50294064)
    b57xdbd.sys                 Mon Aug 13 13:59:16 2012 (50294074)
    bScsiSDa.sys                Tue Aug 14 14:15:16 2012 (502A95B4)
    aPs2Kb2Hid.sys              Wed Aug 29 23:40:57 2012 (503EE0C9)
    igdkmd64.sys                Wed Sep 26 15:49:04 2012 (50635C30)
    nvlddmkm.sys                Fri Oct 12 01:22:51 2012 (5077A92B)
    athw8x.sys                  Mon Oct 15 05:03:29 2012 (507BD161)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    ETD.sys                     Tue Nov 20 02:25:48 2012 (50AB307C)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    speedfan.sys                Sat Dec 29 15:59:35 2012 (50DF59B7)
    IntcDAud.sys                Fri Jan 11 08:55:16 2013 (50F019C4)
    dump_iaStorA.sys            Mon Jan 14 13:00:27 2013 (50F447BB)
    iaStorA.sys                 Mon Jan 14 13:00:27 2013 (50F447BB)
    RTKVHD64.sys                Tue Mar 19 08:14:59 2013 (514856C3)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Apr 17 14:44:33.636 2013 (UTC - 4:00)**************************
    RTKVHD64.sys                Tue Jun 12 06:02:32 2012 (4FD713B8)
    IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
    iaStorA.sys                 Mon Jul  9 16:42:33 2012 (4FFB4239)
    dump_iaStorA.sys            Mon Jul  9 16:42:33 2012 (4FFB4239)
    nvpciflt.sys                Fri Oct 12 01:23:17 2012 (5077A945)
    MfeASKM.sys                 Thu Dec  6 11:27:09 2012 (50C0C75D)
    mfehidk.sys                 Tue Jan 15 13:21:15 2013 (50F59E1B)
    mfewfpk.sys                 Tue Jan 15 13:21:30 2013 (50F59E2A)
    mfeapfk.sys                 Tue Jan 15 13:21:56 2013 (50F59E44)
    mfeavfk.sys                 Tue Jan 15 13:22:16 2013 (50F59E58)
    mfefirek.sys                Tue Jan 15 13:24:04 2013 (50F59EC4)
    cfwids.sys                  Tue Jan 15 13:24:37 2013 (50F59EE5)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Apr  8 20:38:43.227 2013 (UTC - 4:00)**************************
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
    iaStorA.sys                 Thu Aug 16 16:32:56 2012 (502D58F8)
    dump_iaStorA.sys            Thu Aug 16 16:32:56 2012 (502D58F8)
    
    http://www.carrona.org/drivers/driver.php?id=NTIDrvr.sys
    http://www.carrona.org/drivers/driver.php?id=UBHelper.sys
    http://www.carrona.org/drivers/driver.php?id=safedrv.sys
    http://www.carrona.org/drivers/driver.php?id=mwlPSDFilter.sys
    http://www.carrona.org/drivers/driver.php?id=mwlPSDNServ.sys
    http://www.carrona.org/drivers/driver.php?id=mwlPSDVDisk.sys
    http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys
    http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
    http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
    bScsiMSa.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=btath_bus.sys
    b57xdmp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    b57xdbd.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    bScsiSDa.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    aPs2Kb2Hid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=athw8x.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=ETD.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=speedfan.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=nvpciflt.sys
    MfeASKM.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=mfehidk.sys
    http://www.carrona.org/drivers/driver.php?id=mfewfpk.sys
    http://www.carrona.org/drivers/driver.php?id=mfeapfk.sys
    http://www.carrona.org/drivers/driver.php?id=mfeavfk.sys
    http://www.carrona.org/drivers/driver.php?id=mfefirek.sys
    http://www.carrona.org/drivers/driver.php?id=cfwids.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
      My System SpecsSystem Spec

  3. #3


    Turning off bluetooth to save battery on my Notebook. The Nvidia drivers which I autoscan my laptop shows that i need to get the update from my manufacturer website. I'm seeing one Nvidia VGA update and I'll get all of them updated tomorrow and will post back if any of the BSOD appears again. THANKS SO MUCH FOR THE DETAILED explanation.

    P.S: I uninstalled NTI
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    A short discussion about driver updating (from my experience. Sorry for rambling here, but this is mostly a driver updating guide with some discussion about BSOD issues:

    First off, if it's a new, out of box system - I update drivers using Windows Update. While there I also grab ALL available Windows Updates for the system. IME this is the easiest step to keep the system functioning smoothly.

    If it's my own system, I update drivers when there's a minor problem. As I'm generally pretty aware of problems (and know which drivers are involved) this is relatively easy for me - but would be harder for someone who doesn't have as much driver knowledge as I do. In these cases I target the fixes at the sub-systems that are having problems (for example: If I'm having problems with Steam, I remove and reinstall Steam).

    Removal vs upgrade - In the olden days, installers would leave older files when installing newer files - so a problem file might not be removed (and the "fix" wouldn't fix it). In those cases we developed the un-install/re-install method. That was that you uninstalled the program completely - and then installed a freshly downloaded copy of the latest compatible version.

    This fixed most problems - and there were 3rd party un-installers that did an even more thorough job of removing all traces. There were even programs that tracked every change made as a program was installed - and then it gave you the option to "fix" all of these changes when un-installing it.

    I found them to be unwieldy and time-consuming - and eventually stopped using them. It was my experience that the remaining drivers were fairly easy to isolate (if they were causing problems) and were amenable to manual removal methods which I now use. The problem with manual removal is that some drivers are tied to the boot process - so just deleting them will actually cause your system to stop booting. In response to this I've developed a several step method to "safely" remove drivers - and so far it seems to have been fairly successful the limited number of times that it's been used. The best point to this method is that it provides a recovery mechanism in case the system still refuses to boot.

    So, in short, the more severe problems can probably benefit from the un-install/re-install process (rather than just upgrading - or installing the new driver over the old one). It's what I suggest in the majority of cases.

    Then is the discussion about where to get your drivers from. If not having any problems, I don't see any problems with Windows Update drivers (with some notable exceptions). But make sure that you have all the Windows Updates also.

    BUT if you're having problems, you want the absolute latest fixes incorporated into your drivers. The only way to do that is to get the drivers from the website of those who developed the driver in the first place. There are certain exceptions to this, but it's the first place that you should check for the latest updates. The Driver Reference Table ( Driver Reference Table (DRT) ) was developed to make this chore a bit easier. It has links to the best known site to download the most current drivers from.

    If the driver isn't available from the originators website, then the next best place is the OEM manufacturer of your system/motherboard. While not as current as the originator, these folks will generally keep up with updates that affect their equipment.

    If unable to get drivers from the OEM website, then an internet search is probably the next best place to look. But be careful as there are scammers out there!!! DO NOT PAY TO DOWNLOAD DRIVERS or for driver "fixing" software!!!

    Finally is Windows Update. Please remember here that Microsoft only provides the server space for the 3rd party driver updates and doesn't validate the drivers that manufacturer's upload to it. Recently I installed Win8 on my old mobo - and Windows Update picked up a driver from 2005 for it (and installed it). That driver is a known cause of BSOD's on some Windows systems - so I have to wonder about it's inclusion. But also know that I don't get BSOD's from that driver - and haven't for a long, long time!

    This brings us to a discussion about BSOD's. I work in a computer repair shop and we see upwards of 40 different computers a week. And BSOD's are rare there (we see maybe a couple in a month's time). While we see a lot of BSOD's here - it's only a small sample of the entire population. In short, while a BSOD is a traumatic, overwhelming problem for those who have them - there just aren't that many happening in the real world. IMO Windows Updates fix more BSOD's than anything else that we do. Have a look at the listing of articles at this page: BSOD Index

    Driver Update example: Suppose you have a video card from eVGA that uses an nVidia chipset and it came installed on an Asus system.
    - the first place to check for the most current drivers is the nVidia website
    - the next most current place would be the eVGA website
    - the next most current place would be the Asus website
    - at some point here, you may want to look for other systems with this device (search the internet) - as they may have released drivers that eVGA or Asus didn't
    - lastly check at Windows Update for drivers

    BSOD's are caused by:
    - 3rd party drivers (over 90%)
    - hardware (less than 10%)
    - Windows (less than 1%) - but this presumes that all Windows Updates are installed

    Also, problems that appear to be hardware can be caused by:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    This is what makes the BSOD analyst's job so difficult.

    Good luck!
      My System SpecsSystem Spec

  5. #5


    So far uninstalled daemon tools and No BSOD for 2 days. Will look if there's any BSOD in the near future. I've check every known updates from my manufacturer and all are updated ( Some even more updated than given ones ) , BIOS up to date and windows update are all done. Only question is that nvidia needs me to get updates from manufacturer as Nvidia doesnt support the drivers for my Gcard and can only be obtained from the OEM website.
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    You've done a great job in fixing these things.
    Now just sit back and be sure that the BSOD's have stopped (I suggest waiting 2 weeks before saying "It's fixed!"

    There are many, many differences and exceptions when it comes to driver updating - and video drivers are some of the most frustrating one's that I've seen. If nVidia won't let you have a driver - then it's the manufacturer that they sold it to that's responsible for the updates. This makes you wonder if they're getting the latest (and if they're releasing it to you) - but the only alternative here is to contact the manufacturer and request a more up-to-date driver (which they may/may not have).

    In situations like this I will try to search the internet to see if other manufacturer's (that use the same chip) might have more updated drivers. Then I'll test to see if I can use their drivers on the card that I'm having trouble with (lot's of backups and System Restore points). Not a real successful venture most times - but on occasion I do get lucky and find a fix that way (hasn't happened for me in a couple of years tho').
      My System SpecsSystem Spec

  7. #7


    So far....no BSOD but my windows hang out of no where twice in 2 days....Only mouse moves and rest nothing moves and I had to press the power button 5 sec to off it even ctrl+alt+del not working. This acer is bringing lots of problem. I've been using speedfan to monitor my temperature and I managed to check my HDD fitness is 86% ...and this laptop is barely 3 months old
      My System SpecsSystem Spec

  8. #8


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please run the report collection app again (even though you're not having BSOD's): Blue Screen of Death (BSOD) Posting Instructions

    Please also do the following:
    - open Event Viewer (eventvwr.msc)
    - expand the Custom Views category (left click on the > next to the words "Custom Views")
    - right click on Administrative Events
    - select "Save all Events in Custom View as..."
    - save the file as Admin.evtx
    - zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
    - upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
      My System SpecsSystem Spec

  9. #9


    Sorry been busy lately. I'll get all the info if i ever gets a hang of BSOD again. So far I'm still fine since the Laptop hang. Thanks so much for your time and info <3
      My System SpecsSystem Spec

  10. #10


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Not a problem. If I don't respond within 2 days, send me a PM to jog the system.
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
BSOD...for driver_power_state_failure
Related Threads
Bsod driver_power_state_failure in BSOD Crashes and Debugging
Hello, Recently I've had a few driver power state failure BSODs - no pattern, just occasionally crashing while I'm using my laptop. SF Debug files are attached. Any help would be appreciated.
BSOD driver_power_state_failure in BSOD Crashes and Debugging
Been getting what seems to be the same BSOD for the last few days now. I have a G551J ASUS Laptop with Windows 8.1 Someone please help.
BSOD with DRIVER_POWER_STATE_FAILURE in BSOD Crashes and Debugging
Hi, I got several times BSOD on 5/15/2014 night and one time on 5/16/2014. It also happened some weeks earlier and I can't remember the date. And all of them are BSOD with DRIVER_POWER_STATE_FAILURE. It happens when I play games like Dark souls 2 or just right click on the desktop will also...
bsod driver_power_state_failure in BSOD Crashes and Debugging
Hi since upgrading to 8.1 I am getting bsod when computer resumes from suspension. Attached sf zip file. Regards
BSOD: DRIVER_POWER_STATE_FAILURE help please in BSOD Crashes and Debugging
Hi all, Driving me up the wall this ! As new Sony Vaio Pro 13 laptop which originally came with W8 - I then clean installed W8 Pro as I had a licence already and now have upgraded to 8.1 Pro (MSDN) Problem is, while everything was fine in W8 Pro, in 8.1 I can't sleep (lid closed) or shutdown...
Driver_power_state_failure bsod in BSOD Crashes and Debugging
So, I'm in need of help. Not sure where else to look, I googled for days but still can't find the answer. Attached are the 2 most recent dump files. the 44-01 is the one i get most often, the other one pops up once in a while. So basically the 44-01 happens 90% of the time after the computer...
Solved BSOD driver_power_state_failure in BSOD Crashes and Debugging
First of all, my apologies if the file I attached doesn't work. I left the computer alone for 10 minutes (big mistake) while Windows 8 Log Collector was finishing and when I returned, BSOD again. When I turned on my computer again, the W8 folder was there on the desktop. Please tell me if it...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook