BSOD after update last week

Open file explorer > this PC > C: > in the right upper corner search for: C:\windows \memory.dmp

Zip the file and post a share link into this thread.

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 10/21/2018 09:23:33
Size on disk: 521 MB

Windows driver verifier is a tool that stress tests drivers.
Unstable drivers will cause BSOD crashes.
The bsod crashes should produce dump files.
Debugging the files can display information about problematic software and hardware drivers and malfunctioning hardware.

In order to recover from the crashes the Windows driver verifier tool needs to be turned off.
And in order to turn off the tool after a crash the Windows advanced troubleshooting menu is used.
The methods to turn off or recover from using the tool are in this link:
https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

The tool will be used for 48 hours.
While it is used the computer may become sluggish and boots can become slow.

After the last bsod during the 48 hour period and additional 36 hours will be used for testing.

The tool has customized settings.
All non-Microsoft drivers will be tested at the same time.
The customized tests will start out with three tests and may rise to 19 different tests depending upon the frequency of the bsod.

After each bsod run the beta log collector and post a new zip into the thread.
If problematic drivers are found they will be uninstalled or uninstalled and reinstalled.
Drivers can be installed after all misbehaving drivers are found or immediately after they are uninstalled.
The end result should be the same.

Before using the tool the computer files must be protected.
Backup all important files to another drive or to the cloud.
Make a backup image using Macrium:
https://www.macrium.com/
Make a brand new restore point

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

In start up and recovery system failure > uncheck automatically restart > set to automatic memory dump > reboot to keep the settings
For virtual memory make sure the box is checked to automatically manage paging size for all drives and that the page file is on C:

When you are comfortable with the methods to turn off and recover from using the tool you can start using it.

Memory dump link:

Dropbox - MEMORY.zip

This dump captured in safe mode after several normal boot attempts. Generally, a normal boot loops with a message like 'your pc has a problem we will restart' etc etc.. I hope it is of some use to you.

Maybe its time for me to do a clean windows installation. I have two system image files as well as backups of data. What do you think?

Was the BSOD in normal or safe mode?
If you have a few more BSOD crashes and post memory dumps that would be useful.
The images will have the operating system and drivers in a frozen state from the time the image was made.
Were you confident that the image was at a time when there was computer stability?
If so then clean install is a viable option if it is not inconvenient.
Having a few more memory dumps would be useful as the debugging just got started.
It's your choice.
Either way the stability/instability can be checked by observation or with Windows drive verifer.

For each BSOD please post a BETA zip and memory dump.

Hi zbook, you must get up pretty early :) We are 12 hours apart..

Since the start of this epic the computer has never booted up in normal mode. The memory dumps are taken after a number of abortive boot attempts after which I have to do a hard (power button) shutdown and then booted into safe mode. When in safe mode everything is perfectly stable and anything I have tried to do works ok.
Can I use the driver verifier tool in safe mode? I imagine that some drivers might not be available to the tool..

As long as there are BSOD then windows driver verifier is not needed.
It speeds up the process to produce bsod for debugging.
The more the dump files the more the debugging and the quicker the troubleshooting.
The memory dumps should provide more information than the mini dumps but they take longer to upload and download.

BSOD are caused by misbehaving hardware and software drivers and malfunctioning hardware.


For Windows driver verifier the test settings can be customized.
All non-Microsoft drivers are stress tested using Windows driver verifier.
The test range from 3 to 19 in use at any one time.

Will catch up with you later in the day.

Hi zbook, I made a bootable USB with the Media Creation Tool and tried to install a clean OS but that failed to load. Contacted Lenovo and the machine is going back to them. It is still under warranty.

Thanks for all your help with my problem and sorry it didn't work out. If they tell me what was wrong with it I'll let you know.

Cheers Graham..

Wow.
Was there an error message or code?
Were bios settings modified?
Glad to see that you made headway with Lenovo.

I changed the bios to make it boot from USB.

Thought it was going to be ok and got through the various preliminary screens but then went to blue screen with
'Kernel security check failure' so I gave up and got on the Lenovo chat line, carried out some tests and sent a photo etc etc. so off it goes. Lucky there is another PC here :)

Hi zbook, I got my PC back from Lenovo today. They changed the System Board (motherboard I presume). Lucky it was still in warranty. Thanks for your help over the last few weeks.

Cheers
Graham

That's great.
Use the computer for a week.
Then there will be lots of events in the logs.
If you want the computer log files troubleshooted please post a BETA log collector zip.
If you want to wait for any problems that's ok too.
Again I'm glad to see it sorted.