Laptop hangs while in screen saver

garyfritz said:

It does sound similar. I'm running F.33 now. I'll try reverting to F.27 and see if it helps. Thanks!

No, I haven't posted this to any HP sites yet, just here and on a Microsoft site. I haven't had great luck with the HP sites.

You're most welcome.

Please advise if rolling back the bios improves the condition.

The only advantage of looking at the HP sites might be finding many other users with the same issue. I'm reading a 3rd HP site now and it seems this freezing issue is quite common. How it is triggered seems to vary a bit.

One fix that sounds like it reduces the frequency is enabling virtualization in the bios settings, at least for one user.

I have to step out for a bit but will try to scan more of these HP sites and post anything that looks promising.

garyfritz said:

FWIW: the problem kept getting worse, until it was happening every day or so. I finally gave up and did a Windows "Refresh" -- re-installing the OS while leaving my files (but not apps) intact. A month later I'm still trying to reconstruct my environment the way I wanted it, but -- no hangs. Whatever was causing the problem was cleared up by the Refresh.

Of course, the system just bluescreened .... hadn't done that in at least a year or two. Ya wins some, ya loses some...

Hi Gary, thanks for the update.

Try this DISM online fix.

Use DISM to Repair Windows 10 Image


And follow that with an SFC check. If the SFC tool shows it has corrected integrity violations, run the SFC check again until it shows no violations found.

Run SFC Command in Windows 10

garyfritz said:

Sorry, is that fix supposed to repair the bluescreen problem?

I wouldn't expect SFC to find much, since the system was just refreshed a few weeks ago ...

I wouldn't know what to expect from your PC either which is why I would start with the basics and make no assumptions without supporting data.

DISM & SFC checks are quick, easy and definitive methods to verify the Windows image & System files. A BSOD is most likely a result of a corruption or incompatibility.

If you would prefer to begin troubleshooting without proofing the foundation, that may take longer, that's certainly your choice.
As an alternative approach, you could test if a Clean Boot resolves your BSOD.

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts


Also, feel free to create a new thread in the BSOD area and you will get the attention of members that specialize with that type of fault.
Include a link back to this thread so that these details are available.

https://www.tenforums.com/bsod-crashes-debugging/

Hi Gary, sorry for the delayed response. Fall is incredibly busy with outside chores before the winter hits.

Analyzing CBS logs is somewhat of an artform of MS interpretation. I have always made it a practice to never run these checks unattended and therefore have only limited experience deciphering CBS logs. The summary displayed at the end of these processes tells you most everything you need to know more often than not. It either corrected the corruptions & errors or it didn't.

I have on rare occasion not witnessed the post summary in which case I would sit in front of the PC & use;

Code:

Dism /Online /Cleanup-Image /ScanHealth

As far as using these tools on a regular basis, some users do, some don't. I know there are many users that run both these checks after any significant updates to the OS, that might be worth your time to proactively proof the Component Store & System files.

I choose to only run them if I notice something irregular because I would require to disable a fix I use to control Windows updates and then reset it again afterwards.

If you do choose to use them, I'd suggest being available to read the summary produced at the end. Deciphering CBS logs looks like too much effort if I can avoid it.