LiveKernelEvent Code 117 — LiveKernelEvent 117 occurs during game or 3D activity. The visible error tells you what failed, not necessarily why. Possible branches include display driver recovers after timeout, graphics settings stress driver, and unstable hardware or power causes GPU reset. This guide separates those causes with safe observations before advanced diagnostics.
Symptoms and the first distinction
Treat an event code as evidence to correlate with symptoms, not proof that a specific hardware part must be replaced. Begin by copying the exact wording, product version, timestamp and operation being attempted. Note whether the problem is reproducible on one device, account, connection or file, or everywhere. That scope is usually more useful than searching only for the numeric code.
Do not change several unrelated settings together. The recommended starting sequence is: check reliability monitor timestamps, then compare 3d workload at default clocks. If the first observation isolates a cause, you can often skip the later branches.
Before making a change
Safety boundary: Do not increase TDR delays as first fix; it can hide instability. For any device, database, account or server containing valuable information, preserve a recovery path. Keep screenshots or redacted logs and write down each original setting. For account, payment and production-system incidents, check whether an earlier request already succeeded before repeating it.
Start with the following guided checks. The Beginner method uses reversible tests; the Advanced method is intended for administrators or users who have verified the affected subsystem.
Step-by-Step Troubleshooting
Begin with reversible checks and use advanced work only when the evidence identifies a specific cause. Record any settings you change.
Check Reliability Monitor timestamps
Check Reliability Monitor timestamps. This checkpoint investigates whether display driver recovers after timeout. First record the original symptom and current configuration so the comparison is meaningful. If the outcome changes on the controlled test, note precisely what changed and avoid proceeding to invasive repairs. If nothing changes, continue with: compare 3d workload at default clocks. Document the time and what the application, device or service reported.
Compare 3D workload at default clocks
Compare 3D workload at default clocks. This checkpoint investigates whether graphics settings stress driver. First record the original symptom and current configuration so the comparison is meaningful. If the outcome changes on the controlled test, note precisely what changed and avoid proceeding to invasive repairs. If nothing changes, continue with: disable overlay for one test. Document the time and what the application, device or service reported.
Disable overlay for one test
Disable overlay for one test. This checkpoint investigates whether unstable hardware or power causes GPU reset. First record the original symptom and current configuration so the comparison is meaningful. If the outcome changes on the controlled test, note precisely what changed and avoid proceeding to invasive repairs. If nothing changes, continue with: monitor temperature and gpu utilization. Document the time and what the application, device or service reported.
Monitor temperature and GPU utilization
Monitor temperature and GPU utilization. This checkpoint investigates whether display driver recovers after timeout. First record the original symptom and current configuration so the comparison is meaningful. If the outcome changes on the controlled test, note precisely what changed and avoid proceeding to invasive repairs. If nothing changes, continue with: check reliability monitor timestamps. Document the time and what the application, device or service reported.
Inspect display driver event logs and minidump
Inspect display driver event logs and minidump. Use this advanced path only after the basic results point toward graphics settings stress driver. Collect the exact log, setting, build number or hardware condition relevant to this action. Compare against a known working state where possible and apply the smallest approved change. If the observation does not support this branch, return to the previous settings instead of stacking more fixes. Retest liveKernelEvent 117 occurs during game or 3D activity using the same reproduction steps.
Get-WinEvent -LogName System -MaxEvents 25 | Select-Object TimeCreated, Id, ProviderNameTest signed driver rollback where relevant
Test signed driver rollback where relevant. Use this advanced path only after the basic results point toward unstable hardware or power causes GPU reset. Collect the exact log, setting, build number or hardware condition relevant to this action. Compare against a known working state where possible and apply the smallest approved change. If the observation does not support this branch, return to the previous settings instead of stacking more fixes. Retest liveKernelEvent 117 occurs during game or 3D activity using the same reproduction steps.
Compare PSU and power connectors with technician
Compare PSU and power connectors with technician. Use this advanced path only after the basic results point toward display driver recovers after timeout. Collect the exact log, setting, build number or hardware condition relevant to this action. Compare against a known working state where possible and apply the smallest approved change. If the observation does not support this branch, return to the previous settings instead of stacking more fixes. Retest liveKernelEvent 117 occurs during game or 3D activity using the same reproduction steps.
Run a short controlled graphics validation
Run a short controlled graphics validation. Use this advanced path only after the basic results point toward graphics settings stress driver. Collect the exact log, setting, build number or hardware condition relevant to this action. Compare against a known working state where possible and apply the smallest approved change. If the observation does not support this branch, return to the previous settings instead of stacking more fixes. Retest liveKernelEvent 117 occurs during game or 3D activity using the same reproduction steps.
Why this happens: interpret your findings
The same symptom can result from three different layers. Use the outcomes below to decide what needs attention rather than running every repair indiscriminately.
| Possible cause | How to distinguish it | Next direction |
|---|---|---|
| Display driver recovers after timeout | Check Reliability Monitor timestamps | Inspect display driver event logs and minidump |
| Graphics settings stress driver | Compare 3D workload at default clocks | Test signed driver rollback where relevant |
| Unstable hardware or power causes gpu reset | Disable overlay for one test | Compare PSU and power connectors with technician |
If the first row describes your result, address that specific component, permission, setting or request path; do not assume the other two are also faulty. When disable overlay for one test produces a different outcome, note what changed before performing compare psu and power connectors with technician. If none of the results match, re-check the exact version, endpoint, device model and full error text; it may be a different issue with a similar message.
How to verify the repair
The meaningful success condition is: 3D workload completes without display recovery event. Repeat the exact operation that originally failed rather than substituting a nearby health check. Check for fresh errors at the same timestamp; a green status indicator does not prove the original task is working.
Where safe, repeat the operation after one normal restart, reconnection or new session. If it fails again, compare the new result with the recorded baseline. Did the error text change? Did the failure move earlier or later in the process? Those observations determine whether to revisit display driver recovers after timeout or investigate the alternative path.
Rollback and escalation
If a test introduces a new failure, reverse the most recent change first. Do not increase TDR delays as first fix; it can hide instability. For persistent failures, provide the relevant vendor or system administrator with the exact version, sanitized logs, reproduction steps and the differences from your controlled checks. The most useful escalation evidence is often the result of inspect display driver event logs and minidump, not the original error message alone.
Solution Checklist
Frequently asked questions
Does LiveKernelEvent Code 117 always indicate the same underlying fault?
No. The reported symptom can be associated with display driver recovers after timeout, graphics settings stress driver, or unstable hardware or power causes GPU reset. A second controlled observation is needed before diagnosing a specific component or configuration.
Should I begin with the Advanced method?
Usually not. Begin with check reliability monitor timestamps because it helps establish a baseline. Advanced work such as test signed driver rollback where relevant can require elevated access, service disruption or a documented rollback plan.
What if the problem reappears after a restart?
Capture the fresh timestamp and repeat monitor temperature and gpu utilization. If the results differ from the first test, investigate the changed condition rather than repeating every earlier step. Preserve any work or data before escalation.
Official documentation and related guidance
For exact supported versions, hardware compatibility and vendor-approved recovery steps, consult Microsoft Windows debugging documentation. This is an official reference starting point; it is not a claim that the vendor confirmed each diagnostic branch for every model or version.
Explore additional Diagnostics solutions on PRBLEM. If a different error appears, identify its own code and reproduction steps before following another article.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.