Win32kfull.sys Fault on Drag-n-Drop

[Antman]

I use Kari’s Move Users Folder on several PCs (where there are at least two drives). In each case, the OS drive is an SSD. In two systems, the relocated Users folder is also on an SSD. My only benefit is an extremely small Windows footprint on the “C:” drive. I purchased a case of 32GB SSDs for about $15 each.

For much of the history of WindX, I experienced no challenges or negative affect.

But now - Sometimes, a drag-and-drop action will fault System Service Exceptiom win32kfull.sys. 90% of the time, this action will not fault. The exception occurs under no other condition.

The fault occurs on all systems with the hack. Different chipsets, different video, AMD and Intel, different everything. This should rule out drivers.

I do not have a comm path with Kari.

[veeg]

Hello Ant

Hopefully some of our members will chime in soon.
@georgeks @Rustys jmarket

[Antman]

How do I filter threads for those with a single response? Unanswered threads often returns null, and I am actually seeking threads with a single admin response.

[jmarket]

Hey Antman,

If you’re having issues with just this software, it sounds like the software itself is to blame. You said so yourself you don’t get this fault under any other circumstance.

Just to be safe, do the following for me please:

Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.

Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version – SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.

Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.

Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder

Please attach the SysnativeFileCollectionApp.zip to your post and await further instructions

[Antman]

Chuckle. The software is the Windows 10 Explorer shell.

I changed my system settings to save the dump file and will post on the next fault.

[ATTACH]3168[/ATTACH]

[veeg]

Any updates for us?

[Antman]

Please, do not close at this time. This issue has been driving me nuts, but I do not have a memdump.

I will report that 1709 build 17025.1000 has not presented the fault. This could indicate that there was a bug in earlier builds, spanning several builds, or it could be consistent with the inconsistent nature of the fault.

I could go to one of my other machines which are not running Insider Previews and try to force a fault, but I don’t do PCHF from those.

[veeg]

Any updates for us?

[Antman]

Please close