Kernal 41 critical error / nvlddmkm stopped responding

Hey guys, absolutely gutted to have to come here again with this problem, as I thought I sorted it.

Long story short, I was plagued with a Kernal 41 crash error for months, and after updating the audio driver, I thought it was fixed. I'd gone around 2 months with not even a blip, until today...

So what happened.
I was tidying my cables, so I unplugged every USB device (I have a powered 10 port USB hub for cable management), tidied all my cables up, and put them back in...Not in the same order as last time, as I didn't really think their was any specific order.

Turned my PC on, and I noticed right away my cursor felt a bit laggy, but anyway, not to worry, but then my PC just froze. I waited for a while, but nothing happened, so I switch off and back on, and it was doing a windows update, so I let it do that.

So firstly, I've noticed that this time around, it seems to crash about 2 or 3 minutes after closing a game (Apex through origin).
The game seems to run fine etc, but when I close it down to desktop, I notice that my PC locks up for a few seconds then carries on. I'll open event viewer and see a warning: Display driver NVLDDMKM stopped responding and has successfully recovered..
About 30 seconds after this error, the computer locks up and won't do anything. The mouse cursor moves, but nothing else. If I do a hard reset, I get a kernal 41 error, which used to plague me.

The only difference this time is, it seems it's getting triggered after a game closure, and instead of instantly rebooting itself, it just sits frozen.

Audio driver was the issue last time, so I've reinstalled the latest one, but still no joy.
But speaking of audio, and mentioning I repositioned my USB order, my audio interface (GOXLR) is now named (4-TC-Helicon GoXLR) instead of (3-TC-Helicon GoXLR)

A few things to note:
GPU driver is up to date
No software has been installed
No overlocks on anything.

The only thing to change from yesterday to today is USB positioning on the hub.

V2 log collector 1.11.zip - Google Drive
Above is my BSOD file

Thank you

Macboatmaster said:

It is not your logs, all you have uploaded to Google is the LOG COLLECTOR
from this site

DESKTOP-6QS8L28-(2022-02-11_19-00-35).zip - Google Drive

Damn, sorry, that is the link I assume you'd want

Macboatmaster said:

I cannot spend any longer on this session examining all the logs
as it is 0025 and time to sign off.
What I would do if it were me, is to disconnect from your 10 port usb hub - one item at a time, replacing that if necessary to another system usb port direct
and then test on each disconnection

I appreciate that may be a long job, but if it is a usb issue that may just find it.
Those usb items that are not absoutely necessary can be left disconnected of course, whilst carrying out such tests

Thank you for taking a look at it, I really appreciate any input.
I'll look into the GoXLR driver tomorrow, although according to the auto update through the software, it's up to date, so I'll see on that one.
I'll also look at the C drive and make a bit of space. To be honest it is partitioned, so I can give it some more, but I'm not sure why it's so full anyway.

One update, I'm thinking it may be something to do with OBS, although I have no idea why as nothing has changed since yesterday, but having OBS open (not even streaming), watching someone on twitch and playing Apex really kills my PC. The twitch stream lags, and my game feels a bit off, but as soon as I closed that down mid game tonight, everything turned fine, So I am going to have a look at this.

As for the USB, one by one, I have already accepted that is a job I will have to do tomorrow, no matter how tedious!

Macboatmaster said:

Could not resist the test you set me
I was just about to press the big off button
when I saw your email so I checked the log

Event[7609]:
Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 2022-02-11T15:47:09.9470000Z
Event ID: 2004
Task: Resource Exhaustion Diagnosis Events
Level: Warning
Opcode: Contains the results of the diagnosis.
Keyword: Events related to exhaustion of system commit limit (virtual memory).
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-6QS8L28
Description:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: obs64.exe (21608) consumed 12346982400 bytes, r5apex.exe (24116) consumed 7341985792 bytes, and chrome.exe (14540) consumed 534740992 bytes.

To save you working it out OBS 12GB

and virtual memeory warning
Source: Application Popup
Date: 2022-02-11T15:47:09.1870000Z
Event ID: 26
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-6QS8L28
Description:
Application pop-up: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.


GOODNIGHT I have gone
I doubt it is virtual memory itself that is the problem
as you have 36GB allocated
Just to make certain
check it in system


Good luck see you later either for further work or hopefully to read you sorted it

Thanks again for looking at this.
I see someone who loves the challenge!! haha

I wonder if somehow my C drive has randomly filled up like crazy. If OBS is using 12gb of VM out of 36gb, but my C drive only has 16gb left, I wonder if that is the cause, and will be the first thing I look at today.

I assume VM is all C drive, although I could be massively wrong.
I'm glad you found that though as OBS definitely did seem the PC killer here.

That being said, my physical memory, as I was keeping an eye, yesterday was only topping out at about 40%

- - - Updated - - -

So, just to give an update as to where I am.

I added an extra 150gb to the C drive. (Didn't fix the issue)
Removed OBS and OBS Live and just installed OBS (Didn't fix the issue)
Uninstalled Apex and reinstalled. (Didn't fix the issue)

If Apex and youtube are running, it works fine
If OBS and youtube are running, it works fine
If OBS, Apex and youtube are running, I get the stutters.
I changed Apex to full screen rather than borderless and this actually seemed to help a lot, so I thought I'd try another game. I loaded up Fifa and that was the worst yet. 3 freezes within a minute that lasted for 10 or seconds each. Each time was the nvlddmkm error that restarts the GPU driver, so I knew this wasn't the solution

Spoke on the OBS forum and using an analyser, apparently Hardware accelerated graphics can be detrimental to OBS running.

So for now, I've turned this off (I don't know how useful this is to be honest, and if it is, I'd rather have it on, but oh well), and so far, everything feels better. I can run all 3 programmes and everything appears stable.

One thing to note, I noticed that in task manager, it's almost like my PC wasn't assigning my GPU usage properly.
Apex could easily sit at 100% while others were using 10% etc. Basically resulting in over 100%
Now, everything, well so far anyway!!! seems to be equalling out. Apex is sitting at 80% others all adding up to 100%, so I wonder if it was something to do with this.

I actually turned Hardware acceleration back on and it seemed to work ok too, but for now, I am just going to leave it off.

Macboatmaster said:

NO Virtual memory is in simple terms
Manage Virtual Memory Pagefile in Windows 10
page file and as I said from your log
Application pop-up: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

So if you mean it is ON C drive the answer is YES providing you have not specially configured to move the paging file to another drive - not a good idea
IF HOWEVER you mean it is ALL the space on C drive then no it is as system managed, which is the best setup OR as set.

Hey, yeah I just meant, I assume the allotted amount of VM is from the C drive, and with my drive filling up, it may have caused some problems.

I added an extra 150GB to the C to help with this problem.
Looking at it, my VM is:
Recommended: 4981mb
Current: 4864mb

I've not changed anything in here