Random crashing, no BSoD

Aqryllic · 15 Jun 2019

Hello,

My computer has been crashing since a few weeks ago, I don't remember what significant changes I've made. I did follow this guide to remove bloatware and just making Windows 10 lighter. I followed every instruction except the applications he proposed.

What makes this issue harder is that upon crashing, there's no BSoD; I don't think I have any log files over BSoDs. I know this thread is about solving BSoDs, but I don't think the other threads are more suited than this one.

The crashing happens out of nowhere, so as I am writing this thread, It can crash. It mainly happens when I'm using Adobe Premiere Pro or After Effects, they are resource heavy programs. However, the chances of crashing is lower when I'm playing games.

I have a setup with two storage drives: one SSD for my OS and one HDD for the big files. I have switched my old HDD which was faulty for another one. The crashing happens on the switched one too. I decided to unplug the HDD so that my SSD is the only active one, still having crashes but it seems to be less frequent.

I have the file provided by the V2 Log Collector in the attachments.

Caledon Ken · 15 Jun 2019

Hi Aqryllic

What version / build of 10 are you running?

If you check Windows updates what has been installed, in particular Drivers at the bottom of history.

Did nVidia install a new graphics driver? Can be checked in Device manager, properties of adapter, Details tab, Set Property drop down to Install date.

Is Reliability history reporting anything of substance? Click Start, type reliability History, click app.

If you use a clean boot, not clean install, does the device crash?

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Next I would look at disk(s)

Please install Crystal Disk Info Standard edition

CrystalDiskInfo – Crystal Dew World

Once installed click on "Function" tab > Advance Feature > Raw Values > 10[Dec]

This presents error values in decimal amounts.

What is the overall health status of boot disk? Are any of the categories showing a warning? Are you getting seek, write or read errors?

Then I would test memory

MemTest86+ - Test RAM

Not saying to update BIOS but could you check if you are current.

Have you run sfc /scannow ?

Ken

Aqryllic · 16 Jun 2019

Hello Caledon Ken

I'm currently using version 1809 and the build is 17763.557

I don't see any driver updates in the update history section.

The version of the graphics driver is 430.86 which is the latest update. It was installed on 30/05/2019.

The reliability history shows various critical events. The most common one being the unexpected crashes. They don't have any additional information when I view the technical details. The first unexpected crash was on 09/06/2019. I'll post screenshots of the following days and package it in a zip file if you need to take a look at them.

The computer doesn't crash when I boot into safe boot.

I have installed CrystalDiskInfo and posted screenshots in the attachments. Everything seems to be okay and nothing unusual in my eyes.

Ran MemTest86+ with 7 passes and encountered no errors.

The latest BIOS firmware is installed, which is version F7 for my Gigabyte H81M-HD3 motherboard.

Since the computer kept crashing when running:

Code:

sfc /scannow

I booted into safe mode and ran the code there. It says it fixed things, I'll include the log file in the attachment.

Also, I want to mention that the crashing happens consecutively when booting Windows (not when booting into safe mode). So if I would start the computer, it would crash at the login screen before restarting and crashing again. After a few times, I can finally get into Windows, which can crash again. The consecutive crashing doesn't happen all the time, it's like a period before finally getting over it.

Caledon Ken · 16 Jun 2019

Well I'm going with your graphics driver. Everything lines up.

You said this has been happening for a few weeks and your nVidia driver is exactly that old.

When you boot to safe mode Windows defaults to basic video driver taking your nVidia out of play.

So I would first create a System Image backup with a tool like Macrium Reflect. Create and test Macrium boot media.

Backup and Restore with Macrium Reflect

With a complete Image of the partitions required to start Windows you should be able to restore if issues arise.

Then I would download DDU and get an older nVidia driver. Say mid April.

Official Display Driver Uninstaller DDU Download

DDU will completely remove all nVidia traces. Once back in normal boot install older nVidai driver. Shut off nVidia automated driver updates.

Once everything is operational again take another System Image. You can make and keep versions of your system Images. Next time it acts up restore to a working date.

zbook · 16 Jun 2019

Code:

2019-06-16 15:56:45, Info                  CSI    00004329 [SR] Repairing corrupted file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk from store

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) wmic recoveros set autoreboot = false
6) 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

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

8) The logs displayed multiple BSOD that were not displayed in the reliability monitor

9) Find a flash drive that you can format (> or = 8 GB)

10) Create a bootable Windows 10 iso with the identical iso: 17763 (1809)

11) Run both the DM and V2 log collectors before step #12

12) Perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade

13) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

14) 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

15) 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

16) Run HD Sentinel: (free or trial edition) (all drives)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

Code:

24/04/2019 10:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 154
P2: ffff858bf575a000
P3: fffff3838c98bf80
P4: 2
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042319-8359-01.dmp
\\?\C:\Windows\TEMP\WER-34562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5E1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5F2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5F7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE608.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6656faad-ee4f-49a8-b6f0-ddf7d0bbad62
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
24/04/2019 10:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 154
P2: ffff858bf575a000
P3: fffff3838c98bf80
P4: 2
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042319-8359-01.dmp
\\?\C:\Windows\TEMP\WER-34562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5E1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5F2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5F7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE608.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6656faad-ee4f-49a8-b6f0-ddf7d0bbad62
Report Status: 4
Hashed bucket: 
Cab Guid: 0
27/04/2019 18:05	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 154
P2: ffffde8a30dee000
P3: ffffd78b150ce070
P4: 2
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042719-6437-01.dmp
\\?\C:\Windows\TEMP\WER-16609-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5285.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5311.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5331.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: eefc1c0b-a4e6-414d-93bd-62b16d1a1729
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
27/04/2019 18:05	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 154
P2: ffffde8a30dee000
P3: ffffd78b150ce070
P4: 2
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042719-6437-01.dmp
\\?\C:\Windows\TEMP\WER-16609-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5285.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5311.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5331.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: eefc1c0b-a4e6-414d-93bd-62b16d1a1729
Report Status: 4
Hashed bucket: 
Cab Guid: 0
08/04/2019 09:42	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000006
P3: fffff80317997ef2
P4: ffffdd8b3ffef5e0
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\040819-6437-01.dmp
\\?\C:\Windows\TEMP\WER-10531-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A49.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A5A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A78.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A79.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f6e886d-213d-4028-a7a6-e90ad7a4d670
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
08/04/2019 09:42	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000006
P3: fffff80317997ef2
P4: ffffdd8b3ffef5e0
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\040819-6437-01.dmp
\\?\C:\Windows\TEMP\WER-10531-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A49.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A5A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A78.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A79.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f6e886d-213d-4028-a7a6-e90ad7a4d670
Report Status: 4
Hashed bucket: 
Cab Guid: 0
24/04/2019 10:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000006
P3: fffff80761038ef2
P4: fffff2093f9f6580
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042419-6296-01.dmp
\\?\C:\Windows\TEMP\WER-34562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE582.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5A7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5C7.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 457ac6d4-bc47-4c28-b7ba-57302691589c
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
24/04/2019 10:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000006
P3: fffff80761038ef2
P4: fffff2093f9f6580
P5: 0
P6: 10_0_17763
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\042419-6296-01.dmp
\\?\C:\Windows\TEMP\WER-34562-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE582.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5A7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE5C7.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 457ac6d4-bc47-4c28-b7ba-57302691589c
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/04/2019 12:01	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
\\?\C:\Windows\Minidump\041919-6421-01.dmp
\\?\C:\Windows\TEMP\WER-12265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER739B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73BC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73BD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73EC.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: fb9e5a2f-91b2-465c-abfb-1a610f87ecb1
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
19/04/2019 12:01	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
\\?\C:\Windows\Minidump\041919-6421-01.dmp
\\?\C:\Windows\TEMP\WER-12265-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER739B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73BC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73BD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER73EC.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: fb9e5a2f-91b2-465c-abfb-1a610f87ecb1
Report Status: 4
Hashed bucket: 
Cab Guid: 0
26/04/2019 21:14	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
\\?\C:\Windows\Minidump\042619-8531-01.dmp
\\?\C:\Windows\TEMP\WER-15468-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0BD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0ED.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0F0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD101.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6767293c-765b-491c-8a0b-74f03992ce8c
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
26/04/2019 21:14	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

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

Attached files:
\\?\C:\Windows\Minidump\042619-8531-01.dmp
\\?\C:\Windows\TEMP\WER-15468-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0BD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0ED.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0F0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD101.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6767293c-765b-491c-8a0b-74f03992ce8c
Report Status: 4
Hashed bucket: 
Cab Guid: 0

zbook · 16 Jun 2019

The logs had displayed many entries related to drive problems.

Both disk 0 and disk 1.

What is the status of the removed drive?

Code:

Event[9656]:
  Log Name: System
  Source: Disk
  Date: 2019-06-15T14:41:16.255
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pascal
  Description: 
The IO operation at logical block address 0x4f21318 for Disk 1 (PDO name: \Device\00000035) failed due to a hardware error.

Code:

Event[9849]:
  Log Name: System
  Source: Disk
  Date: 2019-06-15T16:41:22.659
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Pascal
  Description: 
The IO operation at logical block address 0xa4be98 for Disk 0 (PDO name: \Device\00000034) failed due to a hardware error.

Aqryllic · 17 Jun 2019

I'm currently trying to repair install Windows 10, but the crashing keeps the computer from completing the process. How do I get by this?

I ran the cmd codes and got the results as well as the log files of DM and V2 Log Collector.

I removed the graphics driver; there's no driver installed right now.

Regarding the two disks, the only active ones are the SSD and HDD. SSD for OS and HDD for storage, I don't know much about the other ones.

zbook · 17 Jun 2019

The minidump bugcheck was 116: VIDEO_TDR_FAILURE

The misbehaving driver was nvlddmkm.sys or Nvidia GPU drivers.

A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery). This could be down to a number of reasons including drivers, heat, power to the card, a faulty PCI-e slot or simply a defective GPU. It's in your best interests to employ common sense trouble shooting techniques in these situations.

Try later and/or earlier drivers
Measure the GPU's temperatures at idle and under load
Ensure the GPU is free from dust build up and that the fan is working correctly
Reseat the GPU and check all connections are securely made
Check PSU voltages in BIOS
Try a different card.

The computer has both Intel and Nvidia GPU.
Consider temporarily removing the Nvidia GPU card.
Another option may be the ability to attach the display directly to the motherboard.

The in place upgrade repair can often be performed without BSOD using clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Code:

Name	Microsoft Basic Display Adapter
PNP Device ID	PCI\VEN_10DE&DEV_1C02&SUBSYS_37241458&REV_A1\4&1286464&0&0008
Adapter Type	NVIDIA, (Standard display types) compatible
Adapter Description	Microsoft Basic Display Adapter
Adapter RAM	0 bytes
Installed Drivers	Not Available
Driver Version	10.0.17763.1
INF File	display.inf (MSBDA section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 1 hertz
Bits/Pixel	32
Memory Address	0xF6000000-0xF6FFFFFF
Memory Address	0xE0000000-0xEFFFFFFF
Memory Address	0xF0000000-0xF1FFFFFF
I/O Port	0x0000E000-0x0000E07F
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\driverstore\filerepository\basicdisplay.inf_amd64_5103ac179273be89\basicdisplay.sys (10.0.17763.1, 66.50 KB (68,096 bytes), 9/15/2018 9:28 AM)
	
Name	Intel(R) HD Graphics 4600
PNP Device ID	PCI\VEN_8086&DEV_0412&SUBSYS_D0001458&REV_06\3&11583659&0&10
Adapter Type	Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description	Intel(R) HD Graphics 4600
Adapter RAM	1.00 GB (1,073,741,824 bytes)
Installed Drivers	igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll
Driver Version	20.19.15.4531
INF File	oem8.inf (iHSWD_w10 section)
Color Planes	Not Available
Color Table Entries	Not Available
Resolution	Not Available
Bits/Pixel	Not Available
Memory Address	0xF7400000-0xF77FFFFF
Memory Address	0xD0000000-0xDFFFFFFF
I/O Port	0x0000FF80-0x0000FFBF
IRQ Channel	IRQ 4294967289
Driver	c:\windows\system32\drivers\igdkmd64.sys (20.19.15.4531, 7.60 MB (7,966,192 bytes), 11/2/2016 12:05 AM)

Code:

Fri Oct 27 08:49:39 2017 (59F35593)