Bug Check 0x9F DRIVER_POWER_STATE_FAILURE becoming more frequent

Page 1 of 5 123 ... LastLast

  1. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free

    Bug Check 0x9F DRIVER_POWER_STATE_FAILURE becoming more frequent

    Since the preparatory updates before Windows 10 (64-bit) v2004 and now after getting v2004 pushed to my Toshiba laptop, I have been getting DRIVER_POWER_STATE_FAILURE BSODs when sleeping/resuming.

    I would really appreciate some help pinpointing which driver causes this. Windows Update does not suggest any Optional updates/drivers at all. Here's the collected files:
    Attachment 283063

    My Windows 10 is Pro 64-bit v2004 build 19041.329.
      My Computer

  2. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Dump shows you are over clocking the CPU.

    CPUID: "Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz"
    MaxSpeed: 1800
    CurrentSpeed: 2394

    Please remove all over clocking for now, CPU and RAM, see if that makes any difference.

    There is only one dump file in the zip you uploaded. Are you running any cleanup program like CCleaner? If so please uncheck the following so the dumps don't get deleted any more.

    Attachment 283080

    Looks like you had 2 BSODs.

    Bluescreen: P1: 0X0000009f 2020-06-12 21:43
    Bluescreen: P1: 0X0000001a 2020-06-11 12:58

    The current dump is 0X00009f 11:43PM (21:43).

    Try uninstalling and reinstalling the latest version of E1I65X64.SYS.
    e1i65x64 Intel(R) PRO/1000 PCI Intel(R) PRO/1000

    It would also be a good idea to test your RAM. You have 16GB of DDR3 so test it with memtest86+ as described:

    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My Computers

  3. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter

    About overclocking:
    No I am running the laptop according to Toshiba's vanilla install, no performance tweaks.
    The frequencies you are seeing is Intel's standard scheme for laptop processors with a base frequency (1.8GHz) when running all cores and a turbo frequency for single core duties when power limits allow. The i7-4500U has a max turbo frequency of 3.0GHz. See Intel(R) Core™ i7-4500U Processor (4M Cache, up to 3.00 GHz) Product Specifications

    More dumps:
    Unfortunately I have no more dumps of the DRIVER_POWER_STATE_FAILURE problem. I suspect the aftermaths of the v2004 upgrade cleaned out some.

    Memory investigation:
    The memory related dump you found (but I did not include) is from another issue that has already been solved. I will do no further actions or investigations about that and therefore omitted that dump from the upload. Not using cleaners. (The v2004 upgrade had re-enabled my previously disabled memory compression which causes all sorts of issues on my system, now disabled again).

    I will look into upgrading the Intel PRO/1000 PCI driver, thanks!
      My Computer

  4. Posts : 1,479
    Windows 8.1 Enterprise x64

    Update O2Micro smartcard reader driver - O2Micro OZ776 Card Reader Controller Drivers Version
      My Computer

  5. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter

    Ok so I have now upgraded the network device to the latest available according to Intel's download site (Intel® Network Adapter Driver for Windows® 10 v25.0).
    As the device is in an integrated SoC it is named Intel(R) Ethernet Connection I218-V in Device Manager.

    I have now updated the device driver from
    Microsoft, 2018-06-12, e1d68x64.sys,
    Intel, 2019-07-25, e1d68x64.sys,
    ... so will now wait and see if the problem appears again. It doesn't happen on every sleep so might take a number of days too see any difference.

    - - - Updated - - -

    Ztruker said:
    Try uninstalling and reinstalling the latest version of E1I65X64.SYS.e1i65x64 Intel(R) PRO/1000 PCI Intel(R) PRO/1000
    MrPepka said:
    Did the dump reveal that these devices were part of the error stacktrace?
    Or are you pointing out old drivers that MAY be part of the problem?
      My Computer

  6. Posts : 1,479
    Windows 8.1 Enterprise x64

    I called the command! Poaction to view information about the power supply and IRP with this driver was in the S4 state, but maybe the driver incorrectly goes from the S4 state to normal operation, so you need to check it
      My Computer

  7. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter

    Ok nice. Device Manager currently shows:
    O2Micro, 2015-05-29, oz776x64.sys,
    and I updated through Update Driver > Search Windows Update and actually got a quite new driver:
    O2Micro, 2019-07-25, oz776x64.sys,
    Will see how it goes.

    Strangely I still don't get these updates offered as Optional updates in the new v2004 Windows Update...
      My Computer

  8. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter

    The 9F bugcheck happened again today. The scenario is like this:

    I close the lid on the laptop to put it to sleep.

    This should normally put it to sleep within a few seconds with a slowly flashing LED indicating "active" (not hibernated) sleep.

    Instead the laptop keeps on running (power on, fan on, etc) with a black screen and is unresponsive to lid open/close or (short) power button presses. If left alone for a long time it will finally power down but will on the next power-up reboot from scratch and report the 9F bugcheck in the event log.

    Zip file with new dump attached. I removed the previous dump from the zip to save space.

    It would be great to know if you can see any other suspect devices?
      My Computer

  9. Posts : 1,479
    Windows 8.1 Enterprise x64
      My Computer

  10. Posts : 38
    Microsoft Windows 10 Pro 64-bit 10586 Multiprocessor Free
    Thread Starter

    I already updated the I-218V driver in the previous post #5.
    I will look into the wifi driver!

    Did these devices show problems in the dump?
    Was the O2Micro smartcard driver ok this time? I don't use it so I could consider disabling that device if it helps?
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:42.
Find Us

Windows 10 Forums