Solved BSOD ntoskrnl.exe

[dunliku]

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]

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

 

[axe0]

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. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

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

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

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.

[COLOR="red"]BUGCHECK_STR:  0xF4_IOERR[/COLOR]

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:  

[COLOR="red"]FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe[/COLOR]

ANALYSIS_SOURCE:  KM

[COLOR="Red"]FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_csrss.exe[/COLOR]

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

Followup: MachineOwner

 

[dunliku]

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]

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]

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.

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: [U]iaStorA.sys[/U]
    Timestamp:        [COLOR="Red"][U]Fri Apr 04 01:00:05 2014[/U][/COLOR] (533DE7F5)
    CheckSum:         000ABC34
    ImageSize:        002C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[dunliku]

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]

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

 

[dunliku]

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]

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.

 

[axe0]

Please run the tool again and upload the zip file.
I'll need the extra files.

 

[dunliku]

And another BSOD

 

[axe0]

Please run the tool and upload the zip file.
Just dumps won't be enough.

 

[dunliku]

Here is the zip with all the bsod i've had.

edit: my apologizes for not reading what you requested correctly.
Here is the zip

 

[axe0]

Please run the tool from BSOD Posting Instructions

 

[dunliku]

Another BSOD... this happened when i left the computer on with nothing major open (only notepad)

 

[dunliku]

I don't understand what is the source of the problem. The two HDD ran the seagate test fine, and even though the test ran postive, the computer still crashes.
I changed my HDD, yet it still crashes (it can sit there, doing nothing and crash). And when I run only my SSD, the computer runs fine (playing a intensive game and having a livestream open).
I do not think my SSD is corrupted, but I haven't run a chkdsk on it yet. I have ran a chkdsk /r on my SSD and HDD in the past, and they ran fine.
I had a previous problem before, which was my ram. Two of the 4 sticks were corrupted (hyperx fury), so I replaced them. I haven't ran a memtest on them yet, but I REALLY do not think that the fresh new sticks of ram would be corrupted. If so, then It may not be the ram, but rather the motherboard slot. (But i tested the motherboard slots with good sticks of ram, so maybe not...?)

edit: the only possible problems I can think of is maybe the SATA cable is faulty, the SSD is faulty, or something to do with RAID possibly? Because I am not sure if my computer is using RAID, but i do not believe it is (never checked).

 

[axe0]

Remove the Adobe bypass before we continue.

127.0.0.1				activate.adobe.com
127.0.0.1				practivate.adobe.com
127.0.0.1				ereg.adobe.com
127.0.0.1				activate.wip3.adobe.com
127.0.0.1				wip3.adobe.com
127.0.0.1				3dns-3.adobe.com
127.0.0.1				3dns-2.adobe.com
127.0.0.1				adobe-dns.adobe.com
127.0.0.1				adobe-dns-2.adobe.com
127.0.0.1				adobe-dns-3.adobe.com
127.0.0.1				ereg.wip3.adobe.com
127.0.0.1				activate-sea.adobe.com
127.0.0.1				wwis-dubc1-vip60.adobe.com
127.0.0.1				activate-sjc0.adobe.com
127.0.0.1                               adobe.activate.com
127.0.0.1                               adobeereg.com                        
127.0.0.1                               www.adobeereg.com                    
127.0.0.1                               wwis-dubc1-vip60.adobe.com           
127.0.0.1                               125.252.224.90                       
127.0.0.1                               125.252.224.91
127.0.0.1                               hl2rcv.adobe.com

 

[dunliku]

alright, i removed it.

 

[dunliku]

also, here are the chkdsk results

Checking file system on C:
The type of the file system is NTFS.
Volume label is SSD.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
469248 file records processed. File verification completed.
1307 large file records processed. 0 bad file records processed. 0 EA records processed. 50 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
532890 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
469248 file SDs/SIDs processed. Cleaning up 360 unused index entries from index $SII of file 0x9.
Cleaning up 360 unused index entries from index $SDH of file 0x9.
Cleaning up 360 unused security descriptors.
Security descriptor verification completed.
31822 data files processed. CHKDSK is verifying Usn Journal...
37139240 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
469232 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
30536388 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

224948223 KB total disk space.
102107392 KB in 146159 files.
111572 KB in 31823 indexes.
0 KB in bad sectors.
583707 KB in use by the system.
65536 KB occupied by the log file.
122145552 KB available on disk.

4096 bytes in each allocation unit.
56237055 total allocation units on disk.
30536388 allocation units available on disk.