Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
LiveKernelEvent Code 117 means Windows detected a graphics-processing timeout. The GPU or display driver stopped responding quickly enough, so Windows attempted to reset the graphics stack. It is a warning to investigate—not proof that your graphics card is defective. Driver problems, unstable tuning, overheating, power delivery, RAM, firmware, and the GPU itself can all be involved.
Start by recording when the event occurs, then return hardware settings to stock and troubleshoot drivers, workload, temperatures, and power in that order. Avoid registry “fixes” that merely extend the timeout before you know why the graphics stack is hanging.
What LiveKernelEvent Code 117 means
Windows uses Timeout Detection and Recovery (TDR) to respond when the graphics processing unit (GPU) or its driver stops responding. A graphics task runs too long or cannot be preempted; Windows detects the timeout and asks the display driver to reset the GPU. It then tries to reinitialize the graphics stack so the desktop can recover. The default timeout is about two seconds. Microsoft’s TDR documentation describes the detection and recovery process.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe corresponding Windows condition is VIDEO_TDR_TIMEOUT_DETECTED, value 0x117. Microsoft identifies 0x117 as a live-dump code, not a conventional bug-check code in itself. A LiveKernelEvent can therefore appear in Reliability Monitor even when Windows recovers without showing a blue screen. Repeated hangs and unsuccessful recovery can lead to a more serious system crash.
#1 Best Overall
- Powered by Radeon RX 9070 XT
- WINDFORCE Cooling System
- Hawk Fan
- Server-grade Thermal Conductive Gel
- RGB Lighting
Do not confuse 0x117 with VIDEO_TDR_FAILURE, bug check 0x116. The former reports a timeout/live dump; the latter means Windows failed to recover from a display-driver timeout. Neither code alone identifies the faulty component. Microsoft lists possible contributors including drivers, overclocking, memory settings, cooling, power, compatibility, and defective hardware in its Code 117 reference.
Reliability Monitor may label the event a “hardware error.” That wording is a category for the reported failure, not a verdict that a physical part has failed. The cause can be software, firmware, hardware, or power-related.
Confirm what happened and look for a pattern
- Press Start, search for View reliability history, and open Reliability Monitor. You can also run
perfmon /rel. - Select the red failure marker at the relevant time, then choose View technical details.
- Record the Problem Event Name, code, bucket ID, operating-system build, and any driver or module names shown.
- Note what you were doing: gaming, video playback, browsing, waking from sleep, using an external monitor, or sitting at the desktop.
Open Event Viewer with eventvwr.msc and inspect the System log around the same timestamp. Look for display-driver events, WHEA-Logger hardware reports, or Kernel-Power events. A Kernel-Power entry often records an unexpected shutdown; by itself it does not explain what caused it. Use dxdiag to identify display adapters and driver versions, and msinfo32 to record system details. Microsoft’s Windows crash troubleshooting guidance also recommends reviewing diagnostic information and system logs.
A single isolated event followed by normal operation is different from repeated black screens or crashes. One event may be a transient driver or application failure. Recurrence across games, browser use, or idle operation deserves a more systematic investigation.
Troubleshoot in the safest order
Change one thing at a time and keep notes. If several settings change at once, you will not know which one affected the result.
1. Return tuning to stock
Temporarily disable GPU overclocking or undervolting, custom GPU fan curves, CPU overclocking, and aggressive motherboard performance modes. Return XMP/EXPO or other memory profiles to default for testing, too. Close third-party tuning utilities. A factory-overclocked card can also be unstable at its shipped settings, even if you never applied a manual overclock.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
If the events stop at stock settings and return when a profile is enabled, that profile is unstable on your system—even if it passed a short benchmark. Keep the stock configuration while testing other causes.
2. Check for a driver regression or conflict
Identify the GPU in Device Manager > Display adapters (open it with devmgmt.msc) or run dxdiag. Download graphics drivers from the GPU maker or, on a laptop or prebuilt system, the computer manufacturer:
If Code 117 began immediately after a driver change, first try Device Manager > Display adapters > [GPU] > Properties > Driver > Roll Back Driver, if the button is available. Otherwise, test a known-good earlier release from the manufacturer. Do not assume the newest or oldest driver is always best. NVIDIA’s Game Ready and Studio branches suit different workloads; neither is universally the more stable choice.
For a clean reinstall, download the intended official driver first. If Windows keeps replacing it during troubleshooting, temporarily disconnect from the internet, then remove the existing graphics package using an appropriate removal procedure, reboot, and install the downloaded driver. Test before reinstalling optional companion software, overlays, recording tools, or tuning utilities. Third-party driver-removal tools are optional, not Microsoft tools, and should be used carefully; they are not automatically necessary or risk-free.
Laptops with hybrid graphics may depend on both the integrated and discrete GPU drivers, chipset software, BIOS, and manufacturer power-management components. If a generic package causes trouble, test the laptop maker’s recommended driver set rather than updating only the discrete GPU.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Isolate the workload and display path
If one game triggers the event, temporarily turn off overlays and recording features, verify the game’s files, lower graphics settings, cap the frame rate, or try another graphics API if the game offers one. These are diagnostic tests, not guaranteed permanent fixes. If the problem occurs during browsing or video playback, turn off browser hardware acceleration temporarily and see whether the pattern changes.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
If it happens only with an external display, test a direct connection with another cable or port and, where practical, remove the dock, adapter, or converter. High refresh rates, HDR, multiple monitors, USB-C docks, and sleep/wake transitions can all change the graphics path. If possible, compare with the laptop’s internal display or one direct monitor.
4. Check temperatures and cooling under the conditions that trigger it
Observe temperatures while reproducing the problem, not only at idle. Record GPU core, hotspot or junction, and VRAM temperatures when those sensors are available, along with fan speed, clocks, power draw, and CPU temperature. Watch for rapid spikes, abnormal fan behavior, thermal throttling, or shutdowns. There is no single safe temperature threshold that applies to every GPU; compare readings with the specific model’s manufacturer specifications.
Check for dust in filters, fans, and heatsinks, confirm that GPU fans spin, and make sure laptop vents are not blocked. Improve case airflow if needed. If you suspect a desktop GPU is poorly seated or sagging, shut the PC down, disconnect power, and follow safe handling guidance before inspecting it. Avoid opening a laptop or replacing thermal materials unless you are qualified and have considered warranty implications.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall5. Check power and connections
For a desktop, compare the PSU with the GPU maker’s requirements and inspect the card’s power connections. Follow the PSU and GPU instructions for cable use; some high-power cards call for separate PSU cables rather than multiple connectors fed by one cable. Make sure adapters are fully inserted and not sharply bent close to the connector. Shut down and unplug the system before reseating a card or cable, and do not use cheap or unverified adapters.
A PSU wattage label that appears adequate does not clear the power supply. Aging, connector condition, transient-load handling, and system compatibility can still matter. A known-good PSU substitution can be a more useful diagnostic than judging wattage alone.
On a laptop, test with the correct original charger, check whether the fault differs on battery versus AC power, and temporarily remove a dock or USB-C power path if practical. Check the manufacturer’s power mode and confirm that any charger or dock meets the laptop’s requirements.
Rank #4
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
6. Update Windows and platform software carefully
Install pending Windows updates and the appropriate chipset driver. Check the system or motherboard manufacturer for BIOS and firmware updates, especially if the GPU was recently replaced or the issue began around sleep/wake, hybrid graphics, PCIe compatibility, or power-management changes. A BIOS update is not a guaranteed Code 117 fix. Follow the manufacturer’s instructions and proceed only with stable power.
Recommended Free Tools
Test system memory and hardware methodically
Graphics workloads also exercise RAM, the CPU, PCIe connection, and power delivery. If XMP/EXPO is enabled, test at default memory settings. Run Windows Memory Diagnostic or a bootable memory tester such as MemTest86; its free edition is available for basic checks. If a test reports errors, address memory stability before treating the problem as solely a graphics-driver issue. Return memory settings to default, then consider testing one module at a time and using the motherboard’s recommended slots, following the vendors’ guidance.
Compare behavior across workloads: one game points toward a game/API/overlay interaction; several games raise suspicion of a broader driver, GPU, thermal, or power issue; browser playback or desktop idle suggests hardware acceleration, low-power transitions, or hybrid graphics should also be examined. Crashes before Windows loads or during firmware diagnostics make hardware or firmware more likely.
The strongest practical isolation often comes from substitution: test the suspect GPU in a known-good system, try a known-good compatible GPU in the affected computer, or test with a known-good PSU. Integrated graphics can help isolate the discrete card if the CPU and motherboard support it. A stress test that passes does not certify a GPU: different tests exercise different parts of the card and system, and a short test may miss heat-soak failures that appear after hours.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Read dumps only when the basics do not resolve it
For advanced diagnosis, collect the Reliability Monitor details, Event Viewer entries around the event, driver versions, temperature and clock logs, and any live-kernel or crash dump that exists. Microsoft’s WinDbg documentation describes installation and dump analysis. On supported Windows systems, install it with:
winget install Microsoft.WinDbgFor a conventional crash dump, commands such as these can show context about the implicated graphics module:
Best Value
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
!analyze -v
lmvm nvlddmkm
lmvm amdkmdag
lmvm igdkmdnA name such as dxgkrnl.sys, dxgmms2.sys, nvlddmkm.sys, or amdkmdag.sys indicates a component in the graphics path, not necessarily the original cause. Dump attribution often points to where the failure surfaced. Share logs or dumps with the computer or GPU manufacturer if you need support; remove personal information where appropriate.
Should you change TdrDelay in the Registry?
Usually not. Changing TdrDelay changes how long Windows waits before declaring a graphics timeout; it does not repair an unstable GPU, bad driver, overheating, or inadequate power. A longer wait can make a freeze last longer and obscure the cause. It is not a standard first-line repair.
If an advanced user experiments with it for a specific diagnostic reason, back up the Registry or create a restore point first, make only a deliberate temporary change, and revert it after testing. Do not treat a disappearing event as proof that the underlying instability is fixed.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Use the symptoms to choose the next test
| Pattern | Possible direction | Useful next test |
|---|---|---|
| Started after a driver update | Driver regression or installation conflict | Roll back or clean-install a known-good vendor driver. |
| Only one game fails | Game, graphics API, overlay, or driver interaction | Disable overlays; lower settings or try another API if available. |
| Black screen under load | Driver, GPU, thermal, or power instability | Return tuning to stock; monitor temperatures; inspect power connections. |
| Crashes at idle, in a browser, or during video | Hardware acceleration, hybrid graphics, or power-state transition | Test with acceleration disabled and a direct display connection. |
| Artifacts appear before the crash | GPU/VRAM, thermal, or power problem becomes more concerning | Stop repeated stress testing and arrange a known-good GPU/system comparison. |
| Code 117 with WHEA errors | Hardware, PCIe, power, or firmware issue may be involved | Review WHEA details and test components or connections systematically. |
| Stable only after disabling XMP/EXPO | Memory or memory-controller instability | Test RAM at default settings before resuming graphics troubleshooting. |
When hardware repair or replacement becomes more likely
Hardware or power deserves stronger suspicion when the failure recurs at stock settings across several applications, survives a clean driver install, and appears alongside artifacting, WHEA hardware errors, abnormal temperatures, or shutdowns. Evidence is stronger still if the GPU fails in another known-good system, or a known-good GPU works in the affected system. If a different PSU changes the result, investigate the power path rather than replacing the graphics card by assumption.
If the GPU remains stable after a driver rollback or disabling one application feature, software is more plausible. If it fails reproducibly across independent workloads and systems, stop cycling through arbitrary drivers and seek repair or warranty service. Back up important files before further testing. Microsoft’s general guidance for recurring Windows crashes likewise emphasizes working through drivers and system diagnostics rather than guessing at a single cause.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
