Windows 10: Random BSOD Kernal 41 Error

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 AMD64Copyright 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 LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff805`38a00000 PsLoadedModuleList = 0xfffff805`3962a2b0Debug session time: Tue Dec 29 03:18:05.861 2020 UTC - 5:00System Uptime: 9 days 4:14:43.610Loading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff805`38df5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe18a`08d372e0=000000000000000a9: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 000000000002abfc, memory referencedArg2: 00000000000000ff, IRQLArg3: 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 statusArg4: fffff80538dfc7a7, address which referenced memoryDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: aBUGCHECK_P1: 2abfcBUGCHECK_P2: ffBUGCHECK_P3: c6BUGCHECK_P4: fffff80538dfc7a7READ_ADDRESS: fffff805396fa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8053960f330: Unable to get Flags value from nt!KdVersionBlockfffff8053960f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 000000000002abfc BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: Phasmophobia.exeTRAP_FRAME: ffffe18a08d37420 -- .trap 0xffffe18a08d37420NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000a5a rbx=0000000000000000 rcx=000000000002abfcrdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff80538dfc7a7 rsp=ffffe18a08d375b0 rbp=ffffe18a08d37770 r8=0000000000000a5a r9=ffffbf8e619162c0 r10=fffff80538df1870r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up di pl nz na pe ncnt!KxDispatchInterrupt+0x1a7:fffff805`38dfc7a7 488bd7 mov rdx,rdiResetting default scopeSTACK_TEXT: ffffe18a`08d372d8 fffff805`38e07769 : 00000000`0000000a 00000000`0002abfc 00000000`000000ff 00000000`000000c6 : nt!KeBugCheckExffffe18a`08d372e0 fffff805`38e03a69 : 00000000`00000001 00000000`0000002f 00000000`00000002 ffffa880`9f388180 : nt!KiBugCheckDispatch+0x69ffffe18a`08d37420 fffff805`38dfc7a7 : 00000000`00000000 ffffa880`9f5ea180 00000000`0000ffff 00000000`00000000 : nt!KiPageFault+0x469ffffe18a`08d375b0 fffff805`38dfbc7e : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxDispatchInterrupt+0x1a7ffffe18a`08d376f0 fffff805`3902aecb : ffffffff`ffffffff ffffa880`9fe81180 ffffa880`9fe81180 ffffcf8e`6f535340 : nt!KiDpcInterrupt+0x2eeffffe18a`08d37880 fffff805`3902ad01 : ffffcf8e`66dde340 ffffe18a`00100000 00000000`00000000 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0x17bffffe18a`08d37910 fffff805`3902c658 : ffffe18a`08d379e8 00000000`00000000 00000000`00000001 ffffcf8e`00000000 : nt!ObReferenceObjectByHandleWithTag+0x31ffffe18a`08d37960 fffff805`3902c74a : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 ffffcf8e`776c46e0 : nt!ObWaitForSingleObject+0x48ffffe18a`08d379c0 fffff805`38e071b5 : ffffcf8e`6f535340 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWaitForSingleObject+0x6affffe18a`08d37a00 00007ffb`49e6c034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25000000d5`ba2ff958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`49e6c034SYMBOL_NAME: nt!KxDispatchInterrupt+1a7MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.685STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1a7FAILURE_BUCKET_ID: AV_CODE_AV_nt!KxDispatchInterruptOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {9daaa980-1818-188e-1a8b-f7b60be01571}Followup: MachineOwner---------


Dump file 2:


************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`15e00000 PsLoadedModuleList = 0xfffff806`16a2a2b0Debug session time: Fri Dec 18 22:58:53.174 2020 UTC - 5:00System Uptime: 8 days 5:09:45.255Loading Kernel Symbols........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff806`161f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb100`66bbc0f0=000000000000007e13: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 1000007eThis is a very common bugcheck. Usually the exception address pinpointsthe driver/function that caused the problem. Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003. This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG. This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG. This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8061606457e, The address that the exception occurred atArg3: ffff81856419f6c8, Exception Record AddressArg4: ffffb10066bbc920, Context Record AddressDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7eBUGCHECK_P1: ffffffffc0000005BUGCHECK_P2: fffff8061606457eBUGCHECK_P3: ffff81856419f6c8BUGCHECK_P4: ffffb10066bbc920EXCEPTION_RECORD: ffff81856419f6c8 -- .exr 0xffff81856419f6c8ExceptionAddress: fffff8061606457e nt!KeWaitForSingleObject+0x000000000000018e ExceptionCode: c0000005 Access violation ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT: ffffb10066bbc920 -- .cxr 0xffffb10066bbc920rax=0000000002b52650 rbx=ffff8b8d2ae6d040 rcx=ffffb10066b63180rdx=0000000000000000 rsi=0000000000000000 rdi=ffff7472d543226frip=fffff8061606457e rsp=ffff81856419f900 rbp=ffff81856419f991 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000r11=fffff780000003b0 r12=0000000000000000 r13=ffffb10066b63180r14=0000000000000000 r15=ffff8b8d2ae6d180iopl=0 nv up ei pl zr na po nccs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246nt!KeWaitForSingleObject+0x18e:fffff806`1606457e f00fba2f07 lock bts dword ptr [rdi],7 ds:002b:ffff7472`d543226f=????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemREAD_ADDRESS: fffff80616afa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff80616a0f330: Unable to get Flags value from nt!KdVersionBlockfffff80616a0f330: Unable to get Flags value from nt!KdVersionBlockunable 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: c0000005EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: ffffffffffffffffEXCEPTION_STR: 0xc0000005BAD_STACK_POINTER: ffffb10066bbc0e8STACK_TEXT: ffff8185`6419f900 fffff806`2f9e2471 : ffff7472`d543226f ffff8b8d`00000000 00000000`00000000 ffff8b8d`3a90e801 : nt!KeWaitForSingleObject+0x18effff8185`6419f9f0 fffff806`2f9e2f29 : 00000000`00000010 00000000`00000015 00000000`0000000c fffff806`2f9e7150 : mmcss!CiSchedulerWait+0x2d1ffff8185`6419fac0 fffff806`16117e25 : ffff8b8d`00000010 ffff8b8d`2ae6d040 00000000`00000080 fffff806`2f9e2d50 : mmcss!CiSchedulerThreadFunction+0x1d9ffff8185`6419fb10 fffff806`161fcdd8 : ffffb100`66b63180 ffff8b8d`2ae6d040 fffff806`16117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffff8185`6419fb60 00000000`00000000 : ffff8185`641a0000 ffff8185`64199000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: mmcss!CiSchedulerWait+2d1MODULE_NAME: mmcssIMAGE_NAME: mmcss.sysIMAGE_VERSION: 10.0.19041.546STACK_COMMAND: .cxr 0xffffb10066bbc920 ; kbBUCKET_ID_FUNC_OFFSET: 2d1FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_mmcss!CiSchedulerWaitOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_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 thismultiple times a day while Idle and seemed to be fixed somewhat by changing power setting turn off hard disk after 0mins.

:)

 

Event ID 41 Power Kernal Error Crashes

Startup and Recovery

 

Event ID 41 Power Kernal Error Crashes

I have tested the memory in MemTest as a set, twice. The first time for 5 passes and the second time for 10 passes, with zero errors both times. This time I will test them individually. Should I do two sets for each stick (four and four), or four for one and four for the other?

Attached are some screen shots from HWMonitor of current info after running verifier for 11 hours with YouTube playing in the background.










- - - Updated - - -

Side note, temps are probably a tad higher than normal because my A/C is broken (I live in AZ), and it's around 82 in my house, which is higher than usual.

 

Event ID 41 Power Kernal Error Crashes

Both cards perform identically in either computer. They both crash during gaming in the problematic computer, neither crash gaming in my other computer. They both run for hours with no issues running verifier, but both crash if you select the low resources option in verifier.

I thought it made sense to test the system having problems in it's normal configuration, since it responds exactly the same with both cards. If that logic is incorrect, I apologize.

Also, the reason I ran Furmark before PC95 was because I had an hour to run a test and instructions said to run PCMark for 3 hours, so I ran Furmark first.

- - - Updated - - -

Put card B back in the problematic computer and ran Furmark. Had to stop it because it climbed to 87 degrees shortly after starting.





- - - Updated - - -

Prime95 was running really warm as well. It could be because I am still waiting for my A/C to get repaired and the ambient temp is over 80 degrees in my house. I ran OCCT for 1.5 hours with no errors detected (CPU stayed around 74).




- - - Updated - - -

MemTest Results; both sticks, two tests, four passes each.







- - - Updated - - -

The temps in the house finally dropped, so I tried Prime95 again. It still ran a little warm (83), but I ran it for 32 min with no errors.