Windows 10: BSOD and constand crashes Im running out of ideas Minidump from today included.

Ive been dealing with this for a few months now. I've run every file check I can think of and I've already reinstalled windows 11 with the repair edition. Errors on the reliability report point to hardware issues but Im not finding anything obvious.Today I updated the bios but I still want to check the DMP file. https://1drv.ms/u/s!Ap8252S_F4t9guJZdnXsUVLPjmNUfw

:)

 

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.

 

Source of ntoskrnl.exe BSOD, minidump included

Hi,



Thank you for posting your query in Microsoft Community. I regret the inconvenience caused to you. Let me help you.



I suggest you to go through the answer provided by SpiritX MS MVP
for a similar thread and follow the troubleshooting steps and check if it resolves the issue.

Click on,
http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/a-few-bsods-all-have-ntsokrnlexe-driver-crash/6ee6418d-3941-454b-a936-8045dc3e0660



I hope the information helps. If you need any further assistance, please feel free to contact us again. We will be happy to assist you further.

 

BSOD Driver_Power_State_Failure minidump

Every so often I get BSODs due to Driver Power State Failure. I've tried the conventional wisdom of reinstalling corrupt drivers in Safe Mode w/ Networking, but to no avail. I saved a minidump of the most recent crash, but I had problems trying to analyze it in WinDBG (something about incorrect symbol paths... at that point it was too technical for me to comprehend). Could someone please analyze this minidump and advise how to prevent future BSODs?
Many thanks

Running Windows 10 Home 1803 (build 17134) on Asus Q302LA, SMBIOS version 2.7