Question
1041 views

Driver problem (code 37)

MNov asked on

Hey everyone!

Everytime I plug in USB port any of the Texas Instruments evaluation/development boards I get the following message:

Windows cannot initialize the device driver for this hardware. (Code 37)

I tried restarting my computer, uninstalling/reinstalling drivers, manually pointing windows to the drive folder (in the installation folder of the software which came with the hardware products) and nothing works. I'm guessing the problem is with my computer/Windows since none of the other users of this products reported similar issues. 

Also a few days ago I pluged in USB port brand new WD external hard drive, the whole computer just crashed and now it doesn't recognise it when I plug it in. It works fine on a different laptop which is another reason why I think the problem is with my PC/windows. 

Any help or advice would be greatly appreciated. 

I run Windows 7 on a Toshiba Satellite L555.

3 people had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

From that aswMBR log (thanks, by the way) it's showing a hidden service (driver appears to be likely loading at boot). Also, given you tried to run HJT, and it prevented you from doing so noting that the admin set policies (which you yourself clearly did not do), it looks as if my analysis was correct and you're infected with a rootkit.

My expertise is analyzing/debugging, not malware removal by any means. With this said, I myself cannot give you proper removal instructions. I can say that TDSSKiller will probably show the rootkit, and be able to remove it, but using TDSSKiller and removing a rootkit can at times depending on the rootkit render your OS an un-bootable paperweight.

What would I do if I was you? Honestly, just wipe the OS and walk away. Could you remove the rootkit? Maybe, but you are at great risk after that, and when you have an MBR-based rootkit, it's nasty and leaves a lot of problems behind.

You can also since it's your best and your choice try to remove it, and maybe even with the help of our security experts/MVP's here (in the proper forum, of course).

Up to you and some food for thought!

Regards,

Patrick

Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress