New Build, random Blue screen error F4

rjenks

Commendable
Mar 20, 2016
2
0
1,510
CPU: Intel (R) Core (TM) i7-4790K
Motherboard: MSI Z97S SLI Krait Edition Motherboard
RAM: Ballistix 2 - 4GB Sport DDR3-1600
Hard drives: 1) Samsung 250GB SSD 850 EVO
2) Seagate 1TB Desktop HDD SATA 6Gb/s 64MB Cache 3.5-Inch Internal Bare Drive
Power: Corsair CX Series 750 Watt ATX/EPS Modular 80 PLUS Bronze ATX12V/EPS12V 744 Power Supply CX750M
Current Graphics card: galaxy nvidia geforce gt 620
Graphics card removed: EVGA nvidia geforce 660 Ti
An optical drive I pulled from my old HP desktop so I could install software
OS: Windows 7 professional

I have been having BSOD and I/O errors occur for the last three months- ever since I built the gaming PC. Today, the BSOD flashed by so quickly I had a hard time taking down the details but I am pretty sure it was the cause of a x000000F4 error. It happened upon start up right after inputting my password. Upon researching my browser shut down, then my task bar disappeared, and my icons. This was followed by a jusched.exe application error that stated "The instruction at 0x000000724DD9D9 referenced a memory at 0x000000724DD9D9". The required data was not placed into memory because of an I/O error status of 0x000000e. Click ok to terminate" I did and it rebooted.

The jusched.exe error has not been so much of a problem except for the last two weeks or so. I have had something similar to this happen about two weeks ago, when my browser shut down and then the core of my taskbar and start menu were not there. Basically, the task bar and start menu were present but the icons, programs, etc were not. It was like a shell devoid of substance.

I tried to rebuild the BCD upon another tech's recommendation. I feel like that made things worse.

That attempt was followed by a second blue screen incident in the middle of a game download. (went by so fast I did not confirm the stop code)

After that, I took out the HDD to see if that may be contributing. I finally downloaded that game on the SSD. Shut it down.

After rebooting, I encountered another blue screen error (this time confirmed stop code 0x00000000F4) while I was attempting to access the start menu.

So, I tried to remove the SSD, reinsert the HDD, formatted that drive and tried to install Windows clean to attempt to isolate the SSD. Won't let me because "Windows cannot be installed on this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only installed on GPT disks."

Tried to reverse the process and install Windows on the SSD (clean): same problem.

So now both hard drives are back in the computer, it is up and running but I'm patiently awaiting the next blue screen that is bound to pop up.

Past errors have included stop: 0x000000F4. (0x0000000000000003, 0xFFFFFA8006F78B10, 0xFFFFFA8006F78DF0, 0xFFFFF80002F8A750)

I have taken it to two repair places. The first said it was a heat sink issue. That solved nothing. The second place tried to recreate the problem but could not do so consistently so they could not pin point the cause. The one time they did get it to BS they said from the information they gathered, they thought it might be the graphics card. I replaced that last night. No dice obviously. They also said that it might be the power supply. Again, the issue was the inability to recreate the BSOD consistently.

Short version:
My build is two months old
I have been experiencing random Blue Screen errors the entire time
These errors cannot be recreated consistently
Many of them do happen on or immediately after boot-up
I have been told it was a heat issue (tech guy said he "fixed" it)
Been told it was a video card issue (but I switched those, nothing changed) but this was after a week of them servicing the machine and being stumped due to diagnostics coming back clean
I have tried:
1) run a hard drive test for bad sectors (chkdsk /r)
2) run a System File Check (sfc /scannow - from an elevated command prompt window)
3) rebuild the BCD: http://pcsupport.about.com/.../rebuild-bcd-store-windows.htm
4) make sure all hardware drivers are compatible with Win7 and are current.

I don't know what else to do
 
Solution
with any built pc make sure the mb bios has the newest bios file. in the bios make sure the mb set to run at stock speed. if not some mb cpu and ram speed do not get set right. in the bios make sure ram xmp is turned on and set right. uses memtest86 from a boot usb stick. if ram passes use hardware info 64 bit set it to sensor and logging make sure the power supply rails are holding.
the cx power supply not that good of a unit. try another unit if hardware info test show the 12v rail dropping below 12v.

rjenks

Commendable
Mar 20, 2016
2
0
1,510
I should have clarified....

I built this myself. So this would entail returning each separate piece and I am going to assume that if I cannot prove which piece it is, they won't take it back under warranty.
 
with any built pc make sure the mb bios has the newest bios file. in the bios make sure the mb set to run at stock speed. if not some mb cpu and ram speed do not get set right. in the bios make sure ram xmp is turned on and set right. uses memtest86 from a boot usb stick. if ram passes use hardware info 64 bit set it to sensor and logging make sure the power supply rails are holding.
the cx power supply not that good of a unit. try another unit if hardware info test show the 12v rail dropping below 12v.
 
Solution