Share via

BSOD w/dmp file

Anonymous
2023-01-13T16:39:50+00:00

Have been playing COD Modern Warfare II the past couple days and had a BSOD. Any help identifying the problem would be appreciated. DMP results:

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

Loading Dump File [C:\Windows\Minidump\011323-8156-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 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 = 0xfffff80434600000 PsLoadedModuleList = 0xfffff8043522a2d0 Debug session time: Fri Jan 13 11:05:29.779 2023 (UTC - 5:00) System Uptime: 0 days 15:29:26.366 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................... Loading User Symbols Loading unloaded module list ................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804349fa1d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe40da44fe220=000000000000001e 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80434caa238, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000002408, Parameter 1 of the exception

Debugging Details:

************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ContextRecord *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3077

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 4380

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

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

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

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x1e

Key  : Bugcheck.Code.Register
Value: 0x1e

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: 011323-8156-01.dmp

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80434caa238

BUGCHECK_P3: 0

BUGCHECK_P4: 2408

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000002408

READ_ADDRESS: fffff804352fb390: 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 0000000000002408

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Registry

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffe40da44fe218 fffff80434a4150b : 000000000000001e ffffffffc0000005 fffff80434caa238 0000000000000000 : nt!KeBugCheckEx ffffe40da44fe220 fffff80434a0e36c : 0000000000001000 ffffe40da44feac0 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x1c5a6b ffffe40da44fe8e0 fffff80434a09dbd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0x12c ffffe40da44feac0 fffff80434caa238 : fffff80434c1c2e4 0000000000000060 0000000000000008 ffffe40d00000000 : nt!KiPageFault+0x43d ffffe40da44fec58 fffff80434c1c2e4 : 0000000000000060 0000000000000008 ffffe40d00000000 0000000000000000 : nt!HvpGetCellPaged+0x68 ffffe40da44fec60 fffff80434c4f842 : ffffe40d00000008 0000000000000000 0000000000000000 0000000000000001 : nt!CmQueryValueKey+0x284 ffffe40da44fedc0 fffff80434a0d9f8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!NtQueryValueKey+0x5f2 ffffe40da44ff0c0 fffff804349fedb0 : fffff80434c1049d 0000000000000000 ffffbe8dfbb3394c 0000000000000030 : nt!KiSystemServiceCopyEnd+0x28 ffffe40da44ff2c8 fffff80434c1049d : 0000000000000000 ffffbe8dfbb3394c 0000000000000030 0000000052504e50 : nt!KiServiceLinkage ffffe40da44ff2d0 fffff80434caeee6 : ffffbe8dfbd1f850 0000000000000000 0000000000000000 fffff80434fb5019 : nt!RegRtlQueryValue+0x95 ffffe40da44ff3f0 fffff80434c0fbad : ffffbe8de2512db0 ffffffff8000650c ffffe40da44ff5a0 ffffe40da44ff7d8 : nt!_PnpRegQueryValueIndirect+0x76 ffffe40da44ff450 fffff80434c0f969 : 0000000000000000 ffffe40da44ff5a0 ffffe40da44ff7d8 ffffe40da44ff660 : nt!PnpCtxRegQueryValueIndirect+0x4d ffffe40da44ff4a0 fffff80434c0f75b : 0000000000000002 fffff80434cb9547 ffffe40da44ff701 ffffe40da44ff750 : nt!_CmGetDeviceRegPropWorker+0x18d ffffe40da44ff5f0 fffff80434ce7670 : 0000000000000001 ffffe40da44ff918 0000000000000000 ffffe40da44ff758 : nt!_CmGetDeviceRegProp+0xff ffffe40da44ff700 fffff80434cb67e6 : ffffe40da44ff918 000000f12f1acc00 0000000000000038 0000000000000014 : nt!PiCMGetRegistryProperty+0x12c ffffe40da44ff7b0 fffff80434cb6673 : ffffe40da44ff8f8 0000000000000003 00000000000002a0 fffff80434c26aee : nt!PiCMHandleIoctl+0x156 ffffe40da44ff7f0 fffff80434cddfca : 0000000000000000 fffff80434cddf60 0000000000000000 fffff8043481a00a : nt!PiCMFastIoDeviceDispatch+0x53 ffffe40da44ff840 fffff80434c39498 : 00000000000002a0 0000000000000000 0000000000000000 ffffe50b7d13c6b0 : nt!PiDaFastIoDispatch+0x6a ffffe40da44ff8a0 fffff80434c38d56 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x728 ffffe40da44ff9e0 fffff80434a0d9f8 : 0000000000000000 ffffe40da44ffb40 0000000000000000 ffffe50b7cbe11c0 : nt!NtDeviceIoControlFile+0x56 ffffe40da44ffa50 00007ffa3844d1a4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 000000f12f1acaf8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`3844d1a4

SYMBOL_NAME: nt!HvpGetCellPaged+68

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2486

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 68

FAILURE_BUCKET_ID: AV_R_nt!HvpGetCellPaged

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {34042318-aba6-6e2e-31cf-a63f3dbda154}

Followup: MachineOwner

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

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-13T17:51:28+00:00

    Hi

    I’m Gunasekar and I will be happy to help you with your question, I am a Microsoft consumer like you.

    I understand that you are having a Blue screen of death errors in the Windows operating system when playing COD.

    Upon checking the edition of Windows, it states that 19041 (2001 Version), which is the outdated version released in the year 2020. It is recommended to update your Pc to the latest version of Windows 10. When you update, you'll get the latest fixes and security improvements, helping your device run efficiently and stay protected.

    To stay up to date, select Start > Settings > Windows Update > Check for updates.

    If a feature update is available for your device (Version 20H2, OS Build 19042), it will appear separately on the Windows Update page. To install it, select Download and install now.

    If the issue continues, check for hard disk errors or update your drivers.

    Check the performance of the PC after updating your drives. Here's the article for your reference:

    https://support.microsoft.com/help/5c62726c-6489-52da-a372-3f73142c14ad

    I hope this information helps. If you have any questions, please let me know and I’ll be glad to assist you further.

    Best regards,

    Gunasekar N

    0 comments