PC fails to boot and randomly bluescreen's - Bad RAM?

Scott4th

Prominent
Apr 15, 2017
18
0
510
Last April I built a new system and ever since I've been having weird issues, which I've not been able to get to the bottom of. I suspect it maybe bad RAM, however have just "got on" with things and never really fixed it, however it's now really beginning to annoy me.

Issue 1) PC doesn't POST / boot Windows 10.

If I leave my PC for a while (usually overnight) it will often fail to POST. I'll press the power button, the case lights up, the fans spin, the water cooler pumps and the monitor wakes (but displays the no input message), however nothing actually happens.

I then have to reach around the back of the PC and flick off the power supplies on/off switch. I can then turn it back on and it WILL boot.

This doesn't happen all of the time, probably 50% and if it happens once it'll probably happen the next 3 / 4 times when booting.

ISSUE 2) PC bluescreens

The PC will randomly bluescreen with the error "Your system has run in to a problem" and then restarts. This has been happening more recently - 6 times this month - and I suspect it maybe related.

The error log say's it's an Event 41,
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
however no more details are given.

I'm unsure if the issue is RAM, a bad PSU, bad motherboard or CPU? I can't really find the issue.

My thoughts are

  • ■ bad RAM would explain the random blue screens - Would this prevent POST?
    ■ bad PSU could prevent boot - would this lead to random bluescreens? or would it just cut power and turn off?
    ■ bad MB / CPU. I'm not too sure on CPU's and MB's
    ■ BAD GPU - Could the GPU not be initiallized on boot, hence everything lighting up but no display?

I've tried disabling hibernation and fast-boot as I've read that these can cause boot issues, but that hasn't helped.

My build is as per below:

  • ■ Gigabyte Z170-Gaming K3 ATX Motherboard
    ■ Intel i7 6700K Processor
    ■ EVGA SuperNova G2 750W '80 Plus Gold' Modular Power Supply
    ■ 16GB (2x8GB) 2133MHz Corsair Vengeance LPX DDR4 Memory
    ■ XFX Radeon R9 380X Black Edition AMD Graphics Card 4GB
    ■ Boot SSD - 2x Samsung Evo 750 250GB in RAID 0 (500GB total)
    ■ 2nd HDD 2TB Seagate Barracuda SATA III Hard Drive
    ■ Cooler Master Nepton 240M
    ■ Fractal Design Core 2500 Midi Tower Gaming Case
Any help would be greatly appreciated! I need to resolve this issue
 

Scott4th

Prominent
Apr 15, 2017
18
0
510


To clarify, I only turn it off at the back when I'm trying to boot and it won't turn on.

I'll shut it down via the start menu. It's when I come to reboot the next day and it doesn't boot I have to flick the switch at the back to cycle the power. The PC is never "fully operational" when I flick the PSU switch.

When restarting after BSOD the PC boots fine. I only seem to have the none boot issue after the PC has been left for a certain period of time - however I'm unsure how long that period is.
 
This driver is crashing it bwcW10x64.sys your killer network drivers. Could be the Bigfoot Lan drivers on the site.

Did you install the drivers for this off the cd or the site? Or did windows install them?

I would uninstall On/Off charge. It's a known cause of crashes

 

Scott4th

Prominent
Apr 15, 2017
18
0
510
Thanks for checking that. I installed from the internet as at the time I didn't have a disk drive installed.
I guess the NIC wouldn't cause boot issues? So that's probably unrelated?

I've ran the Memory test. There were 0 errors over 1 pass (45 minutes). Does that rule out bad RAM?
 
bad memory address used by the Killer Bandwidth Control Filter Driver
SystemRoot\system32\DRIVERS\bwcW10x64.sys Tue Feb 9 10:23:57 2016

install the updated driver from your motherboard vendor website:
http://www.gigabyte.com/Motherboard/GA-Z170-Gaming-K3-rev-10#support-dl
(this bugcheck was most likely just a bug in their driver)

file date 2016/11/11
-you might also update your BIOS to f22 version you have f1 version.
 
Solution