Being Logged Out with Windows 10 v1803

I don't think I've ran the registry cleaner since clean installing 1803.

I unchecked everything mentioned (Windows log files is checked in the pic, but I unchecked it - missed it in original post).

Attachment 187822

When can I reinstall Malwarebytes? I'm hoping the beta will come to general circulation soon since I get error messages with it with core memory protection enabled.

Will continue to monitor. Thanks again for all your help!

For Ccleaner please un-check Windows Log Files.

Windows driver verifier is a tool that is used to find misbehaving drivers and malfunctioning hardware.
It will repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.
The BSOD are then debugged to check for problems with drivers and hardware.

The Windows advanced troubleshooting menu is used to turn off the tool.
There are three methods to turn off or recover from using the tool:
1) Startup settings > restart > select #6 safe mode with command prompt > type:
verifier /reset
2) Command prompt > Administrator: X:\Windows\System32\cmd.exe > X:\Sources> type:
verifier /bootmode resetonbootfail
3) System restore
The methods used to turn off Windows driver verifer should be used in the sequence above, advancing only if the prior method failed. Using system restore often leads to a loss of the dump files and little progress in the troubleshooting.

The tool will be used for 48 hours. After the last BSOD it will be used for an additional 36 hours of typical computer use. If there are no more BSOD this will conclude the use of this tool.

When using the tool the computer may become sluggish and the boots may become slow. At times it may become necessary to modify the test settings.

Use the information in this link for the customized test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use the information in this link for methods to turn off and recover from using the tool:
Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials

Before using the tool:
a) Backup all files to another drive or to the cloud
b) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
c) Place the backup image onto another drive or into the cloud
d) Make a brand new restore point

For each BSOD post a new beta zip and memory dump into the thread for debugging (C:\Windows\memory.dmp)

Malwarebytes can be reinstalled after the troubshooting and a period of computer stability. Approximately one week after the last BSOD will allow time to evaluate the stability. If the reinstallation of Malwarebytes causes BSOD then find alternative AV software. If there is no new BSOD then continue using the AV software.

For each BSOD
a) post a new beta zip
b) search for C:\Windows\memory.dmp > zip > post a one drive or drop box share link into the thread

The latest two mini dump debugging displayed dbx.sys as the misbehaving driver.
Dbx.sys is related to Drop Box.
Drop box was uninstalled and reinstalled yesterday and should have had new drivers.
Windows driver verifier will be used for several days so if you uninstall drop box and use an alternative software product during the troubleshooting time period that would enable you to continue testing other drivers.
Once all misbehaving drivers have been fixed you can then reinstall software in a staggerd fashion.
One drive is an alternative to drop box.
So uninstall drop box software > restart windows driver verifier to find the next misbehaving driver

The memory dump debugging also displayed the Nvidia GPU drivers: nvlddmkm

1) Uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) Re-install the Nvidia GPU driver from the Dell website
3) If there are recurrent problems with the Nvidia GPU the DDU will be used again and the source will be the Nvidia website.


What is your specialty?
If you have a large period of time where you can test one of the hardware components, the RAM, with Memtest86+ version 5.01 that may be needed. For example the weekend. There is 32 GB of RAM. The best test is testing the multichannel capability of the motherboard with both RAM modules at the same time. If the downtime is too long then one RAM module can be tested at a time but the multichannel capability is not tested. Eight or more passes are required for proper testing to reduce the number of false negatives. The testing is not done by time but by passes. The memtest86+ version 5.01 testing takes 1 -2 hours / GB RAM. A portion of the RAM testing can be done overnight. Testing can be aborted if there is just one error. Then one module is tested at a time to find the malfunctioning RAM module. The RAM testing may be needed in the future. Memtest86+ - Advanced Memory Diagnostic Tool
Memory problems. - Microsoft Community
MemTest86+ - Test RAM | Windows 10 Tutorials

Code:

nvlddmkm.sys Thu Nov 10 16:01:49 2016 (5824EE4D)

Code:

Name    NVIDIA Quadro M620PNP Device ID    PCI\VEN_10DE&DEV_13B4&SUBSYS_07A91028&REV_A2\4&327EEAC7&0&0008
Adapter Type    Quadro M620, NVIDIA compatible
Adapter Description    NVIDIA Quadro M620
Adapter RAM    (2,147,483,648) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nvdm.inf_amd64_790c5c10f20c35fb\nvd3dumx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdm.inf_amd64_790c5c10f20c35fb\nvwgf2umx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdm.inf_amd64_790c5c10f20c35fb\nvwgf2umx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdm.inf_amd64_790c5c10f20c35fb\nvwgf2umx.dll
Driver Version    21.21.13.7586
INF File    oem30.inf (Section228 section)
Color Planes    Not Available
Color Table Entries    Not Available
Resolution    Not Available
Bits/Pixel    Not Available
Memory Address    0xEC000000-0xECFFFFFF
Memory Address    0xC0000000-0xCFFFFFFF
Memory Address    0xD0000000-0xD1FFFFFF
IRQ Channel    IRQ 4294967281
Driver    c:\windows\system32\driverstore\filerepository\nvdm.inf_amd64_790c5c10f20c35fb\nvlddmkm.sys (21.21.13.7586, 13.51 MB (14,163,904 bytes), 05/01/2018 01:53 AM)