Issue regarding CPU upgrade (boot looping)

[Evanokato]

Hello,
Long story, would really appreciatie if you'd take the time and read it.

So i was using a ryzen 7 1700 on a asrock B450 pro4 with stock cooler for 3 years apart from rare crashes and bluescreens there weren't any noticiable defects. I decided it was time for an upgrade. I updated the bios to version 5.00 before installing the new CPU.
I got a ryzen 5 5600x second hand and also bought a gelid solutions phantom cooler. The cooler was working fine with the 1700. At the guys house, the cpu was working fine, I kept in touch with him and it was clearly working on his pc so i dont think i got scammed. Then, when I first booted it with the new CPU, it would get into windows fine, and after 10 sec it would freeze and restart itself. After that, the period of time it gave us before freezing became shorter and shorter until it froze before letting me see the login screen. However, in secure boot (the option you get after the system restarts 3 times) It would sometimes give me a couple minutes before crashing.I could get into the bios and the cpu temprature was not high (34 - 43 Celcius) Once it even stayed on for about 30 minutes until I shut it down myself. After reading on a forum it could be an issue related to the ram so I reseated it. After then it got bad. Now its stuck in a never-ending boot loop. It boots, then just restarts itself after having all the fans spin at maximum speed for 25 seconds while the screen stays black.

Link to the mobo http://www.asrock.com/MB/AMD/B450%20Pro4/#BIOS

what we tried:
Different (the one I had in it first) cpu
Different RAM (tested on each slot)
CMOS battery reset 20 times
CMOS header reset via motherboard
Turned on without a video card
Clean install windows (back when it still booted)
New motherboard (still same issue)

Lmk if you have any questions i really want this fixed :(

[Lunch-b0x]

Perhaps your drive is dying?

[Evanokato]

CLAYT0N eredeti hozzászólása:

Perhaps your drive is dying?

I tested it on my mates pc it booted fine

[Evanokato]

Update: installed new mobo, still same problem. I did manage to download windows this time it would crash before but still can't get into it

[Bad 💀 Motha]

You say you were able to download Windows OS?
Do you mean the ISO?

Then you say still can't get into it? Get into what exactly?

[plat]

Does your newer processor still work in your friend's machine--did you go back there and try it again? If so, I would start taking a look at possibly replacing your board. This was mentioned to you earlier.

Someone already mentioned checking your boot drive for errors-- did you try that in the recovery environment already? Or, do you or your friend have another drive you can try? If it already has Windows on it, that's even better. It's just for testing purposes.

I have a backup nvm-e with Windows 11 on it. Has saved me twice already now.

Edit: my apologies--I didn't see where OP had installed a new board and tested his drive in another machine. OK, can you test your psu with a volt-meter, if available? If you search online, there are various methods.

[PopinFRESH]

Evanokato eredeti hozzászólása:

Update: got my boot drive formatted and got windows on it with a little bit extra effort but its boot looping on my system while all other drives are out. Not even showing bios now screen stays black. It booted fine on my friends pc

How exactly did you do this "with a little bit extra effort"?

Evanokato eredeti hozzászólása:

CLAYT0N eredeti hozzászólása:

Perhaps your drive is dying?

I tested it on my mates pc it booted fine

This sounds like the "little bit extra effort" was you using your friends computer to install Windows on your drive and then moving it back to your computer. If so this still sounds like a BIOS/UEFI configuration issue and not an actual hardware problem.

Again I'd recommend going back and doing as Elucidator or I suggested and booting the system via a USB flash drive with either a bootable Live Linux or bootable DOS+Memtest86 flash drive. I'd recommend as I did before to do a dos bootable flash drive with Memtest86+ on it so you can let it run a memtest for a full pass to 1) make sure there isn't a hardware issue with your memory and 2) ensure its stable in another OS environment.

[Elucidator]

Evanokato eredeti hozzászólása:

Update: installed new mobo, still same problem. I did manage to download windows this time it would crash before but still can't get into it

in that case it can only be the PSU or the cables.

(edit: just to note: I don't entirely understand how though, but technically yes- I mean the psu needs to switch how much power it delivers, maybe it is broken or a cable is broken and so it switches back I suspect)

(also, if you have a new motherboard you have an entirely different computer basically...)

[Evanokato]

Bad 💀 Motha eredeti hozzászólása:

You say you were able to download Windows OS?
Do you mean the ISO?

Then you say still can't get into it? Get into what exactly?

Yes windows os before it would crash while once I wanted to log in. I cant get into windows it will crash when logging in the new motherboard did not change anything

[Chryseus]

How has this thread got to 5 pages, the first post was enough to tell me it's the PSU, nothing else has changed my opinion on that.

[Evanokato]

Chryseus eredeti hozzászólása:

How has this thread got to 5 pages, the first post was enough to tell me it's the PSU, nothing else has changed my opinion on that.

Would you mind explaining yourself? These psu have 10 year warranty and has been used well under its maximum wattage.. if its psu it would have shutdown entirely right? My pc just restarts once i log onto windows

[Chryseus]

Evanokato eredeti hozzászólása:

Chryseus eredeti hozzászólása:

How has this thread got to 5 pages, the first post was enough to tell me it's the PSU, nothing else has changed my opinion on that.

Would you mind explaining yourself? These psu have 10 year warranty and has been used well under its maximum wattage.. if its psu it would have shutdown entirely right? My pc just restarts once i log onto windows

PSU failure doesn't mean it suddenly fails although this is usually the eventual outcome, the primary symptom is instability such as random reboots that do not produce an error code (no BSOD), you've already ruled out the mobo, memory and CPU and I consider a BIOS problem to be very unlikely.

Unfortunately there is no real test that will 100% prove it's the PSU, checking it with a voltmeter can work but it has to be under load at the time, warming it up can also improve stability if it's a capacitor problem, at this point though it's the only thing left that makes sense, as for why it only fails in Windows the reason is quite simple, the biggest load in the system is the GPU which is barely used until Windows is running.

[Evanokato]

Chryseus eredeti hozzászólása:

Evanokato eredeti hozzászólása:

Would you mind explaining yourself? These psu have 10 year warranty and has been used well under its maximum wattage.. if its psu it would have shutdown entirely right? My pc just restarts once i log onto windows

PSU failure doesn't mean it suddenly fails although this is usually the eventual outcome, the primary symptom is instability such as random reboots that do not produce an error code (no BSOD), you've already ruled out the mobo, memory and CPU and I consider a BIOS problem to be very unlikely.

Unfortunately there is no real test that will 100% prove it's the PSU, checking it with a voltmeter can work but it has to be under load at the time, warming it up can also improve stability if it's a capacitor problem, at this point though it's the only thing left that makes sense, as for why it only fails in Windows the reason is quite simple, the biggest load in the system is the GPU which is barely used until Windows is running.

Thanks for the reply. I did find some errors in the event viewer though i shouldve mentioned that.

the following boot start or system start drivers did not load:
bam
cdrom
dam
filecrypt
gpuenergyDrv
npsvctrig
vid
WdFilter

1084
attempting to start the service shellhwdetection with arguments unavailable

[Chryseus]

Evanokato eredeti hozzászólása:

Thanks for the reply. I did find some errors in the event viewer though i shouldve mentioned that.

the following boot start or system start drivers did not load:
bam
cdrom
dam
filecrypt
gpuenergyDrv
npsvctrig
vid
WdFilter

1084
attempting to start the service shellhwdetection with arguments unavailable

Those are fairly non-specific, what I would suggest if you haven't tried already is boot a Linux live system (I.E Ubuntu) since these run 100% in memory and see if it crashes, that will rule out any kind of disk involvement.
If that fails to give any results buy / borrow / steal a new PSU, even a cheapo one will do fine for testing.

[Elucidator]

I am reading conflicting information, this is confusing.

Evanokato eredeti hozzászólása:

I did manage to download windows this time it would crash before but still can't get into it

With this post I assumed you downloaded windows at your friend's place. And with "but still can't get into it", I assumed you couldn't get into any bit of windows. (not the init, not the loading screen, not the login screen, etc.)

and yet, somehow you did get errors in Windows Event Viewer?

Evanokato eredeti hozzászólása:

the following boot start or system start drivers did not load:
bam
cdrom
dam
filecrypt
gpuenergyDrv
npsvctrig
vid
WdFilter

1084
attempting to start the service shellhwdetection with arguments unavailable

That means it did load windows and only rebooted after windows was already being loaded.

Are those errors from your own Boot attempts or from testing the Boot at your friend's PC?

[PopinFRESH]

Chryseus eredeti hozzászólása:

Evanokato eredeti hozzászólása:

Thanks for the reply. I did find some errors in the event viewer though i shouldve mentioned that.

the following boot start or system start drivers did not load:
bam
cdrom
dam
filecrypt
gpuenergyDrv
npsvctrig
vid
WdFilter

1084
attempting to start the service shellhwdetection with arguments unavailable

Those are fairly non-specific, what I would suggest if you haven't tried already is boot a Linux live system (I.E Ubuntu) since these run 100% in memory and see if it crashes, that will rule out any kind of disk involvement.
If that fails to give any results buy / borrow / steal a new PSU, even a cheapo one will do fine for testing.

They've already been told this multiple times and have ignored it. Booting to either a live linux USB/CD or a bootable USB with Memtest86+ would help point toward if its a software or hardware issue. Again I'd recommend either booting to Memtest86+ in order to test the memory while seeing if the systems is stable in an alternative OS environment, or download a trial of PassMark Burn-In-Test and make a bootable disk for that which will be able to run CPU, Memory, 2D GPU, and 3D GPU workloads to test those components while also loading the system (which if its the PSU should expect it to restart during that testing).