Solved BSOD seemingly randomly. No new apps or hardware installed

[Dave76]

Long Generic.

No Long Drive Self Test in the drop down list?
Strange.

Same crash as last time.

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: fffffa800b8d6b30, Terminating object
Arg3: fffffa800b8d6e10, Process image file name
Arg4: fffff8000338b660, Explanatory message (ascii)

PROCESS_NAME:  wininit.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.
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

wininit.exe is used for Disk Check, with this and the HD controller errors, you need to run Seatools.

Let us know the results.

 

[Supermonkey47]

No there is no long drive self test in the drop down.

- I have run the Long Generic test on the SSD (my primary hard drive with windows installed on it) and there are no errors (the result is "Pass").
- I am currently running the Long Generic test on my data storage SATA drive but I doubt it will finish as it will takes hours and the system will BSOD long before then.

 

[Dave76]

Let us know the results for the test on the HDD.

 

[Supermonkey47]

Unfortunately the system wont stay up long enough to complete the Long Generic test on the HDD. However I was able to run the Short Drive Self Test and it passed.

Here are the latest crash dumps.

 

[James7679]

Do you happen to have any other hardware you could swap out for testing purposes? Another hdd, cpu, mobo, anything? The amount, frequency and randomness of your BSODs, would suggest that this could be hw related. Have you tried running memtest immediately after a BSOD?

 

[Supermonkey47]

I have tried running a memtest immediately after the BSOD. I have also tried it with spare RAM modules I have had and the same thing happens.


The next thing I am going to try is the following:

• Disconnect the HDD and leave it solely with the OS on the SSD to test.
• If unsuccessful - disconnect power supply and use a spare I have to test.
• If unsuccessful - disconnect the SSD and install Windows on a spare HDD I have to test.

Other than that I am out of ideas.

 

[James7679]

That's a great plan. Let us know how it goes.

 

[Supermonkey47]

I have solved it! It was a problem with my SSD.

Just before I started swapping HDD's and Power Supplies, I came across an article stating that back in December, reports started popping up in Crucial's forums that the company's M4 SSD was causing BSOD's. After investigating Crucial found a bug in the firmware was causing the drive to become unresponsive after 5,184 hours of system on time, and every hour of use thereafter — hence the sudden problem in previously stable systems like mine. The company released a firmware update that fixes the problem which I have applied with success. I had updated all the mobo drivers, but hadnt thought about the SSD firmware itself!

Thanks to everyone here for all your help along the way, I am so relieved to finally be without the dreaded BSOD.

 

[Dave76]

Congrats on finding the culprit, good work.

 

[James7679]

Congrats Supermonkey47!