Try running Seatools Long and Short Test on your Hard Drive along with check disk SeaTools for DOS and Windows - How to Use
If you run Memtest86+ for less than 8 Passes, you are wasting your time. It requires a minimum of 8 passes to completely check the ram, and with 16 GB of ram it will take 20 hours. I know what a pain it can be, been there, done that. I run it fairly often.
I have run the chkdsk in windows. These are the results.
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
172544 file records processed. File verification completed.
6942 large file records processed. 0 bad file records processed. 0 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
229546 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
172544 file SDs/SIDs processed. CHKDSK is compacting the security descriptor stream
Cleaning up 2604 unused security descriptors.
28502 data files processed. CHKDSK is verifying Usn Journal...
36390488 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
976657407 KB total disk space.
583731912 KB in 136326 files.
89404 KB in 28505 indexes.
0 KB in bad sectors.
305715 KB in use by the system.
65536 KB occupied by the log file.
392530376 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
98132594 allocation units available on disk.
Will be running sea tools later.
It passed both the short and long test in seatools. Right after the test my PC slowed down to a crawl and I couldn't even open any programs. So does that mean i can rule out hard drive being the cause of the problem ?
Not necessarily. No test is 100% accurate. The dump file lists a hard drive code and points to an I/O error. What information we have right now points to the hard drive. Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
After that, please upload the BSOD posting instructions again. Blue Screen of Death (BSOD) Posting Instructions
I have ran the sfc Scannow in windows. It gave me this msg "Windows resource protection did not find any integrity viloations". So that sounds like its alright. 5mins later BSOD again. In a desperate attempt i even changed the sata cable. It still does not help. And thank you for all ur advice and help essenbe.
Last edited by buzztiger; 10 Jun 2015 at 12:12.
The dump is still saying the same thing
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: fffffa8010505b30, Terminating object Arg3: fffffa8010505e10, Process image file name Arg4: fffff800031db940, Explanatory message (ascii) Debugging Details: ------------------ ----- ETW minidump data unavailable----- PROCESS_OBJECT: fffffa8010505b30 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
Try connecting the hard drive to a different port and see what happens. You will probably have to change it in the boot order in BIOS.
The dump analysis blames the card too.
Not to bore you with all the details but preceding the card this is what you seeCode:fffff880`028bb020 fffff880`0f21fb48Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0x20cb48
Code:fffff880`028bc3e8 fffff880`01247f4d Ntfs!NtfsCommonRead+0x1964 fffff880`028bc3f0 fffff880`028bc590 fffff880`028bc3f8 fffff880`0124936b Ntfs!NtfsCleanupIrpContext+0x12b fffff880`028bc400 fffff8a0`00a52808 fffff880`028bc408 00000000`00000000 fffff880`028bc410 00000000`00000000 fffff880`028bc418 00000000`c000000e fffff880`028bc420 00000000`00000000 fffff880`028bc428 fffff8a0`00a529f0 fffff880`028bc430 fffffa80`0d6d4fb8 fffff880`028bc438 fffffa80`0d6d4c60 fffff880`028bc440 fffffa80`0d6d4c60 fffff880`028bc448 fffff880`0124b7fc Ntfs!NtfsExtendedCompleteRequestInternal+0x11c fffff880`028bc450 fffff880`00000001 fffff880`028bc458 00000000`00000001 fffff880`028bc460 fffff880`028bc590 fffff880`028bc468 00000000`00000000 fffff880`028bc470 fffffa80`0db49180 fffff880`028bc478 00000000`c000000e fffff880`028bc480 fffff880`028bc6f0 fffff880`028bc488 fffff880`01254f19 Ntfs!NtfsProcessException+0x829 fffff880`028bc490 fffffa80`0d6d4c60 fffff880`028bc498 00000000`00000000 fffff880`028bc4a0 fffff880`028bc590 fffff880`028bc4a8 fffff880`028bc598 fffff880`028bc4b0 00000000`00000000 fffff880`028bc4b8 fffffa80`10507ad0 fffff880`028bc4c0 00000000`00003200 fffff880`028bc4c8 fffffa80`0db49180 fffff880`028bc4d0 00000000`00000000 fffff880`028bc4d8 00000000`00000000 fffff880`028bc4e0 00000000`00000000 fffff880`028bc4e8 fffffa80`0db49180 fffff880`028bc4f0 fffff880`028bc708 fffff880`028bc4f8 fffff880`028bc618 fffff880`028bc500 00000000`00060000 fffff880`028bc508 fffff880`028bc508 fffff880`028bc510 fffff880`028bc508 fffff880`028bc518 00000000`00000000 fffff880`028bc520 00000000`00000000 fffff880`028bc528 fffffa80`0d6d4c60 fffff880`028bc530 fffff8a0`00a529f0 fffff880`028bc538 00000000`00000000 fffff880`028bc540 fffff880`028bc590 fffff880`028bc548 00000000`00000000 fffff880`028bc550 fffff880`028bc708 fffff880`028bc558 fffff880`012484b4 Ntfs!NtfsFsdRead+0x2d4
Those are NTFS errors. That is the windows file system. Logically, if the hard drive disappeared, the GPU drivers are on the hard drive so the card would have had no drivers.
Quote