Question Gigabyte aorus b550 elite ax v2 power cycling on restarts

[Alexhead137]

Hi, i got the new motherboard and new ram (32gb corsair vengance) pc was working perfectly fine before I changed the motherboard.

Had 0 issues changing the mobo over. once everything was installed I plugged pc in and first got the power cycling issue but finally got it to post after a few force shutdowns. I assumed it was a bois issue so I shutdown and flashed the bois, this went perfectly but after the bois had finish flashing (completed the bois flash) the pc didn't shutdown (it have turn itself on during the flash) and just continued to power cycle so I had to force a shutdown. Now I know that sounds bad but It worked and when I powered up again it posted and all was well. I enabled xmp, reinstalled windows, installed gpu drivers etc.

The only issue is when the pc restarts (during updates for example) it goes straight back into the power cycling again until I force shutdown (something multiple time) until it posts again. When pc is running I'm have 0 issues and everything is working great and if I shutdown normally and power on again it works fine (mostly but not every time, one time when i shut down then tried to power back on almost immediately after it started power cycling)

I'd greatly appreciate any help.

My specs
Amd ryzen 5600x
Gigabyte aorus b550 elite ax v2
32 gb corsair vengeance pro rgb
powercolour rx 6700xt

 

[Ralston18]

This motherboard?

Gigabyte aorus b550 elite ax V2

Regarding:

"The only issue is when the pc restarts (during updates for example) it goes straight back into the power cycling again until I force shutdown (something multiple time) until it posts again"

Look in Reliability Histoy/Monitor and Event Viewer.

Either one or both tools may provide some additional insight (via error codes, warnings, and even informational events) about what is going on or otherwise happening when the power cycling begins and continues until you force a shutdown.

Another thing to consider is that there may be some buggy or corrupted files involved. Maybe caused by the forced shutdowns....

Use "dism" and "sfc /scannow" to look for and fix those sort of problems.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

 

[Alexhead137]

This motherboard?

Gigabyte aorus b550 elite ax V2

Regarding:

"The only issue is when the pc restarts (during updates for example) it goes straight back into the power cycling again until I force shutdown (something multiple time) until it posts again"

Look in Reliability Histoy/Monitor and Event Viewer.

Either one or both tools may provide some additional insight (via error codes, warnings, and even informational events) about what is going on or otherwise happening when the power cycling begins and continues until you force a shutdown.

Another thing to consider is that there may be some buggy or corrupted files involved. Maybe caused by the forced shutdowns....

Use "dism" and "sfc /scannow" to look for and fix those sort of problems.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

yes its the aorus b550 elite ax v2.

i looked on event viewer and found the issuses are as follows. The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. event 41, kernel-power

also found this in Reliability History.
Faulting Application Path: C:\Windows\System32\svchost.exe

 

[Alexhead137]

i have a rather large amount of administrative event errors/ warnings, wonder if i should just do a full windows reinstall

 

[Ralston18]

PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

History of heavy use for gaming, video editing, or even bit-mining?

= = = =

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all cards, connectors, jumpers, RAM, and case connections are fully and firmly in place.

Use a bright flashlight to inspect everywhere for signs of damage: bare conductor showing, melted insulation, kinked or pinched wires, cracks, missing or loose screws, browned or blackened areas, moisture, corrosion - anything at all.

Take your time. If unsure then disconnect/reconnect or seat/reseat connections and cards. Leave the CPU alone - that will be a last resort action.

Keep in mind that there could be a metal to metal short somewhere. Check inside and outside the I/O panel.

 

[Ralston18]

What are the administrative event warnings?

Take some screenshots and post the screenshots here via imgur (www.imgur.com).

Did you run "dism" and "sfc /scannow"?

 

[Alexhead137]

PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

History of heavy use for gaming, video editing, or even bit-mining?

= = = =

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all cards, connectors, jumpers, RAM, and case connections are fully and firmly in place.

Use a bright flashlight to inspect everywhere for signs of damage: bare conductor showing, melted insulation, kinked or pinched wires, cracks, missing or loose screws, browned or blackened areas, moisture, corrosion - anything at all.

Take your time. If unsure then disconnect/reconnect or seat/reseat connections and cards. Leave the CPU alone - that will be a last resort action.

Keep in mind that there could be a metal to metal short somewhere. Check inside and outside the I/O panel.

Corsair CX750f 80 plus bronze

Used for gaming mainly

 

[Alexhead137]

What are the administrative event warnings?

Take some screenshots and post the screenshots here via imgur (www.imgur.com).

Did you run "dism" and "sfc /scannow"?

i tried but it almost opens then dissappears

 

[Alexhead137]

https://imgur.com/a/3sYEVdk

View: https://imgur.com/a/3sYEVdk

 

[Ralston18]

Are you logged into the system with administrator rights?

Also run Event Viewer as admin if that choice is provided.

Focus on the Red circle errors first.

If you click the header in the column labled "Level" the entries should sort alphabetically with all of the Error entries together at the top. May take a few seconds especially if there are many entries. (Your listing has 684 per Imgur image 1/2.)

Also widen the Source column to show more of the contents. You can change column widths by dragging the small vertical bars between the column headers.

The most difficult part is actually finding or figuring out what any particular error code means.

For example, a search using 1796 (one of listed errrors) led to the following link:

https://www.thewindowsclub.com/fix-event-id-1796-the-secure-boot-update-failed

The description, cause(s), and fixes may or may not be fully relevant.

Any given error code(s) must be taken in context with the OS, the hardware, the configuration, and other error codes that are present.

Error code 110 (lots of those) led to:

https://kb.eventtracker.com/evtpass...soft-Windows-CertificationAuthority_61707.asp

https://kb.eventtracker.com/evtpass/evtpages/EventId_110_Microsoft-Windows-TaskScheduler_65982.asp

Do you use Task Scheduler? Per the link it is a "normal condition" - so why flagged with a red circle?

That is why being able to read the full contents of the source Column is important.

For now, I recommend just focusing on the physical checks.

See if you can get "dism" and "sfc /scanow" to run via admin.

Another thing that can be done is to clear the existing Event Viewer logs. Much easier to start fresh and address the more serious error codes - if even applicable.

 

[Alexhead137]

Are you logged into the system with administrator rights?

Also run Event Viewer as admin if that choice is provided.

Focus on the Red circle errors first.

If you click the header in the column labled "Level" the entries should sort alphabetically with all of the Error entries together at the top. May take a few seconds especially if there are many entries. (Your listing has 684 per Imgur image 1/2.)

Also widen the Source column to show more of the contents. You can change column widths by dragging the small vertical bars between the column headers.

The most difficult part is actually finding or figuring out what any particular error code means.

For example, a search using 1796 (one of listed errrors) led to the following link:

https://www.thewindowsclub.com/fix-event-id-1796-the-secure-boot-update-failed

The description, cause(s), and fixes may or may not be fully relevant.

Any given error code(s) must be taken in context with the OS, the hardware, the configuration, and other error codes that are present.

Error code 110 (lots of those) led to:

https://kb.eventtracker.com/evtpass...soft-Windows-CertificationAuthority_61707.asp

https://kb.eventtracker.com/evtpass/evtpages/EventId_110_Microsoft-Windows-TaskScheduler_65982.asp

Do you use Task Scheduler? Per the link it is a "normal condition" - so why flagged with a red circle?

That is why being able to read the full contents of the source Column is important.

For now, I recommend just focusing on the physical checks.

See if you can get "dism" and "sfc /scanow" to run via admin.

Another thing that can be done is to clear the existing Event Viewer logs. Much easier to start fresh and address the more serious error codes - if even applicable.

Yes, going to focus on checking hardware for now, going to take all non essentials off the board and try see if I can recreate the boot cycling, if
It still cycles then would I be wrong to assume that it's the board that's the issue and need to be sent back.

The only warnings on the event viewer now are regarding my hdd on while the computer booted (which isn't my boot drive) and another forum with the same board and simular issues said that removing the hdd solved the issues so I think I'll start there.

The software issues could be rectified with a full fresh windows install but I don't want to do that until I'm sure it won't get stuck boot cycling again.

Thank for your help, I'll update once sorted 👍