Windows 11 BSODs, freezing and crashes, works fine in safe mode.

Understanding and Troubleshooting Windows 11 Blue Screen and System Instability: A Step-by-Step Guide

Introduction

Experiencing frequent Blue Screen of Death (BSOD) errors, system freezes, and crashes can be frustrating, especially when the PC runs smoothly in Safe Mode. This article aims to guide you through a comprehensive troubleshooting process, using a real-world example of a high-end gaming and workstation rig. If you’re facing similar issues, this methodical approach can help identify the root cause—be it hardware, drivers, or software—and lead to an effective solution.

Case Overview

Hardware Configuration:
– Processor: Intel Core i9-14900KF
– Memory: 2x32GB A-Data RAM
– Graphics Card: PNY Nvidia RTX 4080 Super
– Motherboard: ASRock 790PG Riptide

Symptoms:
– System crashes approximately once daily after a month of use
– Starts to be unusable outside Safe Mode about a week ago
– Works fine in Safe Mode but crashes or freezes within minutes in normal mode during gaming, stress testing, or after login

Troubleshooting Steps Taken

  1. Hardware Testing and Configuration
  2. Switched RAM slots and tested with single and dual sticks
  3. Replaced NVMe SSD and performed clean OS installations (Windows 11 and Windows 10)
  4. Changed PCIe slots for drives and unplugged USB peripherals
  5. Updated BIOS and drivers via motherboard software and Windows Update
  6. Ran Windows Memory Diagnostic and MemTest86—no errors detected

  7. System File and Image Repairs

  8. Executed system repair commands:
  9. sfc /scannow
  10. dism /online /cleanup-image /scanhealth
  11. DISM /Online /Cleanup-Image /RestoreHealth
  12. No issues reported

  13. Crash Analysis and Debugging

  14. Collected crash dump files for analysis—focused on minidumps
  15. Observed that many BSODs cite ntoskrnl.exe as the faulting module
  16. Common error codes include PAGE_FAULT_IN_NONPAGED_AREA, IRQL_NOT_LESS_OR_EQUAL, CLOCK_WATCHDOG_TIMEOUT, amongst others

  17. Identifying the Culprit

  18. Noted that certain diagnostic tools, such as CPU-Z from cpuid.com, tend to trigger crashes consistently, indicating potential stress points
  19. Recognized the challenge of pinpointing specific hardware components as root causes, especially when dealing with high-end

Share this content:

Leave a Reply

Your email address will not be published. Required fields are marked *