F5F Stay Refreshed Hardware Desktop Various crashes occur, occasionally due to software or games, yet at times they affect the entire PC?

Various crashes occur, occasionally due to software or games, yet at times they affect the entire PC?

Various crashes occur, occasionally due to software or games, yet at times they affect the entire PC?

K
knickd
Member
99
01-31-2022, 09:07 PM
#1
Hello, this situation is really frustrating for me. The PC occasionally crashes without warning, showing a message like 'we ran into a problem' and then restarting. In Overwatch, the game usually crashes within about 15 minutes. Destiny 2 sometimes does the same, often crashing to desktop right after the first failure. It usually prompts to verify files, which it tries but fails—especially when deleting the Destiny folder in appdata. This typically happens near the end of a mission or during a cutscene, forcing a restart. Error codes are often 'beagle' and 'marmot'.

Most people think it's due to a memory issue, probably related to RAM. I've swapped RAM sticks one by one, tested with MEM tests, but nothing changed. It seems like both sticks could be faulty at once. I also reinstalled Windows and graphics drivers without any difference. Cleaning and disassembling the PC didn’t help either.

I noticed Destiny and Overwatch aren’t on the same drive initially, thinking it might be a disk problem. Any suggestions?

Details:
- OS: Microsoft Windows 11 Home 10.0.26200 Build 26200
- Model: GENESIS (x64-based PC)
- Manufacturer: OriginPC
- Error codes: beagle, marmot
- Specs: 13th Gen Intel i9-13900K, 3000 MHz, 24 cores, 32 logical processors

I’m still unsure what’s causing it.
K
knickd
01-31-2022, 09:07 PM #1

Hello, this situation is really frustrating for me. The PC occasionally crashes without warning, showing a message like 'we ran into a problem' and then restarting. In Overwatch, the game usually crashes within about 15 minutes. Destiny 2 sometimes does the same, often crashing to desktop right after the first failure. It usually prompts to verify files, which it tries but fails—especially when deleting the Destiny folder in appdata. This typically happens near the end of a mission or during a cutscene, forcing a restart. Error codes are often 'beagle' and 'marmot'.

Most people think it's due to a memory issue, probably related to RAM. I've swapped RAM sticks one by one, tested with MEM tests, but nothing changed. It seems like both sticks could be faulty at once. I also reinstalled Windows and graphics drivers without any difference. Cleaning and disassembling the PC didn’t help either.

I noticed Destiny and Overwatch aren’t on the same drive initially, thinking it might be a disk problem. Any suggestions?

Details:
- OS: Microsoft Windows 11 Home 10.0.26200 Build 26200
- Model: GENESIS (x64-based PC)
- Manufacturer: OriginPC
- Error codes: beagle, marmot
- Specs: 13th Gen Intel i9-13900K, 3000 MHz, 24 cores, 32 logical processors

I’m still unsure what’s causing it.

P
ParaGoddess143
Junior Member
43
01-31-2022, 10:17 PM
#2
I reinstalled windows, but there was no change.
Where did you obtain the installer for the operating system? Did you set up the OS without internet access? Installed all drivers manually with the newest versions during offline mode, using an elevated command—Right click installer > Run as Administrator?
I reinstalled graphics drivers, but no difference was noticed.
Could you explain the steps you took?
P
ParaGoddess143
01-31-2022, 10:17 PM #2

I reinstalled windows, but there was no change.
Where did you obtain the installer for the operating system? Did you set up the OS without internet access? Installed all drivers manually with the newest versions during offline mode, using an elevated command—Right click installer > Run as Administrator?
I reinstalled graphics drivers, but no difference was noticed.
Could you explain the steps you took?

G
Ghostiepie
Member
55
02-01-2022, 04:51 AM
#3
It is highly advised to heed the guidance from @Lutfij regarding updating your motherboard BIOS promptly, in order to address the recognized issues with 13th and 14th Gen Intel CPUs.
G
Ghostiepie
02-01-2022, 04:51 AM #3

It is highly advised to heed the guidance from @Lutfij regarding updating your motherboard BIOS promptly, in order to address the recognized issues with 13th and 14th Gen Intel CPUs.

D
143
02-01-2022, 05:53 PM
#4
A new reply came in while I was typing. Wait... I remember hearing about the issues with the 13/14 generation CPUs. I assumed I had already updated the BIOS. Would it help to verify if this is indeed the cause? If so, it doesn’t mean the end of the world—just getting a new CPU might be enough.

Previous message
Ah good to know. You’re not using the latest BIOS with the 0x12F firmware update that fixed problems on your 13th/14th Gen systems. It might be worth flashing to version 4301, clearing the CMOS, and checking if that resolves the issue.

How would I proceed? Should I download the BIOS update from the manufacturer’s site or something similar?
*edit*
If the solution is in one of the links you shared, let me know—I’m still reviewing them.
Where did you get the installer for the operating system? Did you install it offline? Were you installing all drivers manually with the latest versions while using an elevated command, like right-clicking the installer and selecting Run as Administrator?

99% confident it wasn’t in offline mode. I used the reset PC option in settings and followed the instructions to keep files but redownload Windows (from online sources).
I reinstalled the graphics drivers, but there was no difference.
Could you explain the steps in more detail?
D
DaniilKozhuhar
02-01-2022, 05:53 PM #4

A new reply came in while I was typing. Wait... I remember hearing about the issues with the 13/14 generation CPUs. I assumed I had already updated the BIOS. Would it help to verify if this is indeed the cause? If so, it doesn’t mean the end of the world—just getting a new CPU might be enough.

Previous message
Ah good to know. You’re not using the latest BIOS with the 0x12F firmware update that fixed problems on your 13th/14th Gen systems. It might be worth flashing to version 4301, clearing the CMOS, and checking if that resolves the issue.

How would I proceed? Should I download the BIOS update from the manufacturer’s site or something similar?
*edit*
If the solution is in one of the links you shared, let me know—I’m still reviewing them.
Where did you get the installer for the operating system? Did you install it offline? Were you installing all drivers manually with the latest versions while using an elevated command, like right-clicking the installer and selecting Run as Administrator?

99% confident it wasn’t in offline mode. I used the reset PC option in settings and followed the instructions to keep files but redownload Windows (from online sources).
I reinstalled the graphics drivers, but there was no difference.
Could you explain the steps in more detail?

M
MoathyJr
Member
164
02-20-2022, 03:39 AM
#5
As usual, a web search engine should yield relevant results.
You can visit the official CPU monkey page and Intel support articles for more details.
It’s recommended to obtain the motherboard manual and the latest stable BIOS from the manufacturer’s website, then follow the instructions on flashing the BIOS.
I generally skip beta BIOS versions unless you’re certain they are fully stable.
The update is typically carried out through the BIOS menu, by loading the update file from a USB drive connected to the back panel.
A standard BIOS update usually lasts 2 to 3 minutes; avoid turning off the machine during this time to prevent a non-functional system.
If you experience power interruptions or unstable AC power, connect your PC to a reliable UPS before proceeding with the update to ensure a steady power supply.
M
MoathyJr
02-20-2022, 03:39 AM #5

As usual, a web search engine should yield relevant results.
You can visit the official CPU monkey page and Intel support articles for more details.
It’s recommended to obtain the motherboard manual and the latest stable BIOS from the manufacturer’s website, then follow the instructions on flashing the BIOS.
I generally skip beta BIOS versions unless you’re certain they are fully stable.
The update is typically carried out through the BIOS menu, by loading the update file from a USB drive connected to the back panel.
A standard BIOS update usually lasts 2 to 3 minutes; avoid turning off the machine during this time to prevent a non-functional system.
If you experience power interruptions or unstable AC power, connect your PC to a reliable UPS before proceeding with the update to ensure a steady power supply.

X
xAPPLExPIEx
Senior Member
657
02-20-2022, 04:27 AM
#6
I think I might be a bit confused!
😀
I went to install the USB for the BIOS update, but I realized the file was already there. Then I tried updating the BIOS settings, but I couldn't find the update options. Maybe I accidentally rolled back the driver instead of updating it. 🤦‍♂️
X
xAPPLExPIEx
02-20-2022, 04:27 AM #6

I think I might be a bit confused!
😀
I went to install the USB for the BIOS update, but I realized the file was already there. Then I tried updating the BIOS settings, but I couldn't find the update options. Maybe I accidentally rolled back the driver instead of updating it. 🤦‍♂️

F
FireworkFlare
Junior Member
35
02-21-2022, 03:36 AM
#7
If the USB stick isn't properly formatted, the BIOS might fail to recognize the update file.
Use a compact USB stick (32GB or less) and format it as FAT32.
When formatting with exFAT or NTFS, the BIOS may not identify the drive, let alone its contents.
If the BIOS doesn't support the file type, it won't permit installation.
Ensure you've renamed the file after downloading (a necessary step for some updates).
Failure to rename might prevent detection.
I don’t consider a BIOS update file a "driver." That term applies only to small programs that connect hardware to Windows, such as printer drivers.
You can optionally revert drivers in Windows if issues arise with the newest version.
Updating BIOS isn't always reversible; some motherboards lack the ability to restore older versions.
Verify your current BIOS version and match it with the downloaded file(s). Remove any outdated versions from the USB drive.
Transfer the latest BIOS file (rename if needed) to a small FAT32 USB stick, then place it in the root folder of the drive.
Insert the USB into the rear panel, boot the PC, access BIOS settings, and retry.
F
FireworkFlare
02-21-2022, 03:36 AM #7

If the USB stick isn't properly formatted, the BIOS might fail to recognize the update file.
Use a compact USB stick (32GB or less) and format it as FAT32.
When formatting with exFAT or NTFS, the BIOS may not identify the drive, let alone its contents.
If the BIOS doesn't support the file type, it won't permit installation.
Ensure you've renamed the file after downloading (a necessary step for some updates).
Failure to rename might prevent detection.
I don’t consider a BIOS update file a "driver." That term applies only to small programs that connect hardware to Windows, such as printer drivers.
You can optionally revert drivers in Windows if issues arise with the newest version.
Updating BIOS isn't always reversible; some motherboards lack the ability to restore older versions.
Verify your current BIOS version and match it with the downloaded file(s). Remove any outdated versions from the USB drive.
Transfer the latest BIOS file (rename if needed) to a small FAT32 USB stick, then place it in the root folder of the drive.
Insert the USB into the rear panel, boot the PC, access BIOS settings, and retry.

N
niclasdam
Member
175
02-21-2022, 04:14 AM
#8
Oh yeah, I already updated the bios before that last post. That’s why I thought I didn’t see the update menu. Since I don’t remember seeing it before this point (which I should have if I really did update last time), I guess I might have rolled back the bios version instead of updating it.
It looks stable now with the new version, but I’ll keep doing stress tests and will let you know. <3 Thanks again everyone!
N
niclasdam
02-21-2022, 04:14 AM #8

Oh yeah, I already updated the bios before that last post. That’s why I thought I didn’t see the update menu. Since I don’t remember seeing it before this point (which I should have if I really did update last time), I guess I might have rolled back the bios version instead of updating it.
It looks stable now with the new version, but I’ll keep doing stress tests and will let you know. <3 Thanks again everyone!