BSOD 0x000000f4 with new HDD

Greywinde

Honorable
Apr 24, 2013
9
0
10,510
I built a system and shipped it to a friend. Here's a bit of information first though.

The System Build

  • ■ 1 x AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz Socket AM3 125W 6-Core Desktop Processor HDT90ZFBGRBOX - Purchased 1/19/2011
    ■ 1 x RAIDMAX Quantum ATX-798WB Black SECC ATX Mid Tower Computer Case - Purchased 1/24/2011
    ■ 2 x PNY Optima 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model MD8192KD3-1333 - Purchased x1 1/24/2011 and again x1 on 7/9/2011
    ■ 1 x CORSAIR Hydro Series H80 (CWCH80) High Performance Liquid CPU Cooler - Purchased 10/12/2011
    ■ 1 x ASUS SABERTOOTH 990FX R2.0 AM3+ AMD 990FX + SB950 SATA 6Gb/s USB 3.0 ATX AMD Motherboard with UEFI BIOS - Purchased 11/5/2013
    ■ 1 x Antec 850 watt, model "TPQ - 850", trupower quattro PSU, Purchase date ??
    ■ 1 x GH24NSBOR/LG 24x DVD+/-RW Drive Internal; Model HG24NSBO, ROM Ver LN00, Man Oct 2013, Purchased 12/07/13, Warranty Exchanged 3/29/14
    ■ 1 x 8in1-C/Internal Card Reader by Super Talent Purchased 02/09/12
    ■ 1 x 3.5” to 5.25” Bay Mounting Kit Purchased 02/09/12
    ■ 1 x Neodymium Magnets for top panel fan assembly for easy removal and replacement of fans, very small, hard drive a good distance away.
    ■ 1 x XFX HD-585X-ZAFC Radeon HD 5850 1GB 256-bit GDDR5 PCI Express 2.1 x16 HDCP Ready CrossFireX Support Video Card w/ Eyefinity, Purchased 1/17/2011
    ■ 1 x Samsung 1TB New w/ 3yr Wnty - Hard Drive, Purchased 1/17/2011; which was replaced by 2TB Internal Serial ATA Solid State Hybrid Drive for Desktops Model: STCL2000400 SKU: 2045028 as of 05/26/14, due to shipping the previous HDD failed in transit with the click of death.


The History
I installed Windows 7, was working fine when it left here. I played games on it and had no issues whatsoever. Of course, that all changed when the damned thing arrived at my friend's place. Within maybe a week or two, the HDD died. So we replaced it and someone my friend knew helped out with a reinstall since that person happened to be visiting and capable of assisting. It would work for a bit before BSODs would start to occur and become increasingly frequent.

Being that I had installed the system in UEFI mode and the backup image I made didn't work the way I thought (I had used Redo Backup and Recovery since it was free), we had to install from scratch. This friend had no USB thumb drives with which to create a Windows UEFI install, so we tried installation once in ye old standard MBR with the motherboard running in UEFI mode (mainly because I forgot to have that switched off). Issue started to reoccur. Then we tried switching the boot mode to non-UEFI... and it still happened with the existing installation. I think we also, around this point did a Windows Memory Diagnostic on the extended test set for 8 passes (for which there were no errors). I also had my friend check the cables connecting the drives to make sure they were firmly connected and reseated the four RAM chips inside. Still a no go.

I finally got this person to get a thumb drive, reinstalled the OS ANOTHER time with UEFI mode install and the motherboard in UEFI mode, problem is still occurring. Noticably once, it also indicated there were no bootable devices found in a slur of recent restarts trying to get some things fixed.


Currently

  • ■ I've tried updating drivers.
    ■ Speedfan indicates the drive fitness is down to 0% as there are 8 pending sectors that have not been reallocated.
    ■ I'm currently running a more extensive Memory Test as I know not all issues may show up easily (extended test, 20 passes).
    ■ Then having the computer do a full disk check. I realize I may need to have the operating system reinstalled/cleared off in order to remap the bad sectors.
    ■ I also have a log of the BSODs using nirsoft's bluescreen view.

I believe that my best bet here is probably something to do with a faulty drive... again. Any thoughts? Anything I'm missing here?
 
Solution
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
type = process

you might look for malware trying to infect critical system processes.

run a malwarebytes scan. Also run cmd.exe as admin
then sfc.exe /scannow (to look at the core windows files for corruption and fix them if it can)
you can also run
the windows debugger command
!for_each_module !chkimg @#ModuleName
on the memory .dmp file and it will check the memory image for corruption in the core windows files that were loaded into memory.
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION
type = process

you might look for malware trying to infect critical system processes.

run a malwarebytes scan. Also run cmd.exe as admin
then sfc.exe /scannow (to look at the core windows files for corruption and fix them if it can)
you can also run
the windows debugger command
!for_each_module !chkimg @#ModuleName
on the memory .dmp file and it will check the memory image for corruption in the core windows files that were loaded into memory.
 
Solution