Microsoft Windows [Version 10.0.18362.329]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>bcdedit /enum {badmemory}
RAM Defects
-----------
identifier {badmemory}
C:\WINDOWS\system32>bcdedit /enum {badmemory}
RAM Defects
-----------
identifier {badmemory}
C:\WINDOWS\system32>
So far results are good.
Startup and Recovery and Virtual Memory images of settings are attached.
Attachment 246339Attachment 246340
- - - Updated - - -
I've never run CCCleaner on Windows 10, but here are the settings.
Attachment 246342
Settings are good for startup and recovery system failure and virtual memory.
For Ccleaner uncheck:
a) Memory dumps
b) Windows log files
The bugchecks so far were:
WHEA 0x124 (internal timer)
7E
Here's the summary. Do you want to see the log files?
Attachment 246422
- - - Updated - - -
For Ccleaner uncheck:
a) Memory dumps
b) Windows log files
DONE
HP log files are not necessary.
For Driver Easy were you able to uninstall the software and reinstall drivers either from the HP or component manufacturer websites? Or was a system restore performed?
When memtest86+ version 5.01 testing has completed:
a) use a camera or smartphone camera to take pictures and post images into the thread
b) make a new restore point:
Create System Restore Point in Windows 10
c) make a backup image using Macrium and save the image to another disk drive or the cloud:
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect
d) read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread)
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983
Driver Easy was deleted. Drivers are the latest available either from vendors or Microsoft.
Will start on remaining tasks either tomorrow (Sunday) or more probably on Monday.
Thank you.
Loaded and ran Speccy. Snapshot published to:
http://speccy.piriform.com/results/E...zw3mcHrXTsPZU7
RESOLVED (in a way): I was able to determine that the instances of BSOD occurred sometime after waking my computer from Sleep mode. My practice had been never to completely shut down my computer but to put it in sleep mode for a quick start-up. However, a few moths ago, I began to use Hibernate instead of Sleep mode, and the issue of BSOD has not once recurred. From my perspective, Hibernate, unlike sleep, takes a few more seconds to start from a complete shut off, but it does return me to Windows quickly --- AND no BSODs. Thank you Zbook for all your help in diagnosing what was going on.
Nice.
Glad to read that it has been sorted.
You are welcome.
If you post a new V2 it can be scanned and read.
BSOD - Posting Instructions
Quote