Random BSOD after installing new SSD

pilledave

Reputable
Feb 16, 2015
3
0
4,510
I just bought a new SSD (Crucial MX100 256gb) and a new HDD (WD Blue 1TB) for my desktop because my old HDD broke. I installed the new hardware, updated my bios and then installed windows 8 on the new ssd from a windows 8 installation disk. But when the configuratuon and setting up process began, random BSOD began to acure. Every time with a different error message (APC Index Mismatch, Invalid kernel auto boost lock release, Attempted Write to Read Only Memory and 2 more errors that I can't remember, and forgot to write down) each time the computer would restart and continue the configuration/set up process where it left off. I then tried to install windows 7 instead. This time from an USB flash drive. The installation ran flawlessly, but then random BSODs began to happen again. Also alot of the programs that i installed didn't function properly. I would get the "Aw, Snap!" error in chrome a couple of seconds after loading a new page, Steam wouldn't start because it failed to load steamui.dll, and windows security essentials wouldn't update and windows update checker coulnd't find any updates.

Here is the error report for the Windows 7 BSODs:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1030

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800DCB2B30
BCP3: FFFFFA800DCB2E10
BCP4: FFFFF80002D8C130
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\022415-8065-01.dmp
C:\Users\Steff\AppData\Local\Temp\WER-10030-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
http://1.2.1.0/


And here are my specs:

Summary
Operating System
Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i5 2500K @ 3.30GHz 39 °C
Sandy Bridge 32nm Technology
RAM
16,0GB Dual-Channel DDR3 @ 799MHz (9-9-9-24)
Motherboard
ASUSTeK Computer INC. P8P67 REV 3.1 (LGA1155) 27 °C
Graphics
Generic Non-PnP Monitor (1920x1080@1Hz)
14MB NVIDIA Standard VGA Graphics Adapter (ASUStek Computer Inc)
Storage
931GB Western Digital WDC WD10EZEX-08M2NA0 ATA Device (SATA) 23 °C
238GB Crucial_CT256MX100SSD1 ATA Device (SSD) 23 °C
28GB Verbatim STORE N GO USB Device (USB)
Optical Drives
TSSTcorp CDDVDW SH-222AB ATA Device
Audio
High Definition Audio Device


I am also running a custom OC on my CPU, wich haven't been a problem before.
Hope somebody can help me find a solution to my problem.
Have a nice day and thank you!
 
Solution
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

windows check certain memory structures to make sure they are not modified, if they get changed windows will shut down with this bugcheck.

Certain old programs may do this and you just can no longer run them. Viruses and malware might do this to infect your system. You would want to run malwarebytes to try to remove them.
Then run cmd.exe as an admin and run
sfc.exe /scannow
and confirm that it is able to fix any corruptions.

certain hack programs to bypass windows activation can also cause this.

random memory corruptions caused by a bad overclock will also cause this.
you will want to confirm any overclock is ok by running memtest86 for several passes.

and finally, there are a lot of...
Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

windows check certain memory structures to make sure they are not modified, if they get changed windows will shut down with this bugcheck.

Certain old programs may do this and you just can no longer run them. Viruses and malware might do this to infect your system. You would want to run malwarebytes to try to remove them.
Then run cmd.exe as an admin and run
sfc.exe /scannow
and confirm that it is able to fix any corruptions.

certain hack programs to bypass windows activation can also cause this.

random memory corruptions caused by a bad overclock will also cause this.
you will want to confirm any overclock is ok by running memtest86 for several passes.

and finally, there are a lot of 3rd party OEM drivers that corrupt drivers data structures in memory.
Windows will load the drivers in memory in different orders on each boot so different data gets corrupted on each boot but windows only checks certain data for corruption. IE sometimes it can bugcheck in minutes other times days.
 
Solution