I’m running a DIY frame.work laptop with 64G RAM and the top tier i7 mobo.
I’m charging through my Dell USB hub monitor, I’ve only recently been getting this popup, could this be related to recent software installations or is it indictive of a hardware issue ? Any way to characterize further ?
A_Fan
May 27, 2022, 4:23pm
2
Which application is popping this up?
Update: Scratch that. It’s from Windows itself.
Questions:
Do you get the popup when the laptop isn’t connected to the USB-PD charger?
Do you get the popup when using another USB-PD port (one of the other three)?
The issue, although sporadic, is relentless once it starts, a popup comes around once every 7-10 seconds. It renders my Windows Explorer unusable until I close down each and every one of the popup boxes.
I have my USB-C-PD connected on the left/back port going to my USB hub Dell monitor and another USB-C-PD connected to my iPhone lightning jack on the right/back port.
When I pull the USB-C PD charging (on the left/back port) the popup stops.
When I insert the USB-C PD charging cable into the left/front port the popup resumes.
I tried moving the iPhone charger to the left/front port and the monitor connection to the right/back connection, and the popups appeared to cease.
I’m getting the issue again, this time USB-C charging is plugged in right/back port.
I’m running latest v7 BIOS and latest driver package.
The issue also occurs when I’m charging USB-C to my Dell hub monitor from the front/right port.
Thus, the issue is being seen from all ports.
Oddly enough, I’m now seeing the issue persist even when I withdraw all USB-C and the laptop is running natively without any external connections !?!?
I’m going to put this to support’s attention in an attempt to highlight the problem.
The issue is back, it’s coming from the explorer.exe process, perhaps some rogue system tray app running under explorer, maybe BatteryBar. I’ll approach their support team and point them back here.
The issue is back, reapproaching support, this time this issue is happening around a bluescreen with code DRIVER_POWER_STATE_FAILURE (9f)
Senhara
September 1, 2022, 1:55am
7
Sounds like a bad Windows install. Did you run any debloat scripts?
I have already reinstalled Windows once since first installing it last October. I use Norton 360 virus + firewall + utilities as well as Malwarebytes as well as offline virus/malware scans with FixMeStick. The issue is sporadic. I’m mystified on this one. I’m running the latest v3.10 BIOS.
DHowett
September 13, 2022, 5:27pm
9
I can confirm that this error message does not originate from any Windows component. Sorry, I know that’s not terribly helpful!
If you can grab a process dump of explorer.exe
, it may be possible to determine a culprit by seeing whose message loop is running.
2 Likes
I’m still seeing the issue even after upgrading the mobo to the latest i7-1280p. I’ll get a process dump next time I see the issue.
DHowett
November 3, 2022, 3:36pm
12
The first thing that strikes me about this dump file is that you’re using BatteryBar . Looking at the stack traces in that dump, I see that there’s some C# code waiting on a message box.
Given that BatteryBar…
is written in C#
is actual software that might care about the battery
is implicated¹ in the stack that is waiting on the message box
… I’m going to guess that this battery dialog is coming from BatteryBar.
In retrospect, I see you did indicate that BatteryBar might be the cause!
¹
0:001> !DumpStack
Child-SP RetAddr Caller, Callee
...
000000000300a630 00007ff8c88897ee user32!MessageBoxW+0x4e, calling user32!MessageBoxTimeoutW
...
000000000300a840 00007ff84bdbb1fc 00007ff84bdbb1fc, calling System_Windows_Forms_ni+0xb43460
...
0:001> !U /d 00007ff84bdbb1fc
Normal JIT generated code
BatteryBar.Utilities.Controls.MessageBox.Show(System.Windows.Forms.IWin32Window, System.String, System.String, BatteryBar.Utilities.Controls.MessageBoxType)
1 Like
Thanks for pointing this out! I raised a ticket back in June at BatteryBar forum and haven’t heard back, I just made an update noting that BatteryBar had now been specifically implicated. Login - HappyFox
1 Like
The issue happened again, this time with BatteryBar exited (not in the system tray either). windbg dumps via the “Open a crash dump” menu and “!analyze -v” CLI command follow:
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10952
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 11050
Key : Analysis.Init.CPU.mSec
Value: 22312
Key : Analysis.Init.Elapsed.mSec
Value: 293162
Key : Analysis.Memory.CommitPeak.Mb
Value: 161
Key : Timeline.OS.Boot.DeltaSec
Value: 479335
Key : Timeline.Process.Start.DeltaSec
Value: 441253
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
Key : WER.Process.Version
Value: 10.0.19041.2193
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00004f54
PROCESS_NAME: explorer.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`00fdf7b8 00007ffd`f71207ce : 00000000`00000000 00007ffd`f710a523 00000000`00000000 00000000`00fdf8d8 : win32u!NtUserMsgWaitForMultipleObjectsEx+0x14
00000000`00fdf7c0 00007ffd`a33333c3 : 00000000`00000000 00000000`00fdf860 00000000`00000001 00000000`00fdf928 : user32!RealMsgWaitForMultipleObjectsEx+0x1e
00000000`00fdf800 00007ffd`a33b9f46 : 00000000`00000000 00000000`00000006 00000000`00000001 00000000`00000102 : explorerframe!SHProcessMessagesUntilEventsEx+0x87
00000000`00fdf890 00007ffd`a338f819 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000102 : explorerframe!SHProcessMessagesUntilEventEx+0x22
00000000`00fdf8d0 00007ff6`4bce38aa : 00000000`00000000 00000000`00000002 00000000`01257860 00000000`00000000 : explorerframe!CExplorerHostCreator::RunHost+0x38ea9
00000000`00fdf910 00007ff6`4bd62466 : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!wWinMain+0x632
00000000`00fdfd40 00007ffd`f5c574b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!__scrt_common_main_seh+0x106
00000000`00fdfd80 00007ffd`f74826a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`00fdfdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: win32u!NtUserMsgWaitForMultipleObjectsEx+14
MODULE_NAME: win32u
IMAGE_NAME: win32u.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_win32u.dll!NtUserMsgWaitForMultipleObjectsEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.19041.2251
FAILURE_ID_HASH: {ab2d2e3e-edb3-a979-68f2-e3be023a5515}
Followup: MachineOwner
---------
Another dump taken when the problem was seen again :
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 266140
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 271697
Key : Analysis.Init.CPU.mSec
Value: 324984
Key : Analysis.Init.Elapsed.mSec
Value: 866455
Key : Analysis.Memory.CommitPeak.Mb
Value: 591
Key : CLR.BuiltBy
Value: NET48REL1LAST_C
Key : CLR.Engine
Value: CLR
Key : CLR.Version
Value: 4.8.4515.0
Key : Timeline.OS.Boot.DeltaSec
Value: 479347
Key : Timeline.Process.Start.DeltaSec
Value: 82955
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
Key : WER.Process.Version
Value: 10.0.19041.2193
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00004ed4
PROCESS_NAME: explorer.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`0017f3d8 00007ffd`f552104c : 00000000`16092570 00000000`0017f590 00000000`000002e8 00007ffd`f5563297 : win32u!NtUserWaitMessage+0x14
00000000`0017f3e0 00007ffd`f5520e46 : 00000000`0e676e30 00000000`161695e0 00000000`000002e8 00000000`000002e8 : shell32!CDesktopBrowser::_MessageLoop+0x4c
00000000`0017f460 00007ff6`4bce3e99 : 00000000`00000000 00000000`00000df2 00000000`00000000 00000000`000002e8 : shell32!SHDesktopMessageLoop+0x36
00000000`0017f490 00007ff6`4bd62466 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!wWinMain+0xc21
00000000`0017f8c0 00007ffd`f5c574b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!__scrt_common_main_seh+0x106
00000000`0017f900 00007ffd`f74826a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`0017f930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: win32u!NtUserWaitMessage+14
MODULE_NAME: win32u
IMAGE_NAME: win32u.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_win32u.dll!NtUserWaitMessage
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.19041.2251
FAILURE_ID_HASH: {a106cd41-a8b1-c51d-6d94-a75661270841}
Followup: MachineOwner
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 781
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 903
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 530
Key : Analysis.Init.Elapsed.mSec
Value: 5424
Key : Analysis.Memory.CommitPeak.Mb
Value: 119
Key : Timeline.OS.Boot.DeltaSec
Value: 555738
Key : Timeline.Process.Start.DeltaSec
Value: 517657
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
Key : WER.Process.Version
Value: 10.0.19041.2193
FILE_IN_CAB: explorer (4).DMP
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00004f54
PROCESS_NAME: explorer.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`00fdf7b8 00007ffd`f71207ce : 00000000`00000000 00007ffd`f710a523 00000000`00000000 00000000`00fdf8d8 : win32u!NtUserMsgWaitForMultipleObjectsEx+0x14
00000000`00fdf7c0 00007ffd`a33333c3 : 00000000`00000000 00000000`00fdf860 00000000`00000001 00000000`00fdf928 : user32!RealMsgWaitForMultipleObjectsEx+0x1e
00000000`00fdf800 00007ffd`a33b9f46 : 00000000`00000000 00000000`00000006 00000000`00000001 00000000`00000102 : explorerframe!SHProcessMessagesUntilEventsEx+0x87
00000000`00fdf890 00007ffd`a338f819 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000102 : explorerframe!SHProcessMessagesUntilEventEx+0x22
00000000`00fdf8d0 00007ff6`4bce38aa : 00000000`00000000 00000000`00000002 00000000`01257860 00000000`00000000 : explorerframe!CExplorerHostCreator::RunHost+0x38ea9
00000000`00fdf910 00007ff6`4bd62466 : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!wWinMain+0x632
00000000`00fdfd40 00007ffd`f5c574b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!__scrt_common_main_seh+0x106
00000000`00fdfd80 00007ffd`f74826a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`00fdfdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: win32u!NtUserMsgWaitForMultipleObjectsEx+14
MODULE_NAME: win32u
IMAGE_NAME: win32u.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_win32u.dll!NtUserMsgWaitForMultipleObjectsEx
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.19041.2251
FAILURE_ID_HASH: {ab2d2e3e-edb3-a979-68f2-e3be023a5515}
Followup: MachineOwner
---------
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 103453
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 107094
Key : Analysis.IO.Other.Mb
Value: 1
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 7
Key : Analysis.Init.CPU.mSec
Value: 1624
Key : Analysis.Init.Elapsed.mSec
Value: 10320
Key : Analysis.Memory.CommitPeak.Mb
Value: 645
Key : CLR.BuiltBy
Value: NET48REL1LAST_C
Key : CLR.Engine
Value: CLR
Key : CLR.Version
Value: 4.8.4515.0
Key : Timeline.OS.Boot.DeltaSec
Value: 155790
Key : Timeline.Process.Start.DeltaSec
Value: 206
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
Key : WER.Process.Version
Value: 10.0.19041.2193
FILE_IN_CAB: explorerStuckDec7_2022_err_detecting_batteries.DMP
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 0000c0b0
PROCESS_NAME: explorer.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`00a7f228 00007ffb`5c34a5c3 : ffffffff`ff52f9e7 00007ffb`5c34e703 00007ffb`5c34eb96 00000000`00000000 : win32u!NtUserPeekMessage+0x14
00000000`00a7f230 00007ffb`5c34a523 : 00000000`00000000 00000000`014b1610 00000000`00000001 00000000`00000000 : user32!_PeekMessage+0x43
00000000`00a7f2a0 00007ffb`5cb7103c : 00000000`166085a0 00000000`00a7f4c0 00000000`000002f0 00007ffb`5cbb3297 : user32!PeekMessageW+0x143
00000000`00a7f310 00007ffb`5cb70e46 : 00000000`166d7450 00000000`166e0300 00000000`000002f0 00000000`000002f0 : shell32!CDesktopBrowser::_MessageLoop+0x3c
00000000`00a7f390 00007ff7`ee633e99 : 00000000`00000000 00000000`0000109a 00000000`00000000 00000000`000002f0 : shell32!SHDesktopMessageLoop+0x36
00000000`00a7f3c0 00007ff7`ee6b2466 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!wWinMain+0xc21
00000000`00a7f7f0 00007ffb`5e0674b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!__scrt_common_main_seh+0x106
00000000`00a7f830 00007ffb`5e1a26a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`00a7f860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: win32u!NtUserPeekMessage+14
MODULE_NAME: win32u
IMAGE_NAME: win32u.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_win32u.dll!NtUserPeekMessage
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.19041.2251
FAILURE_ID_HASH: {62030ec8-14d0-9919-70d3-cbaa3c2f4413}
Followup: MachineOwner
---------