Your computer is acting strangely and it's hard to figure out what to do.
Your computer is acting strangely and it's hard to figure out what to do.
Experiencing problems with frequent restarts and a crash when shutting down Forza. Closing it triggers a blue screen and an immediate restart. Despite this, I can play for extended periods without issues. Loading 3Dmark for benchmarking always causes a restart with no errors whatsoever, only a black screen followed by a restart. Other titles? Cyberpunk, Genshin Impact, CS2, Horizon Zero Dawn all function properly. Tested so far: temperatures checked on a burn test with Furmak running both GPU and CPU simultaneously for an hour without crash or shutdown. PSU changed from Corsair RMI 750w to HX1000i. Graphics card swapped (including my old 2070 Super). Memory tested for 48 hours with no issues. PC connected only via NVMe, no extra drives. CPU tested on another system and my old R5 3600x also had the same problem. Every power cable changed. Notes: Windows drivers and BIOS updated. Disks show no errors on all drives. This PC is cursed – AMD Ryzen 7 5800X3D, 32GB Corsair Vengeance LPX at 3200MHz. Storage options: 1TB NVMe WD Blue SN550, 1TB SSD WD Blue 3D Nand, 2TB SSD Samsung EVO 860 QVO, 4TB Seagate BarraCuda 7200rpm, plus two 4TB Western Digital Red cards. Monitor: AOC CQ32G1 31.5", CPU cooling from Artic Freezer 2, 240mm AIO case. Case: Corsair Liam Li O 11 Dynamic PSU, Gygabyte B550 Gaming X V2.
It seems the problem might be related to software. Have you attempted reinstalling Forza, or have you tried restoring Windows from a fresh installation media?
Run memtest86 afterward. Then execute your memory test at 2133mhz without xmp.
will attempt xmp during memtest and will inform you it requires a significant duration. This was previously attempted. Windows appears to generate an error log this time: the system restarted due to a bugcheck. The specific issue was 0x00000139 (0x0000000000000002, 0xffffd3013b36ed70, 0xffffd3013b36ecc8, 0x0000000000000000).
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the entire Minidump folder to the Downloads folder (use your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file manipulation there.
They all reference storage drivers. In this specific crash, it seems more likely the issue stems from software conflicting with the storage driver. The stack trace remains consistent each time, which is odd if the storage device were damaged and altering data. There are no indications of a particular driver or program involved. I could dig deeper if I obtained a kernel dump. Minidumps compress large data files to reduce size. Kernel dumps are located at C:\Windows/Memory.dmp. Keep in mind these files can be very large, so a file host might be necessary.
Please remember to compress the kernel dumps. It may cut the file size by up to 90%.
The compressed kernel dump is available online. A full memory dump exists, but the uncompressed version was 33 GB. Thank you for your assistance with this problem.