New Computer won't boot after multiple BSODs

MrMojoRisinUK

Commendable
Dec 12, 2016
3
0
1,510
First my specs
CPU: Intel Core i7-6700K 4.0GHz
CPU Cooler: Noctua NH-D15S 82.5 CFM
Motherboard: MSI Z170A GAMING M5 ATX LGA1151
Memory: Corsair Vengeance LPX 8GB (2 x 4GB) DDR4-3000
Storage: Corsair Force LS 240GB 2.5" Solid State Drive
Storage: Seagate Barracuda 3TB 3.5" 7200RPM Internal Hard Drive
Video Card: MSI GeForce GTX 1080 8GB GAMING X 8G Video Card
Power Supply: FSP Group Hydro G 650W 80+ Gold Certified Fully-Modular ATX Power Supply ($94.99 @ Newegg Marketplace)
Operating System: Microsoft Windows 7 Home Premium SP1 OEM 64-bit ($99.99 @ My Choice Software)

I recent purchased parts for a new computer and built it last week. The build went fine and it started up fine. I installed the OS and connected to the internet after installing the correct drivers. I then downloaded the latest patches and software drivers and began installing AV software and firewalls, browsers etc. I downloaded and installed Steam and downloaded a few games. I started up Cities: Skylines and got about 5 minutes into a game before I got BSOD. I reset, went to desktop and began to run a GPU stress test to make sure everything was OK with my GPU. About 5 seconds into the test it froze and I got BSOD again. Reset, back to desktop and BSOD instantly. Reset, same thing. Reset and this time it got past the BIOS and BSOD. Now it won't boot at all. Power goes to the board and everything starts up but the monitor either stays without any input at all or, when it occasionally does get input, stays blank. Every so often it will get to the BIOS and either allow me into the BIOS or will freeze before loading it. It NEVER gets pat the BIOS though.

I started to diagnose all the components myself. I removed the GPU as I suspected something had gone wrong with it; no change. I then played about with the RAM, different configs, only one stick, then no sticks; no change. I unplugged the SSD and HDD and CD-ROM; no change. At this point I believed it was either the MOBO or CPU. I suspected the MOBO as I'd been checking the temps on the CPU throughout use and it had never gone very high and the cooling is pretty decent. I had a tech guy come and take a look and he thought the same as we re-seated the CPU there and then and it made no change. I replaced the MOBO and put in the new one today, connected all the components back up and started it but the same problem is persisting. This only leaves the CPU IMO. The debug code the MOBO gives is either 62 or 79 which are non-codes (i.e. they don't mean anything).

Should I replace the CPU or could it be something else? I've been over the MOBO manual with a fine toothcomb and haven't found anything I've done wrong. The occasional boots to the BIOS is what is throwing me; can I get there with a faulty CPU?

Thanks for any help you guys can give.
 
Could be your power supply. Also, before you game, ensure that your components are stable by torturing them. Prime95 Small FFTs for your cpu, make sure to run it for 24 hours. If it passes, it's stable, if it doesn't, replace it.

Also, make sure to boot into Safe Mode for your stress tests just in case there's a background process causing the issue.
 


You really think my PSU could be causing this issue? The estimated wattage of my build on PCPartPicker is just under 400W and my PSU is 650W 80+ Gold, so it's not exactly cheap crap. Unless you mean it could be burning out my components? But I checked the voltages in the BIOS before booting and they were all under the recommended ceiling.
 
Honestly, I have no idea if it's your power supply. It seems to be a reputable brand, and it's new and it's Gold. But your post indicates that you know your stuff and you've done a lot of troubleshooting already. When you've eliminated the probable, and all that. Sounds like the only things you haven't replaced are the cpu and the power supply, hence my advice to torture the CPU with Prime95 Small FFTs until it gives you an answer.

If your cpu at stock frequency and voltage survives 6 hours of the latest Prime95(yes, the AVX one) Small FFTs, then the problem isn't your cpu.
 


If I'm perfectly honest I can't see how it could be either of them. There's nothing I could have done to have caused an issue like this to crop up. My only thought is it must have been during manufacturing and the CPU is somehow faulty and broke down when it was put under some stress as I did fail to stress test it prior to gaming, so I will remember to do this in the future.
 

TRENDING THREADS