Windows 10: BSOD Win32kbase.sys During Gaming

Ever since my previous windows build I have been getting a BSOD while trying to play certain games on Steam which is cause by 'Moving my Mouse' Having updated drivers/Reinstalled Windows to the latest Build (18290) I am Still getting a BSOD when I touch my mouse. I have tried using a different mouse but the BSOD still occurs.

When I start a game on Steam it loads as normal ( I can use the keyboard to navigate through the Menu's but as soon as I touch the Mouse a BSOD happens showing a StopCode Win32kbase.sys

Is there a possible Fix for this?

Thank you.



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: ffffe1cc3e5c35b2, Address of the instruction which caused the bugcheck
Arg3: ffffa889fbd90ce0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18290.1000.amd64fre.rs_prerelease.181121-1501

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: ASUS_MB_KBLX

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1603

BIOS_DATE: 11/02/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG RAMPAGE VI EXTREME

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffffe1cc3e5c35b2

BUGCHECK_P3: ffffa889fbd90ce0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
win32kbase!tagObjLock::LockExclusive+12
ffffe1cc`3e5c35b2 48394108 cmp qword ptr [rcx+8],rax

CONTEXT: ffffa889fbd90ce0 -- (.cxr 0xffffa889fbd90ce0)
rax=ffffe30d17f87080 rbx=0000000000000038 rcx=0000000000000038
rdx=0000000000000005 rsi=ffffe18d868258a0 rdi=0000000000000005
rip=ffffe1cc3e5c35b2 rsp=ffffa889fbd916d0 rbp=0000000000000000
r8=0000000000000008 r9=ffffe1cc3e2f95a0 r10=ffffe1cc3e2f95a0
r11=0000000000000000 r12=000000000001003d r13=ffffa889fbd91888
r14=ffffa889fbd917a8 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=00050282
win32kbase!tagObjLock::LockExclusive+0x12:
ffffe1cc`3e5c35b2 48394108 cmp qword ptr [rcx+8],rax ds:002b:00000000`00000040=????????????????
Resetting default scope

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 200004D'00000000 (cache) 200004D'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MAIRTIN-PC

ANALYSIS_SESSION_TIME: 12-06-2018 13:36:24.0983

ANALYSIS_VERSION: 10.0.18272.1001 amd64fre

LAST_CONTROL_TRANSFER: from ffffe1cc3e2044f2 to ffffe1cc3e5c35b2

STACK_TEXT:
ffffa889`fbd916d0 ffffe1cc`3e2044f2 : ffffe18d`806559d8 00000000`00000000 00000000`00000000 00000000`00000004 : win32kbase!tagObjLock::LockExclusive+0x12
ffffa889`fbd91700 ffffe1cc`3e2d8d1f : 00000000`00000000 ffffa889`fbd917f1 ffffe18d`806559c0 ffffe18d`868258a0 : win32kfull!CMultiPerObjectLockExclusive<5>::CMultiPerObjectLockExclusive<5><tagObjLock,tagObjLock,tagObjLock,tagObjLock,tagObjLock>+0xe2
ffffa889`fbd91730 ffffe1cc`3e2d8132 : 00000000`00000002 00000003`****`0017f906 ffffa889`fbd91ad8 : win32kfull!EditionPostRawMouseInputMessage+0x3ef
ffffa889`fbd91850 ffffe1cc`3e2d91b0 : ffffa889`fbd91cd0 ffffe18d`8065a050 00000000`00000000 ffffa889`fbd91b29 : win32kfull!xxxMoveEventAbsolute+0x2e6
ffffa889`fbd919a0 ffffe1cc`3e663640 : 00000000`00000000 00000000`00000000 ffffa889`fbd91ad8 fffff806`00000000 : win32kfull!EditionCommitMousePosAndMove+0x80
ffffa889`fbd91a00 ffffe1cc`3e5c2c6c : 00000000`00000001 ffffa889`fbd91b29 00000000`00000000 00000000`00000001 : win32kbase!ApiSetEditionCommitMousePosAndMove+0xd4
ffffa889`fbd91a70 ffffe1cc`3e5c5e9b : 0000021c`000003c0 ffffa889`fbd91be0 ffffa889`fbd91ca0 ffffa889`fbd91cd0 : win32kbase!CMouseProcessor::CommitMousePosAndMoveCursor+0x118
ffffa889`fbd91b90 ffffe1cc`3e7443a9 : 0000021c`000003c0 ffffe1cc`3e7b90c0 ffffe18d`86c905e0 0000021c`000003c1 : win32kbase!CMouseProcessor:rocessMouseInputData+0xef
ffffa889`fbd91c00 ffffe1cc`3e73c1d6 : ffffe18d`806062d0 ffffe30d`17eba650 00000000`00000018 ffffe18d`806062d0 : win32kbase!CMouseProcessor:rocessInput+0x3b9
ffffa889`fbd91d80 ffffe1cc`3e7301da : ffffe1cc`3e7830e0 ffffa889`fbd91e59 ffffe18d`806062d0 ffffcf82`00490400 : win32kbase!CMouseSensor:rocessInput+0x56
ffffa889`fbd91dc0 ffffe1cc`3e5c5217 : 00000000`00000040 ffffe1cc`3e7830e0 00000000`00000003 fffff806`6f6dc6d8 : win32kbase!CBaseInput::OnReadNotification+0x47a
ffffa889`fbd91ec0 ffffe1cc`3e5c4e42 : ffffffff`ffffffd2 ffffe18d`8068d1a0 00000000`00000006 00000000`0000000c : win32kbase!CBaseInput::OnDispatcherObjectSignaled+0x2ff
ffffa889`fbd91ff0 ffffe1cc`3e628c7b : 00000000`00000001 00000000`00000004 00000000`00000000 00000000`00000000 : win32kbase!CBaseInput::_OnDispatcherObjectSignaled+0x12
ffffa889`fbd92020 ffffe1cc`3e628a11 : 00000000`00000006 00000000`00000004 00000000`0000000b ffffe30d`0000000d : win32kbase!LegacyInputDispatcher:ispatch+0x53
ffffa889`fbd92050 ffffe1cc`3e21322a : ffffe18d`8062a8a0 ffffe18d`8062a8a0 00000000`00000004 00000000`00000001 : win32kbase!LegacyInputDispatcher::WaitAndDispatch+0xf1
ffffa889`fbd92140 ffffe1cc`3e212e8a : 00000000`00000004 ffffe1cc`3e7c5260 00000000`0000000c 00000000`00000005 : win32kfull!xxxDesktopThreadWaiter+0x12a
ffffa889`fbd921c0 ffffe1cc`3e5b6323 : ffffe30d`17f87080 ffffe30d`17f87080 00000000`00000000 00000000`00000005 : win32kfull!xxxDesktopThread+0x3da
ffffa889`fbd922a0 ffffe1cc`3e224ec0 : ffffe30d`17f87080 00000000`00000005 00000000`00000000 00000000`00000000 : win32kbase!xxxCreateSystemThreads+0x273
ffffa889`fbd92390 fffff806`6f88a7d5 : ffffe30d`17f87080 00000000`00000005 000001a8`****`00000470 : win32kfull!NtUserCallNoParam+0x70
ffffa889`fbd923c0 00007ffb`19c91144 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000090`01f3fc28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`19c91144


THREAD_SHA1_HASH_MOD_FUNC: bbd31b63d62cbd92355e68787a94c7309f941889

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 63f968c42ec4527f082bdbf4ba42129a3d8bcd6c

THREAD_SHA1_HASH_MOD: c8c2a0c1dedc385433ecb15358487d191760659b

FOLLOWUP_IP:
win32kbase!tagObjLock::LockExclusive+12
ffffe1cc`3e5c35b2 48394108 cmp qword ptr [rcx+8],rax

FAULT_INSTR_CODE: 8413948

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32kbase!tagObjLock::LockExclusive+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.18290.1000

STACK_COMMAND: .cxr 0xffffa889fbd90ce0 ; kb

BUCKET_ID_FUNC_OFFSET: 12

FAILURE_BUCKET_ID: 0x3B_win32kbase!tagObjLock::LockExclusive

BUCKET_ID: 0x3B_win32kbase!tagObjLock::LockExclusive

PRIMARY_PROBLEM_CLASS: 0x3B_win32kbase!tagObjLock::LockExclusive

TARGET_TIME: 2018-12-06T11:37:08.000Z

OSBUILD: 18290

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1983-08-18 17:51:57

BUILDDATESTAMP_STR: 181121-1501

BUILDLAB_STR: rs_prerelease

BUILDOSVER_STR: 10.0.18290.1000.amd64fre.rs_prerelease.181121-1501

ANALYSIS_SESSION_ELAPSED_TIME: 5db

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_win32kbase!tagobjlock::lockexclusive

FAILURE_ID_HASH: {90f33cda-823e-dd0d-5e50-c69ca0316667}

Followup: MachineOwner
---------

4: kd> !blackboxbsd
Version: 168
Product type: 1

Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE

Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d48d546034f58b
Last reference time checksum: 0x643d41c6
Last update boot id: 28

Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x98
Last boot id: 28
Last successful shutdown boot id: 24
Last reported abnormal shutdown boot id: 27

Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0

Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0


:)

 

win32kbase BSOD






And now?

 

BSOD while gaming - wdf01000.sys


Hi gents,

I have created an account here to ask for some assistance because I am at wit's end with my BSOD issues.

Early January 2018 my PC started acting up and BSODing like a wild savage while gaming. MemTest, OCCT all passed just fine so I moved from a hardware to a software assumption. I decided to reinstall Windows10 since I had never had a clean (only upgraded) Windows 10 install - PROBLEM SOLVED. Or so I thought. The problem has now resurfaced ~2 Months later and I have no idea what the issue is.

• When does it happen? > While gaming
• Result - BSOD of various description but most recently it seems to be wdf01000.sys related:
  • KMODE_EXCEPTION_NOT_HANDLED
  • IRQL not less or equal
  • Many others I can't recall

I have run the forum's BSOD data collection app and attached the result which was generated when running Driver Verifier.

I will try get more dumps as a result of gameplay and upload.

Any help GREATLY appreciated.

A frustrated gamer,

 

BSOD When playing games

Hi Jackson,

Thank you for contacting Microsoft Community.

Please share the information requested below:

• Does the BSOD occur while playing a particular game?
• Is the game downloaded from Windows Store?

I suggest you to update the Graphic Card drivers by following the steps provided below and check if it helps.

• Press Windows key + X, select Device Manager.
• Expand Display Adapters.
• Right click on the driver and select Update Driver Software.
• Follow the on-screen prompts to update.

Refer the link below for more information:

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope this helps. Keep us posted on the status for further assistance.