Computer Spontaneously restarts

[Hawks_Eye]

Hi @cassiopeia2 

Thanks for sharing all the details so thoroughly. You’ve done an excellent job documenting your system’s behavior, and the logs you provided—especially the restart at 14:57—give us a clear picture of what’s happening.

What the logs reveal

Here’s what stands out from your Event Viewer entries:

Volmgr 162: The Volume Manager failed to write a crash dump, which usually means the system shut down too abruptly for Windows to capture diagnostic data.

Kernel-Power 41: This critical event confirms the system rebooted without a clean shutdown—typically caused by a crash, freeze, or sudden power loss.

Kernel-PnP 41: Indicates a device failed to initialize during resume from standby, often tied to driver or hardware resume issues.

EventLog 6008: Confirms the shutdown was unexpected and not initiated by the user or system processes.

BugCheck 10001: Shows that a system crash (blue screen) occurred, pointing to a deeper fault in drivers, memory, or hardware.

Net Log On 3095: Suggests the system was unable to register with the network during startup—likely a side effect of the crash.

Service Control 7000: Indicates a service failed to start properly after the reboot, possibly due to timing or dependency issues.

TPM-WMI 18101: The Trusted Platform Module failed to initialize, which may be a secondary effect of the crash or a BIOS/firmware issue.

These entries strongly suggest a system-level crash during standby or wake, not a power adapter or voltage fluctuation. Let me know if you'd like help interpreting any specific BugCheck codes or testing further.

What to do next

1. Re-enable Microsoft services after clean boot

Yes, you should re-tick the Microsoft services you disabled:

• Open msconfig
• Under Services, check Hide all Microsoft services
• Then click Enable all
• Restart normally

This restores essential background functions.

 

2. Run system file repair (DISM and SFC)

Since you had trouble with elevated Command Prompt, here’s a simple way:

• Press Windows + S, type cmd
• Right-click Command Prompt, choose Run as administrator
• Then copy and paste these one at a time:
  DISM /Online /Cleanup-Image /RestoreHealth
• Wait for it to finish, then:
  SFC /SCANNOW

These commands repair corrupted system files that may trigger kernel crashes.

 

3. Disable hibernation and hybrid sleep

This helps if the crash occurs during wake:

• Open Command Prompt as Administrator
• Run:
  powercfg -h off
• Then go to Control Panel > Power Options > Change plan settings > Change advanced power settings
  • Under Sleep:
    • Set Sleep after: 15 minutes
    • Set Hibernate after: Never
    • Set Allow hybrid sleep: Off

 

4. Update BIOS and chipset drivers

Even if HP’s tool says “passed,” manually check for updates:

• Visit HP Drivers & Downloads
• Enter your exact model (e.g., HP Pavilion All-in-One 23.8")
• Download and install:
  • Latest BIOS
  • Chipset drivers
  • Power management drivers

You’ve done everything right by staying observant and methodical. The logs confirm a system-level crash during standby, not a power adapter fault. 

Let me know how your system behaves after these steps—we’ll keep going until it’s stable.

Regards,

Hawks_Eye

[cassiopeia2]

I've completed task 2, it replies

'Restore operation completed successfully' and 

'Resource Window Protection did not find any integrity violation'

bear in mind the majority of crashes have been during normal active operation, although never whilst under excessive load (as indicated by the processor cooling fan whirling at a high level). However since a few crashes have been during hibernation, this suggests to me it is nothing to do with heat or high load on the system.

I've downloaded and installed the latest BIOS

It tells me I don't need any more drivers at this time

As far as I can tell that is everything you have suggested has been completed.  I'll have to see if it's improved things.

[cassiopeia2]

In addition to the checks you suggested, I downloaded and ran these HP diagnostic programs with the following results.

HDD/SSD [E] Passed

TPM test Passed

System load Passed

Bluetooth modul passed

Fan [S] passed

Fan [IT] Passed

Processor Passed

USB port Failure or passed depending what peripheral I plugged in. 

Note: the restarts haven't occurred whilst the USB port was in use, so I doubt if that is anything to do with the restarting issue.

This morning (20 Nov) at around 8.45am  the computer gave out a horrid loud buzzing sound for about 10 seconds whilst I was playing a youtube video.  It didn't crash though, it just carried on normally afterwards.  This is a note to myself when I check the fault logs!

[Hawks_Eye]

Hello @cassiopeia2 

Thanks for the thorough follow-up and for running both the system file repair and HP diagnostics—your attention to detail is outstanding and really helps narrow things down.

Here’s how to interpret the latest findings and what you can try next:

What your results tell us

• The successful DISM and SFC scans confirm your system files are intact, which rules out corruption as the cause of the crashes.
• The HP diagnostics passing across storage, TPM, processor, fans, and Bluetooth modules is reassuring. The intermittent USB port behavior is likely unrelated since restarts don’t coincide with its use.
• The buzzing sound during YouTube playback could point to a temporary audio driver glitch or GPU stress, especially if it came from the speakers and not the chassis. Since it didn’t crash, it’s worth monitoring but not alarming yet.

Next steps to stabilize further

Check for audio and graphics driver updates

• Visit HP Software and Driver Downloads
• Enter your full product name or serial number
• Download and install:
  • Latest audio driver (Realtek, Conexant, or Bang & Olufsen depending on model)
  • Latest graphics driver (Intel, AMD, or NVIDIA)

Review Reliability Monitor

• Press Windows + S, type Reliability Monitor
• Open it and look for red Xs or warnings around the time of the buzzing or restarts
• This tool gives a timeline of hardware and software events and may reveal patterns or driver faults

Run HP’s Diagnose & Fix tool

• Go to Diagnose & Fix
• Download and run the tool—it checks for common issues and applies automated fixes
• This replaces older tools like Print and Scan Doctor and is more comprehensive

Optional: Enable crash dump logging

• If the system crashes again, enabling full memory dumps can help pinpoint the cause:
  • Press Windows + S, type View advanced system settings
  • Under Startup and Recovery > Settings
  • Set “Write debugging information” to Complete memory dump
  • Ensure the dump file path is %SystemRoot%\MEMORY.DMP

Let’s keep an eye on the buzzing sound and see if it recurs. If it does, we can explore audio driver rollback or GPU stress testing. 

You’re doing everything right—methodical, observant, and proactive. Let me know how it behaves after these steps.

Regards,

Hawks_Eye

[cassiopeia2]

Hawks_eye

It crashed at 12:18

How do I extract information from memory?  I've found the memory dump file it is in C:windows evidently, but I can't access it because I need admin rights and I have forgot how.  It's all very frustrating, time consuming and exhausting, because I'm getting nowhere.  I'm close  to giving up. 

Here is the reliability monitor anyway.

Incidentally according to the monthly report, most of the problems started around the start of November, although I'm sure I had them before this. is it worth resetting the computer back to October?

[cassiopeia2]

The link to the diagnose & fix isn't working.  However I've downloaded HPs software for this a week ago and it found nothing.

[cassiopeia2]

I think I managed to log in as administrator and find a file called memory.dmp; however, I can't open it because it's too big, certainly not in notepad or word.

With regard to the diagnose and fix site, I have already use HPs dedicated apps for this before I came on this thread, they had no effect.

I have removed a program I was tricked into downloading around the time these restarts started to escalate. However, it's probably just a coincidence, because I've had this problem for years, just not as frequent as over the last three weeks..

[cassiopeia2]

Here is the reliability monitor on a weekly/monthly scale.  According to this most of the problems seemed to start a month ago.  However, perhaps it only goes back 1 month?  Seems a bit of a coincidence it's 1 month exactly.

[cassiopeia2]

Hawks_eye

with regards to drivers and other downloads that Hp site tells me  

"Detection was successful but you don’t need any new software or drivers at this time"

so I think that is everything you have suggested has been done

as of now the last restart was more than 24hours ago, however there are several warnings/errors in the last hour consisting of Kernel and  distributed com events. 

Can you remind me of the most important Microsoft start up programs I need to tick.  The only one I've done so far is Microsoft defender because it sounds as if its security related.

[Hawks_Eye]

We sincerely thank you for your patience and co-operation during this troubleshooting process.

If after following these steps you still face issues, consider reaching out to our customer support over the phone for further assistance. 

This might require one-on-one interaction via remote assistance to fix the issue. 

I'm sending you a private message to guide you on the next steps.

To access it, click the private message icon in the upper-right corner of your HP Support Community profile, next to your name.

If this resolves your issue, kindly mark this post as "Accepted Solution" and click "Yes" if it was helpful.

Take care and have a great day!

Regards,

Hawks_Eye