BSOD: Cricial Process Died

So I have an older HP machine that has been prepped for a customer and was seemingly healthy during the install and data transfer process and had no issue running PASSmark Pro without flagging any issues.

Since handing over the PC to the customer she has had several BSODs, at times with different errors, Originally I thought one of the RAM DIMMs was faulty as the PC would not post on boot and the fans would spin up full throttle and once I had removed the RAM modules one by one I thought I'd found the culprit since removing it allowed the PC to boot normally. 24 Hours later she calls me regarding the BSODs shes been getting.

Info:

OS: Windows 10 Pro x64 v1909 fresh install 3 weeks ago
Drive setup: Crucial MX500 250GB SSD - Brand new + 1TB Seagate HDD - Used
All local user directories such as desktop, documents etc redirected to Seagate drive.

So far I have tried the following:

* Ran MemTest 86+ for 15 passes with the remaining 2x 4GB modules installed = No Errors detected
* Ran Chkdsk /r /f /x on the boot drive = No issues found
* Ran Chkdsk I: /r /f /x (Seagate drive) - No Issues found
* Ran SFC /SCANNOW = No Corruption found
* Ran DISM /Online /Cleanup-Image /CheckHealth = No component store corruption found
* Ran DISM /Online /Cleanup-Image /ScanHealth = Ditto
* Ran DISM /Online /Cleanup-Image /RestoreHealth = Restore Operation completed successfully
* Checked both drives with HD Sentinal and both show 100% Health
* Used HD Tune and did a full error scan on both drives, no bad blocks detected.

* Collected logs for you lovely folks

I am returning the computer to the customer tomorrow so that she can further test the computer now that I've done all of the above, however I fear this is not the end of the issue as the above results seem to suggest there is no problem.

If somebody could point me in the right direction that would be ace.

Thank you in advance.

Hi consolerepair08,

See posting instructions:
BSOD - Posting Instructions

Does Reliability History give any reports after each event?
Does---dxdiag--- give any report,especially concerning the Display adapter?If you note the adapter version on the Display page and download it,or a later version from the maker's site,then uninstall,reinstall the adapter,using Display Driver Uninstaller [DDU],in Safe Mode,it may or might not help.
Using sfc and dism seems to indicate the problem is not connected to Win10 but elsewhere.Display adapters are often a cause.

Apologies guys, I accidentally hit submit and then the thread must have gone for approval as I couldn't find it to edit my post and add the bug files.

Attached is a compressed 7zip containing all the logs you'll need, if there are any others you need to see please ask and i'll get them uploaded.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
10) wmic recoveros get autoreboot
11) wmic recoveros get DebugInfoType
12) bcdedit /enum {badmemory}

13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

14) Make sure that there is no over clocking while troubleshooting

15) The RAM modules are mismatched.
Post the approximate time period in which each RAM module was installed

16) The BIOS: Hewlett-Packard J01 v02.15, 10/11/2011
Upgrade the BIOS 2.15 > 2.33

17) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

18) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

19) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

20) Post share links for each of these files:

C:\Windows\LiveKernelReports\NDIS-20200215-2114.dmp
C:\Windows\MEMORY.DMP

Code:

LastWriteTime       Size (MB) FullName                                           
-------------       --------- --------                                           
15/02/2020 21:14:07     11.16 C:\Windows\LiveKernelReports\NDIS-20200215-2114.dmp

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
22/02/2020 22:23:03    415.96 C:\Windows\MEMORY.DMP

21) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


22) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

Wow Zbook, you don't do things by halves do you! Customer is currently testing the PC and so far so good but it did take 6ish minutes to boot which was very strange. She is kicking off a Veeam backup tomorrow which I believe triggers the BSOD but as soon as it fails I'll follow the troubleshooting steps you provided. Thank you for the detailed instructions.