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-01-31T07:51:51+00:00

    Please try again following the instructions I gave earlier.

    Please provide a copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload to your Sky Drive, share with everyone and post a link here. Please say if the report has been obtained in safe mode.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-31T07:45:40+00:00

    yeah, I don't know what is going on. I told MSinfo to save the information, but it won't open it afterward. opening it with notepad reveals that the information is indeed there and has been recorded, but looks like xml code or something was used.   On a side note, after enabling driver verifier as directed, a BSOD occurs during every boot 000.fcl is the reported as the cause. the file is part of one of Cyberlink PowerDVD 13.  I know that under normal conditions (running without verifier) that no blue screen ever occurs, and that PowerDVD 13 is fully functional and does not crash at all. can I safely ignore this BSOD? I would supply a minidump just to be sure, except the whole dump process stalls at "initializing disk to record dump information (sic)"

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-01-31T00:35:41+00:00

    Hi,

    Don't keep Driver Verifier running at all times as it can cause instability when there would

    otherwise be none.

    Your steps so far might resolve the issues.

    Rob - SpiritX

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-01-31T00:08:47+00:00

    I ran the uninstaller for spdt.

    ireg.sys was part of WinDVD BD for Toshiba, I went ahead and uninstalled it since I now have PowerDVD 13.

    I have turned off Diskeeper for now. It is ironic that Diskeeper might be a problem source seeing that Microsoft uses a "lite" version of Diskeeper as part of windows disk defragmenter.

    "

    My general feeling is the real issue is the video hardware just can't play some games which is

    normal for most laptops not actually built specifically for gaming.  "

    this is not related to any problem I am having. My laptop is more than capable of playing many games. the video hardware, while not the most powerful, is good enough that I can play BF4 at low settings (game still looks awesome even at low).

    the BSOD only occurs when I try and restart windows after it as been running for an extended period. by extended, I mean more than a couple of days. I do keep the laptop in s3 when I'm not using it (i.e. when I'm sleeping). I usually don't restart during this period unless windows asks for a restart. so it may take up to a week or two with driver verifier running before the conditions i experienced the BSOD are able to replicated again.

    I have recent (1/7/14) video drivers but will check the NVidia site to see if any newer ones are available.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-01-31T00:06:30+00:00

    Good work! I look forward to your update.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments