Question BSOD (WHEA) - After game runns for 15-30 Min

Jan 6, 2021
Hello, I want to know if my BSOD is really from my GPU (my guess) or if you have other ideas what the root of the errors could be.

Brand new system except GPU.
I get a BSOD every time when I start a game after a short amount of time.
After a BSOD there is a 30% chance that after the restart a other BSOD occurred.
The Game is irrelevant Cyberpunk, Anno 1800, Snowtopia all the same error.
Access to "memory.dmp" can be given when needed.
Zipped memory.dmp from crash:

The funny thing is even if i turn the Graphic Settings in Games extremely low the error happens.

Error Code:
  • 0x00000124 (0x0000000000000000, 0xffffc90feedc5028, 0x00000000bc000800, 0x0000000001010135).
  • CPU - AMD Ryzen 7 5800X
  • RAM - Crucial BL2K16G32C16U4R (16GB x 2)
  • GPU - ASUS Strix R9 390 8GB (5 years old)
  • OS - Windows 10 Pro 20H2
  • Main Board - ASUS ROG STRIX B550-F Gaming
  • Power Supply - Fractal ION+ 760P
  • CPU Fan - be quiet! Pure Rock 2, 120 mm
  • Case - Thermaltake View 37 ARGB Edition
  • Furmark: After some time a BSOD occurs
  • Prime95: Testet for 1 hour no errors
  • memtest86 with both DIMMs
Tested solutions:
  • Clean Windows 10 Installation
  • BIOS Update
  • BIOS default options
  • All drivers installed
  • Turned off SMT
  • 2 power cables from PSU to GPU
  • Changed the 2 DIMMs with each other
If you need anymore information please feel free to ask.
Thanks for your help.
Last edited:


Win 10 Master
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  • copy that file to documents
  • upload the copy from documents to a file sharing web site,
  • and share the link in your thread so we can help fix the problem
WHEA - Windows Hardware Error Architecture
Its an error called by CPU but not necessarily caused by it.
Can be caused by heat
Can be caused by over clocking
can be caused by overclocking software like MSI Afterburner or Asus AI Suite
Can be caused by any hardware
can be caused by device drivers (rare)

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it

try running heaven benchmark and see if you crash - just testing if its gpu


Hi, I ran the dump file through the debugger and got the following information: This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:MEMORY.DMP (Jan 6 2021 - 09:21:57)
Probably caused by:memory_corruption (Process: Anno1800.exe)
Uptime:0 Day(s), 0 Hour(s), 07 Min(s), and 33 Sec(s)

Possible Motherboard page:
There is a new Beta BIOS update available. You are already using a beta version, 1216. We usually don't recommend using betas unless there's a specific need. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
Reactions: Geartwo


Win 10 Master
Dear Asus, please don't have 3 beta bios at once on same board, pick one and release others...

its odd you don't have any drivers running during last crash. its possible a result of a beta bios, I don't know if you have any installed or not.

I see some things in there that don't make sense, I see mention of hiberfile in there while you playing a game. hiberfile used by windows for hibernation and fast startup. I see its 7 minutes after startup, would think that is long enough for it to not have that in memory...

there are small signs it could be GPU. one of the actions it was doing in stack text just before the crash is

fffff8053f4038ba-fffff8053f4038be 5 bytes - nt!MiReplenishBitMap+7a
[ d0 be 7d fb f6:30 76 ec d8 b1 ]
fffff8053f4038c4-fffff8053f4038c8 5 bytes - nt!MiReplenishBitMap+84 (+0x0a)
[ d7 be 7d fb f6:37 76 ec d8 b1 ]
fffff8053f4038d2 - nt!MiReplenishBitMap+92 (+0x0e)
[ f6:b1 ]
fffff8053f403af1-fffff8053f403af5 5 bytes - nt!MiReplenishBitMap+2b1 (+0x21f)
[ d0 be 7d fb f6:30 76 ec d8 b1 ]
fffff8053f403afb-fffff8053f403aff 5 bytes - nt!MiReplenishBitMap+2bb (+0x0a)
[ d7 be 7d fb f6:37 76 ec d8 b1 ]
fffff8053f403b09 - nt!MiReplenishBitMap+2c9 (+0x0e)
[ f6:b1 ]
fffff8053f403b39-fffff8053f403b3d 5 bytes - nt!MiReplenishBitMap+2f9 (+0x30)
[ d0 be 7d fb f6:30 76 ec d8 b1 ]
fffff8053f403b43-fffff8053f403b47 5 bytes - nt!MiReplenishBitMap+303 (+0x0a)
I have been wrong before but bitmap to me is a GPU function.

WHEA error crash reports hardly ever help me.
Jan 6, 2021
I tested to power the GPU with the PSU from my old PC (only the GPU all other things with my new PSU) and to my surprise IT WORKS.
So it can only be a damaged PSU or a <Mod Edit> BIOS that force a power save mode or something.
I will test it further.
Last edited by a moderator:


Win 10 Master
Now 4 beta bios, they aren't listening to me. the 2 oldest beta both say they fix system compatibility and stability but that might only relate to 5 series cards.
could try to flash same bios but with 4 beta to choose from, you can always grab one of them. I expect they stop being beta eventually (I had assumed it be by now).

PSU & MB two hardest things to pin point with errors.
PSU tests -
the paper clip method -
or multimeter,
or in the BIOS to check the +3.3V, +5V, and +12V. -

Motherboard tests -

No, I didn't forget to put anything next to mb. there are no tests. Only way you can say its motherboard is after you know everything else is fine.
Reactions: Geartwo