Windows 10: BSOD with ntkrnl.exe error from WinDbg. Please help. Pc crashing multiple times for the...

Mostly with IRQL less than or equal to error or page fault in non paged area error. I have tried everything from running sfc scan , reinstalling windows, updating drivers, been hapening for the last 4-5 months. but frequency has increased now. I have attached a debug analysis of WinDbg showing a ntkrnl.exe error causing the system to crash. Any fixes around this please help urgently. ******************************************************************************** ** Bugcheck Analysis

:)

 

Various BSOD Errors Help

Hey all,

I've received multiple BSOD errors the past 2 days after rebuilding my PC. I've been trying to figure out the issue.

These are the few BSOD messages I remember seeing:

• DPC_WATCHDOG_VIOLATION (multiple times)
• CRITICAL_PROCESS_DIED (one time)
• IRQL_NOT_LESS_OR_EQUAL (one time)
• WHEA_UNCORRECTABLE_ERROR (multiple times)

Here's a link to the dmp files and system information: Microsoft OneDrive

Steps I've taken:

• fully updated drivers
• applied all Windows updates
• Removed unnecessary hardware
• Monitored CPU/GPU temps (log file on temps during last crash in share)

Any help would be appreciated.

 

Constant BSOD and Random Crashing

I'm sorry to hear about the issues you're facing with your computer. Random crashes and Blue Screen of Death (BSOD) errors can be frustrating to troubleshoot, but analyzing minidump files can provide valuable information about the underlying causes.

Unfortunately, as a text-based AI model, I'm unable to directly access or analyze files or attachments. However, I can provide you with some general guidance on how to analyze minidump files yourself or suggest alternative troubleshooting steps.

1. Analyzing minidump files:
   
   • To analyze minidump files, you'll need a debugger tool like WinDbg, which is part of the Windows Software Development Kit (SDK). Install the SDK and WinDbg on your computer.
     
   • Open WinDbg and go to "File" > "Open Crash Dump." Browse and select the minidump file you want to analyze.
     
   • WinDbg will load the minidump and display information about the crash. Look for the error message or the faulting module that caused the crash. This information can help identify the potential cause of the problem.
     
   • If you're unfamiliar with WinDbg or analyzing minidump files, you can search for specific error messages or faulting modules online or seek help from forums and communities dedicated to Windows troubleshooting.
     
2. Alternative troubleshooting steps:
   
   • Since you suspect faulty RAM, testing it with new RAM modules is a good step. Faulty RAM can cause various stability issues, including crashes and BSOD errors. Consider ordering new RAM and replacing the existing modules to see if it resolves the problem.
     
   • Ensure that all your drivers, including motherboard chipset drivers, graphics card drivers, and other hardware drivers, are up to date. Outdated or incompatible drivers can lead to system instability.
     
   • Monitor your computer's temperature using software like HWMonitor or Core Temp. Overheating components can cause crashes. Make sure your computer's cooling system is working properly and clean any dust buildup on the CPU cooler and other components.
     
   • Check for any recently installed software or drivers that may be causing conflicts. Uninstalling or rolling back recent changes can help isolate the problem.
     
   • If the issues persist, you may want to consider seeking assistance from a professional computer technician or contacting the customer support of your computer's manufacturer.
     

Remember to always back up your important data before making any major changes to your system or replacing hardware components.

I hope these suggestions help you in troubleshooting and resolving the issues you're experiencing with your computer.

 

BSOD when coming out of sleep, multiple error codes

Thanks for the assistance, I've run all the necessary steps. It looks like there might be an issue found when running that first command. I have also installed all the driver updates recommended by the dell support check.

You can find the logs of the command prompt window in the cmd.log file

cmd logs.txt