Restart Windows Bugcheck Fix
Restart Windows Bugcheck Fix
Hello everyone, I've noticed many discussions about this problem, yet I've tried most solutions and feel stuck. I'm encountering a situation where my monitors shut down while gaming, audio plays briefly, and then the PC restarts. In Event Viewer, I see an error: the system rebooted due to a bugcheck with ID 0x00000116. A dump was saved at C:\WINDOWS\MEMORY.DMP. When I opened it in WinDbg, it showed a VIDEO_TDR_FAILURE message and pointed to a driver issue. The log file indicated the problem came from a driver failure. I cleaned my Nvidia drivers and tried older stable versions, but the issue remained. After upgrading my PC for PSU and cooling problems, temperatures stayed normal. I limited FPS to 120 in games, but it still worked. I ran a memtest with no errors and replaced cables, yet the problem continued. I considered using DP1.0 ports and even tried different GPU ports, but nothing resolved it. I'm unsure if any recent changes or port issues caused this. The crashes seem random—sometimes after hours of play, other times not. They don't appear to happen while browsing. My next step is replacing the monitors, but I can't buy new ones right now. Could there be something missing? I'm hoping someone has faced a similar issue before, as I'm running out of options.
Hello, I'm going to give it a shot. I plan to disable Intel XeSS in the game as well—though I haven't noticed this causing problems before, but it's worth trying. I'll run some tests, but it takes time for the issue to appear, so results might not be immediate. I'll try both approaches and let you know what I find.
The most annoying crashes are the ones that rarely occur. If it only happens when under stress, it likely points to faulty hardware or lack of power. If you're willing to test: Use a LiveUSB of Linux Mint (which feels similar to Windows) to see if the issue persists, as Linux is quite sensitive to hardware problems. If it continues, the problem probably lies in software.
Hello Radium, thank you for your patience. The troubleshooting has been quite extensive due to timing issues, so here’s what I’ve tried recently: Set up Linux on a live USB, booted it, and experimented with it for some time without encountering any problems. It’s unclear whether I pushed too hard or if it would have failed immediately under stress, but no errors appeared. I turned off Intel Xeon overclock in the game, which didn’t stop the issue. I removed and reinstalled drivers via DDU, repositioned the GPU, updated the BIOS, and kept monitoring power and temperature—both stayed normal.
I also noticed a recurring BSOD linked to this bug, though I usually see it as black screens followed by restarts. In my case, it’s just a black screen that ends up restarting. It seems performance isn’t affected during crashes or while playing games. For context, the game causing the crashes is 'Judgement' on Steam, while 'Terraria' is a lighter title. I suspect the problem might be more related to 'Judgement' rather than the game itself, since others aren’t reporting the same issue.
In my next attempt, I’ll try disabling XMP settings—something that pops up during research about overclocking. I usually don’t overclock, but enabling XMP could help. I’ll also replace the PSU extension cables, as I’ve had some issues with them recently. A fresh Windows 10 install might be worth a shot too.
If none of these steps resolve it, I’ll likely wait until I can upgrade my monitors and GPU before continuing.
I've noticed XMP often creates more complications than it resolves... it's not worth risking unless you're comfortable reverting everything to the original BIOS settings and testing the outcome. I've seen discussions about these issues popping up. It's unclear exactly what caused them, but swapping them out resolved the user's problems. Still, it seems like a very unlikely solution before you go ahead and replace them. If you can, try moving your power supply closer to the components and connecting it directly without the extension cables, and observe the results.
So the latest update has shown me my GPU is likely failing. After checking everything else and noticing no performance drops or visual glitches, I’ve ruled out most possibilities. I’ve tried disabling XMP settings, ran an SFC/scan which fixed some problems but didn’t resolve the TDR crash, turned off hardware acceleration in Chrome, used different PSU cables instead of extensions, and even swapped out the power supply. New extensions helped a bit, and a fresh Windows install cleared disk errors. I’m also testing another PSU and noticed BIOS changes affecting system logs. It seems like the issue might be with the GPU itself. I’m pretty sure it’s time to wait until I can afford a replacement. Thanks for your help, Radium – this post should help others who face the same problem. I’ll share my full list of attempts later. Appreciate your time!
Drivers can become corrupted, but based on your explanation you reinstalled Windows (possibly with faulty drivers). 1) Anything above 60hz, you configured drivers for Enhanced Sync (AMD), Fast Sync (nVidia), and turned off V-Sync everywhere in every game. 2) If your monitor supports it, enable Freesync (AMD), G-Sync (nVidia), and ensure they're active in the drivers. 3) When setting FPS limits, cap them at the maximum vertical refresh rate. Regarding dump files, if you leave the pagefile disabled, it will cause a persistent error in the event viewer and block dump file creation; I left it off and had no problems.
Do you have an extra graphics card available for testing? It would definitely assist in confirming if the issue lies with the GPU.
Hey everyone, here’s another update. I followed your advice and set up two 144Hz monitors. I turned off V-sync/FPS limits in-game and switched to fast sync via the control panel. Sadly, the problem didn’t go away. Right now, I’m not seeing any improvement—I also attempted an RMA, but Gigabyte handled it through their vendor. When I reached out to Newegg, I learned they don’t accept international warranty claims; they only cover orders processed by them. That’s a lesson I should have noticed when ordering. I don’t have anyone with a gaming PC nearby for advice. I experimented with extra settings, like adjusting the TDR delay to see if the display would stabilize. Unfortunately, it didn’t. Now I’m encountering a new error before shutdown, which might be linked to the shorter TDR delay. The event description for ID 0 from nvlddmkm isn’t available—possibly the issue stems from an uninstalled component or a corrupted installation. You could try reinstalling or repairing it locally. I dug up some fixes online, but most people I found only dealt with CTDs, not full crashes and resets. I changed my approach: set the game to maximum performance mode in Nvidia’s settings, enabled debug mode, and reinstalled a much older driver (about a year back). After that, I checked the game more closely. Cyberpunk stood out because it was more demanding. It was on sale as a taxing title and DX12, which might have contributed to the new error I’m seeing. I managed to play it for about an hour without a crash, but I need to test longer to confirm.
I tried to figure out why Judgement didn’t show this issue at first—why it worsened over time, and why it kept coming back after a Windows reset. I considered a corrupted save file (it could have caused a full crash), but that didn’t help much. I looked at Steam discussions and noticed most crashes were CTDs, not system-wide failures. I’m planning to play more Cyberpunk, maybe extend sessions to see if the TDR restarts automatically. If it runs smoothly, I’ll focus on Judgement.
The good news was with Cyberpunk: it didn’t crash during my test today, but I’ll keep playing to be sure. If it still doesn’t work, I might need to upgrade hardware.