-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- 17m-ch1013dx Crashing

Create an account on the HP Community to personalize your profile and ask a question
12-28-2023 07:46 PM
This 17m-ch1013dx has received all MS patches and HP driver/bios updates. I've run all HP diagnostics including extended diags; all clear. Beginning 2 days after the following MS updates in June 23 it has been throwing lots of errors and crashing.
2023-06 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5027231)
2023-06 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5027119)
Here is a snapshot of the windows syslog leading up a crash.
Critical 12/28/2023 5:41:11 PM Kernel-Power 41 (63)
Information 12/28/2023 5:41:11 PM Kernel-Power 125 (86)
Information 12/28/2023 5:41:11 PM Kernel-Power 125 (86)
Information 12/28/2023 5:41:11 PM FilterManager 6 None
Information 12/28/2023 5:41:11 PM FilterManager 6 None
Error 12/28/2023 5:41:11 PM volmgr 161 None
Information 12/28/2023 5:41:11 PM Ntfs (Microsoft-Windows-Ntfs) 98 None
Information 12/28/2023 5:41:09 PM FilterManager 6 None
Information 12/28/2023 5:41:09 PM FilterManager 6 None
Information 12/28/2023 5:41:09 PM FilterManager 6 None
Information 12/28/2023 5:41:26 PM RST Middleware 25 None
Information 12/28/2023 5:41:07 PM HAL 16 None
Information 12/28/2023 5:41:07 PM Kernel-General 20 (6)
Information 12/28/2023 5:41:07 PM IsolatedUserMode 3 None
Information 12/28/2023 5:41:07 PM Hyper-V-Hypervisor 165 None
Information 12/28/2023 5:41:07 PM Hyper-V-Hypervisor 156 None
Information 12/28/2023 5:41:07 PM Hyper-V-Hypervisor 129 None
Information 12/28/2023 5:41:07 PM Hyper-V-Hypervisor 2 None
Information 12/28/2023 5:41:07 PM Hyper-V-Hypervisor 1 None
Information 12/28/2023 5:41:07 PM Kernel-Boot 30 (21)
Information 12/28/2023 5:41:07 PM Kernel-Boot 27 (33)
Information 12/28/2023 5:41:07 PM Kernel-Boot 25 (32)
Error 12/28/2023 5:41:07 PM Kernel-Boot 124 (80)
Information 12/28/2023 5:41:07 PM Kernel-Boot 238 (101)
Information 12/28/2023 5:41:07 PM Kernel-Boot 20 (31)
Information 12/28/2023 5:41:07 PM Kernel-Boot 32 (58)
Information 12/28/2023 5:41:07 PM Kernel-Boot 18 (57)
Information 12/28/2023 5:41:07 PM Kernel-Boot 153 (62)
Information 12/28/2023 5:41:25 PM EventLog 6013 None
Information 12/28/2023 5:41:25 PM EventLog 6005 None
Information 12/28/2023 5:41:25 PM EventLog 6009 None
Error 12/28/2023 5:41:25 PM EventLog 6008 None
Information 12/28/2023 5:41:07 PM Kernel-General 12 (1)
Information 12/28/2023 5:25:02 PM HttpService 114 HTTP Configuration Property Trace Task
Information 12/28/2023 5:25:02 PM Service Control Manager 7040 None
Information 12/28/2023 5:23:23 PM Kernel-General 16 None
Information 12/28/2023 5:23:22 PM Kernel-General 16 None
Information 12/28/2023 5:23:22 PM Kernel-General 16 None
Information 12/28/2023 5:22:58 PM HttpService 113 HTTP Configuration Property Trace Task
Here is a summary of all the critical errors since purchase:
Critical 10/29/2023 9:27:05 AM Kernel-Power 41 (63)
Critical 11/20/2023 9:40:56 AM Kernel-Power 41 (63)
Critical 11/22/2023 10:42:10 AM Kernel-Power 41 (63)
Critical 10/27/2023 1:26:02 PM Kernel-Power 41 (63)
Critical 9/2/2023 10:12:05 AM Kernel-Power 41 (63)
Critical 12/12/2023 5:38:40 PM Kernel-Power 41 (63)
Critical 10/1/2023 6:40:17 PM Kernel-Power 41 (63)
Critical 11/18/2023 4:42:11 PM Kernel-Power 41 (63)
Critical 12/28/2023 5:41:11 PM Kernel-Power 41 (63)
Critical 12/14/2023 11:29:12 AM Kernel-Power 41 (63)
Critical 8/6/2023 10:40:23 PM WinREAgent 4502 None
Critical 11/29/2023 10:38:41 AM Kernel-Power 41 (63)
Critical 6/20/2023 8:35:13 PM Kernel-Power 41 (63)
Critical 9/18/2023 1:28:44 PM Kernel-Power 41 (63)
Critical 12/8/2023 9:05:19 AM Kernel-Power 41 (63)
Critical 7/18/2023 4:47:36 PM Kernel-Power 41 (63)
Critical 10/22/2023 4:50:19 PM Kernel-Power 41 (63)
Critical 9/19/2023 7:25:50 PM Kernel-Power 41 (63)
Critical 12/22/2023 10:51:22 AM Kernel-Power 41 (63)
Critical 10/28/2023 9:14:06 AM WinREAgent 4502 None
Critical 12/13/2023 10:42:48 AM Kernel-Power 41 (63)
Critical 8/12/2023 9:22:41 AM Kernel-Power 41 (63)
Critical 11/12/2023 5:23:15 PM Kernel-Power 41 (63)
Critical 9/7/2023 4:27:27 PM Kernel-Power 41 (63)
Critical 11/28/2023 11:16:39 AM Kernel-Power 41 (63)
Critical 12/21/2023 3:28:42 PM Kernel-Power 41 (63)
Critical 12/26/2023 11:32:23 AM Kernel-Power 41 (63)
Critical 9/18/2023 8:13:42 PM Kernel-Power 41 (63)
Critical 12/27/2023 9:01:39 PM Kernel-Power 41 (63)
Critical 10/12/2023 5:24:39 PM WinREAgent 4502 None
Critical 9/30/2023 12:36:01 PM Kernel-Power 41 (63)
Critical 11/17/2023 12:01:01 PM WinREAgent 4502 None
Critical 12/12/2023 10:35:41 PM WinREAgent 4502 None
Critical 7/22/2023 2:32:48 PM Kernel-Power 41 (63)
Critical 7/2/2023 8:59:12 PM Kernel-Power 41 (63)
Critical 12/1/2023 2:47:01 PM Kernel-Power 41 (63)
Critical 12/27/2023 9:20:22 AM Kernel-Power 41 (63)
Critical 8/7/2023 10:24:02 AM Kernel-Power 41 (63)
Critical 12/7/2023 9:00:31 AM WinREAgent 4502 None
Critical 9/8/2023 9:01:29 AM Kernel-Power 41 (63)
Critical 12/2/2023 10:54:45 AM Kernel-Power 41 (63)
Critical 12/28/2023 6:23:18 AM Kernel-Power 41 (63)
Critical 8/24/2023 8:00:04 AM Kernel-Power 41 (63)
Thoughts?
Solved! Go to Solution.
Accepted Solutions
12-29-2023 11:17 AM - edited 12-29-2023 02:58 PM
Answering my own question.... looks like an incorrect firefox user agent string was triggering entries in the kernel trace back file who's default allocation was too small (20MB). Solution was to reinstall firefox *AND* increase the kernel trace back allocation size (40MB).
After these 2 fixes the machine went from > 300 errors plus > 1 critical per day to about 60 per day , none critical
Long night. too long for this retired engineer.
12-29-2023 11:17 AM - edited 12-29-2023 02:58 PM
Answering my own question.... looks like an incorrect firefox user agent string was triggering entries in the kernel trace back file who's default allocation was too small (20MB). Solution was to reinstall firefox *AND* increase the kernel trace back allocation size (40MB).
After these 2 fixes the machine went from > 300 errors plus > 1 critical per day to about 60 per day , none critical
Long night. too long for this retired engineer.