Blizzard client causes PC to crash directly into bios

Desktop App Tech Support
1

PC Specs:

  • Mobo: MSI b450i itx w/ bios v. 7A40vAC (latest)
  • CPU: AMD Ryzen 5 1600AF (not overclocked)
  • GPU: Radeon 5600xt ITX (not overclocked)
  • RAM: G.Skill AEGIS 16gb (2x8gb) DDR4 3200mhz memory
  • Storage: Sabrent 512gb NVMe m.2 ssd (SB-ROCKET-512)
  • PSU: Enhance 600w flex psu (ENP-7660B)
  • OS: Windows 10 v. 20H2

3 days ago, I started experiences intermittent crashes on while playing BOCW. Except it would crash my entire PC directly into the bios. I tried using the scan and repair option on the game but that didn’t work either. Then, out of the blue, my PC would consistently crash into bios even when not playing BOCW. When checking the event viewer it would say “Dump file creation failed due to error during Dump creation”. At this point I could not physically use my PC so I had to delete all files and reinstall windows. Reinstalled latest AMD drivers again and flashed the latest bios on my MSI motherboard. PC was back to normal with no issues. So I then downloaded the battle.net client again, logged in, and went to install BOCW when suddenly the PC crashed again directly into bios with the same error. Now again I cannot physically use my PC anymore since the battle.net client keeps crashing it on startup. Seems like a huge memory leak issue. Please help. Might have to wipe the drive and reinstall windows again because the battle.net client is crashing it on startup (was not happening before I installed the client on the fresh windows install and bios update).

1 Like
2

Hey there Allesbaba,

Thanks for reaching out with this information. If the crashes persist through re-installing Windows, this indicates that something deeper – likely hardware-related – is causing the system’s instability and subsequent Blue Screen crashes, and sadly will fall outside of the scope of what we can diagnose or troubleshoot here. I recommend giving these steps a try to narrow down what’s causing the problem, but if you have no luck, your best option will be to reach out to Microsoft’s Support or a local computer technician to diagnose the system.

I hope this information proves useful!