Windows 10: win32kfull.sys bluescreen

Is it possible to run SFC /scannow in "safe mode"? I know sometimes certain utilities won't check devices/drivers that aren't running, so you end up with a situation where you can't keep the system running long enough to diagnose it.

 

SFC = System File Checker, it works in safe mode but it does NOT check device drivers as those are no system files.

 

So I did run sfc /scannow in safe mode, which returned with no errors. Also ran memtest overnight, and that found no errors (both memory chips are the same make/model, so that addresses another issue often brought up here).

I was trying to run the dm_log_collector utility in regular mode, but the machine doesn't stay running long enough now to bring it up to run. I will run it in "safe mode" for now (since it is called a "log" collector, as opposed to a driver checker) and see what I get.

Now, since it is a Technical Preview (build 14342), it may be out of the realm of this forum, but I'm also trying to triage it to send a report to MS. For some reason it's not doing proper minidumps (it should be giving me multiple dumps, but even though I've told it not to overwrite the prior dump, it still only keeps one). Trying to revert to the prior build fails, as well as using the "reset" option. Since this is a "grandfathered" test system (running since before they required an old W7 or 8.x license number even for the TP, and that particular machine had a Vista license) I can't wipe and reinstall.

 

How are your settings? Please make a screenshot or clear photo of it and post it.
The overwriting is meant for complete/kernel memory dumps (the complete dump includes user mode memory which makes the file a lot larger than a kernel memory dump), not the minidumps.

 

Attachment 80500

This is the current settings screen for "Startup and Recovery" (don't know just why the screenshot is so fuzzy). The dm_log_collector script ran, but didn't put anything in the .zip file (completely empty).

However, going through a process of disabling all startup-applications and enabling one at a time, I determined it was ZoneAlarm. Their latest release is a miserable P.o.S., was not thrilled with how it worked on MSWin7 or 8.1, but it outright crashes MSWin10 TP. It looks like it's time to find a new firewall, as ZA has been getting worse on each iteration (but has never outright crashed a system before). For now the system is "stable" again (as much as a MSWin system could ever be called stable).