Question Kernel Power 41 event consistently while laptop is asleep ?

Toggle sidebar Toggle sidebar
S

SBazu

Apr 17, 2025
17
0
10
Recently I noticed that when I went to wake my laptop from sleep, it was fully powered off. This happens fairly consistently, although not all the time (sometimes it will sleep properly, as indicated by the pulsing power light. Other times it shuts off.)

Checking event viewer, this is always a Kernel Power 41 event. It is listed with either BugCheckCode 0, 307, or 335. I am unsure if there's any consistency in events leading up to this.

I have collected 6 minidump files generated on each critical error. They are in a .zip here:
https://www.mediafire.com/file/kas8o4v0vbbuvjd/minidumps.zip/file

I have no experience in reading these files, I'm hoping someone could spot any consistent issue in them.

Otherwise, I have updated my BIOS and many drivers to the latest version, I have changed sleep wait time to 0 minutes (something recommended for similar issues elsewhere), I have updated Windows and so on, but the problem persists. I have absolutely no issues with this system, crashes or otherwise, besides this.

Any help or insight is much appreciated.
Thanks.
 
Sort by date Sort by votes
overall, looks like some driver is taking too long and causing other drivers not to get time to respond.
need a kernel memory dump to figure out the driver name.
best guess is the hpomencustomcapdriver.sys
just because capture drivers take time and it is old.
------------
so far best guess is
hpomencustomcapdriver.sys Wed Oct 25 14:24:00 2017
taking too long.
(still have one bugcheck to look at)
last bugcheck was in nvidia display container
NVDisplay.Cont looks like it is a victim.
--------
one timeout had
mullvad-wireguard.sys Tue Jun 4 05:21:55 2024
on the stack, looks like some network function issue.
(it could just be a victim rather than the cause of the problem)
normally, you would update the driver, and the wifi, ethernet and bluetooth drivers since you don't know the cause of the slowdown.
-----------
you might update or uninstall the hp omen gaming drivers.

will take a look at the dumps to see if I can see the driver name that is causing the timeout.

looks like you need to provide a kernel dump in order to debug this problem. The minidump does not contain the proper debug info.

looks like some driver is taking too long and is causing a bugcheck. One bugcheck was in DAM.sys which is desktop activity monitor. This is used to allow certain functions while the screen is turned off.

still looking at the other dumps.
 
Last edited:
Upvote 0 Downvote
johnbl said:
looks like you need to provide a kernel dump in order to debug this problem.
Click to expand...
Another identical crash occurred, however a kernel dump file was not generated and I'm unsure why. There is no MEMORY.dmp in my root folder.

I have changed the dump type from advanced system settings and ensured my page file is large enough (it was set to 25GB by default, which is considerably more than my memory already.) The minidumps were created without issue, so I have no idea what went wrong here. I have an error in event viewer stating the dump file creation failed:
Log Name: System
Source: volmgr
Date: 18/04/2025 04:57:12
Event ID: 161
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SUZUPC
Description:
Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x10080804
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volmgr" />
<EventID Qualifiers="49156">161</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-04-18T03:57:12.7737200Z" />
<EventRecordID>9186</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="424" />
<Channel>System</Channel>
<Computer>SUZUPC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolume3</Data>
<Data>0x10080804</Data>
<Binary>000000000200300000000000A10004C004080810010000C000000000000000000000000000000000</Binary>
</EventData>
</Event>

As far as I can tell from listing my disk volumes, volume 3 is apparently my second SSD. The page file and root directory are correctly set to my first SSD, where the operating system is located. All crash dump events, including the successful ones, reference \Device\HarddiskVolume3
 
Last edited:
Upvote 0 Downvote
SBazu said:
Another identical crash occurred, however a kernel dump file was not generated and I'm unsure why. There is no MEMORY.dmp in my root folder.

I have changed the dump type from advanced system settings and ensured my page file is large enough (it was set to 25GB by default, which is considerably more than my memory already.) The minidumps were created without issue, so I have no idea what went wrong here. I have an error in event viewer stating the dump file creation failed:
Log Name: System
Source: volmgr
Date: 18/04/2025 04:57:12
Event ID: 161
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SUZUPC
Description:
Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x10080804
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volmgr" />
<EventID Qualifiers="49156">161</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-04-18T03:57:12.7737200Z" />
<EventRecordID>9186</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="424" />
<Channel>System</Channel>
<Computer>SUZUPC</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolume3</Data>
<Data>0x10080804</Data>
<Binary>000000000200300000000000A10004C004080810010000C000000000000000000000000000000000</Binary>
</EventData>
</Event>

As far as I can tell from listing my disk volumes, volume 3 is apparently my second SSD. The page file and root directory are correctly set to my first SSD, where the operating system is located. All crash dump events, including the successful ones, reference \Device\HarddiskVolume3
Click to expand...
google how to force a window memory dump using a keyboard.
then make the registry settings and use your keyboard to force a memory dump on the working system. Do this to make sure your system is configured correctly for a kernel dump.
 
Upvote 0 Downvote
error code is unusual.

C:\Users\Cloud\Downloads>err_6.4.5.exe 0x10080804
# Value 0x10080804 is an NTSTATUS value: treating as 0x80804
# No results found for hex 0x80804 / decimal 526340
# NOT FOUND: 0x10080804


maybe error code 804
STATUS_CONTENT_BLOCKED
An operation failed because the content was blocked.
code 0x10080804 breaks down to
1= severity code = failure
0080 = facility-itf code (subsystem that made the code) 8 = Used for additional error codes from Microsoft-defined interfaces.

804 would be the actual error code
 
Last edited:
Upvote 0 Downvote
johnbl said:
google how to force a window memory dump using a keyboard.
then make the registry settings and use your keyboard to force a memory dump on the working system. Do this to make sure your system is configured correctly for a kernel dump.
Click to expand...
I can confirm that a 2GB MEMORY.dmp file was successfully generated on a forced crash.

johnbl said:
error code is unusual.

C:\Users\Cloud\Downloads>err_6.4.5.exe 0x10080804
# Value 0x10080804 is an NTSTATUS value: treating as 0x80804
# No results found for hex 0x80804 / decimal 526340
# NOT FOUND: 0x10080804


maybe error code 804
STATUS_CONTENT_BLOCKED
An operation failed because the content was blocked.
code 0x10080804 breaks down to
1= severity code = failure
0080 = facility-itf code (subsystem that made the code) 8 = Used for additional error codes from Microsoft-defined interfaces.

804 would be the actual error code
Click to expand...
I am unsure what this is referring to. I do not have a Cloud folder in my Users folder, and I don't think I've ever had one (this is a very new laptop.)
 
Upvote 0 Downvote
SBazu said:
I can confirm that a 2GB MEMORY.dmp file was successfully generated on a forced crash.


I am unsure what this is referring to. I do not have a Cloud folder in my Users folder, and I don't think I've ever had one (this is a very new laptop.)
Click to expand...
no I was just running a utility to look up error codes on my machines. utility was called err_6.4.5.exe
error code looking up was 0x10080804

cloud directory was on my local machine.
edit: microsoft error lookup tool
https://www.microsoft.com/en-my/dow...0432&msockid=190d9e52241a6eda33d48b3925376f94
 
Upvote 0 Downvote
if you want to, you can put the kernel dump that you made on the running system and I can take a quick look. often errors show up hours before the system crashes. Or you can wait for the system to crash. the kernel dumps should have hardware info and internal logs.
 
Upvote 0 Downvote
johnbl said:
if you want to, you can put the kernel dump that you made on the running system and I can take a quick look. often errors show up hours before the system crashes. Or you can wait for the system to crash. the kernel dumps should have hardware info and internal logs.
Click to expand...
I've been waiting for the crash to reoccur, but it hasn't happened yet. Instead, when going to wake my PC, my display driver was unable to start up properly, leaving the screen black with only my mouse visible. This persisted across restarts, and was only fixed by changing from discrete mode (dgpu only) to hybrid mode (both igpu and dgpu) in the BIOS.
I'm unsure if this is just a symptom or the cause. Or an entirely different issue.

In the meantime, I've uploaded the previous forced crash log. Maybe something will be in there.
https://www.mediafire.com/file/df4pl9wfv66qu5w/MEMORY.zip/file
 
Upvote 0 Downvote
notes:
looking at running kernel dump.
dxgkrnl!DpiPowerArbiterThread

mtkwl6ex.sys looks like it is in the wrong sleep RTKVHD64.sys looks like wrong sleep state

usb3 hub 1 port 4 invalid request. looks like the media tek drive did not know what the wakeup signal was.
looks like you have a default driver installed.
SystemRoot\System32\DriverStore\FileRepository\mtkwl6ex.inf_amd64_26d24c0f77478254\mtkwl6ex.sys Tue Jun 11 04:00:17 2024

machine info:
BiosVersion = F.11
BiosReleaseDate = 11/04/2024
SystemManufacturer = HP
SystemProductName = OMEN Gaming Laptop 17-db0xxx
SystemFamily = 103C_5335M7 HP OMEN

looks like there is a update for the realtek driver:
https://support.hp.com/us-en/drivers/omen-17.3-inch-gaming-laptop-pc-17-db0000/2102136812

no update from the vendor for the media tek driver.
I would go into windows control panel, device manager. find the media tec driver (wifi?) right mouse click to bring up properties and disable the option to let windows turn if off to save power. (it look like it does not know how to wake up correctly)
I would then try to find a driver update directly from media tek.

looks like the microsoft update catalog has newer drivers

https://www.catalog.update.microsoft.com/Search.aspx?q=MediaTek Wi-Fi 6E MT7922 (RZ616) 160MHz Wireless LAN Card

i would check window update first (maybe under optional updates)

i think if you get the update files (2-12-2025)
from the microsoft catalog, you have to download them, extract them then go into windows control panel device manager, and attempt to update the drivers but not use the automatic update but the option that lets you pick the drivers from your local machine. Then you have to put the location where you downloaded and extracted the driver on the local machine.

I would expect there are a lot of machine failures due to this error.
I think another work around would be to tell the usb3 ports not to sleep. via windows control panel, device manager (right click on the usb3 port to bring up properties and go to the power management tab and disable the option to let the port sleep)
in your case usb 3 port 4. who knows about other machines. EU regulations require that the usb ports are set to sleep by default to save power.
 
Last edited:
Upvote 0 Downvote
Thanks, I'll give all this a shot. I've updated everything now, will have to see if the problem reoccurs or not.

For the mediatek driver, I assume the relevant value is Advanced > Power Saving > Disabled. It doesn't have a Power Management tab of its own.

johnbl said:
I think another work around would be to tell the usb3 ports not to sleep. via windows control panel, device manager (right click on the usb3 port to bring up properties and go to the power management tab and disable the option to let the port sleep)
in your case usb 3 port 4. who knows about other machines. EU regulations require that the usb ports are set to sleep by default to save power.
Click to expand...
As for this, I'm unsure how to determine which device would be relevant here. I have four "AMD USB 3.10 eXtensible Host Controller" devices and four "USB Root Hub" devices but none list the port they're for. Should I just set them all to power saving disabled? Also, this laptop only has 3 USB ports. Not sure why there's four listed.

Again, much appreciated. Thanks for your time on this.
 
Upvote 0 Downvote
use this tool to view the usb tree. (from a german developer)
https://www.uwe-sieber.de/usbtreeview_e.html

laptops now connect internal devices to the usb port and route the signals inside the laptop to the pci/e bus. Only a few of the port connections have a external port plug that you can see from outside of the machine. bugs on any of the drivers on the internal usb can hang the pci/e port. makes it hard to figure out the problem.
 
Upvote 0 Downvote
i think this update is the one you want:

https://support.hp.com/us-en/driver...top-pc-17-db0000/model/2102136834?sku=A2DK3EA

AMD Neural Processing Unit (NPU) Driver
update on Apr 7, 2025
it is under the driver chipset section. looks like there is a bios update and others also.

(i would update the bios/firmware and drivers, I am pretty sure it is a bug and you did not unplug your amd ipu from your motherboard, (as indicated in the memory dump)
-------------
if you can not find a bios or chip update, you might be able to disable the IpuMcdmDriver service and reboot.
you will not have the AI but it will not block access to the
dxgkrnl!DpiPowerArbiterThread
see if you can find a update to ipustack.sys
-------------
look in control panel,device manger at amd ipu
(amd image processing unit) try to update the driver or find out why it failed. looks like the device is an ai processor in the newer chips. I would look for a update
maybe in the cpu chipset drivers. (or bios update, not sure)

I think the device failed and left the service holding a lock. looks like other video services can not get service since they can not get the lock.

BiosVersion = F.11
BiosReleaseDate = 11/04/2024
SystemProductName = OMEN Gaming Laptop 17-db0xxx
SystemFamily = 103C_5335M7 HP OMEN

15: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3793
Identifier = REG_SZ AMD64 Family 25 Model 117 Stepping 2
ProcessorNameString = REG_SZ AMD Ryzen 7 8845HS w/ Radeon 780M Graphics

------------
system hit a watchdog timeout while running a vpn wiregaurd.
looks like it was sending a bunch of datagram packets thru windsock out the network at the time.

the only really interesting thing it looks like your video driver was sending network packets, hitting the symcryptk driver then routing it to your storage driver. maybe streaming to disk but slowing down the network driver.

looks reasonable if you were streaming to disk at the time.

i think with the streaming, encryption and the vpn the wireless driver just got bogged down and something timed out.

the through put of a wireless driver is a function of the distance from the wireless antenna to the router antenna. it is a 1/(r^2) function.. ie through put drops by the square of the distance.

So, decrease the distance from the computer router to the computer. (or increase the power to the antenna on the computer and router if you can) on windows, you set your wireless card to run in high performance mode and not let it go into low power mode and you should avoid this bugcheck.
(best guess)

edit: turn off the nvidia card streaming to disk if you left it on by mistake

looks like you have a plug and play problem,
it tried to remove a device but it was locked. then the device was removed anyway.
error was
15: kd> !error 0xc0000182
Error code: (NTSTATUS) 0xc0000182 (3221225858) - The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect.
the service was IpuMcdmDriver
i think ipu measnimage processing unit.
vender id =1022 device id =1502
1022= AMD

looks like amd ipu driver is not installed correctly. (or failed)
check control panel device manager for yellow caution icons

looks like your vpn is waiting for the device to return
and that leads to the watchdog timeout.
MullvadWireGuard
focus on amd ipu driver for a working fix
 
Last edited:
Upvote 0 Downvote
johnbl said:
it is under the driver chipset section. looks like there is a bios update and others also.

(i would update the bios/firmware and drivers, I am pretty sure it is a bug and you did not unplug your amd ipu from your motherboard, (as indicated in the memory dump)
-------------
if you can not find a bios or chip update, you might be able to disable the IpuMcdmDriver service and reboot.
you will not have the AI but it will not block access to the
dxgkrnl!DpiPowerArbiterThread
see if you can find a update to ipustack.sys
Click to expand...
This is one of the drivers I updated previously after you linked the HP drivers previously. I went through a full install of every driver on that page, including BIOS and that AI chip driver.
It should have been up to date for the Apr. 7th release at the time of this dump.
If the dump is showing that it was still an older version, I'm not sure why.

I noticed just now that it had a yellow caution icon on it, so I rolled it back. I don't think I have any use for it, I don't use any of the AI programs on my PC and I've uninstalled copilot, so I have no qualms disabling that service.

johnbl said:
the only really interesting thing it looks like your video driver was sending network packets, hitting the symcryptk driver then routing it to your storage driver. maybe streaming to disk but slowing down the network driver.

looks reasonable if you were streaming to disk at the time.

edit: turn off the nvidia card streaming to disk if you left it on by mistake
Click to expand...

I'm unsure what you mean by the nvidia card streaming to disk. I tried searching on google and the results didn't point me anywhere. I don't know if I'd want to turn that off, or how to.
 
Upvote 0 Downvote
SBazu said:
This is one of the drivers I updated previously after you linked the HP drivers previously. I went through a full install of every driver on that page, including BIOS and that AI chip driver.
It should have been up to date for the Apr. 7th release at the time of this dump.
If the dump is showing that it was still an older version, I'm not sure why.

I noticed just now that it had a yellow caution icon on it, so I rolled it back. I don't think I have any use for it, I don't use any of the AI programs on my PC and I've uninstalled copilot, so I have no qualms disabling that service.



I'm unsure what you mean by the nvidia card streaming to disk. I tried searching on google and the results didn't point me anywhere. I don't know if I'd want to turn that off, or how to.
Click to expand...
the stack showed the nvdia driver sending to the network driver and then to the nvme driver.
maybe nvidia shadow play is turned on? lets you record to disk.
try alt+z and see if the overlay comes up. then see if you are sharing your session.
https://www.partitionwizard.com/partitionmagic/how-to-disable-nvidia-overlay.html

looked like the recording was working without problems.

I think the ai processor had a problem, disconnected from the bus and left the service holding a lock that cause everything to back up. I think the device is hardwired in and should never disconnect and it disconnected anyway. Looks like the ai processor was doing something to all of the video sources before other drivers got their access. if you disable the service that talks to the ai chip it should prevent the lock. IE disable
the service for amd ipu IpuMcdmDriver
(i see three different names for the module)
and reboot. better to get it fixed if you can.

note: you might have to stop the service, disable it, reboot before you run the update. Or the update might not get installed.
 
Last edited:
Upvote 0 Downvote
johnbl said:
the stack showed the nvdia driver sending to the network driver and then to the nvme driver.
maybe nvidia shadow play is turned on? lets you record to disk.
try alt+z and see if the overlay comes up. then see if you are sharing your session.
https://www.partitionwizard.com/partitionmagic/how-to-disable-nvidia-overlay.html
Click to expand...
I always have the nvidia game overlay off, and even in the overlay settings I have all recording settings turned off. I have no idea what it could be doing.
Trying to look up this behaviour on google is giving me nothing.
 
Upvote 0 Downvote
SBazu said:
I always have the nvidia game overlay off, and even in the overlay settings I have all recording settings turned off. I have no idea what it could be doing.
Trying to look up this behaviour on google is giving me nothing.
Click to expand...
maybe discord is recording?

you have a something called
l1vhlwf.sys
it looks like there is a unprintable character before the name. (strange)
some hypervisor service?
https://www.thewindowsclub.com/hypervisor-feature-is-not-available-to-the-user
 
Last edited:
Upvote 0 Downvote
johnbl said:
maybe discord is recording?

you have a something called
l1vhlwf.sys
it looks like there is a unprintable character before the name. (strange)
some hypervisor service?
https://www.thewindowsclub.com/hypervisor-feature-is-not-available-to-the-user
Click to expand...
I don't believe so? Frankly I'm confused as to what could be doing this. I don't believe I have any programs I'm aware of that would be doing anything like that while the computer is idling. It's a little bit concerning, honestly.

I don't think I use the hypervisor platform at all, so I've just disabled that service in the registry for now.

johnbl said:
from the kernel dump most of your device are ready and running but you have one device that is in D3 state.
nvvad_WaveExtensible
you might uninstall the nvidia drivers and do a clean install of the current one. (looks like other devices were in d0 state)
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/device-power-states
Click to expand...
Looks like issues with this device are fairly common. I've uninstalled my nvidia display device and reinstalled it with the latest drivers, leaving the nvidia HD audio drivers unchecked (which seems to be what nvvad_WaveExtensible is related to.)

I've also now disabled the neural processor, as I don't think I need it for anything. I couldn't find a way to disable the related service you listed, however.

I did have two crashes between my last post and now. I have a kernel dump of the first one, but the second one only generated a minidump. Checked my settings, and I'd somehow been switched back to minidumps. Fixed now.

With all that done, I'll await another crash (hopefully not).
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom