Could not identify the reason for the unexpected shutdown during startup.
Could not identify the reason for the unexpected shutdown during startup.
Thanks for sharing. It seems like the only remaining issue is a faint odor, possibly indicating the mobo isn’t fully replaced yet and could be the source. The remote failure is unlikely but not out of the question. I’d have expected it to appear earlier after upgrading from the 7800 XT to the 7800 XT model. Interestingly, after applying the furmark and prime treatment, the system still runs smoothly—CPU at 86°C, GPU hotspot around 90°C, and VRAM at 88°C. I ran a benchmark at 1440p with 60.000ms three times using prime95 since the first test, and everything looks stable.
It seems unusual. Could be short-lived surges. Should have a setting for both testing and benchmarking. These readings are normal and within limits—power virus files just put a lot of strain on the system. That’s not a typo, is it?
I’m still trying to understand these options better now. Regarding your question: yes, it’s a solid one, but I did switch my GPU recently. Update @OddOod : Keep it up! I ran it for about 30 minutes and it didn’t shut down. I’m even more puzzled about what caused this problem now. I just double-checked, and it shut down again after a short time in Expedition 33.
Check the Event Viewer summary for critical and error logs. We’ll skip the Kernel Power 41/43 events since they occur at startup. The most recent shutdown was marked as unclean.
Thanks, I'll handle it once I'm back at home. Let me update @OddOod: I've addressed the critical issue I mentioned before and saved all prior errors for today. Included the exported evtx file with the same selection. I can't replicate the exact screen you're seeing—can you locate that view in the event viewer? At this stage, I'm considering a full system wipe and reinstallation of Windows, games, drivers, etc., just to be safe. errors-and-critical-up-to-failure.evtx
The system logs indicate Windows didn’t power down before losing electricity. These details aren’t directly helpful. The distCOM messages resemble OneDrive notifications, possibly indicating a VBox issue. It might be a running service causing instability. TPM warnings could point to an unusual Windows installation, though likely not critical. A SFC/DISM scan may reveal a problematic USB device. Consider using minimal peripherals and inexpensive ones to avoid LED indicators. If the game is large, it probably isn’t the main issue. As a last resort, disable C-States in BIOS. To view the summary, open Event Viewer, select “Event Viewer (Local)” from the right pane, and wait for the Summary section to appear.
Thanks in advance! I noticed my first name is listed and I’m fine with that. Appreciate the guidance on accessing that view—I’ll share it once I’m back online. I’m aware of the limited storage, so I’ll free up some space from those development projects. Also planning to clean up without any USB drives as you recommended. Plus, I’ll try the full recovery for both my drives and Windows since there are strange setup errors.
I was checking to determine if there’s anything about lights on the MB after shutting it off. Play, crash, and remove the side if necessary—search the board thoroughly for any illumination. -Flashing lights might assist in identifying the issue. As you mentioned, this is the only component that hasn’t been replaced or tested.
Additionally performed the suggested SFC and DISM checks/repairs; it identified an issue that is now fixed. I’m planning a test run of Expedition 33 using only minimal USB devices and will provide an update. Appreciate your feedback—I haven’t initiated a new shutdown yet, but I’ll remember this when I do next time. I just ran Cinebench now; all metrics were normal and the program finished without interruption. ---- Update: Completely wiped all drives, reinstalled Windows 11, and managed to play Expedition 33 for an hour without any crashes. Hope everything stays stable. Thanks for your support!