BSOD when restarting windows after exteneded user session.

Anonymous
2014-01-30T10:12:20+00:00

My PC has BSOD'ed on me several times when I tell it to restart windows. It keeps giving the DRIVER_POWER_STATE_FAILURE error in the BSOD.

I have traced the problem back to NTOSKRNL.EXE. the address in the stack is ntoskrnl,exe+78a8a. both times windows crashed during during the shutdown phase of a windows restart.

Full error:

ntoskrnl.exe ntoskrnl.exe+78a8a fffff80003408000 fffff800039ed000 0x005e5000 0x521ea035 8/28/2013 5:13:25 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18247 (win7sp1_gdr.130828-1532) Microsoft Corporation C:\windows\system32\ntoskrnl.exe 

Bug Check Code: 0x1000009f

I am not sure why my system is BSOD'ing on me, much less why ntoskrnl.exe is causing it. I'm not running or doing anything strange on my machine. Just BIONC (Seti@Home), games and the occasional document. I have already run SFC, as well as chkdsk, and the checksur utility, but nothing was found wrong. I ran a full scan using MSE and Malwarebytes, and came up clean there too. I want to know if this error's cause lies in the hardware or if windows is just complaining because I have had it running fro so long with out a restart.

If someone wants to look at the minidump files made by my system, let me know and I will post them to my skydrive. when I examined the minidumps using bluescreenview, only ntoskrnl.exe was highlighted in red. I can discern no other cause of this problem.

Windows for home | Previous Windows versions | Windows update

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

58 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-03-11T12:10:32+00:00

    Patrick Barker made this suggestion on 30 January 2014 Diskeeper is known to cause crashes, please remove it for troubleshooting purposes.

    Did you not remove it or did you remove it and put it back on your system?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-03-11T06:50:20+00:00

    there have been no updates released by Toshiba for my laptop in a long time (years). I have all the latest drivers they have made available. I use Microsft Security Essentials for my AV needs, and I have yet to see any sort of conflicts from it. as for verifier, activating it causes my system to bsod on me at boot, if you see my previous post on what happened last time I activated it, you will see what happens. I'm not in any sort of mood right now to mess with safe mode unless I absolutely have too. I don't know what this "DRIVER_POWER_STATE_FAILURE " is, but it is annoying that it happens so inconstantly, which makes it hard to diagnose. I did notice the crash address is different than last time, this time it is listed as "ntoskrnl.exe+75bc0"

    there hasn't been any real changes to my system's setup aside from some new games and updates from Microsoft. Maybe windows is not designed to run continuously for such long periods of time?

    Update....

    Boy do I feel stupid...... apparently my system not only made a kernel dump of the event, but a minidump of it as well..... I am uploading it as we speak as well as copies of my application and system event logs.

    here is an updated link to (hopefully) all the necessary files for troubleshooting

    --> http://1drv.ms/1cM07ZJ  <--

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-03-11T03:24:03+00:00

    ntoskrnl.exe is a Windows component which means something else drove it into Fault.

    Please review ALL the methods in the previously posted troubleshooters. Do ALL the updates

    you can. That means BIOS, chipset drivers, and all major drivers.

    A very intermittent BSOD issue is often the program you are running or antivirus. Though it

    can be anything those are the most likely causes for very sporadic occurrences.

    After ALL of those (and not before) run Driver Verifier to see if it can indicate an issues. See

    methods in the previously posted troubleshooter.

    Rob - SpiritX

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-03-11T03:19:38+00:00

    using 7-zip I was able to shrink memory.dmp down to 125 MB as opposed to the 234 Mb .ZIP file. is this size and file format acceptable to you? if so, I will upload it immediately.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-03-11T03:09:21+00:00

    the dump setting was set at kernel dump which is what either Microsoft of Toshiba had set it at.

    The error seems to be coming from ntoskrnl.exe, so I don't see how anything but a kernel dump would be helpful. I have now changed the dump setting to small memory dump.

    in any case, since this problem is intermittent, it may take a month or more before it happens again. when it does happen again, I will make a new set of files and post them here.

    Was this answer helpful?

    0 comments