Ryzen 5 1600 boot loop

[That.Cyborg.Relay]

Hi, I've been running my ryzen 5 1600 at 3.85 stable for some time now. Temps stayed nice and low and everything was fine. However I recently started having a crashing problem after I tried bumping it up just a bit further. I have since reset my CMOS. however, after the reset my bios had 1.42 set as the base voltage at all times. Now my PC will boot into windows, however it crashes within seconds of logging in. Please help me figure out what's going on. I can't afford a major problem right now.

[NelizMastr]

Undo your overclock if you can't deal with instability tbh. Reset CMOS, tune your memory back to spec and just let your CPU run stock.

 

1.42v is also rather high by the way, for a 24/7 overclock. I wouldn't go over 1.4. Your CPU is basically a dud if it can't go over 3.8 at 1.4.

[GoldenLag]

What motherboard are you running?

 

Its most likely related to the very toasty voltage you are using.

[HystericalII]

Try undoing the overclock back to stock and lower your voltage im pretty sure its to high for daily usage 

[Brent744]

Complete the following.

 

1. Unplug absolutely everything from the tower. (monitor, usb, audio cable, etc.).

2. Hold power button for 30 seconds, release then hold for another 30 (this is to discharge all remaining power from board).

3. Reset CMOS.

4. Enter bios and select "Load Optimized Defaults".

5. Reboot machine and see if it boots to Windows.

 

If you do not complete steps 1 and 2, then step 3 may not work as even the power from a monitor cable can prevent the CMOS from completely resetting.

Good luck and let us know how you make out.

[That.Cyborg.Relay]

Okay, so specs. 

Mobo: aorus gaming k5

Cpu: ryzen 5 1600

Ram: Corsair vengeance RGB ddr4 3000

GPU: reference gtx 1080

Boot drive: WD blue m.2 nvme

PSU: 650w bronze certified

Case: R6

 

I've tried clearing my CMOS and backing everything back down to base however the vcore is still set at 1.42 (which wasn't what I was running my OC at). I've tried manually undervolting to stock however the problem still occurs. And I would like to stress that it's booting into windows fine. It could stay on the lock screen and never crash, however the second I sign in windows crashes. Thanks for all the help

[Brent744]

1 hour ago, E.Mon said:

Okay, so specs. 

Mobo: aorus gaming k5

Cpu: ryzen 5 1600

Ram: Corsair vengeance RGB ddr4 3000

GPU: reference gtx 1080

Boot drive: WD blue m.2 nvme

PSU: 650w bronze certified

Case: R6

 

I've tried clearing my CMOS and backing everything back down to base however the vcore is still set at 1.42 (which wasn't what I was running my OC at). I've tried manually undervolting to stock however the problem still occurs. And I would like to stress that it's booting into windows fine. It could stay on the lock screen and never crash, however the second I sign in windows crashes. Thanks for all the help

When clearing cmos did you complete this task as per steps I outlined earlier? If not, then there's no guarantee that cmos was completely cleared.

[That.Cyborg.Relay]

1 hour ago, Brent744 said:

When clearing cmos did you complete this task as per steps I outlined earlier? If not, then there's no guarantee that cmos was completely cleared.

I sure did. However here is where it gets interesting. I finally narrowed it down. Nothing is wrong with the CPU/Mobo (although the voltage thing is kinda concerning). I had a spare boot drive that I forgot about that I used to boot a different instance if windows. Everything ran fine when neither GPU drivers nor MSI afterburner were present. I think some instability with my GPU is crashing and causing the boot loop. That or hard drive failure.

[That.Cyborg.Relay]

So with the new information (crashes are being caused by either an unstable GPU clock or hard drive failure) I want to start by resetting MSI afterburner, however my computer doesn't stay active long enough for me to reset in software. Is there a way to just remove the AB overclock before opening windows?

[kevinisbeast707]

If you can boot with the other boot drive then you can open your files on the first drive and go to wherever you have msi afterburner installed at and delete it. That would rule out that possibility.

[Brent744]

18 hours ago, kevinisbeast707 said:

If you can boot with the other boot drive then you can open your files on the first drive and go to wherever you have msi afterburner installed at and delete it. That would rule out that possibility.

If Kevin's method doesn't work. I'd recommend wiping the drive with DBAN and reinstalling Windows. The reinstall is quite fast these days with their Media Creation Tool

[That.Cyborg.Relay]

On 11/13/2018 at 12:15 PM, kevinisbeast707 said:

If you can boot with the other boot drive then you can open your files on the first drive and go to wherever you have msi afterburner installed at and delete it. That would rule out that possibility.

I wish I had seen/known this before I reset windows. Either way I got it working again 

[kevinisbeast707]

On 12/7/2018 at 1:20 PM, E.Mon said:

I wish I had seen/known this before I reset windows. Either way I got it working again 

Rip but a clean install is never bad. I have to reinstall mine because windows search doesn't work anymore... For some reason