Having a BSOD System_Service_Exception win32kbase.sys

[xiaotk1]

My SSD and HDD are in good using crystaldisk to check
Any solution to solve this ?
Minidump file using windbg analysis below


Microsoft (R) Windows Debugger Version 10.0.15063.468 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122017-6343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff801`81817000 PsLoadedModuleList = 0xfffff801`81b78ff0
Debug session time: Wed Dec 20 20:17:05.359 2017 (UTC + 8:00)
System Uptime: 1 days 6:21:25.335
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, ffffe62c25e4a9b8, fffff401f8fe6470, 0}

Probably caused by : win32kbase.sys ( win32kbase!CFlipToken::CFlipToken+10 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffe62c25e4a9b8, Address of the instruction which caused the bugcheck
Arg3: fffff401f8fe6470, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7B38

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.20

BIOS_DATE: 09/20/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350M PRO-VD PLUS (MS-7B38)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffffe62c25e4a9b8

BUGCHECK_P3: fffff401f8fe6470

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!CFlipToken::CFlipToken+10
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1

CONTEXT: fffff401f8fe6470 -- (.cxr 0xfffff401f8fe6470)
rax=ffffe64bc3cbd980 rbx=000268e5a4e39c00 rcx=ffffe64bc3cbd980
rdx=0000000000000001 rsi=0000000000000000 rdi=00000000c3cbd980
rip=ffffe62c25e4a9b8 rsp=fffff401f8fe6e60 rbp=0000000000000001
r8=ffff8400d8e13490 r9=00000000000000db r10=ffffe66f40002000
r11=0000000000000080 r12=0000000000000000 r13=fffff401f8fe7030
r14=fffff401f8fe6f48 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
win32kbase!CFlipToken::CFlipToken+0x10:
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1 ds:002b:000268e5`a4e39c90=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-VVP4MR1

ANALYSIS_SESSION_TIME: 12-20-2017 20:20:39.0642

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from ffffe62c25e4e328 to ffffe62c25e4a9b8

STACK_TEXT:
fffff401`f8fe6e60 ffffe62c`25e4e328 : ffff8400`d8e13490 ffff8400`d8e13490 00000000`00000001 ffffe62c`25e4e8e0 : win32kbase!CFlipToken::CFlipToken+0x10
fffff401`f8fe6e90 ffffe62c`25e4e3ac : ffff8400`d8e13490 fffff401`f8fe7030 00000000`00000b00 ffffffff`ffffffff : win32kbase!CFlipToken::CreateCompleted+0x74
fffff401`f8fe6ef0 ffffe62c`25e4e439 : 00000000`00000000 fffff401`f8fe7030 00000001`d99cb700 00000000`00000000 : win32kbase!CToken::CreateFlipToken+0x2c
fffff401`f8fe6f30 ffffe62c`25e485e7 : 00000000`00000000 00000000`00000000 ffff8400`d8e13490 ffffffff`80002874 : win32kbase!CToken::CreateFromCompletedFlipToken+0x5d
fffff401`f8fe6f80 ffffe62c`25e488b6 : 00000000`00000000 fffff401`f8fe70c0 ffffe64b`c0005ee0 00000000`00000000 : win32kbase!CTokenManager::CreateFlipExToken+0x37
fffff401`f8fe6fc0 ffffe62c`25e48ade : ffff8400`00000001 fffff401`00000800 00000000`00000002 fffff401`f8fe7a68 : win32kbase!CTokenManager:rocessDxgkAdapterTokens+0x23a
fffff401`f8fe7870 ffffe62c`25dfec40 : 00000000`00000000 ffff8400`dae77650 fffff401`f8fe79a0 00000000`00000890 : win32kbase!CTokenManager:rocessTokens+0x10e
fffff401`f8fe7920 ffffe62c`25dfeb26 : fffff401`f8fe7b80 fffff801`818bb2c7 ffff8400`00000000 ffff8400`00000000 : win32kbase!CTokenManager::TokenThread+0xd0
fffff401`f8fe79e0 fffff801`81986553 : ffff8400`d99cb700 00000000`00000000 00000000`00000020 00007ffd`0d7333c0 : win32kbase!NtTokenManagerThread+0x146
fffff401`f8fe7b00 00007ffd`0ef87864 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000003`3e57fa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0ef87864


THREAD_SHA1_HASH_MOD_FUNC: 6cf358591b19eaffea6eb3dba16775525362dbe8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ddddf0d97574baa407a80a742343e09cac93698c

THREAD_SHA1_HASH_MOD: 1d00f8293a4950c2c1c0542d58ebac09b104126c

FOLLOWUP_IP:
win32kbase!CFlipToken::CFlipToken+10
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1

FAULT_INSTR_CODE: 9083c748

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32kbase!CFlipToken::CFlipToken+10

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.16299.125

STACK_COMMAND: .cxr 0xfffff401f8fe6470 ; kb

BUCKET_ID_FUNC_OFFSET: 10

FAILURE_BUCKET_ID: 0x3B_win32kbase!CFlipToken::CFlipToken

BUCKET_ID: 0x3B_win32kbase!CFlipToken::CFlipToken

PRIMARY_PROBLEM_CLASS: 0x3B_win32kbase!CFlipToken::CFlipToken

TARGET_TIME: 2017-12-20T12:17:05.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

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: 2017-12-08 05:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 706

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_win32kbase!cfliptoken::cfliptoken

FAILURE_ID_HASH: {b6a19393-2e66-0453-7695-5ca6e4836ba2}

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffe62c25e4a9b8, Address of the instruction which caused the bugcheck
Arg3: fffff401f8fe6470, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd

SYSTEM_PRODUCT_NAME: MS-7B38

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.20

BIOS_DATE: 09/20/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd

BASEBOARD_PRODUCT: B350M PRO-VD PLUS (MS-7B38)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffffe62c25e4a9b8

BUGCHECK_P3: fffff401f8fe6470

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!CFlipToken::CFlipToken+10
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1

CONTEXT: fffff401f8fe6470 -- (.cxr 0xfffff401f8fe6470)
rax=ffffe64bc3cbd980 rbx=000268e5a4e39c00 rcx=ffffe64bc3cbd980
rdx=0000000000000001 rsi=0000000000000000 rdi=00000000c3cbd980
rip=ffffe62c25e4a9b8 rsp=fffff401f8fe6e60 rbp=0000000000000001
r8=ffff8400d8e13490 r9=00000000000000db r10=ffffe66f40002000
r11=0000000000000080 r12=0000000000000000 r13=fffff401f8fe7030
r14=fffff401f8fe6f48 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
win32kbase!CFlipToken::CFlipToken+0x10:
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1 ds:002b:000268e5`a4e39c90=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: c80

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-VVP4MR1

ANALYSIS_SESSION_TIME: 12-20-2017 20:20:41.0440

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from ffffe62c25e4e328 to ffffe62c25e4a9b8

STACK_TEXT:
fffff401`f8fe6e60 ffffe62c`25e4e328 : ffff8400`d8e13490 ffff8400`d8e13490 00000000`00000001 ffffe62c`25e4e8e0 : win32kbase!CFlipToken::CFlipToken+0x10
fffff401`f8fe6e90 ffffe62c`25e4e3ac : ffff8400`d8e13490 fffff401`f8fe7030 00000000`00000b00 ffffffff`ffffffff : win32kbase!CFlipToken::CreateCompleted+0x74
fffff401`f8fe6ef0 ffffe62c`25e4e439 : 00000000`00000000 fffff401`f8fe7030 00000001`d99cb700 00000000`00000000 : win32kbase!CToken::CreateFlipToken+0x2c
fffff401`f8fe6f30 ffffe62c`25e485e7 : 00000000`00000000 00000000`00000000 ffff8400`d8e13490 ffffffff`80002874 : win32kbase!CToken::CreateFromCompletedFlipToken+0x5d
fffff401`f8fe6f80 ffffe62c`25e488b6 : 00000000`00000000 fffff401`f8fe70c0 ffffe64b`c0005ee0 00000000`00000000 : win32kbase!CTokenManager::CreateFlipExToken+0x37
fffff401`f8fe6fc0 ffffe62c`25e48ade : ffff8400`00000001 fffff401`00000800 00000000`00000002 fffff401`f8fe7a68 : win32kbase!CTokenManager:rocessDxgkAdapterTokens+0x23a
fffff401`f8fe7870 ffffe62c`25dfec40 : 00000000`00000000 ffff8400`dae77650 fffff401`f8fe79a0 00000000`00000890 : win32kbase!CTokenManager:rocessTokens+0x10e
fffff401`f8fe7920 ffffe62c`25dfeb26 : fffff401`f8fe7b80 fffff801`818bb2c7 ffff8400`00000000 ffff8400`00000000 : win32kbase!CTokenManager::TokenThread+0xd0
fffff401`f8fe79e0 fffff801`81986553 : ffff8400`d99cb700 00000000`00000000 00000000`00000020 00007ffd`0d7333c0 : win32kbase!NtTokenManagerThread+0x146
fffff401`f8fe7b00 00007ffd`0ef87864 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000003`3e57fa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`0ef87864


THREAD_SHA1_HASH_MOD_FUNC: 6cf358591b19eaffea6eb3dba16775525362dbe8

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ddddf0d97574baa407a80a742343e09cac93698c

THREAD_SHA1_HASH_MOD: 1d00f8293a4950c2c1c0542d58ebac09b104126c

FOLLOWUP_IP:
win32kbase!CFlipToken::CFlipToken+10
ffffe62c`25e4a9b8 48c7839000000001000000 mov qword ptr [rbx+90h],1

FAULT_INSTR_CODE: 9083c748

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32kbase!CFlipToken::CFlipToken+10

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.16299.125

STACK_COMMAND: .cxr 0xfffff401f8fe6470 ; kb

BUCKET_ID_FUNC_OFFSET: 10

FAILURE_BUCKET_ID: 0x3B_win32kbase!CFlipToken::CFlipToken

BUCKET_ID: 0x3B_win32kbase!CFlipToken::CFlipToken

PRIMARY_PROBLEM_CLASS: 0x3B_win32kbase!CFlipToken::CFlipToken

TARGET_TIME: 2017-12-20T12:17:05.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

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: 2017-12-08 05:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 705

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_win32kbase!cfliptoken::cfliptoken

FAILURE_ID_HASH: {b6a19393-2e66-0453-7695-5ca6e4836ba2}

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

 

[Mark RM]

First thing to do is test your RAM with memtest86 , you can download a bootable USB stick image from them.
https://www.memtest86.com/download.htm

If it passes, target all drivers for updates, video card (clean uninstall with DDU and replacement ), sound and printer are especially prone to causing this error.

Other considerations: how are you system temperatures under load?

 

[xiaotk1]

I tested memtest86 before is great all driver latest ,my temperature is good no idea why bsod ,getting it while watching chrome video in animewebsite ,i keep getting aw snap from chrome when i refresh watch for a few momment and get bsod

 

[ARICH5]

try going to chrome settings advanced and click reset.

 

[Mark RM]

Link me to the website where chrome crashes please.

 

[xiaotk1]

http://www3.animetv.to/ , and another issue my steam ,dota 2.exe keep auto close due by no error msg ,any solution?

 

[Mark RM]

OK, list your system specifications, CPU GPU ETC please

I have a couple ideas. Did your system recently update to the fall creators upgrade?

 

[xiaotk1]

OS-Window 10 Pro
CPU-AMD RYZEN 5 1400 Quad-Core Processor
Motherboard-MSI B350M PRO-VD PLUS
RAM-16GB G.Skill Aegis DDR4-2400 one stick*
Graphic-GTX 1060 Gigabyte Mini ITX OC 3G
PSU-Gigabyte PB 500W
SSD-GALAX TA1D0120A 120GB
HDD-WD Blue 1TB Desktop Hard Disk Drive - 7200 RPM
window version duno where to check i disable window update so it did not show history,by the way i having other bsod lastly i duno is even connected to it or not.
this is other thread i created http://www.tomshardware.com/forum/id-3595320/bsod-gaming-chrome-idea-caused.html

 

[xiaotk1]

ok i found system version is 1709 ,OS build 16299.125,window 10 pro

 

[Mark RM]

Allright, try this;
change your default browser to Edge in Windows
https://support.microsoft.com/en-ca/help/4028606/windows-change-your-default-browser-in-windows-10
Install the actual Realtek drivers from
http://www.realtek.com/downloads/
it's under ----->High Definition Audio Codecs (Software)

Test

Test

If it still fails, disable the Nvidia sound device in device manager
Search for device manager in the search bar, open it
Open "Sound, Video and Game Controllers"
Right click "NVIDIA High Definition Audio" -- Select Disable
Right Click "NVIDIA Virtual Audio Device" -- Select Disable

 

[xiaotk1]

Mine realtek is actual driver, does changing default browser to edge helps a lot? I will try Ur method will giv u a answer lately

 

[Mark RM]

It helps with a lot of random steam errors, yes.

 

[Mark RM]

The type of error you linked me to in that dump file is most often caused by a corrupted RAM error read.

So basically I think you are looking at a hardware issue, where the RAM you have and are using isn't fully compatible with your motherboard.
You pretty much need to pick RAM from the QVL when using Ryzen

https://www.msi.com/Motherboard/support/B350M-PRO-VD-PLUS#support-mem-12

You can try turning off all overclocks, updating the BIOS to 7B38v22 if you have not already. But with the memory/ryzen stuff I've seen i'd stick to RAM off the QVL.

 

[xiaotk1]

If my ram is out of qvl any other solution?
Just checked mine is c17s ,suited is c15s and c16s.

 

[Mark RM]

You can try a .1 bump in the ram voltage and see if it stabilizes things, it's sometimes a quick fix. Other than that you could try; reduce the RAM speed in BIOS, custom tweak you own settings to find stable RAM timings etc.

 

[johnbl]

-run a Malwarebytes scan. the driver that is failing is often a target of malware/virus
- run cmd or powershell as an admin and run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth

turn off your virtual memory and reboot so you delete your hidden c:\pagefile.sys then turn your virtual memory back on. (some malware infects the pagefile.sys)

check the task scheduler to see if there is a task scheduled that reinstalls the malware.

- normally bad ram timings would not break the system in the same driver location on two different boots.
- the dism.exe command should fix hacked versions of the core windows files.
- deleting the page file should dump hidden hacks that are being saved to disk during sleep.
- Malwarebytes scan will remove adware that USA scanners are not allowed to remove
most major virus scanners get sued if they remove certain adware programs.

 

[xiaotk1]

Any guide webpage for bump ram voltage?

 

[Mark RM]

I can't find an exact match and the manual for you baord is all but useless, but normally the function sticks right out in your face.... like DRAM VOLTAGE 1.35 or whatever it is. I still thinks it's a long shot but it's easy to do and try and easy to change back.

 

[xiaotk1]

hmmm..if i go get a ram that compatible with amd board will it totally fix my bsod? if it will i gona buy it

 

[Mark RM]

The issue is we're not not sure of that,

but when you don't have stuff that's compatible and known to work together, how do we know it's not that?