Asrock X399 Phantom Ggaming 6 - Bios Flashback £

Hey,

Does the X399 Phantom Gaming 6 have no Flashback Option ?

Cant find any and the descriptions are for the Fatality and Taichi.


Got Hands on a X399 Phantom Gaming 6 - looks perfect, switches on, but not much is happening.
After maybe 30sec it turns off and restarts - repeats that till eternity.

Took several PSU, multible Rams, 2x CPU - it always does the same.

Only Idea i got was to flashback the Bios, but... cant, since there is no Flashback-button ?! Or am i blind ?

Thanks and greetings

Hey,

Thanks - ok, so i am not blind and it rly does not have a Flashback-Option.

...and the Bios-Chip is welded in too - was thinking of plugging it out and flash it then somewhere else.. "oh no wait...has to be soldered"

Ye, quite Budget the Board it seems :(

CPU i am sure it is connected - Pins look awesome. Slider is perfect. Retentionmodule is fine and aligned. I am used to Socket 2011, 3467 and had now 3x other TR4 Boards before this one - ofc always the chance the pressure isnt sitting and hitting all Pins.

But it does look CPU is working - else it would do "other" stuff.

Weird is that behaviour ;

Switches on - no beep, 25sec later it switches off and restarts.
PSU i have several, all have at least one 8-Pin.
CMos button was pressed and Bios-batterie also replaced, old one still had 2.94V - but just in case, brand new one in.
Ram Slots i tried with one at first, but doesnt seem to make difference if 1,2,4 or 8.

Sadly I dont have an PCI-E Post-Card, only for older Boards with PCI.

Is this generally known to happen to Asrock Mainboards after maybe failed Bios-Flash ?

Thinking of buying new Bios-Chip and solder it on - but might be hopeless anyway ?!

Thanks sofar & Greetings :)

Hey,

Thanks - good idea, with the Rom Writer and clips :)
I did wire the Chip with 20cm cables then to the Rom-Writer/reader and i could read and write it - But sadly no help - The chip is fine and the Bios was fully functional and error free - Could read every corner, view it all and microcodes in viewer - all there, nothing wrong - did flash it anyway, but didnt help.

Issue still the same - and now worse ;

Also you mentioned letting it try run for 5, 10min.

I did try and let it run rebooting for over 20minutes in loop - but nothing came. Felt also like this XMP "cant read memory OC profile", tries 3x and then usually goes into safe-mode. But after 20min I aborted that.

Now the worst part ;

Since I didnt use the 2nd 12V Pin-plug, I thought time to test that.
2nd one isnt needed anyway, only for OC - has to work with one.
What was weird ;
System reboots 25-30 seconds if I had the 24Pin+ 1x8 Pin plugged on - but when I left out the 8-Pin, Board didnt shut itself down and rebooted, it ran.
Which felt like "cant give stable 12v?!"

So i did plug in 2nd 8-Pin in and tried again ...and at first it stood, no reboot, even the RGB colours under the Cooler went colorful, waited bit more - and then you could hear something feeping, bruzzling - RGB flickered, system stuttering - so I switched off.

Board still does the same issue, works as before - but my PSU is dead :(
The Board killed my beloved 600 Watt Be-quiet Modular one - it wont turn on anymore :(

I guess something went/is/was haywire with the additional 12V Supply for the Mainboard - cant get 12V working, so no further CPU-Initialize = shutdown and retry.
After I then Added "morre Power" - it might have had the chance to finally give the 12V Power/Watt needing to fully initialize...but yeah, something on the Board obviosly cant hold it anymore.

I ofc dont dare to plug in any other PSU with 2x 8-Pin and retry - with 1x 8-pin it still works as before.


Story of Board itself ;

it was an perfectly well working System, very well maintained, clean, dustfree, smoking free, animal free - bit richer Person, having an extraordinary System of the Time - not suffering or working too much, no OC, were only 3200Mhz Modules on it, 1950X, good/normal cooling - Did every day work, without beeing an 24/7 or even 12/7 system running on 80% CPU all the time.
But then this "bug" just appeared on day

as computers always are "but yesterday it workerd totally fine" :(

Well so much for that then.

Thanks for the help and answers! :)
was afraid nobody was answering