BSODs since new keyboard

Hello,

I recently (16.01.2022) got a new keyboard (Glorious GMMK Pro). However, since I started using it I experienced an extreme amount of Blue Screens. I tried resetting Windows but it also didn't help. After that I unplugged the new keyboard and started using my old one again. Since then I got no Blue Screen anymore (since yesterday evening) and everything runs stable. The three chrashdumps are from AFTER resetting Windows, but I still have the ones before resetting Windows if you need/want them. Is it possible that a keyboard(-driver) is causing multiple Blue Screens?

Version: 10.0.19042 Build 19042

Btw. There was no specific trigger: Windows crashed watching YouTube Videos/ attending Zoom conferences and playing games.

The log is in the attchments or alernatively in my OneDrive account

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.DESKTOP-1SD2B0A-(2022-01-18_17-29-57).zip

Update BIOS - MPG X570 GAMING EDGE WIFI
Update AMD chipset drivers - https://www.amd.com/en/support/chips...ocket-am4/x570

Ztruker said:

011722-10281-01.dmp 9:10PM C:\Program Files\Riot Vanguard\vgk.sys Riot Vanguard Anti-cheat system

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffc18fd56f5a28, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80436007628, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

011722-8203-01.dmp 9:11PM \SystemRoot\system32\drivers\wd\WdFilter.sys Defender Mini-Filter Driver 9:17PM

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffde8fd554e4e0, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff80012207bc8, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

011722-7343-01.dmp 9:17PM

Code:

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000006, 
Arg2: 00000000003d316f
Arg3: 0000000000000001
Arg4: 0000000005460001

No failing module name indicated.

Did you load a driver with the new mouse? I do see it has software that needs to be loaded for the keyboard. Since removing the keyboard resolves the problem it is almost a certainty that the software is the problem. Contact Glorious or see if there is a user forum to ask about it. I'd return it and find an alternative.

Well, strangely it started working again. I really don't know what the problem was, but I don't have any problems since 2 days now. Glorious Core (the Software for the keyboard) was not installed btw. I am happy I don't have to use a 3rd party firmware or hit up the support :)