BSOD - Critical Process Died

XTMercenary · 06 Jan 2018

Hi All,

Would appreciate if someone could take a look at this bluescreen for me, crashes whilst playing destiny 2, but has also occurred outside of the game.

I have already done the following:
Scanned SSDS for faults
run memtest86 on RAM
Clean installed Windows 10 1709
SSD configuration raid 0 2x Samsung 850
OS Drive - Samsung SSD 840

Any help much appreciated.

Cheers

zbook · 07 Jan 2018

Hi XTMercenary,

Welcome to Ten Forums BSOD Forum.

There were 2 BSOD mini dump files.
The debugging did not yet indicate a definitive misbehaving driver.

Please update the system specs in the "MyComputer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

For all steps please post post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) 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

6) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

7) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

8) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

10) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

11) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed
12) Click analyze > look for dead or deaddead in the results > post the results into the thread

13) Run this log collector after the above steps and post a zip into the thread:
log collector v2-beta06.zip

14) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

15) Backup all files to another drive or to the cloud
16) Make a backup image using Macrium
Macrium Software | Macrium Reflect Free
17) Save the backup image to another drive or to the cloud
18) Make a brand new restore point

19) Read these links on Windows driver verifier
20) Do not use Windows driver verifier until it is communicated in the thread.
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Code:

06/01/2018 17:38    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: ef
P2: ffffd1802c108580
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\010618-5156-01.dmp
\\?\C:\Windows\TEMP\WER-10171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CCA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CEA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_9cd8fea6a9e4b431d9b144f03372bedd85f0_00000000_cab_03143ce9

Analysis symbol: 
Rechecking for solution: 0
Report ID: f64c4473-61eb-4029-b9cd-6705018d193a
Report Status: 4
Hashed bucket:06/01/2018 17:09    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: ef
P2: ffffdd8a6f893080
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\010618-3468-01.dmp
\\?\C:\Windows\TEMP\WER-8515-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER321C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER322B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER324C.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_c6b979a83f893a9b7ba259a7cde4d5206c8fc763_00000000_cab_030c324b

Analysis symbol: 
Rechecking for solution: 0
Report ID: 42ae7f3f-f6e6-40eb-9b93-3a7d70fc1312
Report Status: 4
Hashed bucket:

Code:

06/01/2018 17:09    Windows Error Reporting    Fault bucket 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_IOERR_c000000e_IMAGE_hardware_disk, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 848973f6-f709-442c-83fa-ec1ff4fe9a1e

Problem signature:
P1: ef
P2: ffffdd8a6f893080
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\010618-3468-01.dmp
\\?\C:\Windows\TEMP\WER-8515-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER321C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER322B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER324C.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_c6b979a83f893a9b7ba259a7cde4d5206c8fc763_00000000_cab_248861f6

Analysis symbol: 
Rechecking for solution: 0
Report ID: 42ae7f3f-f6e6-40eb-9b93-3a7d70fc1312
Report Status: 268435456
Hashed bucket:

Code:

06/01/2018 17:38    Windows Error Reporting    Fault bucket ACCESS_VIOLATION_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0efd51c3-a202-446b-8ff3-64b418a5cc2d

Problem signature:
P1: ef
P2: ffffd1802c108580
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\010618-5156-01.dmp
\\?\C:\Windows\TEMP\WER-10171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CCA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CEA.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_9cd8fea6a9e4b431d9b144f03372bedd85f0_00000000_cab_28706e98

Analysis symbol: 
Rechecking for solution: 0
Report ID: f64c4473-61eb-4029-b9cd-6705018d193a
Report Status: 268435456
Hashed bucket:

Code:

Event[1579]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2018-01-05T21:03:23.663  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Zack-PC  Description: Windows failed fast startup with error status 0xC00000D4.

Code:

Event[1785]:  Log Name: System  Source: volmgr  Date: 2018-01-06T14:39:47.593  Event ID: 161  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Zack-PC  Description: Dump file creation failed due to error during dump creation.

XTMercenary · 07 Jan 2018

traced this back to a faulty gpu.

Thanks for taking a look though.