Bsod

The logs displayed the use of Windows driver verifier.

How come it is being used?

When was it started?

Which link was used for the customized settings?

Which drivers were installed using driver booster?

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
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

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

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

14) Please install this driver followed by performing Windows updates:
https://www.dell.com/support/home/us...tcode=xps-8700

15) Run the Dell diagnostics customized test overnight with these boxes checked: (post images of the results into the thread)

https://www.dell.com/support/home/us...-8700/diagnose

Code:

Performance
Bluescreen analyzer
Hard drive
Hard drive stress
Memory
Memory stress
Motherboard
Processor
Processor stress
System stress

Code:

Video capture
Video card
Video card stress

16) For all steps / tests please post images into the thread:

Take Screenshot in Windows 10

How to Upload and Post Screenshots and Files at Ten Forums

I used verifier like an idiot after googling before i found this forum. I will NEVER use that again.

- - - Updated - - -

Also ran the OCCT stress test for 2 hours and it came back with nothing I am starting the new suggestions as we speak and waiting for a flash drive for the ram test. I appreciate all of your help on this

- - - Updated - - -

Also at what point do I give up and do a fresh install of windows 10. I haven't had another BSOD in a day or two but I don't EVER want to see that screen again. Running requested tests from Zbook now will update when they are done

- - - Updated - - -

this is one of the requested cpu tests

With the current available information there is no need for a clean install.
The troubleshooting is ongoing.

BSOD are designed by Windows to shutdown the processes to reduce the likelihood of damage.
So there is a silver lining.

Windows driver verifier is designed to stress test drivers.
It serves no purpose unless the end user has the tools to debug the dump files.
There are software such as bluescreenview and whocrashed that run limited commands.

With the hardware tests, windows driver verifier, debugging, and troubleshooting logs we are able to identify the cause and fix most BSOD. There are a limited number of computers that require clean install. Some desktops may require swap testing hardware.

Microsoft Windows [Version 10.0.18363.535]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc/scannow

Beginning 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> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.535

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.535

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning 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 /scan
The type of the file system is NTFS.
Volume label is OS.

Stage 1: Examining basic file system structure ...
784640 file records processed.
File verification completed.
10505 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
44487 reparse records processed.
945314 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
44487 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
80338 data files processed.
CHKDSK is verifying Usn Journal...
37458136 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

954001407 KB total disk space.
380781624 KB in 364628 files.
189360 KB in 80339 indexes.
0 KB in bad sectors.
969059 KB in use by the system.
65536 KB occupied by the log file.
572061364 KB available on disk.

4096 bytes in each allocation unit.
238500351 total allocation units on disk.
143015341 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DEV-PC\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 = 7
Updating property(s) of '\\DEV-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\WINDOWS\system32>

Looks good.

Just did the driver and windows update says im good on that

It can be frightening when the computer crashes.
When using Windows driver verifier you must know the methods to turn off or recover from using the tool.

These are links on Windows driver verifier:

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

The tool may be used later in the thread.
Learn the commands to use in the Windows recovery environment.

So i ran the diagnostic over night and my computer went to sleep so i think it messed it up. The little thing that shows the progress is gone but it’s still says running tests on the screen do i just keep waiting?

The Dell diagnostics I've not used in many years.
It should have displayed the approximate time for the tests.

If there are drive problems it can take longer than the software predicted.
Let it keep running unless you can tell that it is frozen.
It may need to be run again.

Ok so I have tried to run that support assist three times and it never works so I give up lol I have not had another blue screen though so that is good