Where is there a log for a Startup failure

Hi

I did a repair install and ran the tests you advised
here is the data you requested from SFC; DISM; CHKDSK,HDTune; MEMTEST



Regards

Daniel

Nice progress.
See if the beta log collector using extract works with different browsers:
log collector v2-beta08.zip
If not then use the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums

Hi

do I need to run whocrashed first?

cheers

Daniel

The test crash dump can be run to see if the settings have been optimized.
Open Whocrashed > above analyze click on tools > click crash dump test > type: ACCEPT
Click analyze > post an image of the results into the thread
Run the beta log collector with different browsers clicking extract > post a zip into the thread.

Hi

I ran both log collectors, please see attached files.

Regards

Daniel

1) Please post an image of the Whocrashed analyze results.
2) In the left lower corner type: system > open system control panel > on the left pane click advanced system settings >
a) under performance click settings > under performance options click the advanced tab > under virtual memory click change > post an image of the virtual memory window into the thread

b) under startup and recovery click settings > post an image of the startup and recovery window into the thread

3) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

4) Open file explorer > this PC > C: > in the right upper corner search for livekernelreports > zip > post the folder/file into the thread

Hi

here are the files

cheers

Daniel

1) Backup all files on the computer to another drive or to the cloud
1) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
2) Make a brand new restore point

Hi

I have my boot drive cloned with Casper10, ready to be copied back in case of a problem
and all my other drives backed up, twice.

None of my data is kept on the boot drive, it is OS only plus necessary install files,
all of my programs are installed on my D drive.

I have made a restore point.

Will that be okay for what you need me to do?

Cheers

Daniel

The first log collector zip displayed approximately 10 unexpected restarts/crashes.
None of the crashes were BSOD crashes.
The crashes could have been power off with unexpected restart after system freezes or they could have been spontaneous reboots. It would be what you remember from January.

Ideally if there is a BSOD crash dump files would be created so that they could be debugged.
The Whocrashed testing indicated that the settings are correct however there were no BSOD files.
There were no error messages.
Viewing the settings also indicated that they were properly configured.

An in place upgrade repair was done to make sure that there were no problems with the operating system.
It appears to me that everything possible is fixed short of a clean install and that could be done if there were registry problems.

So what I would like to see is whether there are or are not any misbehaving drivers.
And if there are any misbehaving drivers whether you would or would not be able to troubleshoot by finding either:
mini, memory, or kernel dump files/reports.

This is optional and does not need to be done at this time.
It is puzzling that the computer has not created dump files with the crash dump test.

If you turn on Windows driver verifier and there are any misbehaving drivers it should BSOD.
In the BSOD window it should display a bugcheck and sometimes it may display a misbehaving driver in the form *.sys.
If you have no misbehaving drivers or malfunctioning hardware there will not be any BSOD.
If there are BSOD you will want to be able to find files to debug them and fix the misbehaving drivers or malfunctioning hardware.

So if you turn on Windows driver verifer it will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off.

There are 3 methods to turn off the tool or recover from the crash and they are using the Windows advanced troubleshooting menu.
a) startup options (not startup repair) > click restart > select #6, safe mode with command prompt > type:
verifier /reset
b) command prompt > Administrator: X:\Windows\system32\cmd.exe > X:\Sources:> type:
verifier /bootmode resetonbootfail
c) system restore
To turn off windows driver verifer the first method should always be choice a followed by choice b, then choice c. Using system restore often leads to loss of the files and little progress is made in the troubleshooting.

So after any dump > turn off windows driver verifier > return to the desktop > run whocrashed > view the analyzed results > uninstall the misbehaving driver > a replacement driver can be reinstalled immediately or after all misbehaving drivers have been fixed.

Submit a new zip after each BSOD for troubleshooting.

Whocrashed will indicate whether there is nor is not a dump file.
This would indicate whether there is a mini or memory dump.
Whocrashed is not likely to view the livekernelreports file.

So after any BSOD open file explorer > this PC > C: > in the right upper corner search for livekernelreports > zip > post into the thread

Start with the 3 customized test settings in this link:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

If there are no BSOD, no sluggishness,no delayed boots, then use the 19 customized test settings in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

The number of customized tests can be modified if there is sluggishness or delayed boot.

Hopefully there won't be any BSOD and if there are that there will be dump files to troubleshoot.
If there are BSOD and no dump files then there is limited ability to troubleshoot.

Correction: There were GPU problems, and page file problems reported earlier in the thread.