F5F Stay Refreshed Hardware Desktop the motherboard won't remain active even after a brief flash.

the motherboard won't remain active even after a brief flash.

the motherboard won't remain active even after a brief flash.

P
Pollerino
Member
223
11-07-2019, 08:17 AM
#1
I acquired a B450 Auros Elite V1 and attempted all possible fixes. The motherboard light flashes briefly before turning off. I checked for loose components, removed every piece of hardware and connections, but the issue persisted. I also suspected a power supply problem since the 24-pin connector was missing, though that’s typical. My current power supply works fine. The seller mentioned running at 3600 volts, which matches my unit. I’m unsure if anyone else has encountered this problem.
P
Pollerino
11-07-2019, 08:17 AM #1

I acquired a B450 Auros Elite V1 and attempted all possible fixes. The motherboard light flashes briefly before turning off. I checked for loose components, removed every piece of hardware and connections, but the issue persisted. I also suspected a power supply problem since the 24-pin connector was missing, though that’s typical. My current power supply works fine. The seller mentioned running at 3600 volts, which matches my unit. I’m unsure if anyone else has encountered this problem.

J
jameson627
Member
50
11-10-2019, 10:56 AM
#2
The system likely switched into protection mode due to an issue like a faulty or shorted CPU or another board component. Were all other parts functioning correctly before the board change? If yes, it probably indicates a defective board—likely a single failed component that triggered the detection. It would be helpful if you had additional CPUs, GPUs, etc., to thoroughly test the board with different parts in place and confirm the exact cause.
J
jameson627
11-10-2019, 10:56 AM #2

The system likely switched into protection mode due to an issue like a faulty or shorted CPU or another board component. Were all other parts functioning correctly before the board change? If yes, it probably indicates a defective board—likely a single failed component that triggered the detection. It would be helpful if you had additional CPUs, GPUs, etc., to thoroughly test the board with different parts in place and confirm the exact cause.

A
Azure_
Junior Member
31
11-11-2019, 11:00 AM
#3
I have a spare CPU available on another machine, but I'm concerned about the possibility of damage if the board shorts.
A
Azure_
11-11-2019, 11:00 AM #3

I have a spare CPU available on another machine, but I'm concerned about the possibility of damage if the board shorts.

T
TandemTea
Member
53
11-11-2019, 04:02 PM
#4
You could remove the CPU and attempt to power the motherboard back on to check if the indicator stays lit. Also, placing a faulty CPU on a new board might cause further issues if it's defective.
T
TandemTea
11-11-2019, 04:02 PM #4

You could remove the CPU and attempt to power the motherboard back on to check if the indicator stays lit. Also, placing a faulty CPU on a new board might cause further issues if it's defective.

H
HellaDapper
Member
225
11-22-2019, 02:49 AM
#5
It's a possibility but unlikely—if it hasn't activated yet, you can safely attempt it. Protect mode is meant to stop further harm by preventing full power-up and ensuring it behaves as described. You're unlikely to cause additional damage beyond the current issues. While it's doable, most faulty CPUs won't function properly. I owned one that failed completely due to a board issue, which involved a lot of sparks. That situation didn't match your description, so it probably isn't happening here. Understanding what to fix is key, and so far there haven't been any risky actions from your post.
H
HellaDapper
11-22-2019, 02:49 AM #5

It's a possibility but unlikely—if it hasn't activated yet, you can safely attempt it. Protect mode is meant to stop further harm by preventing full power-up and ensuring it behaves as described. You're unlikely to cause additional damage beyond the current issues. While it's doable, most faulty CPUs won't function properly. I owned one that failed completely due to a board issue, which involved a lot of sparks. That situation didn't match your description, so it probably isn't happening here. Understanding what to fix is key, and so far there haven't been any risky actions from your post.

H
homedawg_
Member
131
11-22-2019, 09:44 AM
#6
I removed the chip and attempted to power it up again. After a brief flash, it booted normally in my other system. I then decided to leave it in place since both CPUs were identical (both 3600). I didn’t realize I hadn’t checked the TPM, which might have been involved. I ended up redoing the pin configuration and was interrupted by a system shutdown. Later, I found the CPU fan wasn’t properly secured and fixed that issue, but it triggered an error code Oxc00000e9. I tried reinstalling Windows on another USB drive, but the same message appeared. I’m now attempting to install another ISO on a different USB stick. This is really frustrating.
H
homedawg_
11-22-2019, 09:44 AM #6

I removed the chip and attempted to power it up again. After a brief flash, it booted normally in my other system. I then decided to leave it in place since both CPUs were identical (both 3600). I didn’t realize I hadn’t checked the TPM, which might have been involved. I ended up redoing the pin configuration and was interrupted by a system shutdown. Later, I found the CPU fan wasn’t properly secured and fixed that issue, but it triggered an error code Oxc00000e9. I tried reinstalling Windows on another USB drive, but the same message appeared. I’m now attempting to install another ISO on a different USB stick. This is really frustrating.

T
Tumscraftnl_YT
Junior Member
34
11-28-2019, 06:23 PM
#7
T
Tumscraftnl_YT
11-28-2019, 06:23 PM #7

M
Meowables
Senior Member
608
12-06-2019, 06:38 AM
#8
the chip is now on a different board, which is my personal one, and that's causing the new error. the fan wasn't secured properly when I installed the new CPU, but I fixed that issue. however, the error still persists. the other motherboard is faulty, so I ended up with two broken computers. lol.
M
Meowables
12-06-2019, 06:38 AM #8

the chip is now on a different board, which is my personal one, and that's causing the new error. the fan wasn't secured properly when I installed the new CPU, but I fixed that issue. however, the error still persists. the other motherboard is faulty, so I ended up with two broken computers. lol.

P
Piethomassen
Junior Member
12
12-06-2019, 07:18 AM
#9
I managed to get the other machine up and running again. Now I’m focusing on checking if the motherboard needs replacing, which seems likely. If you have any suggestions, please share. Thanks for your support!
P
Piethomassen
12-06-2019, 07:18 AM #9

I managed to get the other machine up and running again. Now I’m focusing on checking if the motherboard needs replacing, which seems likely. If you have any suggestions, please share. Thanks for your support!

D
Dephunkpunk_2
Senior Member
484
12-11-2019, 02:04 AM
#10
If everything points to it as being bad, then that's how I'd have to judge it myself if it was me testing it. Process of elimination is how I go about it and if you've determined all the other components are fine, that has to be it. Now - Here's something to think about. If you can get your money back, don't mess with it , just send it back for the refund so they can't claim you caused it's problems by tinkering with it. Big thing here is to ask - Worst case scenario is for them to say "No" but doesn't hurt to anyway so do that. Yes, I'd ask the seller about it first before any tinkering is done. Be sure to describe the symptoms it's having and if the seller is anyone decent they should work with you on it I'd think. If not and you're stuck with it, first thing I'd do is to remove the board's heatsinks and check the MOSFETS. You may have one that's blown on that board and if so, well.... There you go. If so then post good, clear detailed pics of the damage for further evaluation and we can go from there in terms of advising you about it.
D
Dephunkpunk_2
12-11-2019, 02:04 AM #10

If everything points to it as being bad, then that's how I'd have to judge it myself if it was me testing it. Process of elimination is how I go about it and if you've determined all the other components are fine, that has to be it. Now - Here's something to think about. If you can get your money back, don't mess with it , just send it back for the refund so they can't claim you caused it's problems by tinkering with it. Big thing here is to ask - Worst case scenario is for them to say "No" but doesn't hurt to anyway so do that. Yes, I'd ask the seller about it first before any tinkering is done. Be sure to describe the symptoms it's having and if the seller is anyone decent they should work with you on it I'd think. If not and you're stuck with it, first thing I'd do is to remove the board's heatsinks and check the MOSFETS. You may have one that's blown on that board and if so, well.... There you go. If so then post good, clear detailed pics of the damage for further evaluation and we can go from there in terms of advising you about it.