Question Weird crashing/can't update bios

Dec 6, 2019
11
0
10
0
So, about a year ago I built this computer: MSI b450 pro A, ryzen 3600(stock cooler), and Powercolor 5700 xt
So, when I originally build it I put A9 bios on it from July 2019. It ran fine, but tried to upgrade the bios for more memory support. It didn't work, when I would go into bios menu it would display in Chinese or spam some words across the screen and then freeze. When I did get into Windows it would run for 30 seconds to a minute and BSOD.
Fast forward to now. Still on the A9 Bios, but randomly I will get a black screen crash. It is 50/50 that I will get a crash dump. It restarts on its own, then it is fine. But it is completely random. Sometimes I will go a month without one, sometimes a couple a week. Tried to update the BIOS last night, but the same thing occurred within windows. Took 30 seconds and then BSOD. The computer runs well beyond the random black screen crash. Can game for long periods etc. The black screen crash occurs with XMP on and off.
Any ideas on what this could be? Thanks


I have five crash dumps, two are when I had the updated BIOS on. The other three are after.
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: AMDRSServ.exe
STACK_TEXT:
fffff48c53164720 fffff80746c25dbc : ffffe483a117fa40 ffffe48300000001 ffffe48300000000 0000000000000000 : nt!ExAcquireCacheAwarePushLockSharedEx+0xee fffff48c53164760 fffff80746c24490 : fffff48c53164930 fffff48c53164903 0000000000000000 0000000000000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x9c fffff48c53164880 fffff80746c5b405 : fffff48c53165000 fffff48c5315f000 ffffe4839cef50c0 fffff80747aefbce : FLTMGR!FltpPassThroughFastIo+0xc0 fffff48c53164900 fffff80747ab97bf : ffffe483a3aa3ed0 0000000000000000 0000000000000000 ffffe48300000000 : FLTMGR!FltpFastIoRead+0x165 fffff48c531649b0 fffff80747805fb8 : 0000000000004600 0000000000000000 0000000000000000 0000000000000000 : nt!NtReadFile+0x37f fffff48c53164a90 00007ffc8a86be54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000a9726fd918 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc8a86be54
SYMBOL_NAME: nt!ExAcquireCacheAwarePushLockSharedEx+ee
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .cxr 0xfffff48c53163d20 ; kb
BUCKET_ID_FUNC_OFFSET: ee
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ExAcquireCacheAwarePushLockSharedEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fb5b860e-1d50-315b-d7d2-f477bf970c1e}
[SIZE=6][B]Followup: MachineOwner[/B][/SIZE]
PROCESS_NAME: CC_Engine_x64.exe
STACK_TEXT:
ffff9e80d57fc660 fffff80756cf566a : ffffa203b79e8a00 ffff9e80d57fc8c8 0000000000000040 ffffa203b78c5560 : nt!ObpLookupObjectName+0x315 ffff9e80d57fc830 fffff80756bff52f : ffffffff00000000 00000062646ff508 0000000000000000 0000000000000001 : nt!ObOpenObjectByNameEx+0x1fa ffff9e80d57fc960 fffff80756bff109 : 00000062646ff4c8 0000000000000000 00000062646ff508 00000062646ff4d0 : nt!IopCreateFile+0x40f ffff9e80d57fca00 fffff80756a05fb8 : 0000000000000458 0000000000000000 0000000000000000 ffffa203c6d32350 : nt!NtCreateFile+0x79 ffff9e80d57fca90 00007fff295cc834 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 00000062646ff448 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff
295cc834
SYMBOL_NAME: nt!ObpLookupObjectName+315
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .cxr 0xffff9e80d57fbc60 ; kb
BUCKET_ID_FUNC_OFFSET: 315
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObpLookupObjectName
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {eb722ab6-4e0f-4d2b-99b4-f82b1fe1ab8a}
Those two are while I updated the BIOS. Removed both AMDRSServ.exe and MSI Dragon Center.

PROCESS_NAME: amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.504_none_e781e76525fb2
STACK_TEXT:
ffffd488de7f0908 fffff8031f06c834 : 0000000000000018 ffffc408b3af17a0 ffffc408cf127530 0000000000000001 : nt!KeBugCheckEx ffffd488de7f0910 fffff8031f2ed70e : ffffc408b3af17a0 0006000000000000 ffffffff00000000 ffffc408b3af17a0 : nt!ObfDereferenceObjectWithTag+0x190e54 ffffd488de7f0950 fffff8031f2f138c : 0000000000000924 000000869377c098 00000221868788e0 0000022100000001 : nt!ObCloseHandleTableEntry+0x29e ffffd488de7f0a90 fffff8031f005fb8 : ffffc408c1b75000 ffffc40800000000 ffffd488de7f0b80 ffffc408c487d850 : nt!NtClose+0xec ffffd488de7f0b00 00007ffbf974bf74 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000869377c2f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffbf974bf74
SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+190e54
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 190e54
FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWithTag
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}
ROCESS_NAME: AMDRSServ.exe
BAD_STACK_POINTER: ffff9e00ee0be018
STACK_TEXT:
ffff930431e30a90 00007ffe627abe54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x157 0000006bd06fd608 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe
627abe54
SYMBOL_NAME: nt!KiSystemServiceExit+157
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .cxr 0xffff9e00ee0be920 ; kb
BUCKET_ID_FUNC_OFFSET: 157
FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KiSystemServiceExit
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9f5a3c54-765e-bd49-e5a3-397bebf29764}
(this is where I removed AMDRSServ.exe)
And this latest one I haven't seen. But, it may be since I updated windows to a beta version on accident.

STACK_TEXT:
ffffe90db8c29608 fffff8055a5fdd1b : 0000000000000139 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx ffffe90db8c29610 fffff8055a528e7c : ffff910c478df010 0000000000000000 ffffffffffffffd2 fffff8056c06ea52 : nt!_chkstk+0x7b ffffe90db8c29640 fffff8055a527d13 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeClockInterruptNotify+0x2a7c ffffe90db8c296f0 fffff8055a527004 : 0000000000000000 00001f800000020c 0000000000000000 ffffe90db8c29cc0 : nt!KeClockInterruptNotify+0x1913 ffffe90db8c29af0 fffff8055a5f8d34 : ffffffff00000000 ffff8100fdeeb340 ffff910c4cc7f080 000000000000060c : nt!KeClockInterruptNotify+0xc04 ffffe90db8c29c60 0000000000000000 : ffffe90db8c2a000 ffffe90db8c24000 0000000000000000 0000000000000000 : nt!KeSynchronizeExecution+0x2904
IMAGE_VERSION: 10.0.19041.610
STACK_COMMAND: .thread ; .cxr ; kb
EXCEPTION_CODE_STR: DC50CCE6
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!DC50CCE61046000
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_19041.1.amd64fre.vb_release.191206-1406_TIMESTAMP_870217-011414_DC50CCE6_nt_wrong_symbols!DC50CCE61046000
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b9bcbca0-8ce2-53ba-7d1b-055bcb827959}
Since it won't let me get the symbols through command lines etc through debugger.
 

Colif

Win 10 Master
Moderator
Have you thought about a BIOS flashback back to A8? Its the first bios that supported 3600 so it might fix the weirdness?

are you updating bios inside windows or using the tool built into bios? see page 57 here - https://download.msi.com/archive/mnu_exe/mb/E7B86v2.1.pdf

how do you accidentally update win 10 to a beta version? hand slipped and I was suddenly in Insiders :)

exe files don't cause BSOD, they are normally what crashes. Something normally causes them to crash. You are victim blaming by saying the process that crashed was the cause. You can't remove ntoskrnl as windows won't work afterwards. Its the windows kernel
 
Dec 6, 2019
11
0
10
0
Haven't tried A8, since A9 is the only one that allows my computer to work at all. As for where I have upgraded the bios from: https://www.msi.com/Motherboard/support/B450-A-PRO. That and the one time recently I tried the MSI Dragon Center.

As for the accidently upgrading the windows to beta, I went to check for updates and hit the button to try version 20H2. And, since I updated to version 20H2 the BSODs are wrong symbols.
 

Colif

Win 10 Master
Moderator
20H2 isn't beta, its just the latest version of win 10. Its likely the windbg program needs to be updated for it.

MSI dragon centre would have got the bios files from same place. It might be safer to update the bios from inside the bios and not in windows.

I would have asked on the MSI forums when the bios went odd. I think its probably best you ask on there as maybe someone has a good idea. The bios sounds glitchy and you may be able to get a replacement board - https://forum-en.msi.com/index.php
 

ASK THE COMMUNITY