F5F Stay Refreshed Software Operating Systems I've been dealing with frequent random BSODs for a while now?

I've been dealing with frequent random BSODs for a while now?

I've been dealing with frequent random BSODs for a while now?

G
gmoney_1114
Junior Member
49
03-17-2023, 07:06 AM
#1
Hello everyone,
As the title indicates, I've been experiencing random BSODs for some time now. A few weeks ago, I even performed a clean install of Windows 11 on a new NVMe M.2 drive, but the issue persisted.
Since then, I've flashed the BIOS, installed fresh RAM, and updated all drivers I could find, yet the problem remains.
Around the time these BSODs began, I also noticed the computer felt slower overall, especially when playing games I used to enjoy without any issues.

Here is my System Information:
Windows version: Windows 11 Pro, Version 10.0.26100 Build 26100
Memory: B450 GAMING PLUS (MS-7B86)
CPU: AMD Ryzen 7 2700X Eight-Core Processor, 3700Mhz
RAM: 4x CORSAIR Vengeance LPX 8GB, DDR4 3200Mhz
GPU: Nvidia GeForce RTX 4070

I've attached my minidumps here:
https://drive.google.com/drive/folders/1...drive_link

Please let me know if anyone needs further details.
Thank you
G
gmoney_1114
03-17-2023, 07:06 AM #1

Hello everyone,
As the title indicates, I've been experiencing random BSODs for some time now. A few weeks ago, I even performed a clean install of Windows 11 on a new NVMe M.2 drive, but the issue persisted.
Since then, I've flashed the BIOS, installed fresh RAM, and updated all drivers I could find, yet the problem remains.
Around the time these BSODs began, I also noticed the computer felt slower overall, especially when playing games I used to enjoy without any issues.

Here is my System Information:
Windows version: Windows 11 Pro, Version 10.0.26100 Build 26100
Memory: B450 GAMING PLUS (MS-7B86)
CPU: AMD Ryzen 7 2700X Eight-Core Processor, 3700Mhz
RAM: 4x CORSAIR Vengeance LPX 8GB, DDR4 3200Mhz
GPU: Nvidia GeForce RTX 4070

I've attached my minidumps here:
https://drive.google.com/drive/folders/1...drive_link

Please let me know if anyone needs further details.
Thank you

L
leonardo0803
Member
180
03-22-2023, 04:05 PM
#2
PSU details: make, model, wattage, age, condition (original to build, new, refurbished, used)?
Regarding Reliability History/Monitor and Event Viewer: which error codes, warnings, or messages are being recorded, particularly around or during a BSOD?
L
leonardo0803
03-22-2023, 04:05 PM #2

PSU details: make, model, wattage, age, condition (original to build, new, refurbished, used)?
Regarding Reliability History/Monitor and Event Viewer: which error codes, warnings, or messages are being recorded, particularly around or during a BSOD?

A
angel856
Junior Member
34
04-08-2023, 05:54 PM
#3
PSU: EVGA SuperNOVA 650 G2, 80+ GOLD 650W 220-G2-0650-Y3
The power supply is original from 2019, GPU added in January/February this year, RAM installed two weeks ago, and the rest remains original from 2019.
For reliability history/monitor and Event Viewer, can I export all data or should I just check the codes before the BSOD? Should I focus only on critical events?
A
angel856
04-08-2023, 05:54 PM #3

PSU: EVGA SuperNOVA 650 G2, 80+ GOLD 650W 220-G2-0650-Y3
The power supply is original from 2019, GPU added in January/February this year, RAM installed two weeks ago, and the rest remains original from 2019.
For reliability history/monitor and Event Viewer, can I export all data or should I just check the codes before the BSOD? Should I focus only on critical events?

A
AmazinglyCool
Senior Member
695
04-12-2023, 03:56 PM
#4
From the dumps, it seems the most probable issue is faulty RAM. I'm observing numerous bugchecks, which frequently stem from memory problems. Two critical bugchecks, CRITICAL_PROCESS_DIED, are almost always linked to a hardware failure—usually RAM. Given your 32GB of RAM spread across four sticks, the best approach is to remove two sticks and operate with just 16GB for a day or three, or until another BSOD occurs. Then replace the sticks and run on the remaining two for a few days. If each pair of sticks triggers a BSOD independently, it's likely not related to RAM. Remember: ensure the sticks you select are placed in the correct slots.
A
AmazinglyCool
04-12-2023, 03:56 PM #4

From the dumps, it seems the most probable issue is faulty RAM. I'm observing numerous bugchecks, which frequently stem from memory problems. Two critical bugchecks, CRITICAL_PROCESS_DIED, are almost always linked to a hardware failure—usually RAM. Given your 32GB of RAM spread across four sticks, the best approach is to remove two sticks and operate with just 16GB for a day or three, or until another BSOD occurs. Then replace the sticks and run on the remaining two for a few days. If each pair of sticks triggers a BSOD independently, it's likely not related to RAM. Remember: ensure the sticks you select are placed in the correct slots.

S
Shiba_lnu
Junior Member
9
04-27-2023, 11:15 AM
#5
All four RAM sticks are quite new, purchased about two weeks ago and installed. I might be unlucky and received a faulty pair. For a long time, I only used two slots, so I cleaned the other two with a small new cleaning brush. It could be either that I got unlucky with the RAM or those two connectors are dirty. I can test by removing the two sticks from those connectors—would you think Memtest would also be useful?
S
Shiba_lnu
04-27-2023, 11:15 AM #5

All four RAM sticks are quite new, purchased about two weeks ago and installed. I might be unlucky and received a faulty pair. For a long time, I only used two slots, so I cleaned the other two with a small new cleaning brush. It could be either that I got unlucky with the RAM or those two connectors are dirty. I can test by removing the two sticks from those connectors—would you think Memtest would also be useful?

C
coolman9222
Posting Freak
754
04-27-2023, 05:06 PM
#6
if your ram is fine, I’d check the audio subsystem for memory corruption.
I’d examine the driver listed:
Nahimic_Mirroring.sys Wed Sep 8 00:38:40 2021
or look for an update.
Regardless of the issue, corruption can occur in just one or two days and cause crashes. You might want to switch to a kernel memory dump and use verifier.exe debug flags so the system fails at the moment of corruption instead of later when critical data is accessed.
I believe aehd.sys isn’t passing verification because of memory issues or leaks. Consider removing or excluding this driver from verifier checks.
You can download Driver Explorer, delete the driver store for this device, and remove the device to prevent reinstallation:
https://github.com/lostindark/DriverStor...g/v0.12.88
Also, manually uninstall the service/driver:
https://www.reddit.com/r/MSI_Gaming..._u...?rdt=40804
and note the presence of aehd.sys along with BlackCat1.sys and l1vhlwf.sys (the name has an unusual character, possibly from a bad installer).
C
coolman9222
04-27-2023, 05:06 PM #6

if your ram is fine, I’d check the audio subsystem for memory corruption.
I’d examine the driver listed:
Nahimic_Mirroring.sys Wed Sep 8 00:38:40 2021
or look for an update.
Regardless of the issue, corruption can occur in just one or two days and cause crashes. You might want to switch to a kernel memory dump and use verifier.exe debug flags so the system fails at the moment of corruption instead of later when critical data is accessed.
I believe aehd.sys isn’t passing verification because of memory issues or leaks. Consider removing or excluding this driver from verifier checks.
You can download Driver Explorer, delete the driver store for this device, and remove the device to prevent reinstallation:
https://github.com/lostindark/DriverStor...g/v0.12.88
Also, manually uninstall the service/driver:
https://www.reddit.com/r/MSI_Gaming..._u...?rdt=40804
and note the presence of aehd.sys along with BlackCat1.sys and l1vhlwf.sys (the name has an unusual character, possibly from a bad installer).

U
urinnerchild87
Junior Member
49
04-29-2023, 02:33 PM
#7
Removing two RAM modules and later swapping them doesn't require using any memory diagnostic software.
U
urinnerchild87
04-29-2023, 02:33 PM #7

Removing two RAM modules and later swapping them doesn't require using any memory diagnostic software.

P
Poketerp
Member
132
04-30-2023, 08:10 AM
#8
Sorry for the silence for a few days; I've been quite occupied at work.
I decided to go along with your advice.
@johnbl
followed your suggestion to clean up Nahimic and related drivers by checking the Reddit post you mentioned.
I'm not sure what to do with your last part about three drivers, as I couldn't locate them.
Hopefully, the issue was due to faulty sound drivers, and I'll keep you updated.
P
Poketerp
04-30-2023, 08:10 AM #8

Sorry for the silence for a few days; I've been quite occupied at work.
I decided to go along with your advice.
@johnbl
followed your suggestion to clean up Nahimic and related drivers by checking the Reddit post you mentioned.
I'm not sure what to do with your last part about three drivers, as I couldn't locate them.
Hopefully, the issue was due to faulty sound drivers, and I'll keep you updated.

D
Desertical
Junior Member
25
04-30-2023, 03:02 PM
#9
Short update, nahimic was reinstalled the next day after my cleanup.
After a full day running smoothly, it reinstalled again and fixed a BSOD.
The event viewer indicates some conflicts between MSI software (presumably nahimic) and the registry.
I’m planning to stop it from reinstalling to check if that resolves the issue.
D
Desertical
04-30-2023, 03:02 PM #9

Short update, nahimic was reinstalled the next day after my cleanup.
After a full day running smoothly, it reinstalled again and fixed a BSOD.
The event viewer indicates some conflicts between MSI software (presumably nahimic) and the registry.
I’m planning to stop it from reinstalling to check if that resolves the issue.

Z
zLeoZiin
Senior Member
503
04-30-2023, 11:43 PM
#10
It has been a while since my last update; I've been working hard to resolve some issues here and there. The updates were becoming less frequent. I haven't had a backup in a while, and the computer feels more stable now. Using a driver booster to update all my drivers made a big difference at first. Eventually, removing the NVIDIA drivers with DDU and installing them again seemed necessary. It seems that after changing the graphics card, some drivers became corrupted, and a simple update didn't fix it. Overall, I want to thank everyone for their advice and support, and I hope I never have to ask for help again. 😀
Z
zLeoZiin
04-30-2023, 11:43 PM #10

It has been a while since my last update; I've been working hard to resolve some issues here and there. The updates were becoming less frequent. I haven't had a backup in a while, and the computer feels more stable now. Using a driver booster to update all my drivers made a big difference at first. Eventually, removing the NVIDIA drivers with DDU and installing them again seemed necessary. It seems that after changing the graphics card, some drivers became corrupted, and a simple update didn't fix it. Overall, I want to thank everyone for their advice and support, and I hope I never have to ask for help again. 😀