Perform a full factory reset on Windows and ensure no system logs are retained.
Perform a full factory reset on Windows and ensure no system logs are retained.
I was using Train Sim World on my PC when a sudden buzzing sound came from the speakers, followed by a freeze, a black screen, and then the system restarted automatically. After that, I booted directly without encountering any BSOD. I checked Event Viewer (filtering for Error or higher in Windows Logs since the crash) and found entries indicating recurring Intel Graphics Software App errors 220 and 221 on every startup, not just after a failure. These logs show issues even before the crash. I’ve also reviewed the Intel.GraphicsSoftware.App logs, which display an error message at 21:31:04 related to firmware problems. The system rebooted cleanly without a full shutdown. This pattern suggests a persistent issue that could stem from hardware or software instability. I ran a SFC scan and confirmed no integrity issues with Windows Resource Protection. A CHKDSK check on both my PC and storage found no errors. Memtest86 completed successfully, and there are no dump files in the expected directory. This marks my first such incident. Recently, I upgraded from an integrated graphics card to a discrete one, and I have the following specifications: CPU: AMD Ryzen 5 8600G, Motherboard: ASUS PRIME B650M-R, GPU: Acer Nitro OC, Intel Arc B580, RAM: 2 x 16GB Corsair Vengeance DDR5-6000, Power Supply: Gigabyte UD750GM PG5 750W. Storage: 500GB Kingston NV3 and 500GB Crucial P3 Plus. The PSU should be well above recommended power needs, even accounting for spikes. I’ve been playing Train Sim World on this system for about two weeks, alongside other titles, and this is the first time something like this happened. Previously, crashes in Train Sim World only generated an Unreal Engine traceback without a black screen. Any assistance would be greatly appreciated—feel free to share logs if you have them. EDIT: I also noted that with gaming and Folding@Home running, temperatures stayed stable around 54°C, and no crashes occurred. This stress testing has helped confirm the hardware’s reliability under load.)
From gut feeling and past encounters, ChatGPT agrees but adds that the power supply is also likely faulty. My understanding of this configuration: Arc A580 paired with an AMD Ryzen setup is known for stability issues, particularly with older BIOS/AGESA versions. The Gigabyte UD750GM PG5 PSU has a history of early failures under sudden GPU demands. Even if it’s a newer revision, it remains less dependable. Intel driver warnings strongly suggest the GPU or driver crashes just before failure. Possible actions: upgrade BIOS (ASUS PRIME B650M-R) to the latest version—Arc performance improves significantly with AGESA 1.1.0.x. Update Intel Arc drivers to the newest WHQL. Inspect the PSU (if it’s an older model of UD750GM, replacing it could help). Use Event Viewer → System and Reliability Monitor near crash time to detect extra WHEA errors or “Display driver stopped.” Turn on minidumps if not already enabled so future crashes may record more data. Based on the logs, I’d prioritize Arc driver/firmware problems first, then consider the PSU.
It's a severe impact, so no records would be created for analyzing the root cause. Now you just need to check your parts actively to confirm they function as intended (based on power supply specs).
The BIOS is already version 1.2.0.x AGESA. They are currently the most recent drivers available. I don’t need another power supply unit to test with, and I wouldn’t want to purchase one unless absolutely necessary. 4 + 5. As mentioned, there are no additional logs. When I pushed my CPU and GPU under stress, everything functioned properly. Also, since I frequently run Folding@home—using both GPU and CPU at full capacity—it hasn’t caused any crashes or unusual behavior. I could get another PSU if that’s the only possible reason, but I’m puzzled by this situation given the consistent performance during tests.
This appears to be an isolated incident. Diagnosing non-recurring crashes can be challenging. From what I understand, a crash dump is typically produced during the BSOD event. A severe crash usually results in such a dump.
The PSU doesn't seem to be the main problem since the GPU draws less than 200W under PPT. The likely cause is probably an incompatibility or bug between Intel drivers and certain games. You might want to check earlier versions to see if it worked before, or wait for updates. Stress tests aren't very reliable for stability because each program uses the GPU differently depending on its graphics engine and API. I can adjust my GPU voltage significantly and still get good results in stress tests, but it crashes in some games, so I had to lower it.
Folding relies on GPU in a different way than playing games. Coming from someone who managed numerous mining rigs, I often performed memory tuning on my GPUs, which would cause crashes if used for gaming. However, for mining or folding tasks it remained stable. This suggests there might be an issue specific to your new dedicated GPU and your AMD setup. It seems the power supply isn’t the main problem—your system is well within its limits. Unfortunately, I haven’t worked much with Intel GPUs, so I can offer little insight. I hope you resolve this. You might also test different driver versions on the GPU.
View the Details section for Kernel-Power Event ID 41. The 6008 entries are essentially the same as Event 41, but they occur during the crash itself. Therefore, 6008 crashes typically lack valuable information.
Yeah, but I've been running games for the past few days and it hasn't had anything like this before. Image form: Spoiler Text form: Spoiler System - Provider [ Name ] Microsoft-Windows-Kernel-Power [ Guid ] {331c3b3a-2005-44c2-ac5e-77220c37d6b4} EventID 41 Version 10 Level 1 Task 63 Opcode 0 Keywords 0x8000400000000002 - TimeCreated [ SystemTime ] 2025-09-01T20:30:07.3714873Z EventRecordID 23653 Correlation - Execution [ ProcessID ] 4 [ ThreadID ] 8 Channel System Computer NoctuaRedux - Security [ UserID ] S-1-5-18 - EventData BugcheckCode 0 BugcheckParameter1 0x0 BugcheckParameter2 0x0 BugcheckParameter3 0x0 BugcheckParameter4 0x0 SleepInProgress 0 PowerButtonTimestamp 0 BootAppStatus 0 Checkpoint 16 ConnectedStandbyInProgress false SystemSleepTransitionsToOn 1 CsEntryScenarioInstanceId 2 BugcheckInfoFromEFI false CheckpointStatus 0 CsEntryScenarioInstanceIdV2 2 LongPowerButtonPressDetected false LidReliability false InputSuppressionState 0 PowerButtonSuppressionState 0 LidState 3 WHEABootErrorCount 0