Windows 10: Unknown parameters on INTERNAL_POWER_ERROR Bug Check

So I've had a blue screen two times now with INTERNAL_POWER_ERROR and wanted to inspect why I'm getting this error.


I opened the minidump with Windbg.exe and got the following analysis:


INTERNAL_POWER_ERROR (a0)

The power policy manager experienced a fatal error.

Arguments:

Arg1: 0000000000004001, (INTERNAL_POWER_ERROR_KE_SUBCODE) An internal failure has

occured in kernel executive during a power operation.

Arg2: 0000000000000102, (INTERNAL_POWER_ERROR_KE_SETDESTINATION_FAILED)

Failed to change the target destination of an

interrupt line.

Arg3: ffff820b17a56060, (reserved)

Arg4: ffffffffc0350057, (reserved)



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for KfeCo10X64.sys

*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



SYSTEM_MANUFACTURER: Dell Inc.



SYSTEM_PRODUCT_NAME: XPS 15 9570



SYSTEM_SKU: 087C



BIOS_VENDOR: Dell Inc.



BIOS_VERSION: 1.10.1



BIOS_DATE: 04/26/2019



BASEBOARD_MANUFACTURER: Dell Inc.



BASEBOARD_PRODUCT: 0D0T05



BASEBOARD_VERSION: A00



DUMP_TYPE: 2



BUGCHECK_P1: 4001



BUGCHECK_P2: 102



BUGCHECK_P3: ffff820b17a56060



BUGCHECK_P4: ffffffffc0350057



BUGCHECK_STR: 0xa0_4001



CPU_COUNT: c



CPU_MHZ: 8a0



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXPNP: 1 (!blackboxpnp)





CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



PROCESS_NAME: System



CURRENT_IRQL: 2



ANALYSIS_SESSION_HOST: SANDER-XPS



ANALYSIS_SESSION_TIME: 05-17-2019 11:41:11.0150



ANALYSIS_VERSION: 10.0.18362.1 x86fre



DPC_STACK_BASE: FFFFB707322B7FB0



LAST_CONTROL_TRANSFER: from fffff8005f4924b8 to fffff8005f45eef0



STACK_TEXT:

ffffb707`322b7628 fffff800`5f4924b8 : 00000000`000000a0 00000000`00004001 00000000`00000102 ffff820b`17a56060 : nt!KeBugCheckEx

ffffb707`322b7630 fffff800`5f395129 : ffffb707`322b7660 fffff800`5f38e1ca ffffcb01`00000001 00000000`00000002 : nt!KiIntSteerSetDestination+0x1aa270

ffffb707`322b7670 fffff800`5f394ccc : fffff800`5f6c7260 00000000`00000002 00000000`00000001 ffffb707`322b7840 : nt!KiIntSteerDistributeInterrupts+0xd9

ffffb707`322b76b0 fffff800`5f394700 : 00000000`00000001 0f0f0f0f`0f0f0f0f fffff800`5f6bca80 00000000`000008a0 : nt!KeIntSteerPeriodic+0xbc

ffffb707`322b77c0 fffff800`5f3e1c30 : fffff800`5f6bca80 ffffcb01`753c0180 00000000`00000000 ffffcb01`753c0180 : nt!PpmParkSteerInterrupts+0x3e0

ffffb707`322b7bf0 fffff800`5f324677 : ffffcb01`753c2f80 00000000`00000000 ffff820b`8c8e4518 ffffcb01`753c0180 : nt!PpmCheckRun+0x40

ffffb707`322b7c60 fffff800`5f323cbe : 00000000`00000002 00000000`00989680 ffff820b`1bab6080 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7

ffffb707`322b7da0 fffff800`5f465d65 : 20193fe3`2f2d3d04 ffffcb01`753c0180 ffffb707`356a7840 00000000`00000000 : nt!KiRetireDpcList+0x1ae

ffffb707`322b7fb0 fffff800`5f465b50 : 000000ba`00000005 00000046`0000005a 3fea3725`dc4efe5d 80000000`00000000 : nt!KxRetireDpcList+0x5

ffffb707`356a7790 fffff800`5f46523c : 00000000`3f800000 00000000`00000000 c025a372`5dc4efe6 00000000`00000000 : nt!KiDispatchInterruptContinue

ffffb707`356a77c0 fffff800`5f2afc0d : ffff820b`1be7b090 fffff800`b8b4785d 00000000`00000000 00000000`00000246 : nt!KiDpcInterrupt+0x2dc

ffffb707`356a7950 fffff800`b8b31f8d : ffff820b`1be7b0e0 fffff800`be3dec78 00000000`00000000 ffffb707`356a7aa9 : nt!KeReleaseInStackQueuedSpinLock+0x6d

ffffb707`356a7980 ffff820b`1be7b0e0 : fffff800`be3dec78 00000000`00000000 ffffb707`356a7aa9 00000000`00000000 : KfeCo10X64+0x1f8d

ffffb707`356a7988 fffff800`be3dec78 : 00000000`00000000 ffffb707`356a7aa9 00000000`00000000 ffff820b`8c24e278 : 0xffff820b`1be7b0e0

ffffb707`356a7990 00000000`00000000 : ffffb707`356a7aa9 00000000`00000000 ffff820b`8c24e278 00000000`00000002 : KfeCo10X64+0x58aec78





THREAD_SHA1_HASH_MOD_FUNC: 1af05bb6254265d6ba6d29e8df8399dc092a3606



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: fe55c8c871502d5155450c287f13b939012205ec



THREAD_SHA1_HASH_MOD: 3acb7afb4e645cf4f5fb04db1314d875e083e6a7



FOLLOWUP_IP:

KfeCo10X64+1f8d

fffff800`b8b31f8d 4c8d5c2450 lea r11,[rsp+50h]



FAULT_INSTR_CODE: 245c8d4c



SYMBOL_STACK_INDEX: c



SYMBOL_NAME: KfeCo10X64+1f8d



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: KfeCo10X64



IMAGE_NAME: KfeCo10X64.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 5b5b5487



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 1f8d



FAILURE_BUCKET_ID: 0xa0_4001_KfeCo10X64!unknown_function



BUCKET_ID: 0xa0_4001_KfeCo10X64!unknown_function



PRIMARY_PROBLEM_CLASS: 0xa0_4001_KfeCo10X64!unknown_function



TARGET_TIME: 2019-05-17T09:12:12.000Z



OSBUILD: 17763



OSSERVICEPACK: 503



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: 2021-07-31 17:45:35



BUILDDATESTAMP_STR: 180914-1434



BUILDLAB_STR: rs5_release



BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



ANALYSIS_SESSION_ELAPSED_TIME: d787



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0xa0_4001_kfeco10x64!unknown_function



FAILURE_ID_HASH: {81e20c9f-0513-f14e-8b5c-7cd3ce39ba66}



Followup: MachineOwner

---------


So I headed to the Bug Check page and noticed that the first parameter code (4001) is not even in the table, so I don't know how to inspect further.


Googling the text codes INTERNAL_POWER_ERROR_KE_SUBCODE and INTERNAL_POWER_ERROR_KE_SETDESTINATION_FAILED also yielded no results.


Please help me solve this problem,


synologix

:)

 

GPU-Z what command line parameter ?

Current /? (-?) or / help (-help) parameter is invalid

 

INTERNAL_POWER_ERROR Windows 10 Restart Loop

Hi Krishna,



INTERNAL_POWER_ERROR indicates that the power policy manager experienced a fatal error. Refer to the article for more information:

Bug Check 0xA0: INTERNAL_POWER_ERROR



To troubleshoot the issue, follow these methods:



Method 1:

Step 1:

Start your computer in safe mode and check if the issue persists:

http://windows.microsoft.com/en-in/windows-10/changing-the-start-up-settings-in-windows-10#v1h=tab01



Step 2:

If it works fine in safe mode, perform clean boot to check if any third party application is causing the issue, as clean boot helps in eliminating software conflicts.

How to perform a clean boot in Windows

https://support.microsoft.com/en-us/kb/929135



Note: After troubleshooting, see the section “How to reset the computer to start as usual after troubleshooting with clean boot” to return the computer to a
Normal startup mode.



Method 2:

I would suggest you to use these commands to repair Windows:

• Open an Administrator CMD window. If you can’t find a way, use these steps:
  
• Press CTRL+Shift+ESC to open Task Manager.
• Click File > Run New Task
• Make sure you have a check mark beside “Create this task with administrative privileges”
  
• Type CMD
• Type the following commands at the CMD prompt:
  
  dism /online /cleanup-image /restorehealth
  
  sfc /scannnow

Let us know the results.

 

How to Dump Networking Parameters?


Had a customer with this problem, they had a brand new Dell Optiplex 3050, with Windows 10 1709, and Realtek Gbit Family of lan adapters (wired connection). After much troubleshooting (many suggestions listed in the course of this thread), it turned out the PC needed a bios update. Among the updates listed on the dell website for bios version 1.52 (I flashed it with the latest 1.92) was "Update RealtekLOM".

LOM is "lan on motherboard" and the Realtek has flashable firmware.

One step for others having this issue is to check their computer manufacturer's website for "Lom" firmware updates for the particular network adapter - whether integrated or an add-in.