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-11T03:03:22+00:00

    the dump was set as kernel dump, which whar either Microsoft or Toshiba set it at. I have changed it to small memory dump. but since the error is occurring with ntoskrnl.exe I don't see how a non kernel dump would help.

    in any case, since the 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
  2. Anonymous
    2014-03-11T01:24:40+00:00

    Hi,

    All we need is a minidump. You must have it set for memory.dmp instead which will

    be huge and I will not download it. A minidump is only 2 hundred K or so each.

    Rob - SpiritX

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-03-11T00:32:52+00:00

    ?huh? I' am not sure what you mean. placed my cursor in the system information file??? what does that even mean? in any case, I will reupload the file.

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-03-11T00:00:15+00:00

    The dump file are not accessible using your latest link.

    You have placed your cursor within the body of the System Information file so that only a small fraction the files has been uploaded. Please do not place your cursor within the body of the report before you upload.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-03-10T23:31:14+00:00

    I have done as you have asked plus a little extra. I made new versions of the files asked for before.

    all that remains is the upload of the ZIP file containing the memory.DMP to finish.

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

    the .ZIP file with memory.dmp finally finished uploading and is available to view

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

    Was this answer helpful?

    0 comments