Windows 10: BSOD's with different stopcodes.

This week I've had almost everyday a BSOD while playing different games. All of the BSOD's had a different stopcode. I will post 5 crashdumps from dec 11 to dec 4.

At first my at first my thought was that the problem was caused by my headset driver (HID-compliant headset driver) because Windows Event Viewer kept saying:

The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.

A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.


In Device manager It kept saying the driver is not working correct so I decided to uninstall the driver and unplug my heaset. Still I managed to get BSOD's.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Dec 11 03:17 SYSTEM_SERVICE_EXCEPTION
Bugcheck: 0x0000003b (0x00000000c0000005, 0xfffff80060a18d14, 0xffffaa8e0844e270, 0x0000000000000000)

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86


Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121119-5843-01.dmp]


Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff800`60400000 PsLoadedModuleList = 0xfffff800`60848170

Debug session time: Wed Dec 11 03:17:14.218 2019 (UTC + 1:00)

System Uptime: 0 days 13:42:36.852

Loading Kernel Symbols

...............................................................

................................................................

................................................................

............

Loading User Symbols

Loading unloaded module list

..............

For analysis of this file, run !analyze -v

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: fffff80060a18d14, Address of the instruction which caused the bugcheck

Arg3: ffffaa8e0844e270, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



DUMP_TYPE: 2



BUGCHECK_P1: c0000005



BUGCHECK_P2: fffff80060a18d14



BUGCHECK_P3: ffffaa8e0844e270



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:

nt!ExpAllocateHandleTableEntry+e4

fffff800`60a18d14 498b4708 mov rax,qword ptr [r15+8]



CONTEXT: ffffaa8e0844e270 -- (.cxr 0xffffaa8e0844e270)

rax=0000000000000000 rbx=ffffe5849be07080 rcx=ffffc30ea11cb080

rdx=ffffe5849be07080 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80060a18d14 rsp=ffffaa8e0844ec60 rbp=0000000000000008

r8=ffffaa8e0844ec68 r9=0000000000000000 r10=0000000000000000

r11=ffffaa8e0844ece0 r12=0000000000000000 r13=ffffaa8e0844ed08

r14=ffffe5849be07040 r15=f7ffe584a1dd6e10

iopl=0 nv up ei ng nz na pe nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282

nt!ExpAllocateHandleTableEntry+0xe4:

fffff800`60a18d14 498b4708 mov rax,qword ptr [r15+8] ds:002b:f7ffe584`a1dd6e18=????????????????

Resetting default scope



BUGCHECK_STR: 0x3B_c0000005



CPU_COUNT: 8



CPU_MHZ: fa8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 5e



CPU_STEPPING: 3



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: NZXT CAM.exe



CURRENT_IRQL: 0



ANALYSIS_SESSION_HOST: DESKTOP-VH5VC3R



ANALYSIS_SESSION_TIME: 12-11-2019 16:58:01.0789



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff80060a18bb8 to fffff80060a18d14



STACK_TEXT:

ffffaa8e`0844ec60 fffff800`60a18bb8 : ffffc30e`00004400 ffffc30e`a46afad0 ffffe584`9be07040 ffffc30e`a11cb080 : nt!ExpAllocateHandleTableEntry+0xe4

ffffaa8e`0844ecb0 fffff800`60a5f657 : ffffc30e`a46afad0 00000000`00000000 ffffaa8e`0844efa0 ffffc30e`a46af400 : nt!ExCreateHandleEx+0x78

ffffaa8e`0844ed00 fffff800`60a5e4f5 : ffffc30e`a12f50c0 00000000`00000000 ffffc30e`92c9db01 ffffaa8e`0844ef01 : nt!PspAllocateThread+0x423

ffffaa8e`0844eea0 fffff800`60a2d641 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!PspCreateThread+0x209

ffffaa8e`0844f150 fffff800`605d2d15 : 00000000`00000000 ffffc30e`a11cb080 ffffc30e`a12c26e0 fffff800`60ab03ed : nt!NtCreateThreadEx+0x221

ffffaa8e`0844f990 00007fff`a53dd854 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

000000e8`d62fd098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`a53dd854





THREAD_SHA1_HASH_MOD_FUNC: 454b7b3e1171da49a281bcbd828f03aaf38c0ebe



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6c143bd49f4aca31958d9d8b1fbb53888cf6bffe



THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693



FOLLOWUP_IP:

nt!ExpAllocateHandleTableEntry+e4

fffff800`60a18d14 498b4708 mov rax,qword ptr [r15+8]



FAULT_INSTR_CODE: 8478b49



SYMBOL_STACK_INDEX: 0



SYMBOL_NAME: nt!ExpAllocateHandleTableEntry+e4



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9



IMAGE_VERSION: 10.0.18362.476



STACK_COMMAND: .cxr 0xffffaa8e0844e270 ; kb



BUCKET_ID_FUNC_OFFSET: e4



FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ExpAllocateHandleTableEntry



BUCKET_ID: 0x3B_c0000005_nt!ExpAllocateHandleTableEntry



PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!ExpAllocateHandleTableEntry



TARGET_TIME: 2019-12-11T02:17:14.000Z



OSBUILD: 18362



OSSERVICEPACK: 476



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: 2011-12-30 00:28:41

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 56b6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!expallocatehandletableentry

FAILURE_ID_HASH: {4245cfff-51b0-70b0-a5d4-f7d134d883a6}

Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------------------------------------------------
Dec 09 21:46 IRQL_GT_ZERO_AT_SYSTEM_SERVICE
bugcheck was: 0x0000004a (0x00007ffb564fc1a4, 0x0000000000000002, 0x0000000000000000, 0xfffffc8787d37a80)


Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Windows\Minidump\120919-9515-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff805`62000000 PsLoadedModuleList = 0xfffff805`62448170

Debug session time: Mon Dec 9 21:46:20.530 2019 (UTC + 1:00)

System Uptime: 2 days 20:05:28.831

Loading Kernel Symbols

...............................................................

................................................................

................................................................

................

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

7: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)

Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.

Arguments:

Arg1: 00007ffb564fc1a4, Address of system function (system call routine)

Arg2: 0000000000000002, Current IRQL

Arg3: 0000000000000000, 0

Arg4: fffffc8787d37a80, 0



Debugging Details:

------------------





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



DUMP_TYPE: 2



BUGCHECK_P1: 7ffb564fc1a4



BUGCHECK_P2: 2



BUGCHECK_P3: 0



BUGCHECK_P4: fffffc8787d37a80



PROCESS_NAME: audiodg.exe



BUGCHECK_STR: RAISED_IRQL_FAULT



FAULTING_IP:

+0

00007ffb`564fc1a4 ?? ???



CPU_COUNT: 8



CPU_MHZ: fa8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 5e



CPU_STEPPING: 3



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: DESKTOP-VH5VC3R



ANALYSIS_SESSION_TIME: 12-11-2019 17:06:06.0011



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff805621d32e9 to fffff805621c14e0



STACK_TEXT:

fffffc87`87d37848 fffff805`621d32e9 : 00000000`0000004a 00007ffb`564fc1a4 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffffc87`87d37850 fffff805`621d3193 : ffff8009`d596a080 00000086`b2e7f638 fffffc87`87d379a8 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffffc87`87d37990 00007ffb`564fc1a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe

00000086`b2e7f608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`564fc1a4





THREAD_SHA1_HASH_MOD_FUNC: 1b1fd012b2a510c586295e696f84a9476c8f91e5



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6a054393ae1713fef08345a54701ed3a92fa10c6



THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b



FOLLOWUP_IP:

nt!KiSystemServiceExitPico+1fe

fffff805`621d3193 4883ec50 sub rsp,50h



FAULT_INSTR_CODE: 50ec8348



SYMBOL_STACK_INDEX: 2



SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9



IMAGE_VERSION: 10.0.18362.476



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 1fe



FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_audiodg.exe_nt!KiSystemServiceExitPico



BUCKET_ID: RAISED_IRQL_FAULT_audiodg.exe_nt!KiSystemServiceExitPico



PRIMARY_PROBLEM_CLASS: RAISED_IRQL_FAULT_audiodg.exe_nt!KiSystemServiceExitPico



TARGET_TIME: 2019-12-09T20:46:20.000Z



OSBUILD: 18362



OSSERVICEPACK: 476



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: 2011-12-30 00:28:41



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 29f7



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:raised_irql_fault_audiodg.exe_nt!kisystemserviceexitpico



FAILURE_ID_HASH: {d857256f-d712-d29c-2cea-02dce2f986b6}



Followup: MachineOwner

----------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEC 7 01:41 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bugcheck: 0x0000007e (0xffffffffc0000005, 0xfffff8006c4e0e60, 0xfffff48c29d125f8, 0xfffff48c29d11e40)


Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\120719-6187-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff800`6c400000 PsLoadedModuleList = 0xfffff800`6c848170

Debug session time: Sat Dec 7 01:36:41.851 2019 (UTC + 1:00)

System Uptime: 0 days 13:36:26.157

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.................

Loading User Symbols

Loading unloaded module list

..............

For analysis of this file, run !analyze -v

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

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.

Some common problems are exception code 0x80000003. This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG. This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG. This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff8006c4e0e60, The address that the exception occurred at

Arg3: fffff48c29d125f8, Exception Record Address

Arg4: fffff48c29d11e40, Context Record Address



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1



Key : AV.Fault

Value: Read





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



SYSTEM_MANUFACTURER: MSI



SYSTEM_PRODUCT_NAME: MS-7978



SYSTEM_SKU: Default string



SYSTEM_VERSION: 2.0



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: A.A0



BIOS_DATE: 12/21/2016



BASEBOARD_MANUFACTURER: MSI



BASEBOARD_PRODUCT: Z170A GAMING M3 (MS-7978)



BASEBOARD_VERSION: 2.0



DUMP_TYPE: 2



BUGCHECK_P1: ffffffffc0000005



BUGCHECK_P2: fffff8006c4e0e60



BUGCHECK_P3: fffff48c29d125f8



BUGCHECK_P4: fffff48c29d11e40



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



FAULTING_IP:

nt!MiInPageSingleKernelStack+3cc

fffff800`6c4e0e60 4c3978f8 cmp qword ptr [rax-8],r15



EXCEPTION_RECORD: fffff48c29d125f8 -- (.exr 0xfffff48c29d125f8)

ExceptionAddress: fffff8006c4e0e60 (nt!MiInPageSingleKernelStack+0x00000000000003cc)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff



CONTEXT: fffff48c29d11e40 -- (.cxr 0xfffff48c29d11e40)

rax=f7fff48c2f57f5e0 rbx=fffff48c29d12aa0 rcx=0200000000000000

rdx=0000000000000001 rsi=fffff48c2f578000 rdi=00000000000003e0

rip=fffff8006c4e0e60 rsp=fffff48c29d12830 rbp=fffff48c29d12930

r8=00000ffffffffffe r9=fffff48c29d128b1 r10=0000000000000001

r11=fffff48c29d128b1 r12=0200000000000002 r13=ffffa47a4617abc8

r14=ffffa47a4617abc0 r15=ffffbd01b264e240

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

nt!MiInPageSingleKernelStack+0x3cc:

fffff800`6c4e0e60 4c3978f8 cmp qword ptr [rax-8],r15 ds:002b:f7fff48c`2f57f5d8=????????????????

Resetting default scope



CPU_COUNT: 8



CPU_MHZ: fa8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 5e



CPU_STEPPING: 3



CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



CURRENT_IRQL: 0



FOLLOWUP_IP:

nt!MiInPageSingleKernelStack+3cc

fffff800`6c4e0e60 4c3978f8 cmp qword ptr [rax-8],r15



BUGCHECK_STR: AV



READ_ADDRESS: fffff8006c9733b8: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

ffffffffffffffff



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



EXCEPTION_CODE_STR: c0000005



EXCEPTION_PARAMETER1: 0000000000000000



EXCEPTION_PARAMETER2: ffffffffffffffff



ANALYSIS_SESSION_HOST: DESKTOP-VH5VC3R



ANALYSIS_SESSION_TIME: 12-11-2019 17:09:39.0158



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff8006c4e055e to fffff8006c4e0e60



STACK_TEXT:

fffff48c`29d12830 fffff800`6c4e055e : 00000000`00000000 00000000`00000002 ffffbd01`b264e240 00000000`00000000 : nt!MiInPageSingleKernelStack+0x3cc

fffff48c`29d12a80 fffff800`6c587f9a : 00000000`00000000 ffffbd01`00000000 00000000`00000000 00000000`00000000 : nt!KiInSwapKernelStacks+0x4e

fffff48c`29d12ad0 fffff800`6c52a7a5 : ffffbd01`a5557080 fffff800`6c587f20 fffff800`6c86a400 00000000`00000000 : nt!KeSwapProcessOrStack+0x7a

fffff48c`29d12b10 fffff800`6c5c8b2a : ffff9181`60552180 ffffbd01`a5557080 fffff800`6c52a750 00000000`00000000 : nt!PspSystemThreadStartup+0x55

fffff48c`29d12b60 00000000`00000000 : fffff48c`29d13000 fffff48c`29d0c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a





THREAD_SHA1_HASH_MOD_FUNC: 75ea4c03f873be1b2bbf6d13b885f615b6464fb3



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 01f1527208e5ec29a2a3bbf051bddc0e740f1bc5



THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84



FAULT_INSTR_CODE: f878394c



SYMBOL_STACK_INDEX: 0



SYMBOL_NAME: nt!MiInPageSingleKernelStack+3cc



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9



IMAGE_VERSION: 10.0.18362.476



STACK_COMMAND: .cxr 0xfffff48c29d11e40 ; kb



IMAGE_NAME: memory_corruption



BUCKET_ID_FUNC_OFFSET: 3cc



FAILURE_BUCKET_ID: AV_nt!MiInPageSingleKernelStack



BUCKET_ID: AV_nt!MiInPageSingleKernelStack



PRIMARY_PROBLEM_CLASS: AV_nt!MiInPageSingleKernelStack



TARGET_TIME: 2019-12-07T00:36:41.000Z



OSBUILD: 18362



OSSERVICEPACK: 476



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: 2011-12-30 00:28:41



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 29df



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:av_nt!miinpagesinglekernelstack



FAILURE_ID_HASH: {e1b83711-ad47-dba3-7e35-8cdc963be31b}



Followup: MachineOwner

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

DEC 4 02:51 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bugcheck: 0x0000007e (0xffffffffc0000005, 0xfffff8016a0e0e60, 0xfffff48b5b1125f8, 0xfffff48b5b111e40).

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff801`6a000000 PsLoadedModuleList = 0xfffff801`6a448170
Debug session time: Wed Dec 4 02:49:41.555 2019 (UTC + 1:00)
System Uptime: 0 days 0:57:19.726
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8016a0e0e60, The address that the exception occurred at
Arg3: fffff48b5b1125f8, Exception Record Address
Arg4: fffff48b5b111e40, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7978

SYSTEM_SKU: Default string

SYSTEM_VERSION: 2.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: A.A0

BIOS_DATE: 12/21/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z170A GAMING M3 (MS-7978)

BASEBOARD_VERSION: 2.0

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8016a0e0e60

BUGCHECK_P3: fffff48b5b1125f8

BUGCHECK_P4: fffff48b5b111e40

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

FAULTING_IP:
nt!MiInPageSingleKernelStack+3cc
fffff801`6a0e0e60 4c3978f8 cmp qword ptr [rax-8],r15

EXCEPTION_RECORD: fffff48b5b1125f8 -- (.exr 0xfffff48b5b1125f8)
ExceptionAddress: fffff8016a0e0e60 (nt!MiInPageSingleKernelStack+0x00000000000003cc)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff48b5b111e40 -- (.cxr 0xfffff48b5b111e40)
rax=f7fff48b5c3ef360 rbx=fffff48b5b112aa0 rcx=0200000000000000
rdx=0000000000000001 rsi=fffff48b5c3e8000 rdi=00000000000003e0
rip=fffff8016a0e0e60 rsp=fffff48b5b112830 rbp=fffff48b5b112930
r8=00000ffffffffffe r9=fffff48b5b1128b1 r10=0000000000000001
r11=fffff48b5b1128b1 r12=0200000000000002 r13=ffffe8fa45ae1f48
r14=ffffe8fa45ae1f40 r15=ffffd60fc11d5240
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!MiInPageSingleKernelStack+0x3cc:
fffff801`6a0e0e60 4c3978f8 cmp qword ptr [rax-8],r15 ds:002b:f7fff48b`5c3ef358=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

FOLLOWUP_IP:
nt!MiInPageSingleKernelStack+3cc
fffff801`6a0e0e60 4c3978f8 cmp qword ptr [rax-8],r15

BUGCHECK_STR: AV

READ_ADDRESS: fffff8016a5733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffffffffffffffff

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

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

ANALYSIS_SESSION_HOST: DESKTOP-VH5VC3R

ANALYSIS_SESSION_TIME: 12-11-2019 17:17:20.0610

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER: from fffff8016a0e055e to fffff8016a0e0e60

STACK_TEXT:
fffff48b`5b112830 fffff801`6a0e055e : ffffd60f`00000000 00000000`00000002 ffffd60f`c11d5240 00000000`00000000 : nt!MiInPageSingleKernelStack+0x3cc
fffff48b`5b112a80 fffff801`6a187f9a : 00000000`00000000 ffffd60f`00000000 00000000`00000000 00000000`00000000 : nt!KiInSwapKernelStacks+0x4e
fffff48b`5b112ad0 fffff801`6a12a7a5 : ffffd60f`95cd5080 fffff801`6a187f20 fffff801`6a46a400 fec74e7a`cc4f81c1 : nt!KeSwapProcessOrStack+0x7a
fffff48b`5b112b10 fffff801`6a1c8b2a : ffffbf81`00152180 ffffd60f`95cd5080 fffff801`6a12a750 ba647c25`f1458bdb : nt!PspSystemThreadStartup+0x55
fffff48b`5b112b60 00000000`00000000 : fffff48b`5b113000 fffff48b`5b10c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC: 75ea4c03f873be1b2bbf6d13b885f615b6464fb3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 01f1527208e5ec29a2a3bbf051bddc0e740f1bc5

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FAULT_INSTR_CODE: f878394c

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiInPageSingleKernelStack+3cc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9

IMAGE_VERSION: 10.0.18362.476

STACK_COMMAND: .cxr 0xfffff48b5b111e40 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 3cc

FAILURE_BUCKET_ID: AV_nt!MiInPageSingleKernelStack

BUCKET_ID: AV_nt!MiInPageSingleKernelStack

PRIMARY_PROBLEM_CLASS: AV_nt!MiInPageSingleKernelStack

TARGET_TIME: 2019-12-04T01:49:41.000Z

OSBUILD: 18362

OSSERVICEPACK: 476

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: 2011-12-30 00:28:41

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 29ee

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!miinpagesinglekernelstack

FAILURE_ID_HASH: {e1b83711-ad47-dba3-7e35-8cdc963be31b}

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

DEC 4 01:52 UNEXPECTED_KERNEL_MODE_TRAP
Bugcheck: 0x0000007e (0xffffffffc0000005, 0xfffff8016a0e0e60, 0xfffff48b5b1125f8, 0xfffff48b5b111e40).


Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\120419-5828-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff806`7da00000 PsLoadedModuleList = 0xfffff806`7de48170

Debug session time: Wed Dec 4 01:50:23.901 2019 (UTC + 1:00)

System Uptime: 0 days 4:22:59.255

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..................

Loading User Symbols

Loading unloaded module list

..............

For analysis of this file, run !analyze -v

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

bugcheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a *portion* of those codes:

If kv shows a taskGate

use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

use .trap on that value

Else

.trap on the appropriate frame will show where the trap was taken

(on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: fffff80682084e50

Arg3: f7fff682e6b77650

Arg4: fffff8067dbc86ea



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



SYSTEM_MANUFACTURER: MSI



SYSTEM_PRODUCT_NAME: MS-7978



SYSTEM_SKU: Default string



SYSTEM_VERSION: 2.0



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: A.A0



BIOS_DATE: 12/21/2016



BASEBOARD_MANUFACTURER: MSI



BASEBOARD_PRODUCT: Z170A GAMING M3 (MS-7978)



BASEBOARD_VERSION: 2.0



DUMP_TYPE: 2



BUGCHECK_P1: 8



BUGCHECK_P2: fffff80682084e50



BUGCHECK_P3: f7fff682e6b77650



BUGCHECK_P4: fffff8067dbc86ea



BUGCHECK_STR: 0x7f_8



TRAP_FRAME: fffff80682084e50 -- (.trap 0xfffff80682084e50)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff8067df8e9c0 rbx=0000000000000000 rcx=ffffd586ba245080

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8067dbc86ea rsp=f7fff682e6b77650 rbp=000024efbd9bbfff

r8=0000000000000118 r9=0000000000000000 r10=fffff80685ca15a0

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!SwapContext+0x1aa:

fffff806`7dbc86ea e8e158f2ff call nt!KiUpdateSpeculationControl (fffff806`7daedfd0)

Resetting default scope



CPU_COUNT: 8



CPU_MHZ: fa8



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 5e



CPU_STEPPING: 3



CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C6'00000000 (cache) C6'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: MemCompression



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: DESKTOP-VH5VC3R



ANALYSIS_SESSION_TIME: 12-11-2019 17:19:34.0289



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff8067dbd32e9 to fffff8067dbc14e0



STACK_TEXT:

fffff806`82084d08 fffff806`7dbd32e9 : 00000000`0000007f 00000000`00000008 fffff806`82084e50 f7fff682`e6b77650 : nt!KeBugCheckEx

fffff806`82084d10 fffff806`7dbce145 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69

fffff806`82084e50 fffff806`7dbc86ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5

f7fff682`e6b77650 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext+0x1aa





THREAD_SHA1_HASH_MOD_FUNC: 2dc38c3eb2f3fe5052756524c65d29ad3ccb36f3



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ba232f5a0c07c0093745b7f01775af4616758b01



THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791



FOLLOWUP_IP:

nt!KiDoubleFaultAbort+2c5

fffff806`7dbce145 90 nop



FAULT_INSTR_CODE: 6666c390



SYMBOL_STACK_INDEX: 2



SYMBOL_NAME: nt!KiDoubleFaultAbort+2c5



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 4efcf7a9



IMAGE_VERSION: 10.0.18362.476



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 2c5



FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort



BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbort



PRIMARY_PROBLEM_CLASS: 0x7f_8_nt!KiDoubleFaultAbort



TARGET_TIME: 2019-12-04T00:50:23.000Z



OSBUILD: 18362



OSSERVICEPACK: 476



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: 2011-12-30 00:28:41



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 465c



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x7f_8_nt!kidoublefaultabort



FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}



Followup: MachineOwner

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

:)

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

7 different BSoD

First off this is what I went through once I installed them 11.1 drivers . BSOD till I had to reinstall the OS .
It seems that some maybe missing the point here this STARTED for you after you installed the 11.1 drivers and then as it would seem you are getting them after a clean install of the old drivers . Correct ? If so have you wiped the HDD and did a clean install of the OS ?
If not then I would do this before thinking your cards are going out .

 

BSOD random with various different stopcodes eg DPC Violation or memor


I upgraded to Windows 10 from Windows 7 on Microsoft online upgrade offer. Shortly after the upgrade I started experiencing random BSOD. I can’t pinpoint any pattern or specific activity that triggers it. The stopcodes given also seems to vary. The most recent stopcodes given was IEQL less or not equal; DPC Watchdog violation and memory management. I can’t always see what the stopcodes are as the computer reboots quite quickly after showing the BSOD. The last stopcode a few minutes ago was Memory management. The frequency of the BSOD are quite random with some days only once or twice and at other times they come in quick succession. For the two weeks prior to the 16 Nov update on Windows 10 the computer was quite stable with no BSOD, but after the update it has returned with a vengeance.

While creating my profile I could not immediately determine the motherboard and graphics card and because the instructions said that I could add that later to my profile I created the profile without that info. I have however not been successful in updating my profile with that info, therefore I will list what I could determine from physically looking at the motherboard and graphics card.

The graphics card has the following number on a sticker on the card – D33006.G.C
The driver has the following info on the “about” in the help screen:
NIVIDIA Control Panel version 8.1.970.0
I am also running a dual screen.

The motherboard has the following markings on it:
PCI Express / ECS Elite Group / FSB 1333 / EA = 002511CCB23 / G31T-M7. Rev 1.0 and 15-V83 011000

It seems that Chrome is also having issues with frequent “page has stopped responding” error messages. However the Microsoft Edge browser and Mozilla FireFox fares no better. I am running MalwareBytes anti exploit with the browsers and my anti virus software is Avast free anti virus.

At times the screen just goes black for a while before returning to normal and at times there was a graphics error message (I can’t exactly remember the wording) That has not happened recently however, but the screen going black is quite frequent. This makes me suspect that there is some issue between NVIDIA and Windows 10, but I can’t say for sure. While posting this I experienced another BSOD stopcode Memory management and had to restart my query.

If I knew how I would have reverted back to Windows 7, but alas that is not within my know how. I am really sorry that I upgraded to Windows 10, but for now it seems that I am stuck with it. L

Sorry if this is a bit long winded, but I have tried to give as much info as possible. Any help that I can get will be appreciated. I have also attached the log file as per the instructions for posting BSOD queries.