Share via

Windows 10 BSOD Help

Anonymous
2024-06-04T18:26:05+00:00

Hi, I need help with some BSOD errors I've had.
A couple weeks back, I was getting BSOD's every couple days (if I remember correctly, the error was PFN_LIST_CORRUPT) so I decided to reinstall Windows on a clean drive. Everything was working fine until this morning, when I BSOD a couple mins after startup.
Sys info and Minidump: https://drive.google.com/file/d/1GsVGobg2vHVi16X6LJPpDxJakK1QU_M9/view?usp=drive_link

Here is the bugcheck:

Microsoft (R) Windows Debugger Version 10.0.27553.1004 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 (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff80325e00000 PsLoadedModuleList = 0xfffff80326a2a7c0 Debug session time: Tue Jun 4 12:14:07.491 2024 (UTC + 1:00) System Uptime: 0 days 20:46:34.114 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........ Loading User Symbols PEB is paged out (Peb.Ldr = 000000f29d03b018). Type ".hh dbgerr001" for details Loading unloaded module list ................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803261fdaf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8d8a`4bb1e050=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: fffffffffffffff7, 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: fffff803260315f0, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved)

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0xd94f, File: 0x72fd - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key  : AV.Type
Value: Read

Key  : Analysis.CPU.mSec
Value: 3639

Key  : Analysis.Elapsed.mSec
Value: 7123

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

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

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

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

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

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

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x50

Key  : Bugcheck.Code.LegacyAPI
Value: 0x50

Key  : Bugcheck.Code.TargetModel
Value: 0x50

Key  : Failure.Bucket
Value: AV\_R\_(null)\_nt!RtlpHpVsChunkSplit

Key  : Failure.Hash
Value: {12526db6-e4fb-55be-2865-7837579713ad}

Key  : Hypervisor.Enlightenments.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 16908288

Key  : Hypervisor.Flags.ValueHex
Value: 1020000

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 50

BUGCHECK_P1: fffffffffffffff7

BUGCHECK_P2: 0

BUGCHECK_P3: fffff803260315f0

BUGCHECK_P4: 2

FILE_IN_CAB: MEMORY.DMP

READ_ADDRESS: unable to get nt!PspSessionIdBitmap fffffffffffffff7

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: svchost.exe

TRAP_FRAME: ffff8d8a4bb1e2f0 -- (.trap 0xffff8d8a4bb1e2f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffffff rbx=0000000000000000 rcx=00000000db2629c6 rdx=00000000db262e26 rsi=0000000000000000 rdi=0000000000000000 rip=fffff803260315f0 rsp=ffff8d8a4bb1e480 rbp=ffff8d8a4bb1e4f8 r8=610b05db4b3e89d9 r9=0000000000000000 r10=00000000000000dc r11=00000000000000dc r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!RtlpHpVsChunkSplit+0x590: fffff803260315f0 8b4bf8 mov ecx,dword ptr [rbx-8] ds:fffffffffffffff8=???????? Resetting default scope

STACK_TEXT:
ffff8d8a4bb1e048 fffff8032623921b : 0000000000000050 fffffffffffffff7 0000000000000000 ffff8d8a4bb1e2f0 : nt!KeBugCheckEx ffff8d8a4bb1e050 fffff8032601c270 : 0000000000000111 0000000000000000 ffff8d8a4bb1e370 0000000000000000 : nt!MiSystemFault+0x1de1db ffff8d8a4bb1e150 fffff8032620dc6d : 0000000000000000 ffff8d8a4bb1e370 0000000000000082 0000000000001000 : nt!MmAccessFault+0x400 ffff8d8a4bb1e2f0 fffff803260315f0 : 0000000000000000 ffff8d8a4bb1e4f8 0000000000000082 0000000000000082 : nt!KiPageFault+0x36d ffff8d8a4bb1e480 fffff80326030e8a : 000100820000db26 ffffaa0e6fe25560 0000000000000280 0000000000000000 : nt!RtlpHpVsChunkSplit+0x590 ffff8d8a4bb1e540 fffff8032612014d : ffffaa0e6aee87d0 0000000000000800 ffffaa0e5d600280 ffffaa0e6fe74000 : nt!RtlpHpVsContextAllocateInternal+0x1fa ffff8d8a4bb1e5a0 fffff8032602efa0 : fffff80326a58c40 ffff8d8a4bb1e701 0000000000000001 fffff803267b7074 : nt!RtlpHpVsContextMultiAlloc+0x69 ffff8d8a4bb1e620 fffff803267b7074 : ffff9887f8f93410 0000000000000050 00000000656b6f54 0000000000000000 : nt!ExAllocateHeapPool+0xa70 ffff8d8a4bb1e760 fffff8032642ea19 : ffff9887d30b34e0 0000000000000000 0000000000000000 0000000000000000 : nt!ExAllocatePoolWithTag+0x64 ffff8d8a4bb1e7b0 fffff8032640944c : ffff988700000008 ffff9887d3095f00 0000000000000000 ffff8d8a4bb1e870 : nt!ObpAllocateObject+0x199 ffff8d8a4bb1e830 fffff80326408ac6 : ffffaa0e649c6060 ffff9887fada4890 0000000000000000 0000000000000000 : nt!ObCreateObjectEx+0xfc ffff8d8a4bb1e8b0 fffff80326406ec4 : ffff8d8a4bb1eb80 ffff8d8a4bb1ea30 ffff8d8a4bb1eb00 000000f20000076c : nt!SepDuplicateToken+0x1a6 ffff8d8a4bb1e9a0 fffff80326406a81 : ffff9887e68cb080 000001f502000000 000001f5a0090301 0000000000000000 : nt!NtOpenThreadTokenEx+0x434 ffff8d8a4bb1eac0 fffff80326211b08 : ffff9887e68cb080 ffff9887e3c4fa80 000001f5a0027310 0000000000001ed0 : nt!NtOpenThreadToken+0x11 ffff8d8a4bb1eb00 00007fff9544d534 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000f29d7fef38 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff`9544d534

SYMBOL_NAME: nt!RtlpHpVsChunkSplit+590

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 590

FAILURE_BUCKET_ID: AV_R_(null)_nt!RtlpHpVsChunkSplit

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {12526db6-e4fb-55be-2865-7837579713ad}

Followup: MachineOwner

Looking forward to your responses.
Thanks,
Emmanuel

Windows for home | Windows 10 | 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

Answer accepted by question author

Anonymous
2024-06-05T19:55:53+00:00

The BSOD is being caused by "vgk.sys" which is related to Valorant Vanguard.

Try uninstalling Vanguard anti-cheat and see if the problem persists.

Was this answer helpful?

1 person found this answer helpful.
0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-06-06T09:52:35+00:00

    Hi Jonathan,

    Thanks for identifying the BSOD isssue for me, I really appreciate it.
    I have uninstalled Vanguard.

    Thanks for helping,
    Emmanuel

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-06-05T15:00:35+00:00

    Hi Jonathan, thanks for your reply. I apologise for replying in an untimely manner.

    The minidumps were created, here they are: https://drive.google.com/file/d/14_ZMRyeKVgc7Bzbgx4I75rYohXe7JpmG/view?usp=drive_link
    Looking     forward to hearing from you.

    Thanks,
    Emmanuel

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-06-04T22:12:31+00:00

    My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you today.

    The minidump files do not indicate any driver or hardware causes, only memory corruption.

    Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this.

    Make the BSOD happen 3 times and then see if the files were created.

    Before running Driver Verifier, create a new system restore point.

    https://answers.microsoft.com/en-us/windows/for...

    If you have problems starting Windows after enabling Driver Verifier, follow these steps:

    Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

    Do this two or three times.

    Windows will boot into the Recovery Environment.

    Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

    When restarting, press 4 to enter safe mode.

    Open command prompt as administrator, run these two commands and restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments