Question Bios flash went wrong on MSI b450 mortar

[Fnk]

Msi b450m mortar
Ryzen 5 2600
16gb gskill aegis 3000mhz

Flashed latest bios, windows wouldnt boot, managed to make it boot, pc started randomly rebooting or getting black screens which require manually rebooting. Flashed back original bios, problems continued.

What I've noticed so far, black screens happen randomly, can be 5 seconds after windows booting up, or 15 minutes. When the freeze/black screen happens gpu and case fans spin up, while cpu cooler stops spinning. Ez debug led CPU turns on when that happens and stays active until I manually restart the pc.

Tried different ram combinations with one module and changing slots, tried different gpu and psu. Happens in safe mode too. Cleared cmos multiple times.

After some of those manual reboots windows boots its recovery screen with "BCD error 0xc0000098" but any of the offered options make the screen go black and ez debug led cpu turns on, like pressing F1 to enter recovery.

Pc was working without any problems whatsoever until that bios flash.

Any solutions?

 

[rgd1101]

turn on the xmp memory profile?

 

[Fnk]

turn on the xmp memory profile?

Tried both xmp profiles, still having same issues

 

[yellowcardyc]

Do you have Game Boost enabled? or Dragon Center installed?

 

[Fnk]

Do you have Game Boost enabled? or Dragon Center installed?

Neither. All default values loaded in bios. No MSI software installed in windows.

Cpu was running stable oc @ 4.0 with memory at 2933 before i flashed new bios. I didn't reset cmos before flashing it, could that been what caused the issues?

Tried running hirens boot, but got black screen with debug led CPU on after 30 seconds.

 

[drea.drechsler]

Neither. All default values loaded in bios. No MSI software installed in windows.

Cpu was running stable oc @ 4.0 with memory at 2933 before i flashed new bios. I didn't reset cmos before flashing it, could that been what caused the issues?

Tried running hirens boot, but got black screen with debug led CPU on after 30 seconds.

CMOS reset? do it with power off/unplugged, pull battery then short pins for 5 min's at least.

 

[Fnk]

CMOS reset? do it with power off/unplugged, pull battery then short pins for 5 min's at least.

After bios was flashed and the problems started I reset cmos multiple times by shorting the pins, bios pops up with the "load defaults" message so its confirmed a successful reset. Didn't pull out battery, just shorted the pins.
Do you suggest both taking out the battery and shorting pins?

 

[drea.drechsler]

After bios was flashed and the problems started I reset cmos multiple times by shorting the pins, bios pops up with the "load defaults" message so its confirmed a successful reset. Didn't pull out battery, just shorted the pins.
Do you suggest both taking out the battery and shorting pins?

It's not hard to do and I've had success going that far in the past. Especially when I've gotten mis-configured memory (usually a too-aggressive overclock settings).

 

[Fnk]

It's not hard to do and I've had success going that far in the past. Especially when I've gotten mis-configured memory (usually a too-aggressive overclock settings).

If anything its underclocked and undervolted. Xmp profiles disabled, running at 1.20v, tried upping the voltage to 1.35v as its rated for that, no changes. Currently at 52minutes of memtest with default bios settings.
I'll pull out the cmos battery once memtest finishes.

 

[drea.drechsler]

If anything its underclocked and undervolted. Xmp profiles disabled, running at 1.20v, tried upping the voltage to 1.35v as its rated for that, no changes. Currently at 52minutes of memtest with default bios settings.
I'll pull out the cmos battery once memtest finishes.

So the black screens have stopped now?

What I've read is there are some registers in the CPU that get set during memory training and don't always reset by just resetting memory back to base settings (no XMP) or even with a simple CMOS reset. So pulling the battery and doing the reset for a long time forces them to reset. I've run into that on my Mortar when I pushed memory too far.

 

[drea.drechsler]

Oh and...what BIOS revisions did you flash from/to/back to? I also have a B450M Mortar, btw, although it's running a 3700x.

 

[Fnk]

So the black screens have stopped now?

What I've read is there are some registers in the CPU that get set during memory training and don't always reset by just resetting memory back to base settings (no XMP) or even with a simple CMOS reset. So pulling the battery and doing the reset for a long time forces them to reset. I've run into that on my Mortar when I pushed memory too far.

Well memtest can run successfully without black screens, if i boot to windows or hirens boot it then crashes.

I pulled out cmos battery for an hour, still crashing.

Just black screen, ez debug led cpu ON, screen says no signal. All fans spinning until i reboot.

Oh and...what BIOS revisions did you flash from/to/back to? I also have a B450M Mortar, btw, although it's running a 3700x.

Went from 7B89v16 to 7B89v1D and then it wouldnt boot windows, so i flashed back to 7B89v16.

 

[drea.drechsler]

Well memtest can run successfully without black screens, if i boot to windows or hirens boot it then crashes.

I pulled out cmos battery for an hour, still crashing.

Just black screen, ez debug led cpu ON, screen says no signal. All fans spinning until i reboot.


Went from 7B89v16 to 7B89v1D and then it wouldnt boot windows, so i flashed back to 7B89v16.

I wouldn't go to v16...excepting v1D I'd go no later than v12. After v12, with AGESA 1006, they started adding 'new cpu' support (I think that meant Ryzen 3000) that doesn't help 2600 CPU's at all and can actually cause problems.

But then have you considered that your Windows might have gotten corrupted? Can you get into safe mode? Usually after 2 or 3 failed attempts to start it will offer to go into safe mode to troubleshoot.

EDIT add: Forget the BIOS rev rabbit hole (although I do prefer v12 for 2600's anyway). I googled the "BCD error 0xc0000098" error you got it looks like your BCD might be corrupted. BCD is the Boot Configuration Data file, without it Windows can't boot.

Check out this MS Answer:
https://answers.microsoft.com/en-us...098-help/67c56008-766c-424f-b591-0bd846290e83

watch this video:

View: https://www.youtube.com/watch?v=LCOTKbIRpOA

 

[mitch074]

Well memtest can run successfully without black screens, if i boot to windows or hirens boot it then crashes.

I pulled out cmos battery for an hour, still crashing.

Just black screen, ez debug led cpu ON, screen says no signal. All fans spinning until i reboot.


Went from 7B89v16 to 7B89v1D and then it wouldnt boot windows, so i flashed back to 7B89v16.

You can try adding .01V to your RAM voltage - I had similar problems with a PC I built for a pal. Same thing, updated the BIOS and Windows freshly installed would crash here and there. Memtest86+ would have no problem either (I suspect this happens when power draw on the motherboard gets a bit higher than only the CPU writing random stuff to RAM). Increased RAM voltage, reinstalled Windows and latest chipset drivers - rock solid now.

 

[Fnk]

I wouldn't go to v16...excepting v1D I'd go no later than v12. After v12, with AGESA 1006, they started adding 'new cpu' support (I think that meant Ryzen 3000) that doesn't help 2600 CPU's at all and can actually cause problems.

But then have you considered that your Windows might have gotten corrupted? Can you get into safe mode? Usually after 2 or 3 failed attempts to start it will offer to go into safe mode to troubleshoot.

EDIT add: Forget the BIOS rev rabbit hole (although I do prefer v12 for 2600's anyway). I googled the "BCD error 0xc0000098" error you got it looks like your BCD might be corrupted. BCD is the Boot Configuration Data file, without it Windows can't boot.

Check out this MS Answer:
https://answers.microsoft.com/en-us...098-help/67c56008-766c-424f-b591-0bd846290e83

watch this video:

View: https://www.youtube.com/watch?v=LCOTKbIRpOA

Actually cant roll back to v12, mflash doesnt allow me to flash lower then v16 when i tried v14. Flashed v17 and problems continue.

I think something is going on with the mflash, because the flashing process gets to 100% and theres no 'exiting mflash process' or whatever the message is, and it doesnt go back to bios. Nothing confirms a successful flash. It reboots, black screen, starts windows loading animation.

Think I should try the flashback button on the motherboard method instead of mflash through bios?


Regarding the bcd error, tried following the video, cant get past the first step. Typing bcdedit /export c:\bcdbackup gives the next error "the store export operation has failed. The requested system device cannot be found."

And by the way, cmd.exe stayed open for 30minutes without crashing, while any other gui based option caused a black screen like trying to system restore or repair.

 

[Fnk]

You can try adding .01V to your RAM voltage - I had similar problems with a PC I built for a pal. Same thing, updated the BIOS and Windows freshly installed would crash here and there. Memtest86+ would have no problem either (I suspect this happens when power draw on the motherboard gets a bit higher than only the CPU writing random stuff to RAM). Increased RAM voltage, reinstalled Windows and latest chipset drivers - rock solid now.

I'll try adding .01V, but like I said, it happens with 1.20V and with 1.35V the same.

 

[drea.drechsler]

... It reboots, black screen, starts windows loading animation.

I can't be positive but I think that's all mine did the last time I flashed it...just completes out to 100% and then reboots with no other messages. I do recall that being a bit disconcerting when it happened until the BIOS screen popped up after spamming DEL.

If you can't roll back to v12 I'd suggest go all-in to v1D. Reason being is v1D is the 'grand unification' AGESA, 1004b, which is supposed to be fully compatible with all the Ryzen processors (until 3100/3300's come along).

Also something to try is changing to BIOS compatibility mode (CSM...or Compatibility Support Mode) in BIOS. If it's in CSM, then change to Windows Enhanced mode or WHQL mode or EFI mode or whatever MSI calls it, just something different to see how Windows likes it.

If you're full-on ultra stock with memory starting up in 2133 or no more than 2400 speed and BIOS screens are working OK I have to think the problem is with Windows' corruption. So, getting to last resorts, if you can get into Windows once booted do a repair install. That re-installs windows and fixes up system files. But if nothing works you may have to bite the bullet and do a clean install.

 

[Fnk]

I can't be positive but I think that's all mine did the last time I flashed it...just completes out to 100% and then reboots with no other messages. I do recall that being a bit disconcerting when it happened until the BIOS screen popped up after spamming DEL.

If you can't roll back to v12 I'd suggest go all-in to v1D. Reason being is v1D is the 'grand unification' AGESA, 1004b, which is supposed to be fully compatible with all the Ryzen processors (until 3100/3300's come along).

Also something to try is changing to BIOS compatibility mode (CSM...or Compatibility Support Mode) in BIOS. If it's in CSM, then change to Windows Enhanced mode or WHQL mode or EFI mode or whatever MSI calls it, just something different to see how Windows likes it.

If you're full-on ultra stock with memory starting up in 2133 or no more than 2400 speed and BIOS screens are working OK I have to think the problem is with Windows' corruption. So, getting to last resorts, if you can get into Windows once booted do a repair install. That re-installs windows and fixes up system files. But if nothing works you may have to bite the bullet and do a clean install.

Flashed v1D over flashback button (MSI.ROM method) still having same issues.
Everything looks normal in bios, but cant stay in windows for longer than 20 seconds before black screen.

The thing is, I cant do a repair install cos i selected safe boot in msconfig and now it only boots to safe mode and crashes when before i can edit it back to normal boot, cant repair install from safe mode.

Only situations where i didnt get a black screen for prolonged periods were memtest and command prompt window (while trying to fix bcd).

Makes me almost certain its going to crash in the middle of repair install if I even get to it.

 

[mitch074]

I'll try adding .01V, but like I said, it happens with 1.20V and with 1.35V the same.

If it crashes with 1.35V when running in XMP, yeah, that is my point. If it crashes at 1.35V at 2133MHz, then your problem is elsewhere.

 

[Fnk]

If it crashes with 1.35V when running in XMP, yeah, that is my point. If it crashes at 1.35V at 2133MHz, then your problem is elsewhere.

Crashes at 1.35v without changing anything else, running bios defaults at 2133mhz

 

[drea.drechsler]

....
Makes me almost certain its going to crash in the middle of repair install if I even get to it.

If Windows is corrupted, BIOS won't fix it. It's just that v1D is the best bios for a 2600 at this point. Just make sure you're running full-stock so you can rule anything out.

With the error code you got I do not believe it's hardware related though. Did you take a backup? Can you get in long enough at least to do that? If the repair install doesn't work then the next logical is a clean install.

 

[Fnk]

If Windows is corrupted, BIOS won't fix it. It's just that v1D is the best bios for a 2600 at this point. Just make sure you're running full-stock so you can rule anything out.

With the error code you got I do not believe it's hardware related though. Did you take a backup? Can you get in long enough at least to do that? If the repair install doesn't work then the next logical is a clean install.

Decided to try a couple of live cd linux distros before trying to repair install windows.

Knoppix ran without problems, linuxmint didnt boot - same black screens as in windows, ubuntu booted but got black screen while choosing between install/try ubuntu.

All of this was done from a usb stick with ssd and hdds disconnected so no trace of windows.

This makes me think its a hardware problem, but I cant figure out why knoppix ran while other two failed. Could it be that theyre more cpu/gpu intensive?

I wanted to make an image of my ssd from a linux distro so i can do a clean install. Any suggestions on a distro i could try?

 

[drea.drechsler]

...
This makes me think its a hardware problem, but I cant figure out why knoppix ran while other two failed. Could it be that theyre more cpu/gpu intensive?
...

Have you tried one memory DIMM at a time?

 

[Fnk]

Have you tried one memory DIMM at a time?

I have, tried one dimm at a time, in different slots too, tried setting rated timings and voltage in bios too, nothing changed. Cpu led always glowing on the mobo.

Tried two more live cd distros, both failed to start their gui after going through the initial cmd/shell based setup. Weird thing is, it happens with two different gpus so its definitely not gpu related even though it goes to black screen only after the initial phase.