Share via

Multiple BSOD Errors

Anonymous
2024-09-12T23:28:07+00:00

So I recently Installed a new CPU Motherboard and Ram, along with doing the built in upgrade to windows 11. I have had constant BSODS and driver issues. Have reinstalled wifi gpu (with DDU) and chipset drivers to no avail. I ran a memory test that came back clean (8 passes) and have updated and done the onboard reinstall of windows. I have encountered Secure Kernel Error IRQL Errors and most recently page fault in non paged area. Becasue of the windows reinstall I only have the most recent BSOD which I will paste the windbg file below with the latest minidump. My assumption is that something must be wrong with the ram.

Specs:

Motherboard: gigabyte gaming B650 X AX V2

CPU: Ryzen 7 7700x

GPU: NVIDIA RTX 3060 TI FE

RAM: G. SKILL FLARE X5 2x16GB 6000

Lastest Windbg from minidump:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.141 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

Loading Dump File [C:\Windows\Minidump\091224-8828-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff803`25c00000 PsLoadedModuleList = 0xfffff803`268134f0
Debug session time: Thu Sep 12 17:03:21.229 2024 (UTC - 6:00)
System Uptime: 0 days 1:28:35.824
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000047`3c595018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`26016000 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9f8f`b1586190=0000000000000050
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff8183d4377442, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff803263b90e7, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x208038, File: 0x2080c6 - C:\ProgramData\Dbg\sym\BTHport.sys\2AFD096C202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1686

    Key  : Analysis.Elapsed.mSec
    Value: 5460

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Bugcheck.Code.TargetModel
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_R_(null)_nt!CmKeyBodyRemapToVirtualForEnum

    Key  : Failure.Hash
    Value: {39d4694d-327c-64cf-a7fb-eb49a6d0d6dd}

BUGCHECK_CODE:  50

BUGCHECK_P1: ffff8183d4377442

BUGCHECK_P2: 0

BUGCHECK_P3: fffff803263b90e7

BUGCHECK_P4: 2

FILE_IN_CAB:  091224-8828-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffcf85cbc22080

READ_ADDRESS: fffff8032691d470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffff8183d4377442 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffff9f8fb15863b0 -- (.trap 0xffff9f8fb15863b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9f8fb15866d0 rbx=0000000000000000 rcx=ffff9f8fb1586750
rdx=ffff9f8fb1586758 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803263b90e7 rsp=ffff9f8fb1586540 rbp=ffff9f8fb1586640
 r8=0000000000000000  r9=ffff9f8fb1586730 r10=fffff80325e449f0
r11=ffff9f8fb1586968 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!CmKeyBodyRemapToVirtualForEnum+0x137:
fffff803`263b90e7 6641397642      cmp     word ptr [r14+42h],si ds:00000000`00000042=????
Resetting default scope

STACK_TEXT:  
ffff9f8f`b1586188 fffff803`26071c14     : 00000000`00000050 ffff8183`d4377442 00000000`00000000 ffff9f8f`b15863b0 : nt!KeBugCheckEx
ffff9f8f`b1586190 fffff803`25e67fdc     : 00000000`00000001 00000000`00000000 00000000`00000000 ffff8183`d4377442 : nt!MiSystemFault+0x24fb74
ffff9f8f`b1586290 fffff803`2602727e     : 00000000`00000000 ffff9f8f`b15867f0 ffff9f8f`b1586ed0 0a000005`4afd9867 : nt!MmAccessFault+0x29c
ffff9f8f`b15863b0 fffff803`263b90e7     : ffff9f8f`b1586700 00000000`00000000 ffff9f8f`b1586660 fffff803`25e6bf0f : nt!KiPageFault+0x37e
ffff9f8f`b1586540 fffff803`262e70e0     : ffffffff`00000008 00000000`00000000 00000000`00000000 00000000`00000001 : nt!CmKeyBodyRemapToVirtualForEnum+0x137
ffff9f8f`b1586970 fffff803`2602b608     : 00000000`000001ff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryValueKey+0x490
ffff9f8f`b1586c60 fffff803`2601baf0     : fffff803`26297249 00000000`00000200 00000000`00000000 00000000`000079f7 : nt!KiSystemServiceCopyEnd+0x28
ffff9f8f`b1586e68 fffff803`26297249     : 00000000`00000200 00000000`00000000 00000000`000079f7 fffff803`25fd2e41 : nt!KiServiceLinkage
ffff9f8f`b1586e70 fffff803`262970fe     : 00000000`00000000 00000000`00000200 ffff9f8f`b1586fa0 ffff9f8f`b1587050 : nt!RtlQueryRegistryValueWithFallback+0x99
ffff9f8f`b1586ed0 fffff803`2629739b     : 00000000`00000047 ffff9f8f`00000200 fffff803`00000000 00000000`000079f7 : nt!EtwpGetGuidSecurityDescriptor+0x82
ffff9f8f`b1586f30 fffff803`26295f30     : fffff803`25c0e6f8 ffffa183`e7855101 ffffa183`faa948e0 ffff9f8f`b15871a0 : nt!EtwpGetSecurityDescriptorByGuid+0xcb
ffff9f8f`b1587030 fffff803`26293994     : ffff9f8f`b15871a0 ffffcf85`00000000 ffff9f8f`b15871a0 ffffcf85`00000000 : nt!EtwpAccessCheckFromState+0x24
ffff9f8f`b15870a0 fffff803`26295e0f     : 00000000`00000000 00000000`00000001 00000000`00000038 00000000`00000000 : nt!EtwpAddRegEntryToGroup+0x354
ffff9f8f`b1587220 fffff803`26295c31     : 00000000`00000000 00000000`00000090 ffffffff`ffffffff 00000000`0132cb8a : nt!EtwpSetProviderTraitsCommon+0x1a7
ffff9f8f`b15872d0 fffff803`26294377     : ffffcf85`b878ba10 00000000`0000001e 00000000`00000005 ffffcf85`b878ba10 : nt!EtwpSetProviderTraitsUm+0x16d
ffff9f8f`b1587350 fffff803`2602b608     : 00000000`0000001e 00000047`3c2beae8 00000000`00000018 00000047`3c2beb00 : nt!NtTraceControl+0x337
ffff9f8f`b15873f0 00007ff9`01033b84     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000047`3c2beaa8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`01033b84

SYMBOL_NAME:  nt!CmKeyBodyRemapToVirtualForEnum+137

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4169

STACK_COMMAND:  .process /r /p 0xffffcf85c546d0c0; .thread 0xffffcf85cbc22080 ; kb

BUCKET_ID_FUNC_OFFSET:  137

FAILURE_BUCKET_ID:  AV_R_(null)_nt!CmKeyBodyRemapToVirtualForEnum

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {39d4694d-327c-64cf-a7fb-eb49a6d0d6dd}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-09-13T08:55:10+00:00

    Hi Ethan30017

    Welcome to Microsoft Community.

    Based on your description, I understand that you installed a new CPU, motherboard and RAM and upgraded your system to Windows 11. Constantly experiencing blue screens and driver issues, I understand exactly how you feel!

    I will start by describing for you the conclusions I came to after analyzing the dmp file:

    PAGE_FAULT_IN_NONPAGED_AREA usually indicates that it is related to memory management, and it is possible that a hardware failure, a driver failure, or a corrupted or missing system file caused the problem to occur.

    Considering that you have recently upgraded your hardware, with the errors you are currently experiencing, I will provide you with some troubleshooting suggestions:

    Option 1: Since this issue is more related to memory and since we basically install multiple memory sticks in a computer nowadays.

    You can try the following scenario:

    (1) Use only one memory stick each and turn on the computer to see if there may be a problem with one of the sticks.

    (2) After the memory sticks have been eliminated, pick a memory stick that works properly. Repeat the process by inserting it into a different motherboard slot to see if there is a possibility that the problem is caused by the motherboard slot.

    Option 2: You can try to update the BIOS through the motherboard manufacturer's official website to improve the compatibility between hardware and hardware.

    Option 3: Although you have tried running Windows Memory Diagnostics and no errors were detected. However, let me explain that this memory diagnostic is only a shallow tool and some deeper problems may not be detected.

    And I think it's possible that the memory problem is caused by increasing the load.

    So you can perform a stress test on the memory stick and do a deeper detection by using some third party application tools.

    Option 4: Since this issue involves the driver, I think you can try the Verifier driver verification program provided by Windows.

    You can refer to: Driver Verifier - Windows drivers | Microsoft Learn

    Option 5: Although you reinstalled your Windows system, the cause of this error may be due to corrupted or missing system files.

    So to be on the safe side, I'll provide you with the code to scan and repair your system.

    Click “Windows Logo Key” to open the search bar -> Type “cmd” in the search bar and open it with administrator privileges -> Please enter the following commands

    DISM /Online /Cleanup-Image /ScanHealth
    
    DISM /Online /Cleanup-Image /CheckHealth
    
    DISM /Online /Cleanup-Image /RestoreHealth
    
    SFC /Scannow
    

    Please note: The above command needs to be repeated 5-6 times to ensure that the scan is complete!

    If you still have this issue subsequently, you can provide more error messages in the dmp file and event viewer and I'll be able to do a more in-depth analysis!

    Please note: Please provide me with the dmp file and I will analyze it in depth to the specific module. I suggest you upload the dmp file to a cloud drive and include the share link in your reply, thank you very much!

    I sincerely hope that the above solution will solve your problem. Please feel free to contact me if you have any problems or still can't solve them. (Photos related to the question would be great!).

    I look forward to hearing back from you. 

    Best Regards

    Arthur Sheng | Microsoft Community Support Specialist

    0 comments No comments