Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently (1 month ago) installed Windows 8 64 bit on my computer. I formatted my SSD completely, so as new again! I did not get any errors during the installation so I thought everything will be all right. Windows 8 works perfectly but only when I resume my computer from sleep after one minute I get a BSOD. I use BSOD Viewer from Nirsoft to view the errors who caused the BSOD. I did not get this error before I installed Windows 8. This is a link to one of the minidumps, here is a link of another minidump


BSOD Viewer

I tried to install all my drivers again but it did not help anything. My computers specs:

Intel i7 920
Gigabyte EX58-UD5
Crucial M4 128GB SSD
Club3D HD4890 Superclocked Edition
A bunch of hard disks

After sfc /scannow I opened the log file. The last view lines of the log:

2013-01-09 18:10:12, Info                  CSI    00000718 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
2013-01-09 18:12:13, Info                  CBS    Idle processing thread terminated normally
2013-01-09 18:12:13, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2013-01-09 18:12:13, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2013-01-09 18:12:13, Info                  CBS    Ending the TrustedInstaller main loop.
2013-01-09 18:12:13, Info                  CBS    Starting TrustedInstaller finalization.
2013-01-09 18:12:13, Info                  CBS    Ending TrustedInstaller finalization.
2013-01-09 18:12:13, Info                  CBS    Ending the TiWorker main loop.
2013-01-09 18:12:13, Info                  CBS    Starting TiWorker finalization.
2013-01-09 18:12:13, Info                  CBS    Ending TiWorker finalization.

Data from WhoCrashed 4.0.1:

On Thu 10-1-2013 14:58:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-32245-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340) 
Bugcheck code: 0x9F (0x3, 0xFFFFFA80051F7060, 0xFFFFF80242C3EB30, 0xFFFFFA8012FD1C10)
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
share|improve this question
share the dumps, the viewer is not the best tool to see the cause. – magicandre1981 Jan 9 '13 at 8:57
How do I share the dump? – ObAt Jan 9 '13 at 10:34
Export or copy the .dmp file. Upload it at Link the Share-URL in your question – nixda Jan 9 '13 at 11:21
So my editted post – ObAt Jan 9 '13 at 14:14
up vote 1 down vote accepted
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80051f7060, Physical Device Object of the stack
Arg3: fffff800873deb30, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8014e1c800, The blocked IRP

Debugging Details:


DRIVER_OBJECT: fffffa800f11c940

IMAGE_NAME:  atapi.sys



FAULTING_MODULE: fffff88000ff3000 atapi




PROCESS_NAME:  javaw.exe




Driver object (fffffa800f11c940) is for:
Driver Extension List: (id , addr)

Device Object list:
fffffa80157c8600: Could not read device object

DriverEntry:   fffff88000ff6ca0 atapi
DriverStartIo: 00000000 
DriverUnload:  fffff88000a957d0 ataport
AddDevice:     00000000 

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88000a9c508    ataport+0x27508
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff800876cd2ec    nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE                       fffff88000a9c508    ataport+0x27508
[03] IRP_MJ_READ                        fffff800876cd2ec    nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE                       fffff800876cd2ec    nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION           fffff800876cd2ec    nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION             fffff800876cd2ec    nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA                    fffff800876cd2ec    nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA                      fffff800876cd2ec    nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS               fffff800876cd2ec    nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff800876cd2ec    nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff800876cd2ec    nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff800876cd2ec    nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff800876cd2ec    nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL              fffff88000a7d000    ataport+0x8000
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff88000a7cfe0    ataport+0x7fe0
[10] IRP_MJ_SHUTDOWN                    fffff800876cd2ec    nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL                fffff800876cd2ec    nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP                     fffff800876cd2ec    nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT             fffff800876cd2ec    nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY              fffff800876cd2ec    nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY                fffff800876cd2ec    nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER                       fffff88000a7d020    ataport+0x8020
[17] IRP_MJ_SYSTEM_CONTROL              fffff88000a957a4    ataport+0x207a4
[18] IRP_MJ_DEVICE_CHANGE               fffff800876cd2ec    nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA                 fffff800876cd2ec    nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA                   fffff800876cd2ec    nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP                         fffff88000a9569c    ataport+0x2069c

 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa80051f7060 00000000 fffff88000a09720-fffffa800f5945a0 Success Error Cancel pending
          Unable to load image \SystemRoot\System32\drivers\ataport.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
 \Driver\atapi  CLASSPNP!ClasspPowerUpCompletion
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa800f594060 00000000 fffff88000fc2e40-00000000 Success Error Cancel pending
           \Driver\disk partmgr!PmPowerCompletion
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa800f594b10 00000000 fffff800877a032c-fffffa8010a6ac10 Success Error Cancel pending
           \Driver\partmgr  nt!PopRequestCompletion
            Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8010a6ac10    

    Loaded symbol image file: ataport.SYS
    Image path: \SystemRoot\System32\drivers\ataport.SYS
    Image name: ataport.SYS
    Timestamp:        Thu Jul 26 04:29:04 2012 

The atapi driver seams to be the cause. This strange thing is the missing symbols for the atapi.sys. Maybe the file is damaged. Run sfc /scannow to detect and fix broken files.

share|improve this answer
sfc /scannnow found some errors, I hope my pc doesn't chrash anymore :) – ObAt Jan 9 '13 at 17:18
ok, i can see that sfc found and fixed issues: "All files and registry keys listed in this transaction have been successfully repaired" – magicandre1981 Jan 10 '13 at 5:11
I also saw that, I hope it solved the bug who caused the BSOD. My PC did not chrash anymore but I didn't happen everyday. – ObAt Jan 10 '13 at 6:15
My computer chrashed today again with the same error, I uploaded the minidump ( sfc /scannow didn't find anything but I'm now reinstalling java because the error rapport says something about javaw.exe :) – ObAt Jan 10 '13 at 17:21
disable the power saving for hard drives/CD drives. Does this help? – magicandre1981 Jan 10 '13 at 20:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.