Need to migrate Windows 10 installation to new SSD , it's a mess.

NavyLCDR · 15 Jul 2018

Another option would be to manually create a system partition the computer boots from on the new SSD pointing to the Original C:. Computer boots from new SSD, loads the OS from Original C:. Once that is accomplished, copy and shrink the Original C: partition to the remaining empty space on the SSD, then use the BCDBOOT command to point the system partition on the SSD to the Windows 10 that has been copied to the SSD.

A few diskpart commands and using any partitioning program to copy the Original C: partition to the SSD would have it accomplished in no time. Then you could start work on cleaning up the other drives.

lx07 · 15 Jul 2018

Teccmo said:

But when I shrunk the partition on C:, and was going to migrate the OS in USEase Partion Master (the 168 gigs like you said) it says I can move it to a drive with an EFI partition...and can't continue. I don't really understand what that means.

Stop using USEase for a second.

Go to command line and type the bits in bold not red (accepting any warnings)

diskpart
list disk
select disk 2 (...that is your SSD)
convert mbr
clean
exit

Then try again.

You have an unneeded and unallocated 8MB space at the beginning of your SSD and this will remove it. Perhaps USEase, a program I don't know, thinks it is EFI partition although it is (a) too small and (b) not formatted.

Teccmo · 15 Jul 2018

zbook said:

Please update the progress with the steps in post #6.

MiniTool Disk Partition Screenshot

Need to migrate Windows 10 installation to new SSD , it's a mess.-captureminipartition.jpg

RYZEN5-PC (2018-07-15 15 41).zip

I did the Diskpart step that SWI2 explained in post #14 and rebooted, but I still see drive D having the system label.

Need to migrate Windows 10 installation to new SSD , it's a mess.-diskmanagement2.jpg

Teccmo · 15 Jul 2018

Alright so, with a few different options here posted... which one should I take to accomplish the SSD being the only boot drive..is what I'm trying to figure out. Good look, to you guys, I do appreciate the posts and helping me out here.

zbook · 15 Jul 2018

1) The computer logs displayed multiple BSOD with the latest on July 15, 2018
2) There were no mini dumps collected by the log collector.

3) See post #6 step #4 > please post the images into the thread so that the system failure and page file settings can be modified

4) The multiple BSOD displayed bugchecks: 116, 119, A
VIDEO_TDR_ERROR
VIDEO_SCHEDULER_INTERNAL_ERROR
IRQL_NOT_LESS_OR_EQUAL

5) The BIOS: BIOS Version/Date American Megatrends Inc. P3.40, 12/27/2017
The latest BIOS update is version 4.9
Upgrade the BIOS: ASRock > Fatal1ty AB350 Gaming K4

6) Uninstall and reinstall the software related to cfosspeed

7) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 | Windows 10 Tutorials

8) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

9) Open administrative powershell and type or copy and paste:
10) sfc /scannow
11) dism /online /cleanup-image /restorehealth
12) chkdsk /scan
13) get-disk
14) get-physicaldisk
15) Get-Disk 0 | Get-StorageReliabilityCounter
16) Get-Disk 1 | Get-StorageReliabilityCounter
17) diskpart
18) list disk
19) list volume
20) select disk 0
21) detail disk
22) select disk 1
23) detail disk
24) select disk 2
25) detail disk
26) select disk 3
27) detail disk
28) 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

29) Make sure that there is no over clocking while troubleshooting.

30) Use a camera or smart phone camera to take pictures of the BIOS and post images into the thread for:
What are the BIOS 3.3, 5 and 12 voltage values?
What are the CPU voltage and frequency?

The BIOS Mode: UEFI (per the log files)
What are the settings for legacy or UEFI (native or hybrid, with or without CSM) seen within the BIOS?

31) Ensure the GPU is free from dust build up and that the fan is working correctly
32) Reseat the GPU and check all connections are securely made

Code:

+++ WER8 +++:Fault bucket , type 0Event Name: BlueScreenResponse: Not availableCab Id: 0Problem signature:P1: 116P2: ffff8206e89db4a0P3: fffff8040b57fce8P4: ffffffffc0000001P5: 3P6: 10_0_17134P7: 0_0P8: 256_1P9: P10:

Code:

7/4/2018 4:07 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff800fab37c4a0
P3: fffff809260efce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070318-44171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-46750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1FF.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1FE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD21E.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2cac4fea-159b-4b16-9a0b-eca48ac24758
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/4/2018 3:19 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff800fab37c4a0
P3: fffff809260efce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070318-44171-01.dmp
\\?\C:\WINDOWS\TEMP\WER-46750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1BF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1FF.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1FE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD21E.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2cac4fea-159b-4b16-9a0b-eca48ac24758
Report Status: 4
Hashed bucket: 
Cab Guid: 07/14/2018 10:26 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff8206e89db4a0
P3: fffff8040b57fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\071418-55890-01.dmp
\\?\C:\windows\TEMP\WER-68656-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E30.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E40.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E3F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E7F.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 064eee16-080e-4476-96fd-fd32480fab5e
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/14/2018 2:21 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff8206e89db4a0
P3: fffff8040b57fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\071418-55890-01.dmp
\\?\C:\windows\TEMP\WER-68656-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E30.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E40.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E3F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E7F.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 064eee16-080e-4476-96fd-fd32480fab5e
Report Status: 4
Hashed bucket: 
Cab Guid: 07/5/2018 12:55 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff900c9c6ed010
P3: fffff809424cfce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070418-34375-01.dmp
\\?\C:\WINDOWS\TEMP\WER-36312-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0F1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA15D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA229.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3f03495e-31f9-4647-b398-f08b9229c366
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/4/2018 11:02 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff900c9c6ed010
P3: fffff809424cfce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070418-34375-01.dmp
\\?\C:\WINDOWS\TEMP\WER-36312-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0F1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA15D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA229.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3f03495e-31f9-4647-b398-f08b9229c366
Report Status: 4
Hashed bucket: 
Cab Guid: 07/13/2018 11:53 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffc687f9073010
P3: fffff80820c1fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071318-54859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-64875-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER226B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER228B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER228A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22BA.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 61d0968c-6e35-474b-9a99-4a351e8f90af
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/13/2018 4:04 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffc687f9073010
P3: fffff80820c1fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071318-54859-01.dmp
\\?\C:\WINDOWS\TEMP\WER-64875-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER226B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER228B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER228A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22BA.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 61d0968c-6e35-474b-9a99-4a351e8f90af
Report Status: 4
Hashed bucket: 
Cab Guid: 07/3/2018 11:42 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffce87c7370010
P3: fffff8071c17fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070318-39015-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42656-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68E8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6908.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6917.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6928.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a28c16a-8584-44bb-b1f1-207c72212633
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/3/2018 11:26 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffce87c7370010
P3: fffff8071c17fce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070318-39015-01.dmp
\\?\C:\WINDOWS\TEMP\WER-42656-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68E8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6908.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6917.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6928.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a28c16a-8584-44bb-b1f1-207c72212633
Report Status: 4
Hashed bucket: 
Cab Guid: 07/4/2018 5:52 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffd30e968914a0
P3: fffff807a72cfce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070418-41796-01.dmp
\\?\C:\WINDOWS\TEMP\WER-43750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC95.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC94.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB4.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 90857c33-37f1-4664-8e79-0fe6450f47fb
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/4/2018 10:45 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffd30e968914a0
P3: fffff807a72cfce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070418-41796-01.dmp
\\?\C:\WINDOWS\TEMP\WER-43750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC84.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC95.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC94.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB4.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 90857c33-37f1-4664-8e79-0fe6450f47fb
Report Status: 4
Hashed bucket: 
Cab Guid: 07/7/2018 10:11 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffd9020673d4a0
P3: fffff80f92aafce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070718-41312-01.dmp
\\?\C:\WINDOWS\TEMP\WER-44562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6506.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6527.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6526.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6546.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: cabd2da5-3c11-47f5-80f6-0873166f763d
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/7/2018 10:05 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffffd9020673d4a0
P3: fffff80f92aafce8
P4: ffffffffc0000001
P5: 3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\070718-41312-01.dmp
\\?\C:\WINDOWS\TEMP\WER-44562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6506.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6527.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6526.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6546.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: cabd2da5-3c11-47f5-80f6-0873166f763d
Report Status: 4
Hashed bucket: 
Cab Guid: 07/13/2018 3:42 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: 1
P3: 5ddde8
P4: 5dde07
P5: ffffb80a1a96b000
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071218-57500-01.dmp
\\?\C:\WINDOWS\TEMP\WER-69218-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCCC.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1cba8328-db2c-46fc-ba1c-23e97241b9cd
Report Status: 2049
Hashed bucket: 
Cab Guid: 07/13/2018 3:39 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: 1
P3: 5ddde8
P4: 5dde07
P5: ffffb80a1a96b000
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\071218-57500-01.dmp
\\?\C:\WINDOWS\TEMP\WER-69218-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCCC.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 1cba8328-db2c-46fc-ba1c-23e97241b9cd
Report Status: 4
Hashed bucket: 
Cab Guid: 06/16/2018 3:14 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 1f8f010
P3: 2
P4: 0
P5: fffff801b4fbd9d3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061518-50015-01.dmp
\\?\C:\WINDOWS\TEMP\WER-54734-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F05.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FE0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9711.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97ED.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 342add3e-fdc3-4925-ae06-88381b640518
Report Status: 2049
Hashed bucket: 
Cab Guid: 06/16/2018 3:42 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 1f8f010
P3: 2
P4: 0
P5: fffff801b4fbd9d3
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061518-50015-01.dmp
\\?\C:\WINDOWS\TEMP\WER-54734-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F05.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7FE0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9711.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97ED.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 342add3e-fdc3-4925-ae06-88381b640518
Report Status: 4
Hashed bucket: 
Cab Guid: 06/18/2018 3:19 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: e8
P3: 2
P4: 1
P5: fffff80163e58c5a
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061718-38937-01.dmp
\\?\C:\WINDOWS\TEMP\WER-45781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER27DC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B48.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER517C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER521A.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4bdfb1af-b454-4a23-a48b-d0386d427aac
Report Status: 2049
Hashed bucket: 
Cab Guid: 06/18/2018 2:49 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: e8
P3: 2
P4: 1
P5: fffff80163e58c5a
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061718-38937-01.dmp
\\?\C:\WINDOWS\TEMP\WER-45781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER27DC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B48.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER517C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER521A.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4bdfb1af-b454-4a23-a48b-d0386d427aac
Report Status: 4
Hashed bucket: 
Cab Guid: 06/13/2018 10:10 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: fffff28000015ea0
P3: 2
P4: 0
P5: fffff80187c5a700
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061318-35906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-39406-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F58.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F97.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA071.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5C1.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 50b32b3e-0ca9-41d3-afe0-8abd8deafff3
Report Status: 2049
Hashed bucket: 
Cab Guid: 06/13/2018 9:09 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: fffff28000015ea0
P3: 2
P4: 0
P5: fffff80187c5a700
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\061318-35906-01.dmp
\\?\C:\WINDOWS\TEMP\WER-39406-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F58.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F97.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA071.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5C1.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 50b32b3e-0ca9-41d3-afe0-8abd8deafff3
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Event[6552]:  Log Name: System  Source: volmgr  Date: 2018-07-15T15:15:02.444  Event ID: 49  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Code:

Event[6048]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2018-07-14T02:16:21.772  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Ryzen5-Pc  Description: Windows failed fast startup with error status 0xC00000D4.

Code:

Event[4040]:  Log Name: System  Source: volmgr  Date: 2018-07-03T23:59:37.640  Event ID: 46  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Crash dump initialization failed!

Code:

Event[6158]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2018-07-14T10:17:29.324  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: RYZEN5-PC  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffff8206e89db4a0, 0xfffff8040b57fce8, 0xffffffffc0000001, 0x0000000000000003). A dump was saved in: C:\windows\Minidump\071418-55890-01.dmp. Report Id: 064eee16-080e-4476-96fd-fd32480fab5e.

Code:

Event[5941]:  Log Name: System  Source: TPM  Date: 2018-07-13T19:41:21.278  Event ID: 15  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Ryzen5-Pc  Description: The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer.

Code:

Event[5676]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:31.957  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5677]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:34.242  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5678]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:37.456  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5679]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:40.669  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5680]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:43.901  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5681]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:47.097  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5682]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:50.311  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5683]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:53.525  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5684]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:56.739  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.Event[5685]:  Log Name: System  Source: Display  Date: 2018-07-12T23:30:59.953  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Display driver amdkmdap stopped responding and has successfully recovered.

Code:

Event[6384]:  Log Name: System  Source: Service Control Manager  Date: 2018-07-14T18:25:09.228  Event ID: 7026  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: The following boot-start or system-start driver(s) did not load: cFosSpeeddam

Code:

Event[2325]:  Log Name: System  Source: Disk  Date: 2018-07-01T22:13:15.655  Event ID: 157  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Ryzen5-Pc  Description: Disk 0 has been surprise removed.

SIW2 · 15 Jul 2018

I did the Diskpart step that SWI2 explained in post #14 and rebooted, but I still see drive D having the system label.

If you had, then D would no longer be active or the system partition.

elevated command:
diskpart
sel vol c
act
sel vol d
inact
exi
bcdboot c:\windows /s c:

Then reboot the pc.

zbook · 15 Jul 2018

@SIW2,

The D drive is no longer active per the logs.
However it remains system.

The minitool partition also displayed D as system and C as active.

UniqueId : {00000000-0000-0000-0000-100000000000}5000C500A2B4A2B6
AccessPaths : {D:\, \\?\Volume{a541c08d-0000-0000-0000-100000000000}\}
DiskNumber : 3
DiskPath : \\?\scsi#disk&ven_&prod_st2000dx002-2dv1#7&2ee6dc1&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
DriveLetter : D
Guid :
IsActive : False
IsBoot : False
IsHidden : False
IsOffline : False
IsReadOnly : False
IsShadowCopy : False
IsDAX : False
IsSystem : True
NoDefaultDriveLetter : False
Offset : 1048576
OperationalStatus : Online
PartitionNumber : 1
Size : 1.82 TB
Type : IFS

This result may be different than disk management.

SIW2 · 15 Jul 2018

That is odd. Maybe he should try setting Disk1 first in bios boot order.

SIW2 · 15 Jul 2018

Run bootice and check under the Tab that says UEFI.

Then post a screenshot of what bootice says.

BootIce.zip

Teccmo · 15 Jul 2018

Ok. For the long checklist that was posted there.... I'm not going to do all that, because there isn't a need to. I will do some of the steps. I'm not a laymen when it comes to working on Windows and pc's... Not that anyone said I am, but I know why the BSOD's occurred only in one specific program..a game, Titanfall 2... It was a driver conflict with my GPU and some settings...at least i think that's what it was. I never get any BSOD's otherwise.

Windows Fast Boot is off, I tried it for the first time in the last day or two, and when TitanFall 2 crashed, my computer wouldn't boot, so I reset the cmos manually with the plastic clip/pin switch.

This bios, 3.40 is stable, and I don't want to upgrade it if I don't have to. The new bios's are for Zen 2 chips .. that I don't have.. and a few more M2 SSD drives that are added to the offical compatibility list. I upgraded once already to 4.60 and I had problems that caused me to reflash it to 3.40

I already have and use HWmonitor.

As far as overclocking info, it is stable and safe at a voltage under 1.4, and the Ryzen 5 1600x is OC'd at 3.9. I ran Prime95 with the current Bios config, and it is stable...no errors... for an extended period of time. No other voltages are changed.

I just cleaned the whole PC with an air compressor yesterday, when I got this SSD, and installed it into the case. No problems there or with the seating of the GPU.

Cfosspeed is XLan software that came with this ASRock mobo, it broke when the i enabled ultrafast boot (doesn't give you the option to load into the bios unless you reset with ASRock software) yesterday.

I have both UEFI and Legacy option selected for boot devices and whatever else off the top of my head, with CSM enabled.

I'm going to do step #9 right after i post this... phew, lot on that list there. I wasn't tryin to brag btw, I was jus' sayin.. I understand most of what is being said here pretty well, so we're basically on the same page. Thanks.