New build with sporadic BSOD different stop codes

zbook · May 23, 2024

For any BSOD please post a new V2 share link into the newest post.

slickochet · May 23, 2024

Should this PxHLpa64.sys that's causing the driver verification fails not be removed?

zbook · May 23, 2024

Plan to monitor the computer for BSOD using Reliability Monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

For any BSOD please post a new V2 share link into the newest post.

slickochet · May 28, 2024

No BSODs for a few days now. Almost 5 days of uptime so far. I did remove that troublesome driver as well as a bunch of other things using Bulk Crap Uninstaller.

zbook · May 28, 2024

In two days please post a new V2 share link into the newest post.

slickochet · May 31, 2024

No more BSODs as of yet. But I haven't been gaming on it or anything strenuous either.

Log collector link

zbook · May 31, 2024

The logs reported an unexpected shutdown and restart.

Was this a manual power offs after a hang or freeze or was this spontaneous?

Code:

Event[4972]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2024-05-30T08:26:59.6510000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: jimbob_mk_iv
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[4944]
  Log Name: System
  Source: EventLog
  Date: 2024-05-30T08:27:13.7960000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: jimbob_mk_iv
  Description:
The previous system shutdown at 23:56:27 on ?29/?05/?2024 was unexpected.

slickochet · May 31, 2024

Bit complicated to explain....I have an automated routine for bedtime that hibernates the machine, waits 90 seconds then turns off the plug. Sometimes the machine will wake up again right after hibernating (another problem I'm trying to solve) so when the plug turns off, it causes an unexpected shutdown.

slickochet · Jun 3, 2024

3 more days and no more BSODs (but again no heavy use/gaming). Find a new log collector attached.

There was another unexpected shutdown today when I turned off the wrong plug by mistake. Not a BSOD!.

zbook · Jun 3, 2024

See post #32.

How come the settings are not being maintained?

If Windows must be modified over and over again then please close the thread.

slickochet · Jun 3, 2024

Which settings? The dump settings? They are being maintained:

zbook · Jun 3, 2024

Those settings were modified by the script in:

post #2

and again in

post #32

Why not maintain the settings?

slickochet · Jun 4, 2024

I had changed that because it wasn't making dumps with the other settings. Changed back now with tuner log results

slickochet · Friday at 5:45 PM

Still no more BSODs to report. Hopefully they have been fixed but not quite sure what did it....

Log collector and Tuneup logs attached

zbook · Friday at 5:58 PM

There were no recorded BSOD in the last 30 days.

Code:

Event[35111]
  Log Name: System
  Source: BTHUSB
  Date: 2024-06-14T08:26:23.0760000Z
  Event ID: 7
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: jimbob_mk_iv
  Description:
A hardware error occurred. The event contains the vendor-specific error code.

Code:

Event[31173]
  Log Name: System
  Source: EventLog
  Date: 2024-06-03T17:28:54.1510000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: jimbob_mk_iv
  Description:
The previous system shutdown at 17:08:23 on ?03/?06/?2024 was unexpected.

Code:

Event[32380]
  Log Name: System
  Source: Display
  Date: 2024-06-04T17:30:59.6390000Z
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info  g
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: jimbob_mk_iv
  Description:
Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[31198]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2024-06-03T17:28:40.3120000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: jimbob_mk_iv
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

slickochet · Friday at 6:22 PM

It's been 23 days since the last one. It looks like the Windows repair installation wiped their history.

slickochet said:
I just got another BSOD but it restarted before I could see it and it does not seem to have made a dump file despite being told to make a minidump in the advanced startup settings.

Tried running the verifier again with the dump settings to minidump. Got 2 BSODs with it and no dump files generated.