Unknown Device + BSOD  

I have an HP tx2-1020US laptop that I just did a clean install of Windows 7 Build 7100 on. So far, things are working pretty well with the exception of 2 issues. First off, under the device manager, I have an 'unknown device' listed. All of the manufacturer, etc. details are unknown. The only piece of info is the hardware id property which is:

USB\VID_1B96$PID_0001&REV_0000&MI_02
USB\VID_1B96&PID_0001&MI_02

Thus far, I have not been able to find any components which are not working and I have no external USB devices connected to the system. Any ideas how I would go about figuring out what device this is and finding a driver for it?

Then, the second issue is that every time I restart or shutdown the system, it flashes a BSOD. It then reboots without any problems and gives me the windows startup screen asking if I want to use safe mode or boot normally. If I boot normally, Windows gives me a pop-up saying the previous shut down was unexpected, but not other details. I have checked the logs and there is nothing in any of the Windows event logs.

The BSOD screen lists no driver, dll, or sys file, simply the following string of hex codes.

STOP: 0x0000003B (0x00000000C0000046, 0XFFFFF80002A82C4C, 0xFFFFF88008070080, 0X0000000000000000)

I found reference to the first 0x0000003Bcode in google relating to video issues, but I have the latest 64-bit Windows 7 driver installed from ATI already. So, can anybody offer any further translation of these codes?

Thanks.

With respect to the unknown device, it is something that's connected via USB internally.

Go through the support page for your model and compare the devices to the ones in your device manager. That way you might be able to pinpoint the missing drivers.

http://h10025.www1.hp.com/ewfrf/wc/s...roduct=3860689

To find out if the BSOD is video related try uninstalling the ATI Catalyst drivers and revert back to the MS generic driver. If BSOD stops this would suggest video driver issues.
In that case you could try earlier Catalyst versions.

netRAT.

The BSOD issue does appear related to the display driver after all. I was able to uninstall the ATI driver, after which the system did restart successfully. However, as soon as it came back up, Windows updated the driver to the ATI driver (even though I selected to delete the driver on uninstall) and the problem is back.

I just found an update on the ATI site for Catalyst 9.5 which was release a couple of days ago. However, upon trying to run the installer, it crashes. Anybody know where I might get this latest driver without having to have the full Catalyst software?

In terms of the unknown device, no luck there. I have been through all of the devices and drivers listed on the HP site and none of them cause this device to be recognized.

Thanks.

You don't necessarily need the latest driver at the moment. Keep in mind that Win7 drivers are beta and if you find one that works for you stay with that and keep trying when new versions come out.
Many people have had problems with Catalyst ever since 9.2 so you're not alone.
If the updated 9.5 installer actually extracts before crashing the driver files should be in C:\ATI\Support

With respect to the unknown device, by going through the drivers on the support page I did not mean you should install all of the drivers there. Just compare the device names on the page to the ones in device manager. One is missing, therefore is not installed and will not appear in device manager.

Keep an eye out for the following: ENE CIR Receiver Driver
Is that device listed on your device manager ?

Just a hunch...

netRAT.

Hi, I also experience the same problem with an "unknown device" listed in Device Manager:

USB\VID_1B96$PID_0001&REV_0000&MI_02
USB\VID_1B96&PID_0001&MI_02

I was able to identify the device by looking up the USB vendor ID (1B96) and product ID (0001) on the Internet. The vendor is "N-Trig" and the product is "Duosense Transparent Electromagnetic Digitizer", i.e. the digitizer hardware for the multi-touch display.

Since Windows 7 RC on the TX2 works fine with single-touch and pen I left it at that. That said, N-Trig has since released preliminary drivers for Windows 7 RC, if you want to have full multi-touch.

Zidane2424 said:

Unknown Device + BSOD....nice combo I love those

By the way, I don't experience the BSOD; only the "unknown device"; so in this case I think the symptoms are caused by separate issues.

Zidane2424 said:

By the way is there an easy way to find out what a particular "unknown device" is on a machine...I have one myself and I cannot for the life of me figure out what it is...let alone a driver to make it run!

See my previous reply. How-to: Go to Device Manager and open the properties for the unknown device. On the Details page, select "Hardware Ids" in the Property field. The value box will now list the relevant vendor and product IDs. You can then lookup the vendor IDs and product IDs on the Internet to find out more about the device. Search for "USB vendor list" (or "PCI vendor list" depending on the kind of device).

I had the same annoying problem and I have finally solved this issue.

The problem is not caused by the touchscreen, although you might get an error about this, it will work anyways.

The big issue is caused by the FINGERPRINT READER... it doesn't work on Windows 7 64bit and if you get to install it on 32bit it will work but you'll get that annoying message of a "USB" device not working properly and you might get the worst thing, which is that you reboot or turn off and when you get the BIOS screen it stays there and doesn't even allow you to do system recovery.

Disable the AuthenTec Biometric device from the Device Manager and wait until HP updates the drivers for this device on 2010 for Windows 7.

BR,
Eduardo
Colombia, South America

ps. I own a tx2-1025dx

This resolved my "Unknown Device" issue.

N-Trig DuoSense Digitizer Software and Driver
sp46082.exe

HP TX2-1025DX

CompGuru said:

This resolved my "Unknown Device" issue.

N-Trig DuoSense Digitizer Software and Driver
sp46082.exe

HP TX2-1025DX

Welcome to sevenforums

Just an FYI that thread is almost a year old. I hope they have it fixed by now.

Ken