Windows 10: BSoD on ASUS T100TA when detaching tablet from dock

Greetings All:

I installed Windows 10 on a fully compatible ASUS Transformer T100TA yesterday. All is working great except, whenever I remove the tablet from the dock I get the BSoD (kmode_exception_not_handled) and the tablet reboots.

I have done a clean boot and it did the same thing.

I do a proper media eject prior to removing the tablet. I never did this in Windows 8.1 and never had a problem. Media ejected or not the tablet would work properly. In Windows 10 it gives the BSoD regardless which procedure I follow to remove the tablet from the dock.Attachment 27183

:)

 

Why no automatic switching between tablet- and desktop mode?

Why is my Asus transformer book T200 not automaticly switching between tablet-and desktop mode when attaching or detaching keyboard Dock? I have checked the tablet-mode settings.

 

When docked tablet mode doesn't trigger on screen keyboard when needed

I have an Asus T100TA and sometimes I have the tablet docked, but I would still like to use tablet mode. So, I switch it manually to tablet mode. This all seems to work fine. However, when I touch the screen in a text box the on screen keyboard doesn't appear.

If I undock the tablet this does work.

Is it possible to change this?

 

Welcome to TF. I've taken a look at your dumps and they're all blaming the ASUS Touch Service. The driver looks like it's up to date so it may be worth checking with ASUS for any updates to the software, worst case it may not be playing nice with Windows 10 at the moment. Is there any possibility of uninstalling the software if an updated version isn't available?
Code: BugCheck 1E, {c0000005, 0, 8, 0} Unable to load image \SystemRoot\system32\DRIVERS\AsusSGDrv.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for AsusSGDrv.sys *** ERROR: Module load completed but symbols could not be loaded for AsusSGDrv.sys[/quote]

 

With some fighting with Windows, I uninstalled the touchpad driver. Once uninstalled the problem ceased to exist. Windows forced me to reinstall on the next boot and it appears the problem did not return.

Thanks for such a speedy solution.

 

You're more than welcome, glad to see you're running smooth. *Thumbs

If you feel the issue is resolved would you mind marking the thread as Solved? You can always mark it Unsolved if the issue returns.