for clarification I2C HID Device in devmgmt says it stopped the device with error code 43

From what I can tell on other forums this is happening to quite a few people, myself included. You can disable and re-enable the device in the device manager and it will start working. Some people have said that unchecking allow windows to manage this device under the power management tab of the device properties would stop it from happening. Unfortunately it has not prevented it for me.

I have posted on Futaba86's thead as well

en.community.dell.com/.../19490632.aspx

I have alerted my contacts in engineering and hope to have information from them shortly.  

TB

brucee2

If you are still having issues where either the cursor gets stuck or the tablet hangs please send me a private message.  Just click on the link in my signature and then click start conversation.  In your message please include the service tag of the tablet.

Engineering is looking for numbers of affected units and possibly may be looking to capture systems from the field.  Please let me know (in your message) if you are willing to receive a system exchange so that engineering can test your original system and are in the US or Canada as well.

Thanks

TB

Terry B,

I have a Latitude 10 Dell Tablet running Windows 8 with the same problem with the touch screen becoming unresponsive after a period of time in sleep mode.  I purchased this tablet only a month ago.  It is very frustrating to have this happening, especially when I intend to use this tablet for work with customers.

Has Dell found a solution to this problem yet?

Thanks.

I  had limited success by upgrading the bios  to the latest version and then upgrading the chipset driver

perigee  did you happen to wipe the drive and  install Windows.  for a brief period  Dell and I  tried to target a specific  Windows update  that we thought might  have fix ed it  on one of our tablets so you have three things to try.  let me know how it goes

Found this while troubleshooting and just thought I would mention this here in case it becomes important.

I just had this issue in a latitude 10 tablet using a Wacom stylus.  The stylus stopped working but the touch screen still functioned. 

The Device Manager had two HID I2C devices showing up with a bang on them each of which displayed the error "Windows has stopped this device because it has reported problems. (Code 43)" which is rather more generic then I would have liked.  Basically it means "Woops, somethings wrong".   Kinda reminds me of the old error that would pop up in Windows 98 beta that would simply say "What did you do?".

Shutting down completely and starting back up failed to solve the problem.

I ran the troubleshooter and windows identified the devices (Drivers really) with the problem but it was not solved until I restarted again.  This restart was not a full shutdown.

It started just after closing out of a GoToMeeting session.  I have had issues with other devices (desktops, laptops) having video issues after using the GoToMeeting interface for a period of time so I had assumed that might have been the instigator this time but could not say for sure.

I have had issues with the Wacom in the past though normally it's pretty solid.  Now that I think about it though, both times it occurred after Long RDP Sessions.  In those instances though there were no devices listed with a bang and a simple restart solved the problem.

This Tablet is running windows 8 Pro and is on a domain.

Not sure that helps any but hopefully some one might find it useful.

Other wise great tablet.  *** OS though.

I had exactly the same problem as Ratsnackbar with a Latitude 10 I got a week ago.  Running the troubleshooter (as described above) then restarting seems to have fixed it.  I don't have GoToMeeting, so I suspect it is unrelated to that, nor have I used RDP software of any kind on it yet.  I first thought it wasn't playing nice with the Bluetooth mouse that I first connected to it yesterday.

Has this happened to anyone multiple times?  I'd rather not have to deal with this unexpectedly in the future.

I just had the same problem again, but this time the Bluetooth radio also showed the same error.  Additionally, when I first turned the tablet on this morning, the on-screen keyboard didn't show up to enter the password on the lock screen (I had to use the on-screen keyboard in the accessibility options instead).  I don't know if these are related or not.  I should also note that running the troubleshooter and then completely shutting down does not work; it needs to be the soft reboot.  If this keeps up, I may see if getting a replacement is possible.