Windows 10: Minidump for Crash to desktop BSOD. Could someone help me please?

Hello, COuld someone please help me interpret these two examples of a crash to desktop that I have just started reveiving? I am on Wondows 11 with newish hardware and all drivers are up to date to the best of my knowledge. Kind regards, Aidan le Gras, Oatley, New South Wales Australia122321-7093-01.dmp122423-7593-01.dmp

:)

 

Flickering screen at startup, crashes, and BSOD after instaling new GPU

Here are some that are close to the BSOD crash time but i dont think they have to do anything with the BSOD.

 

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.

 

1709 BSOD error on boot: BAD_SYSTEM_CONFIG_INFO; have minidump; need help

Thanks, Pedro, for that link, which has some good recovery suggestions. I am slowly working my way through the list.

So far, I have successfully reverted my system to an earlier system image which did not have the problem at the time. However, it still

does. The symptoms that prompted my post and that continue are:

1. The first boot crashes before reaching the desktop with a BSOD with stop code "BAD_SYSTEM_CONFIG_INFO".

2. The system automatically restarts and succeeds in reaching the desktop without an error.

So far, in that link of suggested fixes, I have tried:

a) boot to safe mode; then restart with normal booting. This did not help

Besides fixing the problem, I would like to understand what is causing it. That's because, earlier, I thought they were caused by the 1803 build. But now that they have returned with my 1709 build, this suggests something else. Hence the minidumps.

alan