BSOD appears immediately after launching Forza Horizon 5
BSOD appears immediately after launching Forza Horizon 5
Hey everyone, seeking some tech advice! I experience occasional PC restarts, usually weeks or months apart while playing Apex Legends and OW2. Recently, I’m getting a BSOD right after launching Forza Horizon 5. I’ve attached a minidump file since I’m unsure how to interpret the output from WinDbg. (Just the dump from the last crash; I’m sure I can re-trigger it if needed.) The error is: BSOD 1: WHEA UNCORRECTABLE_ERROR 2: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1). I’ve changed the BIOS settings and disabled XMP. Windows 10 x64 CPU: 7700K GPU: 3080 MOBO: Asus Z170-A RAM: 16GB 2133MHz. Please let me know if you need more details or want the bugcheck analysis included. Thanks for any assistance!
Do you have a dump file from the WHEA crash? It indicates a hardware problem with the CPU or a PCIe device, which usually helps identify the issue quickly. If you don't have one, NVMe storage becomes the primary suspect.
Thanks for your support! The only available minidump is the latest one. You might want to run it several times to check for the WHEA error. (I have a screenshot of the BSOD if that would be useful.) Since the drive is just two years old, it’s likely still under warranty. It’s also your boot drive. Would you like advice on reinstalling it on the original NVMe or testing it on another drive?
I've received an update. The minidump issue appears unrelated to our current concerns and can likely be disregarded at this time. In previous BSODs (especially new ones with WHEA errors) in Forza, I don't see a mini dump. When reviewing Event Viewer, it shows "Dump file creation failed due to error during dump creation." I've verified my system failure settings and enabled debugging with the path: SystemRoot%\MEMORY.DMP. I've also run sfc /scannow, which identified some issues and fixed them, though a chkdsk scan didn't reveal anything. A Windows memory test came back clean. I've tried various displays, resolutions (1080p vs 4K, HDR on/off), but no clear direction yet.
I don't receive a notification unless you respond or mention me. The absence of a dump file often points to an NVMe SSD issue. If you're using multiple drives, checking Event Viewer for WHEA events can help identify the model. For a single drive, this step isn't needed. Navigate to Event Viewer → Windows Logs → System and use the filter option to locate WHEA logs. Select the appropriate source and save any relevant entries. If no events appear, you may need to test with a different drive or use PowerShell commands to inspect the page file location. Storage-related errors can be decoded from the event details, showing model information in hex format.
Here’s a revised version of your message:
Thanks for the tech advice. I just picked up a new motherboard RAM and CPU, planning an upgrade. I’ll review your suggestions before proceeding, especially since my drive is old and I want to get a warranty as soon as possible (it was bought about 18 months ago). I’ll send an update once I’ve finished.
I have 17 WHEA errors, with the latest one appearing just over two months ago. Using PowerShell, I see:
Status: Name – C:\pagefile.sys | CurrentUsage – 0 | Caption – C:\pagefile.sys | Description – C:\pagefile.sys | InstallDate – 2024-01-18 3:11:10 PM | AllocatedBaseSize – 11776 | PeakUsage – 1 | TempPageFile – False
PSComputerName – CimClass: root/cimv2:Win32_PageFileUsage | CimInstanceProperties – {Caption, Description, InstallDate, Name...} | CimSystemProperties – Microsoft.Management.Infrastructure.CimSystemProperties
Using a hex converter on the newest error, I get:
CPERÿÿÿÿÎ+/ <`ÁR§HÑÙF> we’re dealing with a possible problem with multiple drives or another issue altogether.
Could you help me figure this out? I’m considering swapping the CPU and RAM, or maybe checking the hardware first. Let me know if that’s a viable option.
Thanks again for your support!
WHEA events.evtx
The likelihood of every drive being faulty is low. Therefore, it seems more probable the motherboard, specifically the SATA controller, is the issue.