System will suddenly freeze, reboot or BSOD and shut down and boot priority will change

[Creepy Nick]

This issue has been killing me over the last month, i can't solve it. 

 

Original issue: 

Very often, every hour or so, my PC will freeze making me force a restart or give BSOD, or restart randomly with no warning, yet it will try to reboot to my second storage drive instead of my SSD, even though each time this happens I change my ssd to boot from. No other settings are changed it seems. If I reboot whilst the PC is working, it'll boot to the SSD no problem. Nothing has changed with my system other than the odd Nvidia drivers update. I did a clean install of windows 10 less than a month ago and has been stable since then, motherbaord: Gigabyte z68ap-d3 rev 1

 

Replaced RAM, same BSOD issue.
Replaced 1070, same BSOD issue.
Replaced PSU, same BSOD issue.

I have now replaced the motherboard to an Asus p8z77 Vpro, Now I get a slightly different issue. 
The system seems to be able to idle for many hours. But, when I come back, the windows icon is spinning, I can't open, close or do anything, forcing me to do a hard reset.

I also had a lot of issues finding drivers for the TL WND3800 wifi card I have in the system, tried various versions and one worked but upon a restart, I was greeted with an error code and then I couldn't get any internet and no drivers worked at all. I am currently resetting the PC via the build in reset tool.

 

(Update: been able to use the wifi card without any drivers. The internet issue is restored. Running the system with the new board and a clean Windows 10 with only 1070 drivers and seeing how long it can idle for)  

specs:
2500k + Hyper 212 evo
8gb corsair vengeance 4x2
(originally: Gigabyte z68ap-d3 rev 1) NOW: Asus p8z77 Vpro
128gb Crucial m4 SSD 
GTX 1070
Coolermaster GX 650w

tp link wdn3800 wifi card

1TB back up drive
older mid tower Coolermaster case, unsure on the model

Any ideas or help is greatly appreciated.

[Creepy Nick]

Update: It doesn't seem to be the board. I came back to this screen after an hour of being idle: Error screen

 

(Reboot and Select proper Boot device

or Insert Boot Media in selected Boot device and press a kay_) 

 

 

[Syncrosys]

Hi @Creepy Nick

 

Download HD sentinel (its free to use for 30 days) and check out your SSD. I have a feeling you have a Drive or Sata cable issue. 

 

Let me know if that returns anything.

[Creepy Nick]

43 minutes ago, Syncrosys said:

Hi @Creepy Nick

 

Download HD sentinel (its free to use for 30 days) and check out your SSD. I have a feeling you have a Drive or Sata cable issue. 

 

Let me know if that returns anything.

2

Pretty sure I got the right program, but I replaced the cable and then scanned via HD sentinel,  ( Pic of Sentinel programme ) 

[Syncrosys]

Sweet, well at least its not your SSD. That software is crazy good btw. I swear by it. Keep an eye out of sales, they often have it on sale for 20$ for the Pro version.

 

So, keep an eye out see if the cable makes a difference. If it fails again... RIGHT AWAY extract your Applications and System event logs from Event viewer. and attach them here. (see bellow for instructions on saving event logs)

 

Cheers!

 

To save event logs

1. Click Start, and point to Programs.

2. Point to Administrative Tools, and then click Event Viewer.

3. Right-click the appropriate log file (Application, Security, System, Directory Service, or File Replication Service).

4. Click Save Log File As.

5. Type a name for the file, and click Save.

[Creepy Nick]

19 minutes ago, Syncrosys said:

Sweet, well at least its not your SSD. That software is crazy good btw. I swear by it. Keep an eye out of sales, they often have it on sale for 20$ for the Pro version.

 

So, keep an eye out see if the cable makes a difference. If it fails again... RIGHT AWAY extract your Applications and System event logs from Event viewer. and attach them here. (see bellow for instructions on saving event logs)

 

Cheers!

 

To save event logs

1. Click Start, and point to Programs.

2. Point to Administrative Tools, and then click Event Viewer.

3. Right-click the appropriate log file (Application, Security, System, Directory Service, or File Replication Service).

4. Click Save Log File As.

5. Type a name for the file, and click Save.

Ah fair enough, noted. I'd never used it before

 

Unfortunately, the cable didn't make a difference, came back to it recently and it had the same bios screen open as before but I'm not sure when it failed. 

I'll leave it idling again for an hour then sit with the PC after that so I can grab the event viewer info straight after it boots up again for you. Cheers for the help 

[Creepy Nick]

On 2017-6-9 at 9:09 PM, Syncrosys said:

Sweet, well at least its not your SSD. That software is crazy good btw. I swear by it. Keep an eye out of sales, they often have it on sale for 20$ for the Pro version.

 

So, keep an eye out see if the cable makes a difference. If it fails again... RIGHT AWAY extract your Applications and System event logs from Event viewer. and attach them here. (see bellow for instructions on saving event logs)

 

Cheers!

 

To save event logs

1. Click Start, and point to Programs.

2. Point to Administrative Tools, and then click Event Viewer.

3. Right-click the appropriate log file (Application, Security, System, Directory Service, or File Replication Service).

4. Click Save Log File As.

5. Type a name for the file, and click Save.

2

Sorry for the delay I've not been available for the last few days. But I have since swapped out the 2500k to a 3570k and had the same issue. The only thing I've not swapped is the SSD

[Syncrosys]

That's wild then. What is the life left on it? What did HD sentinel report it as? Was it healthy? 

 

Maybe try a firmware update if its available?

I had a "similar ish" issue with an old OCZ Vertex 4. Its actually still in my system as a spare game install drive and hasn't flinched since.

[Creepy Nick]

6 minutes ago, Syncrosys said:

That's wild then. What is the life left on it? What did HD sentinel report it as? Was it healthy? 

 

Maybe try a firmware update if its available?

I had a "similar ish" issue with an old OCZ Vertex 4. Its actually still in my system as a spare game install drive and hasn't flinched since.

sentinel reported it as 96% health.

This time, at 3:50pm ish the system became unresponsive, I couldn't interact with any windows or anything but the mouse was still moving for a few minutes. 3:53 ish the system rebooted randomly and I was met with a screen saying improper boot device and the SSD was no longer the boot drive, like before.

 

I then saved the application and system logs and uploaded them here: https://drive.google.com/drive/folders/0B4sLmNkWtWI2S2V4bFU1ZXB0Yjg?usp=sharing

[Syncrosys]

I found this in your event logs

 

CldFlt error : https://www.bleepingcomputer.com/forums/t/644758/windows-10-non-responsive-hanging-need-to-hit-reset-button/

This is common after Creator update of W10 apparently.

 

and... I also found this:

 

The description for Event ID 41 from source Microsoft-Windows-Kernel-Power cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 

Which is typical of a corrupted OS install that cant repair itself. 

 

Could also be a memory issue. Or even the memory controller that's on the CPU.

 

Run a http://www.memtest86.com/. I know you already replaced the memory, but you never know. If it fails, try with the old ram. If it fails again, the there's a chance your CPU is having issues. The cpu is sort of making a bit more sense. Too bad you arent close, I have a second Gen i3 lying around I could have lent you to test it with.

 

CPU would explain some issues, and SSD would explain the corruption and the CldFlt error.

 

 

 

 

[Creepy Nick]

On 2017-6-16 at 0:30 AM, Syncrosys said:

I found this in your event logs

 

CldFlt error : https://www.bleepingcomputer.com/forums/t/644758/windows-10-non-responsive-hanging-need-to-hit-reset-button/

This is common after Creator update of W10 apparently.

 

and... I also found this:

 

The description for Event ID 41 from source Microsoft-Windows-Kernel-Power cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 

Which is typical of a corrupted OS install that cant repair itself. 

 

Could also be a memory issue. Or even the memory controller that's on the CPU.

 

Run a http://www.memtest86.com/. I know you already replaced the memory, but you never know. If it fails, try with the old ram. If it fails again, the there's a chance your CPU is having issues. The cpu is sort of making a bit more sense. Too bad you arent close, I have a second Gen i3 lying around I could have lent you to test it with.

 

CPU would explain some issues, and SSD would explain the corruption and the CldFlt error.

 

 

 

 

Popped in an old HDD and installed windows on it, ran stable for 10hrs+, seems like a dead ssd! 

Buying a new one now and seeing if it is stable

[Syncrosys]

Sweet. Congrats on finding your issue buddy.

 

Let me know if you ever need anything else! (message me directly)

 

Cheers!

[Creepy Nick]

2 hours ago, Syncrosys said:

Sweet. Congrats on finding your issue buddy.

 

Let me know if you ever need anything else! (message me directly)

 

Cheers!

Will do. Thanks again for your help