[SOLVED] Frequent BSOD, while idle & while playing games

allachor

allachor

Member
Joined
Feb 7, 2025
Posts
9
This issue started a few months ago, with infrequent BSOD, maybe once a week. Recently it has started happening every hour when a game is running, sometimes every 30 minutes and it's sporadic while idle.

The error code that kept popping up is DPC_WATCHDOG_VIOLATION, with the offending file in BlueScreenViewer being ntoskrnl.exe. This isn't very helpful considering how vague it is, and I've been updating drivers, uninstalling them entirely, removing programs from startup, nothing stops it from occurring.

I'm at a loss at this point, and would very much appreciate any help that could be provided.
 

Attachments

We need the C:\Windows\MEMORY.dmp, which is not there.

Could you double check the system recovery configuration is set for kernel dump
  1. Open Settings app
  2. Go to System and scroll down to About, click on it
  3. Go to Advanced system settings
  4. Under the section Startup and Recovery click Settings
  5. At the dropdown in System Failure, select Kernel memory dump
  6. Click OK, you can close the prompts now
After this is confirmed, we need to wait for another crash to occur for the file to be generated.
 
I need you to upload it to onedrive or a similar service and post a share link.
 
I uploaded the file to a website but I can't post the link here, it says it was filtered.

I used the service mega(.)nz. Figured it out, link below, remove brackets.

https://mega(.)nz/file/iuwF0aQY#hHJb-udIj6kYL-yUPYw3vGyotZDqsTtWxS0jawvAj3c
 
Looking into the logs and kernel dump. Have you kept track of which drivers/programs you have updated/reinstalled?
 
The 0x133 looks to be due to the NVIDIA display driver, but I noticed different crashes too and not due to the NVIDIA display driver but what looks like a driver from Logitech which is very outdated for Windows 11. Have you checked if there are software updates for Logitech?
Code: 
Bugcheck code 00000139
Arguments 00000000`00000003 ffff968b`939b70f0 ffff968b`939b7048 00000000`00000000
Debug session time: Thu Feb  6 15:41:03.237 2025 (UTC + 1:00)
System Uptime: 0 days 0:14:49.849

30: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 (Inline Function) --------`-------- Wdf01000!RtlFailFast+0x5
01 (Inline Function) --------`-------- Wdf01000!FatalListEntryError+0x5
02 (Inline Function) --------`-------- Wdf01000!InsertTailList+0x2a3
03 (Inline Function) --------`-------- Wdf01000!FxIoQueue::ForwardRequestWorker+0x728
04 (Inline Function) --------`-------- Wdf01000!FxIoQueue::ForwardRequest+0x74e
05 ffff968b`939b7280 fffff802`6e66c6c8 Wdf01000!imp_WdfRequestForwardToIoQueue+0x812
06 ffff968b`939b7350 ffff8185`492e4b00 logi_generic_hid_filter+0xc6c8
07 ffff968b`939b7358 ffff8185`492e4b30 0xffff8185`492e4b00
08 ffff968b`939b7360 00000000`00000000 0xffff8185`492e4b30

30: kd> lmvm logi_generic_hid_filter
Browse full module list
start             end                 module name
fffff802`6e660000 fffff802`6e670000   logi_generic_hid_filter T (no symbols)           
    Loaded symbol image file: logi_generic_hid_filter.sys
    Image path: logi_generic_hid_filter.sys
    Image name: logi_generic_hid_filter.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar 15 01:37:10 2019 (5C8AF3B6)
    CheckSum:         0001C3FA
    ImageSize:        00010000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

The NVIDIA display driver seems updated, I would suggest trying older versions of the driver.
Code: 
30: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff802`67500000 fffff802`6d23a000   nvlddmkm   (deferred)             
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Jan 26 08:39:45 2025 (6795E6C1)
    CheckSum:         05B4AEB6
    ImageSize:        05D3A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
I recently updated my Nvidia drivers and the problem kept occurring. I'll try to downgrade. I have not updated my Logitech drivers but it seems like it only caused a crash once? I'll try updating them.

There was a solution posted to reddit a while ago, where someone suggested finding nvlddmkm.sys in system32 and changing the permissions on the file to enable full user control. I tried that and it reduced the frequency of BSOD but didn't stop them.
 
I used DDU to do a clean uninstall of all my Nvidia drivers and then installed an old driver from when this problem wasn't as frequent, I suppose I'll give it a while and hope that fixes things.

I tried to find an updated driver for my Logitech mouse or keyboard but my mouse was fully up to date, and it didn't recognize my keyboard.
 
Looks like Logitech K120 wired keyboard is a plug and play device, meaning there's no additional driver/software for it.
 
It's worth checking that Logitech haven't added a keyboard filter driver that's messing things up. If you're comfortable using regedit then navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e96b-e325-11ce-bfc1-08002be10318}. In there you'll see an UpperFilters key, if there is anything in that list other than kbdclass you have had additional filter drivers added.

To remove those filter drivers follow this....
  1. First export that key, so right-click on the key in the left-hand pane and click export. Save the .reg file to somewhere you can find again.
  2. Right-click the UpperFilter key and click Modify. Delete all entries except kbdclass - this MUST be there.
  3. Reboot and see whether the problem is resolved. You will also need to check what keyboard features are no longer working - these are probably special key combinations etc.
  4. If this causes serious problems, then double-click the .reg key that you exported to return that key to how it was and reboot.
 
ubuysa said:
It's worth checking that Logitech haven't added a keyboard filter driver that's messing things up. If you're comfortable using regedit then navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e96b-e325-11ce-bfc1-08002be10318}. In there you'll see an UpperFilters key, if there is anything in that list other than kbdclass you have had additional filter drivers added.

To remove those filter drivers follow this....
  1. First export that key, so right-click on the key in the left-hand pane and click export. Save the .reg file to somewhere you can find again.
  2. Right-click the UpperFilter key and click Modify. Delete all entries except kbdclass - this MUST be there.
  3. Reboot and see whether the problem is resolved. You will also need to check what keyboard features are no longer working - these are probably special key combinations etc.
  4. If this causes serious problems, then double-click the .reg key that you exported to return that key to how it was and reboot.
Click to expand...
I checked where you said, and there was nothing but the kbdclass listed there in Upper Filters so at least that wasn't the problem.

Since I did a full clean of my Nvidia drivers and reverted back to a half year old set of drivers I haven't had any BSOD, I have been having performance issues but that's nothing compared to crashing every half hour. I'll probably give it a while before I update to the most recent drivers straight from Nvidia's site instead of using GeForce Experience like I have been doing.

Thank you so much axe0 & ubuysa for the assistance, for now I think it has been resolved as a GPU Driver issue.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top