Consistent crashes - related to hpcommrecovery...  

If you can backup all important files you are set.

If there are some files that are important that were not able to be backed up there may be options to use free and pay versions of recovery software.

There are threads related to file recovery where copy and paste had failed.

So if this is not a factor you are set.

Once you receive the RMA drive you can
a) install Windows 10 using a bootable iso
b) install HP drivers
c) install selected HP software
d) install applications
e) restore the backed up files onto the replaced drive


https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

I pulled the Crucial 500 GB SSD stick and installed the original Sandisk 128GB SSD.

I'm still having the unresponsive all black screen problem.When I went to the computer this morning, it was running (I presume an update happened over night). Would not come on, or respond. Touching the volume or cap lock did not toggle the little lights (on/off indicators) for those keys.

I did the hard shutdown. Reliability monitor only showed the "Windows was not properly shutdown" error.

The hpcommrecovery service was running. I didn't think to turn that service off after installing the previous SSD card. I'm going to turn that back off. Interestingly, there was no error reported about hpcommrecovery in reliability monitor. I browsed through the event viewer, no errors noted.

New HD Tune captures look fine:

See post #4 steps 1 - 14.

Download and install > run the latest version of the HP UEFI hardware diagnostics in system > extensive > loop until error or failure overnight.
The next AM run the component tests for graphics (some are interactive) > find a camera or smartphone camera to take pictures and post images into the thread.

After several days or a week of use of the replaced drive run V2 to collect logs > upload into this thread
BSOD - Posting Instructions

Will do.

By the way, I should mention another thing that happens: When running Chrome, after a little bit the PC locks up...just for a period of time, maybe 30 seconds. It only happens with Chrome. So, I have been using different browsers. Occasionally I'll load Chrome to see if it does it, and it does.

- - - Updated - - -

I have run the first couple commands, and continueing on.

But I did find some errors in the sfc /scannow command. I'll paste results from CMD window below, and attach the log file which has some errors noted. It's too much to paste here.

CMD screen results:

Microsoft Windows [Version 10.0.18363.657](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.657[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>

I'm actually wondering if I should just do a completely fresh Windows 10 install and start from there.




- - - Updated - - -

Below is complete window capture of the command run in CMD

Microsoft Windows [Version 10.0.18363.657](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.C:\WINDOWS\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.657[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.657[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is Windows.Stage 1: Examining basic file system structure ... 555520 file records processed.File verification completed. 5034 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 663 reparse records processed. 663484 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 663 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 53983 data files processed.CHKDSK is verifying Usn Journal... 36980144 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 123932873 KB total disk space. 103251352 KB in 329288 files. 168292 KB in 53984 indexes. 0 KB in bad sectors. 669557 KB in use by the system. 65536 KB occupied by the log file. 19843672 KB available on disk. 4096 bytes in each allocation unit. 30983218 total allocation units on disk. 4960918 allocation units available on disk.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is Windows.Stage 1: Examining basic file system structure ... 555520 file records processed.File verification completed. 5034 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 663 reparse records processed. 663484 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 663 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 53983 data files processed.CHKDSK is verifying Usn Journal... 37011200 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 123932873 KB total disk space. 103248972 KB in 329286 files. 168292 KB in 53984 indexes. 0 KB in bad sectors. 669557 KB in use by the system. 65536 KB occupied by the log file. 19846052 KB available on disk. 4096 bytes in each allocation unit. 30983218 total allocation units on disk. 4961513 allocation units available on disk.C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSEC:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSEC:\WINDOWS\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\WINDOWS\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}C:\WINDOWS\system32>

There was one corruption repaired running the scannow after the restorehealth:

Code:

2020-03-07 14:20:02, Info                  CSI    00000220 [SR] Repairing corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\\mscormmc.dll from store

Starting with a new drive or clean install allows you to install only desired software/firmware and reduce confounding factors.

I have put the original SSD stick in the computer, installed fresh Windows 10 load (from recovery), and reinstalled many of my apps.

That night I had it doing a backup with Macrium, and when I got up the next morning the screen was black, the power light was on, the laptop was warm, and there was no response. I had to do an improper shutdown.

The reliablitilty monitor only showed the improper shutdown, nothing else.

Other than that, no reoccurance of this issue. Reliability monitor is clear past 2 days. (I am not loading hpcommrecovery).

I'm waiting on the RMA'd Crucial SSD to reinstall.

With regard to the black screen where I have to hold power and shutdown and reboot to get into the laptop:

I have the hpcommrecovery disabled. So of course not getting errors on that.

The only time I have to do this is every time it updates overnight, it does not shutdown. So I go to the laptop in the morining, it is running. I lift the lid and am presented with a black screen. It never gives me a screen. I have to hold power button, etc.

When I look at the reliability monitor after rebooting, only thing for previous day is the i with information about an update. On current day the only thins listed is the X with message about an abnormal shutdown.

So, the problem at this point relates to an update and non-shutdown of the laptop.

Upload a new V2:
BSOD - Posting Instructions


For any black screen click these 4 keys simultaneously and report results into the thread:
Win + Ctrl + Shift + B


Update the status of disk drives.

There was no response at all to the key combination you told me to do. I had to hard shutdown again.

I ran the lists of tasks you first set out, capture of results are below (all appeared successful with no errors) It makes it harder to read when the newline is not captured:

C:\Diagnostic>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Diagnostic>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.720[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\Diagnostic>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.18362.1Image Version: 10.0.18363.720[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Diagnostic>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Diagnostic>chkdsk /scanThe type of the file system is NTFS.Volume label is Windows.Stage 1: Examining basic file system structure ... 555520 file records processed.File verification completed. 21422 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 3600 reparse records processed. 708744 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 3600 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 76613 data files processed.CHKDSK is verifying Usn Journal... 40454488 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 123932873 KB total disk space. 104183624 KB in 341233 files. 200312 KB in 76614 indexes. 0 KB in bad sectors. 676781 KB in use by the system. 65536 KB occupied by the log file. 18872156 KB available on disk. 4096 bytes in each allocation unit. 30983218 total allocation units on disk. 4718039 allocation units available on disk.C:\Diagnostic>wmic recoveros set autoreboot = falseUpdating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\Diagnostic>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\Diagnostic>wmic recoveros get autorebootAutoRebootFALSEC:\Diagnostic>wmic recoveros get DebugInfoTypeDebugInfoType7C:\Diagnostic>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}C:\Diagnostic>

1) Upload a new V2
2) Indicate the status of any drive that had a bad sector or failed diagnostic testing (replaced / not replaced)