Hi,
Thanks for registering, I appreciate it!
All of the attached DMP files are of the
CRITICAL_OBJECT_TERMINATION (f4)
This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
Code:
BugCheck F4, {3, fffffa80078efb30, fffffa80078efe10, fffff80002dda270}
The 1st parameter is 3 which indicates it was a process as opposed to a thread.
If we look further into the dump as I also said above, we see 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.
What's an I/O error you may ask? An I/O error is when any hardware device (hard disk, flash drive, etc) cannot perform its basic input/output actions such as reading or copying data. When this is the case with a hard disk itself, or any storage related media, it's due to the device PHYSICALLY failing. Do note that with hard disks, the connections can be faulty as well (i.e the SATA cables from the controller on the board to the hard disk itself). Do note that at times a software conflict can exist and cause this error, such as an antivirus causing file system conflicts.
1. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing file system conflicts:
avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal
MSE - Microsoft Security Essentials - Microsoft Windows
2. If the above fails please run Chkdsk (paste log afterwards) and then Seatools:
Chkdsk:
There are various ways to run Chkdsk~
Method 1:
Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)
Elevated CMD should now be opened, type the following:
chkdsk x: /r
x implies your drive letter, so if your hard drive in question is letter c, it would be:
chkdsk c: /r
Restart system and let chkdsk run.
Method 2:
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.
If you'd like to get a log file that contains the chkdsk results, do the following:
Press Windows Key + R and type powershell.exe in the run box
Paste the following command and press enter afterwards:
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt
This will output a .txt file on your Desktop containing the results of the chkdsk.
If chkdsk turns out okay, run Seatools -
SeaTools | Seagate
You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be driver related issues that may cause conflicts or a false positive, it may be a wise decision to choose the most minimal testing environment (DOS). I always recommend running Seatools in DOS if absolutely possible.
-- Run all tests
EXCEPT: Fix All and anything Advanced.
Regards,
Patrick
