New
#111
Please post a BETA log collector zip and memory dump for debugging.
Boot into Safe Mode on Windows 10 | Windows 10 Tutorials
Please post a BETA log collector zip and memory dump for debugging.
Boot into Safe Mode on Windows 10 | Windows 10 Tutorials
There are no dump files available since turning on driver verifier. The PC has not been able to fully boot - it shows the progress bar but does not advance past that. After several restarts the advanced startup repair menu appears and I can get into safe mode from there.
Turn off Windows driver verifier.
Download and install Whocrashed:
http://www.resplendence.com/whocrashed
In the left upper corner above analyze click on tools > crash dump test > type: ACCEPT > perform a crash >
Run the whocrashed analyze > post an image into the thread
Run the BETA log collector > post a zip into the thread.
Open file explorer > this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp > zip > post a one drive or drop box share link into the thead.
After the above plan:
If files are backed up and there is a backed up image consider a clean install.
If the operating system was upgraded from Windows 7 or 8 there should be a digital license.
As a backup make sure that you have a Microsoft account.
With a clean install all partitions will be deleted making an unallocated drive.
Windows 1803 will then be installed using a Windows 10 iso.
When the operating system is installed make sure that there are no connections to the internet (disconnect ethernet/cat5e, and use hardware wireless off if available)
Evaluate the computer as a "vanilla" clean install: Only Windows installed drivers and no Windows updates.
If there are any freezes then report that into the thread.
If there are no freezes then connect to the internet and do not install any drivers or applications.
Perform Windows updates and then evaluate the computer for freezing or bsod with just Windows updates.
If the above does not have any freezing or bsod then open the website for the motherboard manufacturer.
Perform one driver installation and evaluate the computer for freezing.
Continue to install just one driver at a time giving yourself several hours per driver to evaluate any freezing.
Once all motherboard manufacturer drivers are installed then start the component manufacturer drivers.
Do not install the Nvidia GPU or drivers during these steps.
Report into the thread if there is any freezing or BSOD. For any BSOD run the beta log collector and post a new zip. Also post a zipped memory.dmp.
I was able to run the DM log collector and grab the memory.dmp file. Both have been added to the Dropbox folder:
https://www.dropbox.com/sh/kvbhaxc5b...RaKhXRq5a?dl=0
There were 3 new BSOD with mini dump files.
There were no memory dump files posted.
There was no definitive misbehaving identifed in the debugging of the mini dump files.
Please post memory dump files when ever available.
Please use the BETA log collector as it is to replace the DM log collecter. The BETA log collector will collect more useful information.
The newest memory.dmp file is in the Dropbox folder titled "MEMORY_20180520.7Z".
The freezes were occurring when running the beta log tool, which is why I had to use the DM log instead.
There were no definitive misbehaving drivers in the latest memory.dmp.
Continue posting memory dumps as often as there are BSOD.
Consider clean install to better evaluate hardware as possible causes of BSOD.
Latest crash info added to Dropbox:
https://www.dropbox.com/sh/kvbhaxc5b...RaKhXRq5a?dl=0
If I use an image backup with a clean install, will that introduce a corruption path by using some of the old files?
1) There was 1 mini and 1 memory dump debugged.
2) There was 1 misbehaving hardware driver identified: LGBusEnum.sys
3) Uninstall and reinstall this driver:
Updating a driver. - Microsoft Community
LGBusEnum.sys
Logitech Keyboard
Logitech Support + Downloads
Code:LGBusEnum Logitech Gaming Virtua Logitech Gaming Virtua Kernel Manual Running OK TRUE FALSE 5,248 7,552 0 06/13/16 14:47:08 C:\WINDOWS\system32\drivers\LGBusEnum.sys 1,664An old restore point or old image that has malware will continue to have malware unless it has the option to be scanned. The scanning option I don't believe is possible with a restore point but for an image I think the drive with the backup image could be scanned for malware and fixed as needed. This would need confirmation from those that regularly work with these tools. There is a separate forum for malware and if it comes to that please make a thread. For now, fixing the keyboard misbehaving driver may work.Code:LGBusEnum.sys Mon Jun 13 13:47:08 2016 (575EFFAC)
I have performed a clean installation, and there was a freeze within 30 minutes of completion. Beta log and memory.dmp added to Dropbox:
https://www.dropbox.com/sh/kvbhaxc5b...RaKhXRq5a?dl=0