Diagnose GPU crashes and driver timeouts that might be ruining your Fortnite sessions
Created by Fjord ๐
- What Is This?
- Features
- Quick Start
- Menu Options
- What Gets Scanned
- Understanding Results
- Discord Integration
- Troubleshooting
- Requirements
Ever had Fortnite crash with no clear reason? This tool digs deep into Windows Event Viewer to find GPU driver crashes, TDR (Timeout Detection and Recovery) events, and other graphics-related errors that might be the culprit.
Instead of manually combing through thousands of system events, this PowerShell script does the heavy lifting for you and generates a clean, readable report.
- ๐ Automated Event Log Scanning - Searches System and Application logs for GPU-related crashes
- ๐ Detailed Reports - Generates timestamped reports with crash summaries and event details
- ๐ฏ Smart Detection - Finds TDR events, NVIDIA/AMD driver crashes, LiveKernelEvents, and more
- ๐ Flexible Date Range - Search anywhere from 1-30 days back
- ๐ Interactive Menu - User-friendly interface with multiple options
- ๐พ Auto-Save - Reports saved to
Documents\GPU-Crash-Logs\ - ๐ Discord Webhook Integration - Optionally share your report with support teams via Discord
- ๐ File Attachments - Full reports sent as downloadable
.txtfiles - ๐ก๏ธ Admin Detection - Automatically elevates to administrator for full event access
- ๐ Crash Statistics - View crash counts by date and event type
- Double-click
Run-GPU-Crash-Checker.bat - Choose Option 1 to search for GPU crashes
- Enter how many days back to search (e.g.,
7for the last week) - Review results on-screen
- A folder opens automatically with your detailed report
- Right-click
GPU-Crash-Checker.ps1 - Select "Run with PowerShell" (or "Run as Administrator" for best results)
- Follow the interactive menu
Scans Windows Event Viewer for crash events over your chosen time period.
What happens:
- Prompts you to select how many days back to search (1-30)
- Asks if you want to share the report via Discord (optional)
- Scans System and Application logs
- Displays results in real-time
- Saves a detailed report with timestamps, event IDs, and messages
- Opens the output folder automatically
Educational screen explaining:
- What TDR (Timeout Detection and Recovery) means
- Common TDR Event IDs (4101, 117, 141)
- Typical causes (overheating, overclocking, driver issues, etc.)
Close the program cleanly.
The script searches for these specific issues:
| Category | What It Finds |
|---|---|
| ๐ข NVIDIA Crashes | nvlddmkm stopped responding events |
| ๐ด AMD Crashes | amdkmdag stopped responding events |
| Timeout Detection and Recovery (Event IDs 4101, 117, 141) | |
| ๐ฅ LiveKernelEvents | Critical kernel-level GPU errors |
| ๐ฎ Fortnite Crashes | Application errors related to Fortnite or D3D |
| โฑ๏ธ Display Driver Timeouts | Generic display driver timeout messages |
Good news! Event Viewer shows no driver resets or TDR events.
If Fortnite is still crashing, the issue might be:
- ๐ Game-specific bug - Check for Fortnite updates
- ๐ฅ Overheating - Monitor GPU temps with MSI Afterburner or HWiNFO
- โก Overclocking instability - Revert GPU/CPU to stock clocks
- ๐ Power supply issues - Check PSU wattage and cable connections
- ๐ฟ Corrupted game files - Verify game files in Epic Games Launcher
Warning! Windows detected your GPU driver stopped responding and attempted recovery.
-
๐ฅ GPU Overheating
- Monitor temps while gaming (should be under 80-85ยฐC)
- Clean dust from GPU fans and heatsink
- Improve case airflow
-
โก Unstable Overclock
- Reduce GPU core and memory clocks to stock
- Use MSI Afterburner or EVGA Precision to adjust
- Test stability with 3DMark or Heaven Benchmark
-
๐ Outdated or Corrupt Drivers
- Update to latest GPU drivers (NVIDIA GeForce Experience / AMD Software)
- Consider clean install with DDU (Display Driver Uninstaller)
-
๐ Insufficient Power Supply
- Ensure PSU meets GPU power requirements
- Check all PCIe power cables are firmly connected
- Test with a known-good PSU if possible
-
๐ ๏ธ Faulty Hardware
- GPU may be defective
- Try GPU in another system or try another GPU in your system
- Contact manufacturer about RMA if under warranty
When you run a GPU crash scan, the script offers to share your report with Fjord via Discord. This is completely optional and helps improve the tool while potentially getting you direct support.
-
๐ Summary Message (visible in Discord):
- Computer name and OS version
- Total number of crashes found
- TDR detection status
- Most common Event IDs
- Latest crash timestamp
-
๐ Full Report Attachment (downloadable
.txtfile):- Complete event log details
- All crash messages and timestamps
- Crash summary by date
- โ You're asked before every upload (opt-in)
- โ Only includes: computer name, OS info, and event logs
- โ No personal data, usernames, or file paths are shared
- ๐พ Reports are always saved locally regardless of Discord choice
- Uses Discord webhooks (no bot required)
- Sends via
curl.exe(included in Windows 10 1803+) - Falls back to summary-only if
curl.exeunavailable - File size limit: 25MB (typical reports are <100KB)
Solution 1 (Easiest):
Use the .bat file instead of running the .ps1 directly.
Solution 2 (Advanced):
- Right-click PowerShell โ Run as Administrator
- Run this command:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
- Then run the script
Try these steps:
- Verify game files in Epic Games Launcher
- Check GPU temps with HWiNFO64 or MSI Afterburner while gaming
- Update Windows and GPU drivers to latest versions
- Test other games - if they crash too, it's likely hardware/driver related
- Check RAM with Windows Memory Diagnostic or MemTest86
C:\Users\[YourName]\Documents\GPU-Crash-Logs\
Each run creates a new timestamped file:
GPU-Crash-Report_2026-01-09_14-30-45.txt
Possible causes:
- Firewall blocking
curl.exe - No internet connection
- Discord webhook URL changed/expired
Your report is still saved locally! You can:
- Manually upload the
.txtfile to Discord - Share it in support forums
- Email it to support teams
| Requirement | Details | |-------------|---------|| | ๐ฅ๏ธ Operating System | Windows 10 (1803+) or Windows 11 | | โ๏ธ PowerShell | Version 5.1+ (included with Windows) | | ๐ Permissions | Administrator recommended (auto-elevates if needed) | | ๐ Internet | Optional (only for Discord webhook feature) | | ๐พ Disk Space | Minimal (~1MB for reports) |
- โ Run as Administrator for access to all event logs
- โ Check logs soon after a crash for most relevant data
- โ Search 7-14 days for pattern detection
- โ Keep reports to track crash frequency over time
- โ Share reports with support communities for faster diagnosis
This project is licensed under the MIT License - feel free to use, modify, and distribute.
Created by Fjord ๐
Special thanks to the TAU Discord community for testing and feedback, and to Tony's computer for crashing enough to motivate me to write this! ;)
Need help? Found a bug? Have suggestions?
- ๐ฌ Join the TAU Discord: https://discord.gg/FM5gvVNSRQ
- ๐ง Share your crash reports when asking for help
- ๐ Report issues on GitHub (if applicable)
Happy gaming! May your frames be high and your crashes be low. ๐ฎโจ