A recent windows update caused my PC to begin freezing and rebooting

Page 2 of 2 FirstFirst 12

  1. Posts : 41
    Windows 10
    Thread Starter
       #11

    steve108 said:
    None of these 20 TB backups is from a clean install?
    I'm downloading the latest Windows 10 download direct from MS and installing that and going from there.
    I usually do a Clonezilla image right after I install and do the initial updates. But you can only do that once and that was some time ago now. I'd have to do all the updates (on a VERY slow ATT 1Mbps internet connection) and I don't care to do that multiple times.

    But when I talk to ASUS I want to be absolutely sure I used the latest version of Windows 10 on a brand new SSD.
      My Computer


  2. Posts : 41
    Windows 10
    Thread Starter
       #12

    MEMORY.DMP file analyzed with windbgr
    The only part I can sort of under stand is this.....


    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.


    Anyone know what it means or how to correct the issue?

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

    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 19041 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
    Machine Name:
    Kernel base = 0xfffff807`54e00000 PsLoadedModuleList = 0xfffff807`55a2a2d0
    Debug session time: Mon Jan 3 10:41:44.452 2022 (UTC - 5:00)
    System Uptime: 0 days 0:49:32.078
    Loading Kernel Symbols
    ...............................................................
    ........Page 33be not present in the dump file. Type ".hh dbgerr004" for details
    ........................................................
    ..............................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000039`81355018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .........
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff807`551f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff581`99d0ea70=0000000000000050
    6: kd> .hh-dbgerr001
    ^ Syntax error in '.hh-dbgerr001'
    windbg> .hh dbgerr001
    6: 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: fffff58139d0f050, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff807553ee2be, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)

    Debugging Details:
    ------------------
    KEY_VALUES_STRING: 1

    Key : AV.Type
    Value: Read

    Key : Analysis.CPU.mSec
    Value: 3265

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 11708

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

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

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

    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


    FILE_IN_CAB: MEMORY.DMP

    BUGCHECK_CODE: 50

    BUGCHECK_P1: fffff58139d0f050

    BUGCHECK_P2: 0

    BUGCHECK_P3: fffff807553ee2be

    BUGCHECK_P4: 2

    READ_ADDRESS: fffff58139d0f050

    MM_INTERNAL_CODE: 2

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    PROCESS_NAME: chromium.exe

    TRAP_FRAME: fffff58199d0ed10 -- (.trap 0xfffff58199d0ed10)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff807553ee2be rsp=fffff58199d0eea0 rbp=fffff58199d0efa0
    r8=00000000ffffffff r9=7ffff80755a483b8 r10=7ffffffffffffffc
    r11=fffff58199d0ed60 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!CmpParseKey+0x25e:
    fffff807`553ee2be 488b9db0000000 mov rbx,qword ptr [rbp+0B0h] ss:0018:fffff581`99d0f050=ffffaf8e2c946500
    Resetting default scope

    STACK_TEXT:
    fffff581`99d0ea68 fffff807`5524a56f : 00000000`00000050 fffff581`39d0f050 00000000`00000000 fffff581`99d0ed10 : nt!KeBugCheckEx
    fffff581`99d0ea70 fffff807`5509f390 : fffff581`99d0ec60 00000000`00000000 fffff581`99d0ed90 00000000`00000000 : nt!MiSystemFault+0x18d1bf
    fffff581`99d0eb70 fffff807`5520545e : 41c64e6d`a3f16945 fffff807`553f5f01 00000001`00580002 00000001`00140000 : nt!MmAccessFault+0x400
    fffff581`99d0ed10 fffff807`553ee2be : 00000000`0000001c fffff581`99d0ef50 fffff581`99d0ef08 00000000`ffffff01 : nt!KiPageFault+0x35e
    fffff581`99d0eea0 fffff807`553f23ee : fffff807`553ee000 00000000`00000000 ffffaf8e`2c946500 00000000`00000000 : nt!CmpParseKey+0x25e
    fffff581`99d0f040 fffff807`554948aa : ffffaf8e`2c946500 fffff581`99d0f2a8 00000000`00000240 ffffaf8e`230f8f00 : nt!ObpLookupObjectName+0x3fe
    fffff581`99d0f210 fffff807`5549468c : 00000000`00000000 00000000`00000000 00000000`00000000 ffffaf8e`230f8f00 : nt!ObOpenObjectByNameEx+0x1fa
    fffff581`99d0f340 fffff807`554941b1 : fffff581`99d0f810 fffff581`99d0f6b0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x5c
    fffff581`99d0f390 fffff807`554e3212 : 00000000`00000000 ffffaf8e`30cc3700 fffff581`99d0f6d0 fffff581`99d0f690 : nt!CmOpenKey+0x2c1
    fffff581`99d0f5f0 fffff807`55208cb8 : 00000000`00000000 fffff807`55442d74 ffff9302`a10a6030 fffff581`99d0faa0 : nt!NtOpenKey+0x12
    fffff581`99d0f630 fffff807`551fb100 : fffff807`5a26d290 ffffaf8e`33156e90 fffff807`55008633 00000000`0000002c : nt!KiSystemServiceCopyEnd+0x28
    fffff581`99d0f7c8 fffff807`5a26d290 : ffffaf8e`33156e90 fffff807`55008633 00000000`0000002c fffff807`00000000 : nt!KiServiceLinkage
    fffff581`99d0f7d0 fffff807`5a26c268 : ffff9302`00000000 fffff581`00000000 fffff581`99d0f8c0 00000000`00000000 : bam!BampUserSettingsOpenUserKey+0x70
    fffff581`99d0f860 fffff807`5a26b5ea : ffff9302`a32ecb30 00000000`00000000 00000000`00000000 00000000`00000000 : bam!BamUserSettingsGet+0x88
    fffff581`99d0f9a0 fffff807`5a26ab60 : 00000000`00000000 00000000`00000000 fffff581`99d0fb50 ffffaf8e`339d7080 : bam!BampStartThrottledProcessInformation+0xca
    fffff581`99d0fa50 fffff807`5a26a717 : fffff807`55aec538 00000000`0000000b fffff581`99d0fc70 00000000`00000001 : bam!BampThrottlingRegisterProcessEx+0x1e0
    fffff581`99d0fc00 fffff807`554029e5 : 00000000`00002910 fffff581`99d0fc70 ffffaf8e`2c3c3801 ffffaf8e`339d7080 : bam!BampCreateProcessCallback+0x27
    fffff581`99d0fc30 fffff807`554ae9c2 : ffffffff`00000000 fffff581`99d10a10 fffff581`99d10301 ffffaf8e`33d40270 : nt!PspCallProcessNotifyRoutines+0x1a9
    fffff581`99d0fd00 fffff807`5541577d : ffffaf8e`339d8080 ffffaf8e`339d7080 fffff581`99d10490 fffff581`99d1035c : nt!PspInsertThread+0x68e
    fffff581`99d0fdc0 fffff807`55208cb8 : 00000000`00000002 00000000`00000001 00000000`00000000 00000169`662725d0 : nt!NtCreateUserProcess+0xddd
    fffff581`99d10a90 00007ff9`9650e664 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    00000039`8fbfd428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`9650e664


    SYMBOL_NAME: bam!BampUserSettingsOpenUserKey+70

    MODULE_NAME: bam

    IMAGE_NAME: bam.sys

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 70

    FAILURE_BUCKET_ID: AV_R_(null)_bam!BampUserSettingsOpenUserKey

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {c46c4ce7-0f40-035b-1e44-aff62d44c6c8}

    Followup: MachineOwner
    ---------
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:37.
Find Us




Windows 10 Forums