M
maouslime
Hello,
I was having Kernel Error 41s problem and BSOD. Error in the blue screen is normally thread exception.
Here is a reading of the mini dump file:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122920-10390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`38a00000 PsLoadedModuleList = 0xfffff805`3962a2b0
Debug session time: Tue Dec 29 03:18:05.861 2020 (UTC - 5:00)
System Uptime: 9 days 4:14:43.610
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`38df5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe18a`08d372e0=000000000000000a
9: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000002abfc, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c6, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80538dfc7a7, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2624
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4GRQCLS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7726
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 2abfc
BUGCHECK_P2: ff
BUGCHECK_P3: c6
BUGCHECK_P4: fffff80538dfc7a7
READ_ADDRESS: fffff805396fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8053960f330: Unable to get Flags value from nt!KdVersionBlock
fffff8053960f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000002abfc
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Phasmophobia.exe
TRAP_FRAME: ffffe18a08d37420 -- (.trap 0xffffe18a08d37420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000a5a rbx=0000000000000000 rcx=000000000002abfc
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80538dfc7a7 rsp=ffffe18a08d375b0 rbp=ffffe18a08d37770
r8=0000000000000a5a r9=ffffbf8e619162c0 r10=fffff80538df1870
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KxDispatchInterrupt+0x1a7:
fffff805`38dfc7a7 488bd7 mov rdx,rdi
Resetting default scope
STACK_TEXT:
ffffe18a`08d372d8 fffff805`38e07769 : 00000000`0000000a 00000000`0002abfc 00000000`000000ff 00000000`000000c6 : nt!KeBugCheckEx
ffffe18a`08d372e0 fffff805`38e03a69 : 00000000`00000001 00000000`0000002f 00000000`00000002 ffffa880`9f388180 : nt!KiBugCheckDispatch+0x69
ffffe18a`08d37420 fffff805`38dfc7a7 : 00000000`00000000 ffffa880`9f5ea180 00000000`0000ffff 00000000`00000000 : nt!KiPageFault+0x469
ffffe18a`08d375b0 fffff805`38dfbc7e : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxDispatchInterrupt+0x1a7
ffffe18a`08d376f0 fffff805`3902aecb : ffffffff`ffffffff ffffa880`9fe81180 ffffa880`9fe81180 ffffcf8e`6f535340 : nt!KiDpcInterrupt+0x2ee
ffffe18a`08d37880 fffff805`3902ad01 : ffffcf8e`66dde340 ffffe18a`00100000 00000000`00000000 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0x17b
ffffe18a`08d37910 fffff805`3902c658 : ffffe18a`08d379e8 00000000`00000000 00000000`00000001 ffffcf8e`00000000 : nt!ObReferenceObjectByHandleWithTag+0x31
ffffe18a`08d37960 fffff805`3902c74a : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 ffffcf8e`776c46e0 : nt!ObWaitForSingleObject+0x48
ffffe18a`08d379c0 fffff805`38e071b5 : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
ffffe18a`08d37a00 00007ffb`49e6c034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d5`ba2ff958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`49e6c034
SYMBOL_NAME: nt!KxDispatchInterrupt+1a7
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1a7
FAILURE_BUCKET_ID: AV_CODE_AV_nt!KxDispatchInterrupt
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9daaa980-1818-188e-1a8b-f7b60be01571}
Followup: MachineOwner
---------
Dump file 2:
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`15e00000 PsLoadedModuleList = 0xfffff806`16a2a2b0
Debug session time: Fri Dec 18 22:58:53.174 2020 (UTC - 5:00)
System Uptime: 8 days 5:09:45.255
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`161f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb100`66bbc0f0=000000000000007e
13: 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: fffff8061606457e, The address that the exception occurred at
Arg3: ffff81856419f6c8, Exception Record Address
Arg4: ffffb10066bbc920, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2656
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4GRQCLS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 5149
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8061606457e
BUGCHECK_P3: ffff81856419f6c8
BUGCHECK_P4: ffffb10066bbc920
EXCEPTION_RECORD: ffff81856419f6c8 -- (.exr 0xffff81856419f6c8)
ExceptionAddress: fffff8061606457e (nt!KeWaitForSingleObject+0x000000000000018e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffb10066bbc920 -- (.cxr 0xffffb10066bbc920)
rax=0000000002b52650 rbx=ffff8b8d2ae6d040 rcx=ffffb10066b63180
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff7472d543226f
rip=fffff8061606457e rsp=ffff81856419f900 rbp=ffff81856419f991
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=fffff780000003b0 r12=0000000000000000 r13=ffffb10066b63180
r14=0000000000000000 r15=ffff8b8d2ae6d180
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!KeWaitForSingleObject+0x18e:
fffff806`1606457e f00fba2f07 lock bts dword ptr [rdi],7 ds:002b:ffff7472`d543226f=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80616afa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80616a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80616a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
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
EXCEPTION_STR: 0xc0000005
BAD_STACK_POINTER: ffffb10066bbc0e8
STACK_TEXT:
ffff8185`6419f900 fffff806`2f9e2471 : ffff7472`d543226f ffff8b8d`00000000 00000000`00000000 ffff8b8d`3a90e801 : nt!KeWaitForSingleObject+0x18e
ffff8185`6419f9f0 fffff806`2f9e2f29 : 00000000`00000010 00000000`00000015 00000000`0000000c fffff806`2f9e7150 : mmcss!CiSchedulerWait+0x2d1
ffff8185`6419fac0 fffff806`16117e25 : ffff8b8d`00000010 ffff8b8d`2ae6d040 00000000`00000080 fffff806`2f9e2d50 : mmcss!CiSchedulerThreadFunction+0x1d9
ffff8185`6419fb10 fffff806`161fcdd8 : ffffb100`66b63180 ffff8b8d`2ae6d040 fffff806`16117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8185`6419fb60 00000000`00000000 : ffff8185`641a0000 ffff8185`64199000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: mmcss!CiSchedulerWait+2d1
MODULE_NAME: mmcss
IMAGE_NAME: mmcss.sys
IMAGE_VERSION: 10.0.19041.546
STACK_COMMAND: .cxr 0xffffb10066bbc920 ; kb
BUCKET_ID_FUNC_OFFSET: 2d1
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_mmcss!CiSchedulerWait
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {83a1962f-618c-b70a-a759-8817ce688583}
Followup: MachineOwner
---------
If someone can let me know what is causing it I will be very appreciated.
My specs are as followed:
RAM:32GB
CPU:I7-10700k
GPU:RTX-3080Motherboard:Asus Prime Z490-P
Note: File 2 was before file 1, steps I took between the two incidents were updating Nvidia Driver to 460.89 but I got another BSOD 10 days after. Both occurred while playing Phasmaphobia as ghost appeared to kill me.
I was having constant BSOD before this(multiple times a day while Idle) and seemed to be fixed somewhat by changing power setting (turn off hard disk after 0mins).
Continue reading...
I was having Kernel Error 41s problem and BSOD. Error in the blue screen is normally thread exception.
Here is a reading of the mini dump file:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122920-10390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`38a00000 PsLoadedModuleList = 0xfffff805`3962a2b0
Debug session time: Tue Dec 29 03:18:05.861 2020 (UTC - 5:00)
System Uptime: 9 days 4:14:43.610
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`38df5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe18a`08d372e0=000000000000000a
9: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000002abfc, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c6, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80538dfc7a7, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2624
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4GRQCLS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 7726
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 2abfc
BUGCHECK_P2: ff
BUGCHECK_P3: c6
BUGCHECK_P4: fffff80538dfc7a7
READ_ADDRESS: fffff805396fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8053960f330: Unable to get Flags value from nt!KdVersionBlock
fffff8053960f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000002abfc
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Phasmophobia.exe
TRAP_FRAME: ffffe18a08d37420 -- (.trap 0xffffe18a08d37420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000a5a rbx=0000000000000000 rcx=000000000002abfc
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80538dfc7a7 rsp=ffffe18a08d375b0 rbp=ffffe18a08d37770
r8=0000000000000a5a r9=ffffbf8e619162c0 r10=fffff80538df1870
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KxDispatchInterrupt+0x1a7:
fffff805`38dfc7a7 488bd7 mov rdx,rdi
Resetting default scope
STACK_TEXT:
ffffe18a`08d372d8 fffff805`38e07769 : 00000000`0000000a 00000000`0002abfc 00000000`000000ff 00000000`000000c6 : nt!KeBugCheckEx
ffffe18a`08d372e0 fffff805`38e03a69 : 00000000`00000001 00000000`0000002f 00000000`00000002 ffffa880`9f388180 : nt!KiBugCheckDispatch+0x69
ffffe18a`08d37420 fffff805`38dfc7a7 : 00000000`00000000 ffffa880`9f5ea180 00000000`0000ffff 00000000`00000000 : nt!KiPageFault+0x469
ffffe18a`08d375b0 fffff805`38dfbc7e : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxDispatchInterrupt+0x1a7
ffffe18a`08d376f0 fffff805`3902aecb : ffffffff`ffffffff ffffa880`9fe81180 ffffa880`9fe81180 ffffcf8e`6f535340 : nt!KiDpcInterrupt+0x2ee
ffffe18a`08d37880 fffff805`3902ad01 : ffffcf8e`66dde340 ffffe18a`00100000 00000000`00000000 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0x17b
ffffe18a`08d37910 fffff805`3902c658 : ffffe18a`08d379e8 00000000`00000000 00000000`00000001 ffffcf8e`00000000 : nt!ObReferenceObjectByHandleWithTag+0x31
ffffe18a`08d37960 fffff805`3902c74a : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 ffffcf8e`776c46e0 : nt!ObWaitForSingleObject+0x48
ffffe18a`08d379c0 fffff805`38e071b5 : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6a
ffffe18a`08d37a00 00007ffb`49e6c034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000d5`ba2ff958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`49e6c034
SYMBOL_NAME: nt!KxDispatchInterrupt+1a7
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1a7
FAILURE_BUCKET_ID: AV_CODE_AV_nt!KxDispatchInterrupt
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9daaa980-1818-188e-1a8b-f7b60be01571}
Followup: MachineOwner
---------
Dump file 2:
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`15e00000 PsLoadedModuleList = 0xfffff806`16a2a2b0
Debug session time: Fri Dec 18 22:58:53.174 2020 (UTC - 5:00)
System Uptime: 8 days 5:09:45.255
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`161f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb100`66bbc0f0=000000000000007e
13: 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: fffff8061606457e, The address that the exception occurred at
Arg3: ffff81856419f6c8, Exception Record Address
Arg4: ffffb10066bbc920, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 2656
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4GRQCLS
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 5149
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8061606457e
BUGCHECK_P3: ffff81856419f6c8
BUGCHECK_P4: ffffb10066bbc920
EXCEPTION_RECORD: ffff81856419f6c8 -- (.exr 0xffff81856419f6c8)
ExceptionAddress: fffff8061606457e (nt!KeWaitForSingleObject+0x000000000000018e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: ffffb10066bbc920 -- (.cxr 0xffffb10066bbc920)
rax=0000000002b52650 rbx=ffff8b8d2ae6d040 rcx=ffffb10066b63180
rdx=0000000000000000 rsi=0000000000000000 rdi=ffff7472d543226f
rip=fffff8061606457e rsp=ffff81856419f900 rbp=ffff81856419f991
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=fffff780000003b0 r12=0000000000000000 r13=ffffb10066b63180
r14=0000000000000000 r15=ffff8b8d2ae6d180
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!KeWaitForSingleObject+0x18e:
fffff806`1606457e f00fba2f07 lock bts dword ptr [rdi],7 ds:002b:ffff7472`d543226f=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80616afa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80616a0f330: Unable to get Flags value from nt!KdVersionBlock
fffff80616a0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
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
EXCEPTION_STR: 0xc0000005
BAD_STACK_POINTER: ffffb10066bbc0e8
STACK_TEXT:
ffff8185`6419f900 fffff806`2f9e2471 : ffff7472`d543226f ffff8b8d`00000000 00000000`00000000 ffff8b8d`3a90e801 : nt!KeWaitForSingleObject+0x18e
ffff8185`6419f9f0 fffff806`2f9e2f29 : 00000000`00000010 00000000`00000015 00000000`0000000c fffff806`2f9e7150 : mmcss!CiSchedulerWait+0x2d1
ffff8185`6419fac0 fffff806`16117e25 : ffff8b8d`00000010 ffff8b8d`2ae6d040 00000000`00000080 fffff806`2f9e2d50 : mmcss!CiSchedulerThreadFunction+0x1d9
ffff8185`6419fb10 fffff806`161fcdd8 : ffffb100`66b63180 ffff8b8d`2ae6d040 fffff806`16117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8185`6419fb60 00000000`00000000 : ffff8185`641a0000 ffff8185`64199000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: mmcss!CiSchedulerWait+2d1
MODULE_NAME: mmcss
IMAGE_NAME: mmcss.sys
IMAGE_VERSION: 10.0.19041.546
STACK_COMMAND: .cxr 0xffffb10066bbc920 ; kb
BUCKET_ID_FUNC_OFFSET: 2d1
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_mmcss!CiSchedulerWait
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {83a1962f-618c-b70a-a759-8817ce688583}
Followup: MachineOwner
---------
If someone can let me know what is causing it I will be very appreciated.
My specs are as followed:
RAM:32GB
CPU:I7-10700k
GPU:RTX-3080Motherboard:Asus Prime Z490-P
Note: File 2 was before file 1, steps I took between the two incidents were updating Nvidia Driver to 460.89 but I got another BSOD 10 days after. Both occurred while playing Phasmaphobia as ghost appeared to kill me.
I was having constant BSOD before this(multiple times a day while Idle) and seemed to be fixed somewhat by changing power setting (turn off hard disk after 0mins).
Continue reading...