The Pattern Is the Clue

When software crashes unexpectedly, the pattern of crashes tells you more than the crash itself. Does one specific app crash while everything else runs fine? Do crashes happen in multiple apps? Does the crash occur only when doing a specific action, or randomly during normal use? Answering these questions points directly to the most likely cause.

When One App Keeps Crashing

If a single application crashes repeatedly while others run normally, the problem is almost certainly within that app's software, not your hardware.

Standard Fix Protocol

  1. Update the application. Crashes are frequently caused by bugs that have already been fixed. Check for updates within the app or the developer's website.
  2. Update your OS. Some apps depend on OS-level libraries that were updated. Running macOS or Windows behind on updates can cause crashes in newer apps.
  3. Clear the app's cache. On Windows: %AppData%\[AppName] — look for a "cache" folder and delete it. On Mac: ~/Library/Caches/[BundleID].
  4. Delete preferences/settings file. On Mac: ~/Library/Preferences/[com.developer.app].plist. This resets the app to defaults and fixes crashes caused by corrupt settings.
  5. Clean reinstall. Uninstall completely (including leftover folders), reboot, download a fresh installer, install fresh.
  6. Test in a new user account. Create a test user account on your machine and run the app there. If it runs fine, the crash is caused by something in your user profile (a corrupt preference file or a conflicting background process).

When Multiple Apps Are Crashing

Crashes spread across different applications point to a shared underlying problem — usually hardware.

  • RAM: Faulty RAM causes random crashes in any application that uses the affected memory region. Run MemTest86 overnight — any errors confirm bad RAM that needs replacement.
  • Failing hard drive: A drive with bad sectors causes application crashes when the OS reads executable or library files from the damaged area. Check drive health with CrystalDiskInfo (Windows) or Disk Utility (Mac).
  • Overheating: Thermal throttling and shutdowns during crashes, especially after 20–30 minutes of use, point to a cooling problem. Check temperatures with HWMonitor or iStatMenus.
  • Driver conflict: A recently installed or updated driver corrupting memory. Check Device Manager for warning icons and review recently updated drivers in Windows Update history.

Reading Crash Logs

Windows — Event Viewer

  1. Press Win+R → type eventvwr.msc → OK.
  2. Expand Windows Logs → Application.
  3. Find Error entries at the time of the crash.
  4. Look for the "Faulting module name" — this tells you exactly which DLL or component caused the crash.

Mac — Console.app

  1. Open Spotlight → type "Console" → open Console.app.
  2. Select "Crash Reports" in the left sidebar.
  3. Find the report for your crashing application.
  4. Look at "Exception Type" and "Thread 0 Crashed" for the fault location.

The "faulting module" is your best lead. If Event Viewer shows a crash in nvlddmkm.sys, that's an NVIDIA GPU driver. ntfs.sys points to a disk issue. ntdll.dll is usually RAM. Each module name has a well-known meaning that guides the fix.

When Hardware Diagnosis Is Needed

If crashes continue after app reinstalls and OS updates, or if Event Viewer points to hardware-level faults (RAM, disk, GPU), bring the machine in. We run MemTest86, CrystalDiskInfo, GPU stress tests, and thermal analysis to identify the hardware component responsible.

Free hardware diagnostics. We run a full hardware battery test — RAM, drive, GPU, thermals — at no charge. If a hardware component is causing your crashes, we'll identify it and give you a repair estimate before any work begins.