INTERNAL_POWER_ERROR (a0) - The power policy manager experienced a fatal error.

N

navneet

Member
Joined
Mar 8, 2024
Posts
13
Hi @mattcargile
I'm having what seems to be a similar issue. Also on a Dell XPS-17 which shows its a systemic issue with this laptop, been thru it with Dell Tech Support, upgraded BIOS, all Drivers, and it still fails like clockwork. Dell TS now suggesting rolling back to a previous restore point, or reinstalling the OS (Windows 11) which I'm resisting currently. Will try what you've done, however I use an external monitor, and as the XPS only comes with USB-C, I won't be able to disable the USB-C Video that @ubuysa had also suggested. Did you disable this driver too?

Thanks
Navneet

The dmp file, afraid I don't fully understand the various Key/Value pairs and how to interpret those values.

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000001, Error Handling power IRP.
Arg2: 0000000000000006, The system has failed to allocate a necessary power IRP.
Arg3: ffff9f81d14d4e00, target device object
Arg4: 0000000000000001, device power IRP

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2203

Key : Analysis.Elapsed.mSec
Value: 9480

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xa0

Key : Bugcheck.Code.TargetModel
Value: 0xa0

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0xa0_1_nvhda64v!unknown_function

Key : Failure.Hash
Value: {9ffc40dc-a899-185a-b2ec-3fc19f283900}


BUGCHECK_CODE: a0

BUGCHECK_P1: 1

BUGCHECK_P2: 6

BUGCHECK_P3: ffff9f81d14d4e00

BUGCHECK_P4: 1

FILE_IN_CAB: 030824-15046-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffc05`0ba164a8 fffff800`0dcbe5a1 : 00000000`000000a0 00000000`00000001 00000000`00000006 ffff9f81`d14d4e00 : nt!KeBugCheckEx
fffffc05`0ba164b0 fffff800`0db2c299 : ffff9f81`d1d11870 00000000`00000000 ffff9f81`000dd602 ffff9f81`00000001 : nt!PopAllocateIrp+0x1921bd
fffffc05`0ba16580 fffff800`0db2c1d2 : ffff9f81`b3f738a0 00000000`00000001 ffff9f81`d1d11870 00000000`00000000 : nt!PopRequestPowerIrp+0xb9
fffffc05`0ba16610 fffff800`298883e7 : ffff9f81`dce30010 fffff800`0dc57c9d ffff9f81`00000000 00000000`00001001 : nt!PoRequestPowerIrp+0x22
fffffc05`0ba16660 ffff9f81`dce30010 : fffff800`0dc57c9d ffff9f81`00000000 00000000`00001001 00000000`00000000 : nvhda64v+0x83e7
fffffc05`0ba16668 fffff800`0dc57c9d : ffff9f81`00000000 00000000`00001001 00000000`00000000 00000000`00000000 : 0xffff9f81`dce30010
fffffc05`0ba16670 ffff9f81`b3f73ec0 : 00000000`00000f00 ffff9f81`ae002000 00000000`00000000 fffff800`29890151 : nt!IopPerfCallDriver+0xb3
fffffc05`0ba166a0 00000000`00000f00 : ffff9f81`ae002000 00000000`00000000 fffff800`29890151 fffff800`0d800000 : 0xffff9f81`b3f73ec0
fffffc05`0ba166a8 ffff9f81`ae002000 : 00000000`00000000 fffff800`29890151 fffff800`0d800000 ffff9f81`d18636f0 : 0xf00
fffffc05`0ba166b0 00000000`00000000 : fffff800`29890151 fffff800`0d800000 ffff9f81`d18636f0 ffff9f81`ada02140 : 0xffff9f81`ae002000


SYMBOL_NAME: nvhda64v+83e7

MODULE_NAME: nvhda64v

IMAGE_NAME: nvhda64v.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 83e7

FAILURE_BUCKET_ID: 0xa0_1_nvhda64v!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9ffc40dc-a899-185a-b2ec-3fc19f283900}

Followup: MachineOwner
 
Hi, the system has been crashing after being put to sleep. It doesn't crash straight away, but after a few hours. This started a few weeks ago.

I've called on Dell Tech Support, and they have ensured the BIOS is up to date, and that all drivers are up to date. But the system keeps crashing, and Dell are pushing me towards creating a new User Profile and transferring to that, or re installing the OS, and I'm pushing back against both of those.

So now am trying to resolve this issue by searching online and joined this forum.

Appreciate any thoughts on what the issue may be.

System Information using Speccy

http://speccy.piriform.com/results/nOlAR3AhftfCZDgHMPicP2h

System Information

OS Name Microsoft Windows 11 Pro
Version 10.0.22621 Build 22621
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name MICKEY-XPS
System Manufacturer Dell Inc.
System Model XPS 17 9710
System Type x64-based PC
System SKU 0A5D
Processor 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.25.1, 10/01/2024
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 00D5DG
BaseBoard Version A01
Platform Role Mobile
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.22621.2506"
User Name MICKEY-XPS\mickey
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.7 GB
Available Physical Memory 20.7 GB
Total Virtual Memory 33.7 GB
Available Virtual Memory 21.5 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Not enabled
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
 

Attachments

There is never any need to post the output of the WinDbg analyze -v command, just follow the BSOD Posting instructions, as you have done. That SysnativeFilleCollection.zip files contains the dump files and a host of other important problem determination data. Dump analysis is, in any case, way more involved than just running analyze -v.

Your dumps are all very similar, all point to the BSODs being caused by the Nvidia nvhda64v.sys driver. This is a component of the Nvidia graphics driver, it's the Nvidia audio driver that manages audio over HDMI cables....
Code: 
0: kd> lmvm nvhda64v
Browse full module list
start             end                 module name
fffff805`8b220000 fffff805`8b23e000   nvhda64v T (no symbols)     
    Loaded symbol image file: nvhda64v.sys
    Image path: nvhda64v.sys
    Image name: nvhda64v.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jan 20 12:48:10 2023 (63CA716A)
    CheckSum:         0001EE26
    ImageSize:        0001E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
It's not uncommon for the Nvidia audio driver to conflict with the motherboard (or other) audio driver. Unless you are using audio over an HDMI cable via the RTX3060 then you don't need this driver at all. When you install the Nvidia graphics driver choose a Custom (Advanced) install, there you will see check boxes for the various driver components. As mentioned, the audio driver is only needed if you send audio over HDMI, the USB-C driver is only needed if you have a USB-C connected monitor, and the PhysX driver is only needed if you have games that require it. Otherwise uncheck these drivers.

In addition, with laptops it's generally wise (sometimes essential) to install graphics drivers from the laptop vendor's website and NOT from Nvidia. This is because on laptops graphics drivers are often customised for power-saving and interoperability issues. There is a later driver for your RTX3060 driver on the Dell support site for your XPS 17. There is also an update for the iGPU driver there too, it's always wise to update both graphics drivers on a laptop because they work hand-in-hand.

Let us know how things are after you've updated the graphics drivers and, if necessary, excluded any Nvidia drivers that you don't need. If you are using HDMI audio then I'd also suggest updating the Realtek audio driver, there is a later version on the Dell website.
 
Hi @ubuysa many thanks for that. I've uninstalled the Nvidia audio driver, and done a custom (Advanced) install of the Nvidia graphics driver from the Dell support site, and not selecting the audio driver.
I have installed the intel Iris Xe Graphics driver, from the Dell site, as you mentioned these work hand in hand.
Will add a message on how its going after a couple of days.
 
Hi @ubuysa
Its been over a week now, and no more BSOD events. So it has been fixed.

Many thanks for your help with this.

As a more practical form of thanks, I've also made a small donation towards your site.

Kind Regards
Navneet
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top