TechTablets › Forums › Cube Forums › Cube i7 Book › Touchscreen Problem: I2C HID Error 10, Anybody Have This Problem?
- This topic has 9 replies, 5 voices, and was last updated 9 years, 3 months ago by
rafita82.
-
AuthorPosts
-
April 17, 2017 at 12:23 am #65419
I recently replaced my cube i7 book tablet digitizer after dropping it and shattering it. Prior to installation of the replacement screen, I tested it out and it was working fine. After a few days, the screen suddenly stopped responding to touch (even the windows button didn’t work). I checked Device Manager and I have an ! on the I2C HID and Wacom device in the list.
Uninstalling the I2C HID device and rescanning sometimes fixes the problem, but other times it doesn’t. The screen randomly stops responding after a restart or wake from sleep. I’ve tried updating the drivers (there are none for the I2C HID), taking the device apart and resecuring the connection, applying tape over the clamp of the touch screen wire connector, and reformatting and reinstalling windows. Each time, the touch screen will work nicely for a few minutes or an hour, then it’ll die after I put it to sleep or restart.
Has anyone else run into this problem before? Is there any other kind of software fix I can try before just buying another replacement digitizer? Thanks in advance.
April 17, 2017 at 1:25 am #65420I reformatted, and clean installed the new win10 creators edition, with the online media creation tool. When through installing, there were 7 or 8 devices that didn’t automatically get drivers. So I used the drivers from here, in the download section. I had a bit of trouble figuring out which folder to point to when upgrading each driver. I ended up going into the properties for each unknown device, into the details tab, then in the dropdown I go the Hardware ID’s and then copied and searched online for the actual device name associated with the hardware ID, and found all the names 1 by 1. I know there are drivers for I2C HID, in the drivers folders from the downloads section here. I would take the time it takes to redo my install before I go tearing apart the digitizer.
April 17, 2017 at 3:26 am #65427April 17, 2017 at 6:08 am #65428or
April 17, 2017 at 7:08 am #65432Hi John,
Thanks for the input. After a fresh install of Windows, I also ran into the problem of a ton of devices being flagged with an ! . I used the drivers on this site and have updated all unknown devices on the tablet, however, there are no drivers for the I2C HID device, as far as I know. I’ll take a look again, but when pointing to the parent folder of the driver bundle, Device Manager doesn’t find anything.
The touchscreen does work from time to time. For instance, one time, I got the ! on the I2C HID device and couldn’t use the touchscreen, so I turned off the tablet and didn’t touch it for about a week. Upon turning it on, touch was working fine for the couple of hours I was messing with it. After waking it from an overnight sleep, the touch screen failed to start again. It seems to be a recurring problem, and so far, everything I’ve tried hasn’t brought any meaningful improvement.
April 17, 2017 at 10:24 am #65442Try resetting BIOS to default and restoring Windows using the factory image? The fact it works before sleep suggests a software issue.
April 18, 2017 at 1:02 am #65522Thanks for the reply, Papa. I think I’ve done a BIOS reset in the past (using the pinhole button), but nothing has changed as far as I know. I’ll give it another shot when I get home. Fingers crossed that it works.
By the way, I tried to use the tablet this morning, but still no luck; the touch screen and windows home button do not respond to anything.
Any other suggestions would be highly appreciated!
April 18, 2017 at 2:35 am #65524April 24, 2017 at 12:46 am #65914@virgo: Yes, the original screen cracked. I replaced it with a new screen, but it’s the new screen that is giving me the error 10.
I tried a BIOS reset, but no luck. The screen will work for a short while, but will die after a long sleep or restart.
April 24, 2017 at 7:21 am #65927@virgo: Yes, the original screen cracked. I replaced it with a new screen, but it’s the new screen that is giving me the error 10.
I tried a BIOS reset, but no luck. The screen will work for a short while, but will die after a long sleep or restart.
For me it is clearly a Hardware problem. Try to talk with the vendor in order to get a new one.
-
AuthorPosts
- You must be logged in to reply to this topic.

