Share via

Driver power state failure on Windows 7

Anonymous
2014-08-24T22:46:59+00:00

Hi,

New Lenovo T440s laptop with Windows 7.  50% of the time when I try to shut it down, the laptop hangs for 10 minutes or so, and then displays a driver power state BSOD.

I posted the minidump, application and system event logs here: http://1drv.ms/1p4Ana6

Would be very grateful for any pointers for understanding this.  I did run the Lenovo system update to make sure that I have the latest BIOS and Lenovo-supplied drivers.

Thanks,

Chris

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

25 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-08-24T23:34:09+00:00

    These crashes were related to memory corruption (probably caused by a driver). Please run these tests to verify your memory and find which driver is causing the problem.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    Since it is more likely to be a driver please run verifier first.

    1-Driver verifier (for complete directions see our wiki here)

    If verifier does not find the issue we can move on to this.

    **2-Memtest. (**You can read more about running memtest here)

    If you cannot boot after enabling verifier reboot into safe mode

    In Vista & win 7 (F8)

    In win 8**http://www.howtogeek.com/107511/how-to-boot-into-safe-mode-on-windows-8-the-easy-way/**

    Co-Authored by  JMH3143

    .

    0 comments
  2. Anonymous
    2014-08-25T00:19:20+00:00

    Thanks for your reply.

    I can confirm that I am not overclocking this laptop.  I'm looking for reliability, not performance ;-).

    I read the wiki page about the driver verifier and am concerned about using it, because the wiki says it might cause a need for a full system restore.  I am traveling and that sort of heavy lifting is difficult to arrange.

    I will run the driver verifier after a full system backup after I get back from my trip in a week.

    Thanks again for your help,

    Chris

    0 comments
  3. Anonymous
    2014-08-25T00:31:54+00:00

    Cmwd

    It is safe but out of an abundance of caution I included that warning.  If it wasnt safe it would not be built into the operating system.

    There is no rush I will stay subscribed to this thread.

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2014-08-27T09:43:51+00:00

    Hi,

    Thanks for your patience.  I ran verifier and booting normally afterwards did not need anything more than going into safe mode.

    However, the crash it induced was pretty early in the boot process.  The animation of the Windows logo had just started when it froze with a STOP error.  I think it was the IRQ_NOT_LESS_EQUAL but the BSOD went away pretty quickly.

    I could not find any new files in the minidump directory, but I saved the application and event logs which you can get here: http://1drv.ms/1pgmX0O

    Thanks for looking at this!

    CMWD

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2014-08-27T12:36:14+00:00

    CMWD

    We need to wait for the next one to see if it generates a DMP file.  If it does not check these

    For dumps to be produced. . .

    ▪ Page file must be on OS drive

    *Page file base allocation size must be > than installed physical RAM

    *Windows Error Reporting (WER) system service should be set to MANUAL

    *Set page file to system managed on the OS drive

    *Set system crash/recovery options to "kernel Memory Dump"

    *User account control must be running.

    * Sometimes SSD drives with older firmware do not create DMPS (update firmware)

    *Cleaner applications like Ccleaner delete DMP files so dont run them until you are fixed.

    0 comments