Unsolved
This post is more than 5 years old
1 Rookie
•
1 Message
1
264607
September 26th, 2014 09:00
XPS 12 Touch Screen Not Working - I2C HID Device (Code 10)
My XPS 12 Duo touch screen stopped working one day.
My Device Manager shows that the I2C HID Device is not working (With a status of: This device cannot start. (Code 10) STATUS_DEVICE_POWER_FAILURE
I'm not sure why as nothing changed... that I know of.
I have uninstalled and reinstalled the drivers, I have made sure all drivers are up dated (as on dell.com), and eventually I even formatted the HDD thinking some update must have caused this.
Unfortunately I have had no luck. Anyone else have this problem and solved it?
Just to add, Dell replaced my screen (due to ghost images) about a month ago - I'm thinking this could be the cause.
Thanks all
No Events found!
Pajamas06
4 Posts
0
September 29th, 2014 15:00
Having a similar problem with my XPS 12 (9Q33).
Everything was working fine. Just had my screen replaced today (also for image retention issues). Since the replacement my touch screen has not been working. My device manager also shows I2C HID Device not working "The device cannot start. (Code 10)"; "A request for the HID descriptor failed."
Tried updating/disabling/enabling/uninstalling through device manager with no luck.
I went to the Dell website and tried updating my display firmware to A01 but this failed with two error messages: "Aux channel error!" and "DPCD registers mapping error"
Really hoping someone has a fix to this.
ghriddle
1 Message
0
November 14th, 2014 14:00
Same problem here. XPS12 9Q33. Several times in the past year the touchscreen has not worked. Other times Dell technical support was able to fix it while I was on the phone. But this time they gave up.
In the past it was always fixed by doing something in the software, but I do not recall what it was. So now I am working without a touchscreen.
Pajamas06
4 Posts
0
November 14th, 2014 15:00
My problem was in fact related to improper hardware being swapped into my unit and Dell resolved the issues.
Ghriddle, your problem sounds like a different issue. The intermittent nature makes it sound like a driver issue.