• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Code 38.

Status
Not open for further replies.

samuel1

Member
Upon fresh boot of my brand new Windows 7 Razer Blade laptop, my iPhone works perfectly. But, once I unplug it a single time and re-plug it in, the Apple Mobile Device USB Driver no longer functions correctly in the Device Manager and returns the following error message:

"Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)"

Research on the Internet with respect to this, especially from Microsoft, is worthless. Microsoft officially recommends that you "restart the computer." Well, gee, obviously that fixes it -- until I plug it again.

It would seem that it is the job of the OS to take it out of memory instead of telling me that it is still in memory, or at least give me the option to force it out of memory.

Does anyone have any insight into this error message, or how I can actually trace the source of the problem? This is a brand new installation, and since it was one of the first things I installed, I doubt there's any software causing any issues. Loading MSCONFIG with limited startup options didn't solve anything. I am at a loss.

Thanks everyone!
 
I would try to disable/enable your device in the device manager. Make sure you disable every instance of the device. Disabling a device should unload the drivers from memory.
 
Thanks for your suggestions. Nothing works. Enabling and disabling just prompts to reboot -- which would solve the problem anyway.

Any other suggestions?

It seems to me that it is Windows' job to automatically figure out how to unload the drivers if they're persisting in memory. How can I determine what exactly IS in memory? I could theoretically close it out using Process Explorer and maybe write a script to do it each time ~
 
This does the same thing as "uninstalling" via the Device Manager, unfortunately. When I plug it back in, it reinstalls the iPhone driver, then prompts to reboot. Still returns the same Code 38 error message in Windows.

Any other thoughts?
 
Status
Not open for further replies.
Back
Top