How to fix notskrnl.exe orignated System Crash

Question

Hello, I have been troubleshooting on my own for several months. Originally thought it had to do with Display Drivers, so ran DDU to get fresh install. Thought it might be fixed upgrading to windows 11, or even insider but still get the same behavior.

Random freeze of system, leading to hard reset by myself or if I am asleep, it eventually restarts itself and I awaken to fresh log-in screen.

Here is what I have in event View:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff800452cc184, 0xffffc68112f2b900, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fe26ebcc-7e39-42bb-8460-53ac06b6244c.

When running BlueScreenView I see this pointed to as an issue (no idea why time string is like that):

ntoskrnl.exe ntoskrnl.exe+43e2a9 fffff80045000000 fffff80046047000 0x01047000 0xbae3e9d2 5/11/2069 5:51:46 AM

Then in WinDBG I ran !Anaylze -v and it gave me this:

Thank you in advance, I am in all new territory here so please let me know how I can give more information!

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff800452cc184, Address of the instruction which caused the BugCheck
Arg3: ffffc68112f2b900, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1999

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4431

    Key  : Analysis.IO.Other.Mb
    Value: 6

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 31

    Key  : Analysis.Init.CPU.mSec
    Value: 640

    Key  : Analysis.Init.Elapsed.mSec
    Value: 29227

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 102

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x3b

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x3b

    Key  : Bugcheck.Code.Register
    Value: 0x3b

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff800452cc184

BUGCHECK_P3: ffffc68112f2b900

BUGCHECK_P4: 0

CONTEXT:  ffffc68112f2b900 -- (.cxr 0xffffc68112f2b900)
rax=0000000000000002 rbx=ffff81051cbc7480 rcx=000000000081dc02
rdx=ffff81051fdaf158 rsi=ffffc68112f11180 rdi=0000000000000002
rip=fffff800452cc184 rsp=ffffde8a8935d980 rbp=0000000000000001
 r8=0000000000000002  r9=0000000000000000 r10=0000000000000001
r11=ffffb678cb000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffff81051cbc7580
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!KiCommitThreadWait+0x144:
fffff800`452cc184 c4              ???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  AUEPMaster.exe

MISALIGNED_IP: 
nt!KiCommitThreadWait+144
fffff800`452cc184 c4              ???

STACK_TEXT:  
ffffde8a`8935d980 fffff800`452c06b9     : 00000000`00000000 00000000`00000001 ffff8105`00000002 00000207`700aa023 : nt!KiCommitThreadWait+0x144
ffffde8a`8935da30 fffff800`456d2a70     : 00000000`00000000 00000000`00000001 00000000`00000000 00000013`00000002 : nt!KeDelayExecutionThread+0xf9
ffffde8a`8935dab0 fffff800`4543d9e8     : 00000013`06d5e420 00000000`00000000 ffffffff`ffffb1e0 ffff8105`00000000 : nt!NtDelayExecution+0x60
ffffde8a`8935dae0 00007fff`f86ef484     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000013`07aff8a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`f86ef484


SYMBOL_NAME:  nt!KiCommitThreadWait+144

STACK_COMMAND:  .cxr 0xffffc68112f2b900 ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_AuthenticAMD.sys

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {716d112a-8330-4bbb-160c-ec98297019d2}

Followup:     MachineOwner

Answer

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

Answer

Ntoskrnl.Exe BSOD Error on Windows 11/10 [FIXED]

Answer

Please perform the following steps in sequence:

Upgrade the BIOS to the most up to date non-beta BIOS % %
Return the page file from D: to C: during the troubleshooting % .%
Make sure that the computer is rebooted after moving the page file back to C: % %
Run: (bat scripts by default prompt antivirus software and require manual overrides) https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat Post a share link into this thread using one drive, drop box, or google drive. % %
Run Memtest86 (free version) for two tests of four passes each (total eight passes) > take pictures > post images or share links into this thread https://www.memtest86.com/ Memtest86 has a feature to create reports. If possible, please include the text or html reports with the images in the share links % %
Read this link on Windows Driver Verifier (WDV): https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands: verifier /reset verifier /bootmode resetonbootfail % %
After posting Memtest86 results start WDV testing with these settings: a. test all non-Microsoft drivers b. test no Microsoft drivers c. start the testing with the 3 customized test settings in the Ten Forums link % If there is no immediate BSOD then open administrative command prompt and type or copy and paste: verifier /querysettings Post a share link into this thread using one drive, drop box, or google drive % Plan to run WDV for 48 hours and an additional 24 hours after the last BSOD. And plan to run WDV with additional customized test settings. % Report any major performance problems including very slow boot while running WDV. % %
For any new BSOD after starting WDV post a new V2 share link into the newest post.

Answer

Please make a new restore point.
Restart WDV with the following customized tests:
If there is no immediate BSOD then post a new querysettings into the newest post
If there is any BSOD post a new V2 share link into the newest post

Answer

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00000400 IRP logging.

How to fix notskrnl.exe orignated System Crash

8 answers