This new computer restarts unexpectedly.
This new computer restarts unexpectedly.
Parts inventory: PCPartPicker list available at the provided URL.
Processor: AMD Ryzen 7 5800X 3.8 GHz, 8-core (Price: $576.29 on Amazon Canada).
Cooler: Cooler Master MASTERLIQUID ML240L RGB V2 (65.59 CFM, $126.00 on Vuugo).
Thermal paste: Thermal Grizzly Kryonaut 1 g (Price: $14.68 on Amazon Canada).
Motherboard: MSI MAG X570S TOMAHAWK MAX WIFI ATX AM4 (Price: $360.47 on Vuugo).
Memory: Corsair Vengeance RGB Pro 32 GB (2 x 16 GB), DDR4-3600 CL18 (Price: $180.79 on Amazon Canada).
Storage: Samsung 970 Evo Plus 2 TB M.2-2280 PCIe 3.0 X4 NVME SSD (Price: $249.17 at shopRBC).
Video card: Asus TUF-RX6800XT-O16G-GAMING Radeon RX 6800 XT (16 GB, $2247.03 on Amazon Canada).
Case: Corsair iCUE 4000X RGB ATX Mid Tower (Price: $180.79 at Best Buy Canada).
Power supply: Corsair HX850 Platinum 850 W (80+ Platinum certified, $237.29 on Corsair).
Total cost: $4172.51
Shipping, taxes, and any available discounts are included.
Generated by PCPartPicker on 2023-01-10 06:13 EST.
System notes: Operating system – Windows 11 Pro 22H2; BIOS – version 7D54v14 (latest via MSI site).
Build experience: New setup functioning well, except for random crashes and reboots. Most sessions last hours of gaming without issues. Crash occurrences are infrequent, often linked to hardware monitoring open or stable temperatures. No overheating reported during testing. BIOS remains default, no overclocking detected. Power was left in sleep mode overnight without restart.
Tried several fixes: reconnecting power cable, using wall outlet instead of power bar, enabling XMP, switching PSU from multiple to single +12V, adjusting fan and AIO speeds, ensuring proper connections for CPU headers and PCIe slots, reseating GPU, reinstalling RAM and CPU.
No success yet with RAM or CPU re-seating; further advice welcome once tried.
99% of the time no BSOD occurs, though occasional ones do happen. Refer to a guide on analyzing memory dump files (.dmp) in Windows 10 (helpdeskgeek.com) for steps on examining a file generated during a BSOD. Move forward to the section "How to Analyze Windows Memory Dump Files Using WinDbg" and load the dump. Memory dump files may be located at c:\windows\minidump or c:\windows\memory.dmp, depending on your startup and recovery configurations.
I haven’t experienced a shutdown in several days after tweaking the fans and pump to maintain full speed. However, it crashed again with event ID 18. At that moment, the temperature was below 60 degrees, so I don’t believe it’s connected. I’ve included the Event Viewer log for the latest failure. crash.zip
I’ve checked the instructions linked for the latest dump file. The data shared doesn’t hold much personal value, and none of the references point to any drivers I’m familiar with. I’ve included the dump text here in case you or someone else needs more context. Remember, this information isn’t significant to me, and the timestamps and identifiers don’t seem meaningful.
At the end of the analysis you notice "IMAGE_NAME: ntkrnlmp.exe" which indicates the program or driver causing the BSOD. In this scenario it is ntkrnlmp.exe, the core Windows process (kernel). What options do you consider? - Launch cmd.exe with admin rights and execute "chkdsk /f /r c:" which will perform a startup drive scan for NTFS errors or bad disk blocks "sfc /scannow" will verify system file integrity - Apply the newest Windows updates - Turn off page file (virtual memory) for testing The final command before crash is "KiPageFault"; you may try various settings for the page file. I set it to a fixed size (32GB*1.5*3=144GB = 147456MB) on a non-OS drive on a failing customer's system, and he reports the issues are resolved.
I completed a chkdsk and sfc check, both indicating errors. With only one drive on my PC, I can't move the page file to another disk. I'll return in a few days to see if this resolves the issue, as there had been a brief period without problems before it started again.
After more than two weeks without issues, I experienced a few crashes recently. Initially, I believed RiffTheRaff's fix would help, but it didn’t. Instead, I received a clearer event viewer log than the usual generic shutdown message. A critical hardware fault has been detected. This report was submitted by the component: Processor Core Error. Source: Machine Check Exception. Error type: Cache Hierarchy Error. Processor APIC ID: 0. The full event details are attached here. I’ve searched the error description, and it appears others face similar problems—some have no issues temporarily but experience recurring crashes without a clear resolution. crash feb 1.7z
I've faced the same issue for over a year now, and no one seems to have a solution. That's likely why you're facing this situation. My error message reads: A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 29. The details show this has happened more than fifty times. For me, it's occurring consistently whenever the PC's power consumption is extremely low. So, during nights when I run my PC for tasks like saving to a NAS or performing scans, it happens only then. I don't overclock anything except the Auto OC on Ryzen master. For precise data: 5-10% CPU usage and 70% memory usage. (Running in VirtualBox) PC specs: 5950X (latest driver), 6950 XT (latest driver), 1000W Powersupply PowerZone Asus Dark Hero VIII (latest BIOS). It includes two 2x2x2x2 TB NVMe SSDs, one 1 TB SSD, and one 8 TB SSD. Running Windows 10 Pro with G.Skill 64GB/3600. Ripjaws CL16. I haven't encountered any AMD support or response, even though the message is everywhere online. This was the last time I bought an AMD product. I rely on my PC for work, but this unreliability is a major concern. I'm willing to accept a slower Intel if it means fewer random issues.
You couldn't initiate an RMA with AMD. After further investigation, that was the only viable option. The crashes appear to occur unpredictably, and your machine has remained stable for over 48 hours without any issues—provided the window position stayed consistent. These incidents don’t seem linked to gaming or heavy workloads. It’s unclear whether the problem lies with the motherboard or the CPU. At this stage, replacing either component might be your best course of action.