Windows 10: nvlddmkm crash, BSOD, screen goes all glitchy system information + minidump below

Hello, my computer has recently started crashing glitchy pixels on screen and giving an error citing nvlddmkm.sysCorresponding minidump file; https://drive.google.com/file/d/16PAhKwpS-uRhtJZG4tlFWV5TUtOG9ci_/view?usp=sharingPlease let me know what else information may be needed. I am running Windows 11 23H2 22631.4391 and using the latest nVidia driver after removing it using DDU utility.

:)

 

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.

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II