BSOD ntoskrnl.exe

dunliku · 15 Oct 2015

Here are the dump files, I am not to sure how to recreate the problem, the only thing I know is that:
Windows starts to freeze, take a long time to move/copy files.
Couple minutes later, computer crashes and gets BSOD.

dunliku · 16 Oct 2015

beep boop, if you've read this and attempted to read the dump files, thank you.

**axe0** · 16 Oct 2015

Hi dunliku,

Welcome to the 7forums.

There is an Input/Output error meaning the data can't be read from the hard drive.
Please test your hard drives with SeaTools and chkdsk for SSD's.

Diagnostics Test

HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check

Code:

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800f40fb10, Terminating object
Arg3: fffffa800f40fdf0, Process image file name
Arg4: fffff800031c4e70, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800f40fb10

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`086dae38 fffff800`03256cb2 : 00000000`000000f4 00000000`00000003 fffffa80`0f40fb10 fffffa80`0f40fdf0 : nt!KeBugCheckEx
fffff880`086dae40 fffff800`0320dd8b : ffffffff`ffffffff fffffa80`0f57b060 fffffa80`0f40fb10 fffffa80`0f40fb10 : nt!PspCatchCriticalBreak+0x92
fffff880`086dae80 fffff800`03178484 : ffffffff`ffffffff 00000000`00000001 fffffa80`0f40fb10 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29ce6
fffff880`086daed0 fffff800`02ebf853 : fffffa80`0f40fb10 fffff800`c0000006 fffffa80`0f57b060 00000000`02bd0c80 : nt!NtTerminateProcess+0xf4
fffff880`086daf50 fffff800`02ebbe10 : fffff800`02f41929 fffff880`086dba38 fffff880`086db790 fffff880`086dbae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`086db0e8 fffff800`02f41929 : fffff880`086dba38 fffff880`086db790 fffff880`086dbae0 00000000`02bd1990 : nt!KiServiceLinkage
fffff880`086db0f0 fffff800`02ebfc42 : fffff880`086dba38 00000000`000713b8 fffff880`086dbae0 00000000`02bd1468 : nt! ?? ::FNODOBFM::`string'+0x48074
fffff880`086db900 fffff800`02ebe7ba : 00000000`00000000 00000000`77958af4 00000000`00000001 00000000`000713b8 : nt!KiExceptionDispatch+0xc2
fffff880`086dbae0 00000000`779e8f72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02bd13b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779e8f72


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_csrss.exe

FAILURE_ID_HASH:  {183378f4-a174-8cab-8ad7-e5d860a58439}

Followup: MachineOwner

dunliku · 17 Oct 2015

I managed to perform a long generic test for my harddrives, and both of them passed the test with 99% (i dont know why the wd hard drive doesnt show the percentage)
I will do a chkdsk for the ssd tonight, and post the results.

dunliku · 17 Oct 2015

Okay, well I got another bsod, then my computer wasn't able to start up windows (I believe i got a black screen of death). I ran it into safe mode, got into it. Tried to run regularly, which took a bit longer then usual. Now, my HDD is not read by the computer. My guess would be that the HDD is corrupted or broken in some way, even though the test showed nothing. Here is the newest BSOD.

**axe0** · 17 Oct 2015

It is the Intel Rapid Storage Technology this time.
Please check Intel for driver updates if you are using RAID.
If you are not using RAID, you can remove the software.

Code:

0: kd> lmvm iaStorA
start             end                 module name
fffff880`010c6000 fffff880`01389000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Fri Apr 04 01:00:05 2014 (533DE7F5)
    CheckSum:         000ABC34
    ImageSize:        002C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

dunliku · 17 Oct 2015

Is it possible that the original problem from the start of why the hard drive couldn't be read related to Intel Rapid Storage Technology?

**axe0** · 17 Oct 2015

I am certainly not an expert with this driver and hard drives, so I cannot really say if it is or is not.

dunliku · 17 Oct 2015

Okay, well I'm going to try to remove IRST, and try the computer with the SSD installed. Then, if nothing goes wrong, I will install the HDD.

dunliku · 17 Oct 2015

And I got a BSOD right after windows got to the desktop with the HDD installed and IRST uninstalled.
Here you go, and thank you for assisting.