- Joined
- Nov 23, 2017
- Messages
- 4
- Reaction score
- 1
Hi, my first post but not my first time of getting a hell of a lot of answers from here. My problem is this same old code 38 issue with USB;
"Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)"
I get one use of the ports and then I have to do a Shutdown while holding shift, a normal shutdown is not enough now. I am running Windows 10 Home, 64bit, Build 17763, DX12. The laptop is an ASUS R701VM, [email protected], 16MB DDR3 667MHz Patriot Ram running in Dual Channel, With two 1Tb HDD-Pri is Hybrid SSHD and 17"HD monitor with Intel 4000/nVidiaGT630M.
I have tried several searches using broad and keyword but I only seem to get zero response returns. So, I am hoping that asking will provide some answers. When I generic Google search, all I get is update the USB driver, clear the cache, shut down and re-start, but no real answer to the actual problem which to my mind seems to be the inability for windows to flush the memory when you do remove the device from the computer. There has to be a better way to overcome this issue and Microsoft must be able to address it, surely?
Hoping somebody has better answers than those techbots that write tales for magazines and call them solutions.
Kind regards, Jeff
"Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)"
I get one use of the ports and then I have to do a Shutdown while holding shift, a normal shutdown is not enough now. I am running Windows 10 Home, 64bit, Build 17763, DX12. The laptop is an ASUS R701VM, [email protected], 16MB DDR3 667MHz Patriot Ram running in Dual Channel, With two 1Tb HDD-Pri is Hybrid SSHD and 17"HD monitor with Intel 4000/nVidiaGT630M.
I have tried several searches using broad and keyword but I only seem to get zero response returns. So, I am hoping that asking will provide some answers. When I generic Google search, all I get is update the USB driver, clear the cache, shut down and re-start, but no real answer to the actual problem which to my mind seems to be the inability for windows to flush the memory when you do remove the device from the computer. There has to be a better way to overcome this issue and Microsoft must be able to address it, surely?
Hoping somebody has better answers than those techbots that write tales for magazines and call them solutions.
Kind regards, Jeff