Windows 10: BSOD caused by ntsokrnl.exe+41bf10

SummaryI am getting a BSOD because of ntsokrnl.exe and sluggish behavior when using Google Chrome. In games, I first see FPS drop or start very low and then ramp up to max-FPS that I should be getting and stabilize. I am looking for help on exactly what is causing this. I will start by stating what I think could be the obvious problem, but would like to work: I have both an NVIDIA and an AMD card installed in my system. My AMD card is driving the displays, and my NVIDIA card is just set to creator-ready driver mode.Bug Check String: KMODE_EXCEPTION_NOT_HANDLEDCaused By Address: ntoskrnl.ex

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

BSOD caused by ntsokrnl.exe+41bf10

Summary

I am getting a BSOD because of ntsokrnl.exe and sluggish behavior when using Google Chrome. In games, I first see FPS drop (or start very low and then ramp up to max-FPS that I should be getting and stabilize). I am looking for help on exactly what is causing this. I will start by stating (what I think could be the obvious problem, but would like to work): I have both an NVIDIA and an AMD card installed in my system. My AMD card is driving the displays, and my NVIDIA card is just set to creator-ready driver mode.

Bug Check String: KMODE_EXCEPTION_NOT_HANDLED

Caused By Address: ntoskrnl.exe+41bf10

Address In Stack: ntoskrnl.exe+4acc1b

System Information

• Microsoft Windows 11 Pro
  
• 10.0.22000 Build 22000
  
• AMD Ryzen Threadripper 3960X 24-Core Processor, 3793 MHz, 24 Core(s), 48 Logical Processor(s)
  
• Installed Physical Memory: 128 GB
  
• Available Physical Memory: 115 GB
  
• Baseboard: ASUSTeK PRIME TRX40-PRO S
  
• Display Information
  
  • AMD Radeon RX 6800 XT
    
  • NVIDIA GeForce RTX 2070
    

What other information can I provide to help diagnose this? Ideally, I would like to have NVIDIA/AMD cards working properly in the system.

I have tried: sfc /scannow, memtest, DISM, reinstalled display drivers.

Additional Details