question

14306383 avatar image
0 Votes"
14306383 asked DSPatrick answered

Constant power cycle boot loop issues and can't determine the problem

So I've been dealing with a power boot cycle issue for months and cannot figure out what is going on and Microsoft Support told me to post my issue here. I have replaced my Motherboard, Memory, HDD/SDD's, Power Supply, and GPU. I've done a clean reinstall, BIOS update/rollback, still no luck.

I just ran verifier.exe and got a BSOD dump file and I hope this might point out any potential bad drivers causing this issue.

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


Loading Dump File [C:\Users*\Desktop\053021-16171-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 Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`43c07000 PsLoadedModuleList = 0xfffff804`448311b0
Debug session time: Sun May 30 20:07:01.161 2021 (UTC - 4:00)
System Uptime: 0 days 0:00:19.823
Loading Kernel Symbols
...............................................................
.....................................
Loading User Symbols
Loading unloaded module list
..
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`43ffdcf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8408`d0006650=00000000000000c4
0: kd> !analyze -v



  •                      Bugcheck Analysis                                    *
    



DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff80882cf1d93, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000000726274, Pool Tag (if provided).

Debugging Details:




KEY_VALUES_STRING: 1

 Key  : Analysis.CPU.mSec
 Value: 2796

 Key  : Analysis.DebugAnalysisManager
 Value: Create

 Key  : Analysis.Elapsed.mSec
 Value: 15581

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

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

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

 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


BUGCHECK_CODE: c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff80882cf1d93

BUGCHECK_P3: 0

BUGCHECK_P4: 726274

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8408`d0006648 fffff804`445d6e34 : 00000000`000000c4 00000000`00002000 fffff808`82cf1d93 00000000`00000000 : nt!KeBugCheckEx
ffff8408`d0006650 fffff804`441a3d45 : fffff804`44819c98 00000000`00002000 fffff808`82cf1d93 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
ffff8408`d0006690 fffff804`445cddf4 : 00000000`00726274 fffff804`44819c98 fffff808`82cf1d93 00000000`00000000 : nt!VfReportIssueWithOptions+0x101
ffff8408`d00066e0 fffff804`445daff2 : 00000000`00000000 ffff8b87`5c6ff000 00000000`00000018 00000000`00000000 : nt!VfCheckPoolType+0x90
ffff8408`d0006720 fffff808`82cf1d93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VerifierExAllocatePoolWithTag+0x62
ffff8408`d0006770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000080 : ene+0x1d93


SYMBOL_NAME: ene+1d93

MODULE_NAME: ene

IMAGE_NAME: ene.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d93

FAILURE_BUCKET_ID: 0xc4_2000_VRF_ene!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {8c7175c3-41d7-9412-c64e-e43d9572bd5c}

Followup: MachineOwner



any help would be much appreciated thanks!

msc-essentials
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

DSPatrick avatar image
1 Vote"
DSPatrick answered

BSOD's are almost always hardware or driver related. The hardware manufacturer will be your best resource to debug problems with the hardware.

--please don't forget to upvote and Accept as answer if the reply is helpful--





5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.