[SOLVED] INTERNAL_POWER_ERROR BSOD

P

pacofernandez58

Member
Joined
Dec 23, 2021
Posts
12
Hey everyone

I've bought a Lenovo Ideapad 5 Pro three months ago and I was very satisfied, but last month it started to fire BSODs with the code INTERNAL_POWER_ERROR. Here is all the info as requested in Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista:
  • A brief description of your problem (but you can also include the steps you tried)
    • From time to time, while I'm using my computer in a normal way (that means, it doesn't matter what software I'm using), I get a BSOD with the error code INTERNAL_POWER_ERROR. If I check the MEMORY.DMP file with WinDbg, the specific error is INTERNAL_POWER_ERROR_KE_SETDESTINATION_FAILED. I have tried (almost) everything: update all the drivers from Lenovo website, increase the hibernation file size, disable hibernation, re-install the OS... with no luck. I have even filed a RMA and sent the computer to Lenovo technical support in case it was a hardware failure, but they told me the computer passed all the checks and they had just updated the display driver (but the BSODs keeps happening). I believe BSODs happen only when the computer is running from battery, but I'm not sure.
  • System Manufacturer?
    • Lenovo
  • Laptop or Desktop?
    • Laptop
  • Exact model number (if laptop, check label on bottom)
    • Lenovo Ideapad 5 Pro 14ACN6
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
    • Windows 10 Education
  • x86 (32bit) or x64 (64bit)?
    • x64
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system?
    • It came with no OS
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
  • Age of system? (hardware)
    • Three months (bought in Octuber 2021)
  • Age of OS installation?
    • Octuber 2021
  • Have you re-installed the OS?
    • I used the 'Reset my PC' option (deleting all existing files) two weeks ago before sending the computer to the technical support services.
  • CPU
    • AMD Ryzen 7 5800U
  • RAM (brand, EXACT model, what slots are you using?)
    • Since it is a laptop, I have no idea of the exact model. the only thing I know is that it has 16GB of RAM. Sorry :(
  • Video Card
    • Integrated (AMD Radeon RX Vega 8)
  • MotherBoard - (if NOT a laptop)
  • Power Supply - brand & wattage (if laptop, skip this one)
  • Is driver verifierenabled or disabled?
    • Enabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
    • I was using Panda Dome but I uninstalled it in case it was the cause of the BSODs, but it wasn't. Now I'm just using Windows Defender.
  • Are you using proxy, vpn, ipfilters or similar software?
    • No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
    • No
  • Are you currently under/overclocking? Are there overclocking software installed on your system?
    • No
I have attached the results of running the BSOD Collection Application. Here's the link to Speecy snapshot: http://speccy.piriform.com/results/k5oIFYcvvLXpVMwURvpmZhA If you need the MEMORY.DMP file instead of the Minidumps files, I can share it via Google Drive or similar. If you need anything else, please tell me. Finally, as I'm not a native English speaker, sorry if I made any mistakes.

Thank you!
 

Attachments

Could you please provide the MEMORY.DMP as well? Please zip it beforehand though because it can possibly be up to 1GB or more in size.
 
pacofernandez58 said:
(I couldn't attach it directly to my post, it gave me an error saying that the file was too large to be processed by the server)
Click to expand...
Thanks! That's fine, it's too large to attach even when it's been compressed (zipped). I usually ask for users to zip beforehand because it'll be faster to download and upload.
 
Rich (BB code): 
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: ffff868ca9b03c30, (reserved)
Arg4: ffffffffc0350057, (reserved)

The fourth parameter appears to be possibly be an NTSTATUS error code which is the following:

Rich (BB code): 
10: kd> !error c0350057
Error code: (NTSTATUS) 0xc0350057 (3224698967) - The supplied device ID is invalid.

The error code message does fit the context of our bugcheck and the string from the second parameter:

Failed to change the target destination of an interrupt line.
Click to expand...
It would appear we're dealing with some form of interrupt line misconfiguration. The third parameter is the most interesting, I'm not sure what it's related to, however, it has a pool tag of ITrk which is unfortunately not documented in pooltag.txt so I'm not sure what it's for.

Additionally, it's actually passed into the function which where we crashed too:

Rich (BB code): 
01 ffffab8f96cc7580 fffff8003bc1e4d8 nt!KiIntSteerSetDestination+130d94 (perf)
    Parameter[0] = ffff868ca9b03c30
    Parameter[1] = ffff868ca9b03ce0
    Parameter[2] = (unknown)       
    Parameter[3] = (unknown)

Both of those parameters belong to the same pool allocation and are probably part of the same object. Although, judging by the call stack, we know that it is very likely related to PPM (Process Power Management) or PoFx. I'm probably going to have to set aside some time to investigate this properly to be honest.
 
The earlier post did not make it to the thread.

There were 5 mini dump files collected.

There was one misbehaving driver: amdkmdag.sys


Please uninstall the misbehaving GPU driver using DDU:
Wagnardsoft
DDU Guide / Tutorial



Reinstall using the AMD website:
https://www.amd.com/en/support





Mini dump:
Debug session time: Thu Dec 23 12:35:43.496 2021 (UTC - 6:00)


Code: 
ffffab8f`9a166e10  00000000`00197647
ffffab8f`9a166e18  fffff800`4bb024c6Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0362995.inf_amd64_e3f44311ed9ca7e7\B363211\amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for amdkmdag.sys
 amdkmdag+0x324c6
ffffab8f`9a166e20  fffff800`4bad0000 amdkmdag
ffffab8f`9a166e28  00000000`c00000e5
ffffab8f`9a166e30  ffff868c`94223000
ffffab8f`9a166e38  00000000`c000000d
ffffab8f`9a166e40  ffffab8f`9a1678cc
ffffab8f`9a166e48  ffff868c`94223000
ffffab8f`9a166e50  ffffab8f`9a1678cc
ffffab8f`9a166e58  fffff800`4bafbb09 amdkmdag+0x2bb09
ffffab8f`9a166e60  00000000`00000000
ffffab8f`9a166e68  ffff868c`94223000




Memory dump:
Debug session time: Thu Dec 23 12:35:43.496 2021 (UTC - 6:00)


Code: 
ffffab8f`9a166d70  ffffb580`00007000
ffffab8f`9a166d78  00000000`00000470
ffffab8f`9a166d80  00000000`00000010
ffffab8f`9a166d88  fffff800`4badc030 amdkmdag+0xc030
ffffab8f`9a166d90  00000000`00000001
ffffab8f`9a166d98  fffff800`3c651bf0 nt!MiSystemPartition+0x1070
ffffab8f`9a166da0  fffff800`3c651480 nt!MiSystemPartition+0x900
ffffab8f`9a166da8  ffffab8f`9a167b40
ffffab8f`9a166db0  00000000`00000000
ffffab8f`9a166db8  ffff868c`9d5878f0
ffffab8f`9a166dc0  00000000`00000000
ffffab8f`9a166dc8  00000000`00000000
ffffab8f`9a166dd0  80000000`00000000
ffffab8f`9a166dd8  00000000`00000000
ffffab8f`9a166de0  ffffb280`00000000
ffffab8f`9a166de8  3fffffff`ffffffff
ffffab8f`9a166df0  fffff800`3c650b80 nt!MiSystemPartition
ffffab8f`9a166df8  ffffb280`04c62d50
ffffab8f`9a166e00  00000000`04c62d50
ffffab8f`9a166e08  fffff800`3bc35a03 nt!MiPfnShareCountIsZero+0x5c3
ffffab8f`9a166e10  00000000`00197647
ffffab8f`9a166e18  fffff800`4bb024c6 amdkmdag+0x324c6
ffffab8f`9a166e20  fffff800`4bad0000 amdkmdag
ffffab8f`9a166e28  00000000`c00000e5
ffffab8f`9a166e30  ffff868c`94223000
ffffab8f`9a166e38  00000000`c000000d
ffffab8f`9a166e40  ffffab8f`9a1678cc
ffffab8f`9a166e48  ffff868c`94223000
ffffab8f`9a166e50  ffffab8f`9a1678cc
ffffab8f`9a166e58  fffff800`4bafbb09 amdkmdag+0x2bb09
ffffab8f`9a166e60  00000000`00000000
ffffab8f`9a166e68  ffff868c`94223000
ffffab8f`9a166e70  ffffab8f`9a166f09
ffffab8f`9a166e78  ffff868c`94223000
ffffab8f`9a166e80  00000000`00000001
ffffab8f`9a166e88  ffff868c`94223000



Code: 
amdkmdag.sys Fri Jan  8 15:01:58 2021 (5FF8C846)
 
x BlueRobot said:
Both of those parameters belong to the same pool allocation and are probably part of the same object. Although, judging by the call stack, we know that it is very likely related to PPM (Process Power Management) or PoFx. I'm probably going to have to set aside some time to investigate this properly to be honest.
Click to expand...
Don't worry, take all the time you need :-)

zbook said:
There was one misbehaving driver: amdkmdag.sys


Please uninstall the misbehaving GPU driver using DDU:
Wagnardsoft
DDU Guide / Tutorial


Reinstall using the AMD website:
https://www.amd.com/en/support
Click to expand...
I've just uninstalled the GPU driver using DDU and installed the latest version available from AMD website, I will update in case another BSOD happens.


Also, while I entered Safe Mode to uninstall the driver, I remembered Bitlocker is enabled on my computer. Do you think it can be related to my issue in any way?

Thank you both for taking the time to help me!
 
The Bitlocker entries in the event viewer were unremarkable.


How often do you use Hypervisor?

If there are any computer problems as a trial and error step see if turning off HV makes any difference.


HV Host Service
Hyper-V Host Compute Service


Code: 
0xc0350057     STATUS_HV_INVALID_DEVICE_ID                                    ntstatus.h
 
Hmm, I've just stopped those two services and I was checking if I was able to use WSL or Docker (and I couldn't, which is a pity because they are among of my most used tools everyday). Then I got another BSOD, but this one is different because the error code was SYSTEM_SERVICE_EXCEPTION. After the reboot, I stopped those services again and I got the same BSOD. Here's the latest dump: MEMORY (1).zip

I don't know if the new video driver can also be related, because I've installed from AMD and not from Lenovo website, and now the BSODs have a horizontal black stripe in the lower half of the screen (sorry but I couldn't take a picture).
 
zbook said:
For any BSOD please run the Sysnative log collector.
Click to expand...
Whoops, sorry, I forgot to run it when I wrote my previous post. Here's the zip file: SysnativeFileCollectionApp.zip

zbook said:
When the tool is turned on if there is no immediate BSOD open administrative command prompt and type or copy and paste:

verifier /querysettings
Click to expand...
I didn't get any BSOD. Here are the results after running that command: verifier querysettings.txt
zbook said:
How often do you use Vbox?
Click to expand...
I use it pretty often, at least once a week. However, in this week I haven't used it not a single day.
 
I don't feel that Driver Verifier will be of any use here, the only option which will probably be useful is Power Framework Delay Fuzzing, and that isn't designed for the problem at hand. I would disable it for now by entering the following command from a Command Prompt shell:

Rich (BB code): 
verifier /reset

Afterwards, you'll need to reboot the computer.

Since the main issue appears to be with the PPM, then the it is recommended that you update the chipset driver if possible from the AMD support page - https://www.amd.com/en/support
 
Please uninstall all VM software (Vbox) and see if it makes any difference.





Today is 12/25/2021

The computer was placed in use on 12/6.

The computer was free of BSOD for 11 days.

Starting on 12/17 the computer had BSOD with bugcheck A0 (4001)

The bugcheck A0 continued until 12/24

The Nvidia GPU driver was uninstalled and reinstalled.

The bugchecks have been 3B (c0000005) since 12/25.

The debugging displayed: FAILURE_ID_HASH_STRING: km:0x3b_vrf_dxgkrnl!dxgvirtualmachine::iswsl2guest




Options are:

1) See if the uninstallation of Vbox makes any difference
(a Vbox driver was seen during the debugging)

2) Stop troubleshooting and return the computer using Return Merchandise Authorization (RMA)
(brand new computers should not have BSOD)

3) Run the Lenovo Custom Diagnostics overnight:
laptops and netbooks :: 5 series :: ideapad 5 pro 14acn6 :: 82l7 :: 82l7003ysp :: mp22ckef Lenovo PC Support - Lenovo Support US




Code: 
 # Child-SP          RetAddr           Call Site
00 fffffd8d`4572dd90 fffff805`736a860b nt!MiWalkPageTablesRecursively+0xbd
01 fffffd8d`4572de30 fffff805`736a860b nt!MiWalkPageTablesRecursively+0x88b
02 fffffd8d`4572ded0 fffff805`736a860b nt!MiWalkPageTablesRecursively+0x88b
03 fffffd8d`4572df70 fffff805`7360ef4b nt!MiWalkPageTablesRecursively+0x88b
04 fffffd8d`4572e010 fffff805`7371b577 nt!MiWalkPageTables+0x36b
05 fffffd8d`4572e110 fffff805`7393fe49 nt!MiEmptyWorkingSetInitiate+0x107
06 fffffd8d`4572e2e0 fffff805`73940c4e nt!MiEmptyTargetedWorkingSet+0xf1
07 fffffd8d`4572e330 fffff805`73dccc66 nt!MiTrimAllSystemPagableMemory+0xde
08 fffffd8d`4572e380 fffff805`73de3333 nt!MmVerifierTrimMemory+0x72
09 fffffd8d`4572e3b0 fffff805`73de2faa nt!ViKeRaiseIrqlSanityChecks+0xc7
0a fffffd8d`4572e3f0 fffff805`73de1a02 nt!ViKeAcquireSpinLockRaiseToDpcCommon+0x2a
Page 11e7ab not present in the dump file. Type ".hh dbgerr004" for details
Page 11e7ab not present in the dump file. Type ".hh dbgerr004" for details
[HI]*** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys[/HI]
0b fffffd8d`4572e420 fffff802`92e6247d nt!VerifierKeAcquireSpinLockRaiseToDpc+0x12
0c fffffd8d`4572e460 fffff802`92e57b47 [HI]VBoxDrv[/HI]+0x2247d
0d fffffd8d`4572e490 fffff805`73a91e4c [HI]VBoxDrv[/HI]+0x17b47
0e fffffd8d`4572e4c0 fffff805`73a91fba nt!ObpCallPreOperationCallbacks+0x10c
0f fffffd8d`4572e540 fffff805`73a01013 nt!ObpPreInterceptHandleCreate+0xaa
10 fffffd8d`4572e5b0 fffff805`73a713d9 nt!ObpCreateHandle+0xce3
11 fffffd8d`4572e7c0 fffff805`73ab8b9d nt!ObOpenObjectByPointer+0x1b9
12 fffffd8d`4572ea40 fffff805`73ab89d6 nt!PspCreateObjectHandle+0x3d
13 fffffd8d`4572ea90 fffff805`73abb554 nt!PspInsertThread+0x6f2
14 fffffd8d`4572eb50 fffff805`73abb976 nt!PspCreateThread+0x294
15 fffffd8d`4572ee10 fffff805`73812ab8 nt!NtCreateThreadEx+0x266
16 fffffd8d`4572f710 fffff805`73804f30 nt!KiSystemServiceCopyEnd+0x28
17 fffffd8d`4572f918 fffff805`73a172fe nt!KiServiceLinkage
18 fffffd8d`4572f920 fffff805`73670d64 nt!RtlpCreateUserThreadEx+0x156
19 fffffd8d`4572fa60 fffff805`7368c8a1 nt!ExpWorkerFactoryCreateThread+0x10c
1a fffffd8d`4572fb20 fffff805`737be6c9 nt!ExpWorkerFactoryCheckCreate+0x201
1b fffffd8d`4572fb80 fffff805`7375f935 nt!ExpWorkerFactoryManagerThread+0x129
1c fffffd8d`4572fbd0 fffff805`73808728 nt!PspSystemThreadStartup+0x55
1d fffffd8d`4572fc20 00000000`00000000 nt!KiStartSystemThread+0x28
 
x BlueRobot said:
Since the main issue appears to be with the PPM, then the it is recommended that you update the chipset driver if possible from the AMD support page - https://www.amd.com/en/support
Click to expand...

Yesterday I've updated the chipset drivers, but 20 minutes ago I got another BSOD, again with the INTERNAL_POWER_ERROR error code. SysnativeFileCollectionApp (1).zip +
MEMORY (2).zip

I'm almost 95% sure that BSODs only happen when the computer is running on battery, since I can't remember one occasion where I got a BSOD while it was plugged in (but maybe my memory doesn't serve me well, and that's why I'm not 100% sure). I hope that can be helpful in order to solve the issue.

zbook said:
Please uninstall all VM software (Vbox) and see if it makes any difference.
Click to expand...
Okay, I will try uninstalling Vbox.
 
If uninstalling VM software initially creates a stable environment then monitor the computer for a week without reinstallation to have a substantial monitoring period.

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using.



When available please post images of the Lenovo hardware diagnostic tests with their respective results.



If there are recurrent BSOD after uninstalling VM software then consider Return Merchandise Authorization (RMA).



If you want to continue troubleshooting then plan to place the computer in safe mode with networking continuously for 3 or more days.

The longer the continuous safe mode period the better the testing conditions.

Run the Sysnative log collector for any BSOD while in safe mode.
 
Code: 
STACK_TEXT:
ffffab8f`96cc7578 fffff800`3be825f4     : 00000000`000000a0 00000000`00004001 00000000`00000102 ffff868c`a9b03c30 : nt!KeBugCheckEx
ffffab8f`96cc7580 fffff800`3bc1e4d8     : ffff868c`9819ed40 fffff800`3bc15a1a ffffb981`00000002 ffffffff`ffffffff : [HI]nt!KiIntSteerSetDestination[/HI]+0x130d94
ffffab8f`96cc75c0 fffff800`3bc1e2f2     : 00000000`00000000 00000000`00000002 00000000`00000001 ffffab8f`96cc7790 : nt!KiIntSteerDistributeInterrupts+0xd8
ffffab8f`96cc7600 fffff800`3bc1e047     : 00000000`00000001 0f0f0f0f`00000000 00000000`00000001 ffffab8f`96cc7e80 : nt!KeIntSteerPeriodic+0xd2
ffffab8f`96cc7710 fffff800`3bc1f5c0     : ffffab8f`96cc7e80 ffffb981`bea80180 0000b11d`09fbb411 ffffb981`bea80180 : nt!PpmParkSteerInterrupts+0x447
ffffab8f`96cc7b40 fffff800`3bc9a32e     : ffffb981`bea83240 ffff868c`8c7d2000 ffffab8f`96cc7cb0 ffffab8f`00000002 : nt!PpmCheckRun+0x40
ffffab8f`96cc7bb0 fffff800`3bc99614     : ffffb981`bea80180 66f46e37`00000000 00000000`00000008 00000000`003bc917 : nt!KiExecuteAllDpcs+0x30e
ffffab8f`96cc7d20 fffff800`3bdfe115     : d6fa8a16`a3e20d6a ffffb981`bea80180 00000000`00000000 ffff868c`98555740 : nt!KiRetireDpcList+0x1f4
ffffab8f`96cc7fb0 fffff800`3bdfdf00     : 00000000`00000000 ffff868c`98555740 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffab8f`9a1676a0 fffff800`3bdfd5ce     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffab8f`9a1676d0 fffff800`3bca181d     : ffffc9e4`f27937f8 00000000`00000003 ffffab8f`9a167ac0 ffffab8f`9a1679e0 : nt!KiDpcInterrupt+0x2ee
ffffab8f`9a167860 fffff800`3bca0677     : 00000000`00000112 ffffc981`0e8f0168 ffffc981`0e8f0168 ffff868c`985550c0 : nt!MiUnlockWorkingSetShared+0xad
ffffab8f`9a167890 fffff800`3bc9f1da     : 0000021d`1de78000 fffff800`00000000 00000000`00000000 00000000`00000000 : nt!MiUserFault+0xf27
ffffab8f`9a167920 fffff800`3be0525e     : 00000000`00000000 ffff868c`00000001 00000000`00000000 ffffab8f`9a167b40 : nt!MmAccessFault+0x16a
ffffab8f`9a167ac0 00007ffb`5e8a028e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
0000005e`7af18df8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`5e8a028e
a remotedrive is lost when needed, see bold text above.
The reason seems always be GoogleDriveFS.exe
so you should uninstall that remotedrive for a while and test your laptop, without powerconnection (Akku)
 
zbook said:
When available please post images of the Lenovo hardware diagnostic tests with their respective results.



If there are recurrent BSOD after uninstalling VM software then consider Return Merchandise Authorization (RMA).
Click to expand...
This is more than likely already been carried out by the Lenovo support team when the user sent the computer back to them. This was mentioned in the first post.

It'll be interesting to see if removing VMware makes a difference. I think there is a greater underlying problem at hand here.
 
The memory dump in post #19 was not able to be opened.

The mini dump debugging confirmed the uninstallation of Vbox.

When available please update the progress with the steps in post #15 (Lenovo diagnostics, and safe mode).
 

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

Back
Top