BSoD ntoskrnl.exe and ntkrnlmp.exe (win32kbase.sys)

Toggle sidebar Toggle sidebar
A

Arahor

Commendable
Jun 15, 2016
16
0
1,510
Hello. I just got BSoD. From what i can make out of it it's related to "win32kbase.sys" which does not tell me anything.

I ran memtest84+ and it shows no errors.


WhoCrashed says this.

Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17072918528 bytes total



Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 2018-06-24 23:00:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062418-9781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800DEE928A2, 0xFFFFF980D8B86ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2018-06-24 23:00:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x73C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800DEE928A2, 0xFFFFF980D8B86ED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Also WinDbg says this.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`dee8c000 PsLoadedModuleList = 0xfffff800`df2461f0
Debug session time: Sun Jun 24 23:00:37.244 2018 (UTC + 2:00)
System Uptime: 0 days 2:00:25.989
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`046dc018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800dee928a2, fffff980d8b86ed0, 0}

Probably caused by : win32kbase.sys ( win32kbase!EnterSharedCrit+41 )

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

nt!KeBugCheckEx:
fffff800`df024330 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff980`d8b86600=000000000000003b
4: 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: fffff800dee928a2, Address of the instruction which caused the bugcheck
Arg3: fffff980d8b86ed0, 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: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

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

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

SYSTEM_SKU: SKU

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

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2901

BIOS_DATE: 05/04/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: SABERTOOTH 990FX R2.0

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff800dee928a2

BUGCHECK_P3: fffff980d8b86ed0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p 0x%p refererade till minnet p 0x%p. Minnet kunde inte vara %s.

FAULTING_IP:
nt!KxWaitForLockOwnerShipWithIrql+12
fffff800`dee928a2 48890a mov qword ptr [rdx],rcx

CONTEXT: fffff980d8b86ed0 -- (.cxr 0xfffff980d8b86ed0)
rax=0000000000000000 rbx=ffffe505b4cc24a0 rcx=fffff980d8b87928
rdx=0800000000000000 rsi=ffffe505b6cb7700 rdi=fffff980d8b87928
rip=fffff800dee928a2 rsp=fffff980d8b878c0 rbp=fffff980d8b87958
r8=fffff980d8b87980 r9=0000000000000006 r10=0000000000000004
r11=ffffe505b6cb7700 r12=0000000000000002 r13=0000000000000000
r14=000000000000ff00 r15=ffffe505b4cc2500
iopl=0 nv up di ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010082
nt!KxWaitForLockOwnerShipWithIrql+0x12:
fffff800`dee928a2 48890a mov qword ptr [rdx],rcx ds:002b:08000000`00000000=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 10ee

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Discord.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: OLIVER

ANALYSIS_SESSION_TIME: 06-24-2018 23:06:05.0827

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff800deeffe73 to fffff800dee928a2

STACK_TEXT:
fffff980`d8b878c0 fffff800`deeffe73 : ffffe505`b4cc24a0 00000000`00000000 00000000`00000001 fffff800`def145a0 : nt!KxWaitForLockOwnerShipWithIrql+0x12
fffff980`d8b878f0 fffff800`def2081d : ffff88b0`00000002 00000000`00000000 fffff980`d9699930 00000000`00000000 : nt!ExpApplyPriorityBoost+0x533
fffff980`d8b87980 fffff800`def11712 : ffffe505`b4cc24a0 ffffe505`b6cb7700 00000000`00000000 ffff88b0`026f1be0 : nt!ExpApplyPrewaitBoost+0x8d
fffff980`d8b879b0 fffff800`def8ae9a : 00000000`00000002 ffffe505`b4cc24a0 00000000`00000000 00000000`00000000 : nt!ExpAcquireResourceSharedLite+0x3a2
fffff980`d8b87a50 ffff888b`69a6a4b1 : 00000000`00000000 00000000`00000000 00000000`004096b6 ffff888b`00000001 : nt!ExEnterCriticalRegionAndAcquireResourceShared+0x4a
fffff980`d8b87a90 ffff888b`6a41fa8f : 00000000`00000040 fffff980`d8b87b80 00000000`77a85300 00000000`00000020 : win32kbase!EnterSharedCrit+0x41
fffff980`d8b87ad0 fffff800`df034943 : ffffe505`b6cb7700 ffffe505`b6cb7700 fffff980`d8b87b80 00000000`00000000 : win32kfull!NtUserCallOneParam+0x1f
fffff980`d8b87b00 00000000`77a8f304 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00d1ded8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a8f304


THREAD_SHA1_HASH_MOD_FUNC: 73fa94a78ed156cddf0e33ca0b49bf6a63e0457a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 27f1ac4d966042c027cb6a60f5a4981e178655c6

THREAD_SHA1_HASH_MOD: a1065c0f1e29b9ea5565121504105574f7d99b4b

FOLLOWUP_IP:
win32kbase!EnterSharedCrit+41
ffff888b`69a6a4b1 4885c0 test rax,rax

FAULT_INSTR_CODE: 74c08548

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32kbase!EnterSharedCrit+41

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.112

STACK_COMMAND: .cxr 0xfffff980d8b86ed0 ; kb

BUCKET_ID_FUNC_OFFSET: 41

FAILURE_BUCKET_ID: 0x3B_win32kbase!EnterSharedCrit

BUCKET_ID: 0x3B_win32kbase!EnterSharedCrit

PRIMARY_PROBLEM_CLASS: 0x3B_win32kbase!EnterSharedCrit

TARGET_TIME: 2018-06-24T21:00:37.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-06-08 11:00:00

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 60b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_win32kbase!entersharedcrit

FAILURE_ID_HASH: {ff5fe9cc-0a4c-1094-4816-66b27f913d63}

Followup: MachineOwner


Link to dump file: https://1drv.ms/f/s!Av0v4dUc625OjxtDvsHpo0SBrH3J

I'm out of ideas.
 
Sort by date Sort by votes
Just got two more BSoD. Dumps here: https://1drv.ms/f/s!Av0v4dUc625Ojz2hO-WwNDTy8aUW

On Tue 2018-06-26 01:50:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062618-11484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8016D8E9CA4, 0xFFFFF1882C083A10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2018-06-26 01:50:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x73C9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8016D8E9CA4, 0xFFFFF1882C083A10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2018-06-26 01:33:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062618-10531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4CCA4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8020545ACA4, 0xFFFFF8893AAEAF78, 0xFFFFF8893AAEA7C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
So I reinstalled Windows. Deleted everything from both my SSD and HDD so it became a full clean and fresh install.

I installed a couple of things once it was done and I'll try to list them below, including my system spec with age and the new crash dump file with the windbg report.

My Specs are
(No pre-build pc, builded it myself)

OS: Windows 10 64-bit Home, version 1803 (OS-version 17134.112)

Motherboard: Asus Sabertooth 990FX R2.0 (4 Years Old) (https://www.asus.com/us/Motherboards/SABERTOOTH_990FX_R20/)

CPU: AMD FX(tm)-8350 Eight-Core Processor ~4.3GHz (4 Years Old) (https://www.amazon.com/AMD-FD8350FRHKBOX-FX-8350-8-Core-Processor/dp/B009O7YUF6)

GPU: EVGA GeForce GTX 980 4GB (2 Years Old) (https://www.evga.com/products/specs/gpu.aspx?pn=472a80bc-9a78-45b1-8560-6fa1916330e8)

PSU: Corsair 850RM 80 PLUS (4 Years Old) (https://www.corsair.com/us/en/Power/rm-series-config/p/CP-9020056-NA)

RAM: 4x Kingston 4GB 240-Pin DDR3 SDRAM DDR3 1333 (16GB in total, 6 years old) (https://www.newegg.com/Product/Product.aspx?Item=N82E16820139046)

Crucial MX500 250GB (4 Years Old)

Seagate Barracuda 2TB 3.5'' HDD (1 Year Old)

CPU Cooler: Cooler Master Hyper 212 EVO

I figured that it's not my temps. My GPU runs about 50-60c while I game and around 30-40c while Idle. My CPU runs 50-65c while gaming and 40-50c while idle. The temps on my SSD and HDD are nothing remarkable either in my opinion both around 30c.

I have not overclocked, mainly because I dont know how to do it and that I don't want to do it or felt the need to do so. I'm using EVGA PrecisionX 16 to control my fan curve on my GPU for good cooling (mainly because also the GTX 980 also does not activate it's fan untill it gets hot).

So i kept an eye on what I did when I got access to the PC once the reinstallation was fully complete and I'll list all that below.

1. Windows Updates, had to restart 1-2 times before that was fully done.
2. Installing Firefox
3. Installing Discord
4. Installing Steam
5. Installing GeForce Experience
6. Downloading EVGA PrecisionX 16
7. Installing latest NVIDIA drivers (398.36)
8. Installing Razer Synapse
9. Installing drivers for my webbcam (QuickCam Communicate STX) - http://support.logitech.com/en_us/product/quickcam-communicate-stx
10. Installing motherboard drivers - https://www.asus.com/us/Motherboards/SABERTOOTH_990FX_R20/HelpDesk_Download/ (all of them, apart from the BIOS because I already have that installed already)
11. Installing drivers for my headset (RIG 500HD - https://www.plantronics.com/se/sv/support/downloads-apps/rig-500-surround-sound)
12. Restarting Windows so the installations can finish properly.
13. Installing OpenOffice 4.1.5 for work.
14. Installing Chrome for so i can watch the Play feature for TV channels.
15. Installing Spotify.
16. Installing HWMonitor
17. Installing three games in this order from steam. Total War: Warhammer 2 - Elder Scrolls Online - My Time at Portia.
18. Starting to tweak my audio settings in my headset driver for the best audio while listening to Spotify.
19. Bluescreen happens.

That's it pretty much.

I've run memtest84+ (or something) to test my RAM, no errors but might still be bad, I can't say.

Here is what WhoCrashed tells me

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 2018-06-26 18:55:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062618-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4CCA4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800654DCCA4, 0xFFFFD10E1B7CD5C8, 0xFFFFD10E1B7CCE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2018-06-26 18:55:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x4CAC)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800654DCCA4, 0xFFFFD10E1B7CD5C8, 0xFFFFD10E1B7CCE10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


And here is what windbg tells me.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`65490000 PsLoadedModuleList = 0xfffff800`6584a1f0
Debug session time: Tue Jun 26 18:55:49.185 2018 (UTC + 2:00)
System Uptime: 0 days 0:24:42.946
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff800654dcca4, ffffd10e1b7cd5c8, ffffd10e1b7cce10}

Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessCompletedQueuePacketInternal+522 )

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

nt!KeBugCheckEx:
fffff800`65628330 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffd10e`1b7cc610=000000000000007e
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800654dcca4, The address that the exception occurred at
Arg3: ffffd10e1b7cd5c8, Exception Record Address
Arg4: ffffd10e1b7cce10, Context Record Address

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

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

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

SYSTEM_SKU: SKU

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

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2901

BIOS_DATE: 05/04/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: SABERTOOTH 990FX R2.0

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800654dcca4

BUGCHECK_P3: ffffd10e1b7cd5c8

BUGCHECK_P4: ffffd10e1b7cce10

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p 0x%p refererade till minnet p 0x%p. Minnet kunde inte vara %s.

FAULTING_IP:
nt!KxWaitForLockOwnerShip+14
fffff800`654dcca4 48890a mov qword ptr [rdx],rcx

EXCEPTION_RECORD: ffffd10e1b7cd5c8 -- (.exr 0xffffd10e1b7cd5c8)
ExceptionAddress: fffff800654dcca4 (nt!KxWaitForLockOwnerShip+0x0000000000000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffffd10e1b7cce10 -- (.cxr 0xffffd10e1b7cce10)
rax=0000000000000002 rbx=0000000000000000 rcx=ffffd10e1b7cd9b8
rdx=a800000000000000 rsi=ffff8f06361cac20 rdi=ffffd10e1b7cd9b8
rip=fffff800654dcca4 rsp=ffffd10e1b7cd800 rbp=ffffd10e1b7cd960
r8=ffff8f0634aca000 r9=ffff8f0634be67b0 r10=ffff8f0634be6780
r11=ffffd10e1b7cd9b8 r12=0000000000000002 r13=ffff8f0634be6000
r14=ffff8f06361c6bb0 r15=0000000000000002
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!KxWaitForLockOwnerShip+0x14:
fffff800`654dcca4 48890a mov qword ptr [rdx],rcx ds:002b:a8000000`00000000=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 10ee

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

FOLLOWUP_IP:
dxgmms2!VidSchiProcessCompletedQueuePacketInternal+522
fffff807`edae9bb2 4c8b37 mov r14,qword ptr [rdi]

BUGCHECK_STR: AV

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p 0x%p refererade till minnet p 0x%p. Minnet kunde inte vara %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

ANALYSIS_SESSION_HOST: OLIVER

ANALYSIS_SESSION_TIME: 06-26-2018 19:06:19.0112

ANALYSIS_VERSION: 10.0.17674.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff8006558c513 to fffff800654dcca4

STACK_TEXT:
ffffd10e`1b7cd800 fffff800`6558c513 : ffff8f06`361b4730 00000000`00000000 ffff8f06`361cac20 ffff8f06`361b4730 : nt!KxWaitForLockOwnerShip+0x14
ffffd10e`1b7cd830 fffff807`edae9bb2 : ffff8f06`361b4730 ffffd10e`1b7cd960 00000000`000013c7 00000000`00000000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x53
ffffd10e`1b7cd860 fffff807`edae191a : ffff8f06`3071c802 ffff8f06`00000000 00000000`00000000 ffff8f06`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x522
ffffd10e`1b7cda80 fffff807`edb60ef1 : ffff8f06`361b4730 ffff8f06`361c6600 ffff8f06`37bf8700 ffff8f06`00000000 : dxgmms2!VidSchiSubmitMmIoFlipCommand+0x69a
ffffd10e`1b7cdb80 fffff807`edb60d5e : ffff8f06`34be6500 fffff807`edb60cd0 ffff8f06`34be6000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x181
ffffd10e`1b7cdbd0 fffff800`65574cb7 : ffff8f06`34be3700 fffff807`edb60cd0 ffffd480`34c80180 00000224`acbb3dfe : dxgmms2!VidSchiWorkerThread+0x8e
ffffd10e`1b7cdc10 fffff800`6562f7d6 : ffffd480`34c80180 ffff8f06`34be3700 fffff800`65574c70 d0458984`7d89c0ff : nt!PspSystemThreadStartup+0x47
ffffd10e`1b7cdc60 00000000`00000000 : ffffd10e`1b7ce000 ffffd10e`1b7c8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: c81e15a45ce6884bfda901a2bbdf7c3282986e07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 22bc0c1b4e370987c01cc271ba1e66811e3682f5

THREAD_SHA1_HASH_MOD: 7205faa80e78101f22234177c174abd807d35d0d

FAULT_INSTR_CODE: 4c378b4c

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms2!VidSchiProcessCompletedQueuePacketInternal+522

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.112

STACK_COMMAND: .cxr 0xffffd10e1b7cce10 ; kb

BUCKET_ID_FUNC_OFFSET: 522

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchiProcessCompletedQueuePacketInternal

BUCKET_ID: AV_dxgmms2!VidSchiProcessCompletedQueuePacketInternal

PRIMARY_PROBLEM_CLASS: AV_dxgmms2!VidSchiProcessCompletedQueuePacketInternal

TARGET_TIME: 2018-06-26T16:55:49.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-06-08 11:00:00

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 1271

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_dxgmms2!vidschiprocesscompletedqueuepacketinternal

FAILURE_ID_HASH: {b2c3b332-059a-e5f3-ac1f-2810d43d4dff}

Followup: MachineOwner

Dumpfile: https://1drv.ms/u/s!Av0v4dUc625Oj0Jv_K2xj1S-88G6


I did notice this in DXDIAG window though.

https://i.imgur.com/l1p1SRm.png

https://i.imgur.com/bWUlEsJ.png

https://i.imgur.com/OvrBdzI.png

Is that normal? Three audio tabs? Could that be a conflict?

Thanks for taking your time to read through all this. I'm at a loss here, I don't know what's wrong.
 
Upvote 0 Downvote
Hi, the 3 audio tabs are 3 difference devices. Look at the name / Namn of each. I also have 3 tabs. This should be normal.

Since you reinstalled Windows (I'm assuming before the last 2 dumps were posted) I've decided to do 2 different dump file readings since dumps contain a list of drivers (and that could change with a reinstall of Windows). The first ones listed below will be the last two you posted (newest), which I assume is after the Windows reinstall. Below that will be the previous dump files you uploaded.

Info from the 2 newest dump files: https://pste.eu/p/AHJz.html
File: 062618-11484-01.dmp (Jun 25 2018 - 19:50:32)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 56 Sec(s)

File: 062618-10531-01.dmp (Jun 25 2018 - 19:33:51)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: Discord.exe)
Uptime: 0 Day(s), 2 Hour(s), 49 Min(s), and 55 Sec(s)
Motherboard: https://www.asus.com/us/Motherboards/SABERTOOTH_990FX_R20/
You have the latest BIOS installed.

And the 2 previous dumps: https://pste.eu/p/8EtD.html
File: 062618-8468-01.dmp (Jun 26 2018 - 12:55:49)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 24 Min(s), and 42 Sec(s)

File: 062418-9781-01.dmp (Jun 24 2018 - 17:00:37)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: Discord.exe)
Uptime: 0 Day(s), 2 Hour(s), 00 Min(s), and 25 Sec(s)
I can't help you with this. Wait for additional replies. Good luck.
 
Upvote 0 Downvote


That is correct. The ones you have here is from the last bsod after i reinstalled windows. And correct again, I got the latest BIOS update. Thanks for those file readings though, I'll await more answers for further actions.
 
Upvote 0 Downvote
I'm running memtest84 atm. Through each stick at a time. I'll report back on my findings. One ram stick is done and finished 8 passes for 6h 30min, no errors.
 
Upvote 0 Downvote


Just got done with the memtests and all ramsticks passed 8 tests each with 0 errors.

I also installed the latest LAN drivers from the link you provided. Had the options "Change" "Repair" "Remove". So I chosed repair just to be safe.
 
Upvote 0 Downvote
Bit of an update. So far I've been playing a bit of ESO, Guild Wars 2 and My Time at Portia. No bluescreens has happend so far.

Although on the 29th when i woke up the PC had frozen, so I had to do a force reboot.

Once I had logged in I wanted to see WhoCrashed to see if it was a bluescreen or something. But it was not, but my eyes became stuck at the amount of RAM I had. After checking in the task manager I noticed that I only had 8gb of RAM when I have 4x4gb sticks connected, so I should have had 16gb.

I powered down the PC. And plugged out one stick of RAM. Checked the BIOS and it said 8gb ram. Repeated and pulled out another stick, bios still said 8gb ram (at this point, it was correct).

I pulled out a third stick of ram then the bios said 4gb. After that I plugged in the first stick i pulled out into the third slot. Then bios said 8gb ram. I then took the ram stick that were in the third slot before and plugged it into the second slot, then bios said i had 12gb. Then i took the stick that i pulled out of the second ram slot into the first slot and then bios said i had 16gb.

I logged in and everything were in order, 16gb ram everywhere. I know that I played Guild Wars 2 the evening before and I know I had 16gb while doing that too. So something must have happend during the night, that made my pc not recognize two of my ram sticks at that time, which siezed my pc up which made me force restart it and deal with that issue.

Since then I've not had a single issue with the computer yet. So It might be "fixed". I'm looking into to replace the motherboard though, which will mean that there will be a new CPU, MB and new RAM, taking the oppertunity to turning the performance up a notch.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom