PC / Application crash and general Windows Debugging Guide

The Academy - Players helping Players
1

No need to do fancy downloads and pay for software, Windows already offers all tools internally. This is especially handy to figure out that you most likely missed a driver/software update causing your War Thunder to crash.

Windows Event Viewer :

Windows Logs > Application/System > Scroll & Look For errors. Disregard Warnings

Application Logs

  • These logs contain events logged by applications or software programs installed on your system.
  • Examples of events include application crashes, errors in specific software, or custom application logs (e.g., Microsoft Office, Adobe software).
  • Sources: These events are generated by the applications themselves and are generally used for troubleshooting software-specific issues.

System Logs

  • These logs contain events generated by the Windows operating system and its built-in services.
  • Examples of events include driver failures, hardware issues, Windows Update processes, or service start/stop messages.
  • Sources: These events are created by core system components, such as device drivers or system services, and are crucial for diagnosing operating system-level problems.

Event 1

Find error recent to time of crash and look at the reason of crash, related exit code, the exit code usually starts with 0x000. With that look at the event ID. Combining these two in a Google Search will usually give a clear indication of what is wrong.

Event 2
Event 21361×942 69.6 KB

Example :
Event 3

!!NOTE!! - This specific Event ID was brute forced to force crash War Thunder for screenshot purposes.

Device Manager :

Device Manager shows all installed hardware to your system. A very handy tool to have a check on a faulty or corrupt driver or external hardware not being detected by your PC.

1. Open Device Manager

  • Press Windows Key + X and select Device Manager from the menu, or search for it in the Start menu.

2. Look for Warning Signs

  • Yellow Triangle with Exclamation Mark: Indicates a problem with a device, such as a driver issue or hardware conflict.
  • Red X: The device is disabled or not functioning properly.

3. Device Status

  • Right-click on the device with a warning symbol and select Properties.
  • Under the General tab, check the Device Status. This will often provide an error code or description of the issue.

4. Common Error Codes

  • Code 10: Device cannot start.
  • Code 43: Windows stopped this device because it reported problems.
  • Code 28: The drivers for this device are not installed.

5. Update or Rollback Driver

  • Update Driver: Right-click the problematic device, select Update Driver, and choose whether to search automatically or browse for a driver.
  • Rollback Driver: If a recent driver update caused the issue, go to Properties > Driver tab and click Rollback Driver to revert to the previous version.

6. Disable/Enable the Device

  • Disabling and re-enabling a device can help restart or refresh the connection.
  • Right-click on the device and select Disable Device. Wait for a few seconds, then right-click again and select Enable Device.

7. Uninstall and Reinstall the Device

  • Uninstall: Right-click on the device and select Uninstall Device. This removes the device from your system.
  • After rebooting, Windows will attempt to automatically reinstall the necessary drivers.

8. Check for Hardware Changes

  • Right-click in the Device Manager window and select Scan for hardware changes to force Windows to re-detect connected devices.

9. Troubleshoot Compatibility

  • If a device is incompatible with the version of Windows you’re using, try checking the manufacturer’s website for compatibility fixes or alternative drivers.

Device

Rule of Thumb If something breaks, check for updates.

BSoD - Fatal crash to system restart

1. Hardware Issues

  • Faulty RAM: Memory issues can lead to data corruption, which causes system crashes.
  • Failing Hard Drive: A failing or corrupt hard drive can result in read/write errors or corrupted system files, leading to a BSoD.
  • Overheating: Excessive heat due to cooling failure can damage internal components, especially the CPU or GPU.
  • Defective Power Supply: Inconsistent or insufficient power supply can cause system instability.
  • Hardware Incompatibility: Newly installed hardware (e.g., a new graphics card) that is incompatible with the system may cause crashes.

2. Driver Issues

  • Corrupted or Outdated Drivers: Faulty device drivers, especially for critical components like the graphics card, can lead to BSoDs.
  • Incompatible Drivers: Installing drivers that are incompatible with your version of Windows can result in crashes.
  • Driver Conflicts: Multiple drivers trying to control the same hardware can create conflicts, leading to instability.

3. Software Issues

  • Corrupt System Files: Damaged or missing Windows system files can prevent the OS from functioning correctly, causing BSoDs.
  • Faulty Windows Updates: Sometimes, a bad or interrupted update can cause instability or system file corruption.
  • Misconfigured Software: Software or application installations that alter system settings incorrectly can result in system crashes.
  • Malware and Viruses: Malware that targets system files or hardware drivers can cause critical errors that result in a BSoD.

4. Overclocking

  • Overclocking Components: Overclocking the CPU, GPU, or RAM can push components beyond their stable limits, causing crashes and a BSoD.
  • Voltage/Power Issues: Incorrect voltage settings during overclocking may lead to system instability.

5. BIOS or Firmware Issues

  • Outdated BIOS: An outdated or corrupt BIOS/UEFI firmware can cause incompatibility issues, especially after a hardware upgrade.
  • Misconfigured BIOS Settings: Incorrect BIOS settings, such as improper boot order, memory timings, or CPU settings, can cause instability.

6. Software Bugs and Third-Party Applications

  • Bad Software Updates: Sometimes, software updates, especially for critical applications, can introduce bugs that lead to system crashes.
  • Incompatible or Faulty Programs: Installing poorly coded or incompatible software may lead to a BSoD.

7. System Resource Conflicts

  • IRQ Conflicts: Interrupt Request Line (IRQ) conflicts occur when two devices share the same hardware resource, causing a system crash.

8. Low Disk Space

  • Insufficient Storage: Low disk space on the system partition can lead to crashes, especially when virtual memory or paging files cannot expand.

Common Error Codes on BSoD

  • 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED): Often related to hardware or driver issues.
  • 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA): Can be caused by faulty hardware (RAM), or sometimes antivirus programs.
  • 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL): Typically caused by driver issues.
  • 0x0000001A (MEMORY_MANAGEMENT): Indicates a problem with system memory, such as faulty RAM or a hardware driver issue.

How to Troubleshoot BSoD

  1. Check the Error Code: The BSoD screen typically shows an error code that can help you identify the cause of the crash.
  2. Check Event Viewer: After rebooting, use Event Viewer to analyze the crash logs under Windows Logs > System for more details on what caused the BSoD.
  3. Update Drivers: Ensure that all your device drivers are up-to-date, especially for critical components like the GPU and motherboard.
  4. Run Hardware Diagnostics: Test your RAM and hard drive using built-in tools like Windows Memory Diagnostic or chkdsk to identify hardware failures.
  5. Check for Malware: Run a full system scan using a reputable antivirus tool to rule out malware as a cause.
  6. Perform System Restore: If a recent update or installation caused the BSoD, rolling back to a previous system restore point might resolve the issue.
  7. Check for Overheating: Use temperature monitoring software to ensure that your CPU and GPU are not overheating. Task Manager has a temperature readout for your GPU, your Motherboard Software usually gives a temperature readout for your CPU.