iCUE v3.31.81 causing BSOD?

[vyse]

Hello all, I've been having random BSODs while gaming with friends (Conan Exiles + Discord).

 

I ran the DMP file and it seems to point to the iCUE.exe program creating what seems to be some type of deadlock

KxWaitForLockOwnerShip

I could be totally off here, so forgive me if so

 

Any advice? I see there is a new version but I didn't want to update in case one of the devs wanted me to test or run a diagnostic. I pulled the system info and logs from iCUE and attached them here, let me know if there's any other info I can provide.

 

Here's a snip of the DMP that pointed me to iCUE. Thanks for your time:

CONTEXT:  ffffd70194eff930 -- (.cxr 0xffffd70194eff930)
rax=0000000000000000 rbx=ffff978712fa3000 rcx=ffff978712fa3000
rdx=2400000000000000 rsi=0000000000000000 rdi=ffffad024be71cf0
rip=fffff8064bc1bd8e rsp=ffff978712fa2f70 rbp=0000000000000000
r8=000000055d5b8807  r9=0000000000001cff r10=fffff8064bca0490
r11=ffff978712fa3020 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KxWaitForLockOwnerShip+0xe:
fffff806`4bc1bd8e 48890a          mov     qword ptr [rdx],rcx ds:002b:24000000`00000000=????????????????
Resetting default scope

PROCESS_NAME:  iCUE.exe

BAD_STACK_POINTER:  ffffd70194efeff8

STACK_TEXT:  
ffff9787`12fa2f70 fffff806`4bca6c8d     : 00000000`00000032 00000000`00000064 00000000`000000fa 00000000`000001f4 : nt!KxWaitForLockOwnerShip+0xe
ffff9787`12fa2fa0 fffff806`4bca04ec     : ffffad02`4be71c90 00000000`00002710 00000000`000009c4 00000000`0000c350 : nt!KeAcquireInStackQueuedSpinLock+0x7d
ffff9787`12fa2fd0 ffff9a34`a1fcdeb2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000008 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x5c
ffff9787`12fa3030 ffff9a34`a17627a6     : 00000000`00000000 00000000`00000004 ffffad02`4be71cf0 ffffad02`4ea0c080 : win32kbase!UserSessionSwitchLeaveCrit+0x62
ffff9787`12fa30b0 ffff9a34`a1615951     : 00000000`00000000 ffff9a07`42fe2350 00000000`00000000 00000000`00001cff : win32kfull!xxxMsgWaitForMultipleObjectsEx+0x72
ffff9787`12fa3160 fffff806`4bdd4791     : ffffad02`4ea0c080 00000000`1891e898 00000000`00000000 00000000`00001cff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x3c1
ffff9787`12fa3a90 00007ff8`df548704     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2bc
00000000`1891e878 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`df548704


SYMBOL_NAME:  win32kbase!UserSessionSwitchLeaveCrit+62

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.18362.1082

STACK_COMMAND:  .cxr 0xffffd70194eff930 ; kb

BUCKET_ID_FUNC_OFFSET:  62

FAILURE_BUCKET_ID:  0x3B_c0000005_STACKPTR_ERROR_win32kbase!UserSessionSwitchLeaveCrit

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6fab5411-640c-6bdd-6778-1a6b8c24f7e7}

Followup:     MachineOwner

icuedump.zip

[vyse]

One thing I realized is that this started once I went from wireless to corded. Wireless seemed to be fine for the 2 hours I used it. The two BSODs happened within an hour of using the cord