[SOLVED] BSOD w/dmp file output

Dweagar

Reputable
Mar 24, 2017
13
0
4,520
I am experiencing periodic BSOD crashes showing code KMODE_EXCEPTION_NOT_HANDLED

The following is the data from the dump file:

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


Loading Dump File [C:\WINDOWS\Minidump\122921-7171-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80711000000 PsLoadedModuleList = 0xfffff80711c2a1b0
Debug session time: Wed Dec 29 18:10:51.411 2021 (UTC - 6:00)
System Uptime: 0 days 0:15:32.066
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807113f70d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff918628c3b270=000000000000001e
4: 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: fffff807116cc218, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000002ff0, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2702

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 11069

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

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

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


FILE_IN_CAB: 122921-7171-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff807116cc218

BUGCHECK_P3: 0

BUGCHECK_P4: 2ff0

READ_ADDRESS: fffff80711cfb390: 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
0000000000002ff0

EXCEPTION_PARAMETER2: 0000000000002ff0

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 ffff800000000000 STACK_TEXT: ffff918628c3b268 fffff80711459dcb : 000000000000001e ffffffffc0000005 fffff807116cc218 0000000000000000 : nt!KeBugCheckEx ffff918628c3b270 fffff807114091ac : 0000000000001000 ffff918628c3bb10 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x17449b ffff918628c3b930 fffff80711405343 : 0000000000000000 ffff818fea266040 0000000000000003 ffff818fea266040 : nt!KiExceptionDispatch+0x12c ffff918628c3bb10 fffff807116cc218 : fffff807115e8b89 ffff940c43d6e150 ffff940c43d6e150 0000000000000000 : nt!KiPageFault+0x443 ffff918628c3bca8 fffff807115e8b89 : ffff940c43d6e150 ffff940c43d6e150 0000000000000000 fffff80711289392 : nt!HvpGetCellPaged+0x68 ffff918628c3bcb0 fffff807115e892e : 00000000ffffffff ffff918628c3bd90 0000000000000001 ffff940c43d49d30 : nt!CmpConstructNameFromKeyNodes+0x199 ffff918628c3bd30 fffff80711867098 : 0000000000000000 0000000000000017 fffff807119342d0 ffff940c43d49d30 : nt!CmpConstructNameWithStatus+0xee ffff918628c3bd90 fffff807117de537 : ffff940c43d49d30 ffff918600000004 ffff940c43d49d30 ffff940c4f8fdfa0 : nt!CmpEtwDumpKcb+0x70 ffff918628c3be50 fffff80711652c97 : ffff940c43d49d30 ffff940c4f8fd000 00000000000000aa ffff940c4f8fe000 : nt!CmpCleanUpKcbCacheWithLock+0x1f7a0b ffff918628c3be80 fffff80711652aa5 : 0000000000000000 0000000000040000 ffff918628c3c000 ffff918628c3bf20 : nt!CmpCleanUpKCBCacheTable+0xcf ffff918628c3bf10 fffff80711652a25 : 0000000000040000 ffff918628c3c039 ffff940c43d0e520 0000000000000006 : nt!CmpEnumerateAllOpenSubKeys+0x35 ffff918628c3bf50 fffff80711650542 : 0000000000040000 ffff918628c3c039 ffff940c43d0e520 0000000000000006 : nt!CmpDoesKeyHaveOpenSubkeys+0x25 ffff918628c3bfa0 fffff807116502e9 : ffff940c571ce960 0000000000000000 000000000000007a 0000000000000000 : nt!CmpPerformUnloadKey+0x146 ffff918628c3c0a0 fffff8071164fa61 : ffff818100000000 ffff918628c3c360 ffff818fe6cafb00 0000000067655256 : nt!CmUnloadKey+0x42d ffff918628c3c340 fffff80711408ab5 : 0000000000000003 ffff940c419e5080 0000000000000000 0000000000000001 : nt!NtUnloadKey+0x11 ffff918628c3c370 fffff807113faf30 : fffff807115ccdad ffff940c00000002 ffff940c00000000 ffff918628c3c5a0 : nt!KiSystemServiceCopyEnd+0x25 ffff918628c3c508 fffff807115ccdad : ffff940c00000002 ffff940c00000000 ffff918628c3c5a0 ffff918628c3c5a0 : nt!KiServiceLinkage ffff918628c3c510 fffff807115ccc53 : ffff940c5af4b8b0 ffff918628c3c640 ffff940c5a73bc00 ffff940c438197a0 : nt!VrpUnloadDifferencingHive+0x135 ffff918628c3c580 fffff807115ca4fd : 0000000000000000 0000000000000008 ffff818fe0a08700 ffff818f00000060 : nt!VrpCleanupNamespace+0x8f ffff918628c3c5c0 fffff807115ca67f : 0000000000000000 ffff818feea3e500 ffff818feea3e430 ffff8181031f5370 : nt!VrpHandleIoctlUnloadDynamicallyLoadedHives+0x111 ffff918628c3c650 fffff8071128f7d5 : ffff818feea3e430 0000000000000000 0000000000000001 ffff818103105250 : nt!VrpIoctlDeviceDispatch+0x12f ffff918628c3c700 fffff80711675a08 : ffff918628c3ca80 ffff818feea3e430 0000000000000001 ffff818fea227080 : nt!IofCallDriver+0x55 ffff918628c3c740 fffff807116752d5 : 0000000000220018 ffff918628c3ca80 0000000000000005 ffff918628c3ca80 : nt!IopSynchronousServiceTail+0x1a8 ffff918628c3c7e0 fffff80711674cd6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x5e5 ffff918628c3c920 fffff80711408ab5 : 00000000000006d0 000000a3a197ee08 ffff918628c3c9a8 0000000000000000 : nt!NtDeviceIoControlFile+0x56 ffff918628c3c990 00007ffca148ce54 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 000000a3a197eef8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffca148ce54


SYMBOL_NAME: nt!HvpGetCellPaged+68

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1415

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 68

FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!HvpGetCellPaged

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f86e9d75-9ce4-8799-af45-48af90ca5aaf}

Followup: MachineOwner
---------




Any ideas what is causing it? I dont see any driver issues and I've reinstalled the video driver just to make certain. I'm stumped at this point.
 
Solution
my guess is its a driver, it happened after CPU tried to access ram, and not liking result it got

Acer? PC or laptop?
Have you tried updating drivers as that is a common cause

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud...
my guess is its a driver, it happened after CPU tried to access ram, and not liking result it got

Acer? PC or laptop?
Have you tried updating drivers as that is a common cause

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 
Solution

TRENDING THREADS