Mystifying USB Mass Storage Device Issue (Code 38)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Environment
4 computers: Desktop A, Desktop B, Laptop A, Laptop B
Software (same across all computers): Office 2013, Sage 50 Simply Accounting, Sage Act CRM, Adobe XI Reader, FortiClient 5.x, Meraki Systems Manager (MDM)
OS: Desktop A/B & Laptop B are running Windows 7 x64 Professional, Laptop A Windows 7 x64 Home Premium
Hardware: Desktops are custom built and identical, w/Gigabyte motherboards, 8GB RAM, Core i3. Laptop A is Asus K53E, Laptop B is Lenovo ThinkPad Edge E540,
USB: Desktops A/B and Laptop B have USB 2.0 + 3.0 ports. Laptop A only has USB 2.0
Note: all devices stay in the office at all times, and are left powered on 24/7
Problem
A customer has 4 computers, after a few weeks of use, the brand new desktops A/B experienced usb "issues". The below error would appear when you plug in USB flash drives:
(Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
During this time Laptop A experienced no such issues. If the desktop is restarted, the USB device would function as normal (can be unplugged/plugged back in unlimited number of times) for the rest of the day (approx. 24 hours) until the same error would appear the next morning. The only way to clear the error and use the usb device is to reboot.
3-4 Months later (issue still exists), Laptop A was reformatted (for reasons not related to usb issue). In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops.
1-2 Months later (issue still exists), a new Laptop was purchased (Laptop B) with a factory Windows 7 image. In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops and other laptop. Desktop A was removed from the office and brought to a different office for testing, (without changing anything) and it has worked normally for 2 weeks straight with no usb issues.
Timeline (approximation)
Week 1: New desktops are installed in the office - (now total of 3 computers in office)
Week 4: Desktops experienced usb error (code 38))
Week 16: Laptop A was reformatted)
Week 18: Laptop A experienced same usb error)
Week 22: Laptop B was purchased - (now total of 4 computers in office))
Week 24: Laptop B experienced same usb error)
Week 24: Desktop A removed from office)
Week 28: Desktop B and Laptop A/B still experience same usb error, while Desktop A is functional (outside of office)
Process of elimination
- cannot be hardware, as it has happened to 3 distinct devices
- not an issue with OS image, 3 different installation mediums used
- not an issue with brand/type of flash drive, both USB 2.0 and 3.0 devices have been tried, along with brand new out-of-box devices. Issue occurs on both USB 2.0 and 3.0 ports on the computers
What it could be?
- the software that was installed onto the computers?
- virus/spyware/malware etc. ?
- ...and why does Desktop A work, when nothing was done to it?
Next steps/actions
- bring Desktop A back to office, wait and see what happens
- bring new laptop into office, with bare Windows 7 and no software installed, just networked
Any thoughts on WTF is going on???
windows-7 usb usb-flash-drive
add a comment |
Environment
4 computers: Desktop A, Desktop B, Laptop A, Laptop B
Software (same across all computers): Office 2013, Sage 50 Simply Accounting, Sage Act CRM, Adobe XI Reader, FortiClient 5.x, Meraki Systems Manager (MDM)
OS: Desktop A/B & Laptop B are running Windows 7 x64 Professional, Laptop A Windows 7 x64 Home Premium
Hardware: Desktops are custom built and identical, w/Gigabyte motherboards, 8GB RAM, Core i3. Laptop A is Asus K53E, Laptop B is Lenovo ThinkPad Edge E540,
USB: Desktops A/B and Laptop B have USB 2.0 + 3.0 ports. Laptop A only has USB 2.0
Note: all devices stay in the office at all times, and are left powered on 24/7
Problem
A customer has 4 computers, after a few weeks of use, the brand new desktops A/B experienced usb "issues". The below error would appear when you plug in USB flash drives:
(Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
During this time Laptop A experienced no such issues. If the desktop is restarted, the USB device would function as normal (can be unplugged/plugged back in unlimited number of times) for the rest of the day (approx. 24 hours) until the same error would appear the next morning. The only way to clear the error and use the usb device is to reboot.
3-4 Months later (issue still exists), Laptop A was reformatted (for reasons not related to usb issue). In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops.
1-2 Months later (issue still exists), a new Laptop was purchased (Laptop B) with a factory Windows 7 image. In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops and other laptop. Desktop A was removed from the office and brought to a different office for testing, (without changing anything) and it has worked normally for 2 weeks straight with no usb issues.
Timeline (approximation)
Week 1: New desktops are installed in the office - (now total of 3 computers in office)
Week 4: Desktops experienced usb error (code 38))
Week 16: Laptop A was reformatted)
Week 18: Laptop A experienced same usb error)
Week 22: Laptop B was purchased - (now total of 4 computers in office))
Week 24: Laptop B experienced same usb error)
Week 24: Desktop A removed from office)
Week 28: Desktop B and Laptop A/B still experience same usb error, while Desktop A is functional (outside of office)
Process of elimination
- cannot be hardware, as it has happened to 3 distinct devices
- not an issue with OS image, 3 different installation mediums used
- not an issue with brand/type of flash drive, both USB 2.0 and 3.0 devices have been tried, along with brand new out-of-box devices. Issue occurs on both USB 2.0 and 3.0 ports on the computers
What it could be?
- the software that was installed onto the computers?
- virus/spyware/malware etc. ?
- ...and why does Desktop A work, when nothing was done to it?
Next steps/actions
- bring Desktop A back to office, wait and see what happens
- bring new laptop into office, with bare Windows 7 and no software installed, just networked
Any thoughts on WTF is going on???
windows-7 usb usb-flash-drive
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13
add a comment |
Environment
4 computers: Desktop A, Desktop B, Laptop A, Laptop B
Software (same across all computers): Office 2013, Sage 50 Simply Accounting, Sage Act CRM, Adobe XI Reader, FortiClient 5.x, Meraki Systems Manager (MDM)
OS: Desktop A/B & Laptop B are running Windows 7 x64 Professional, Laptop A Windows 7 x64 Home Premium
Hardware: Desktops are custom built and identical, w/Gigabyte motherboards, 8GB RAM, Core i3. Laptop A is Asus K53E, Laptop B is Lenovo ThinkPad Edge E540,
USB: Desktops A/B and Laptop B have USB 2.0 + 3.0 ports. Laptop A only has USB 2.0
Note: all devices stay in the office at all times, and are left powered on 24/7
Problem
A customer has 4 computers, after a few weeks of use, the brand new desktops A/B experienced usb "issues". The below error would appear when you plug in USB flash drives:
(Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
During this time Laptop A experienced no such issues. If the desktop is restarted, the USB device would function as normal (can be unplugged/plugged back in unlimited number of times) for the rest of the day (approx. 24 hours) until the same error would appear the next morning. The only way to clear the error and use the usb device is to reboot.
3-4 Months later (issue still exists), Laptop A was reformatted (for reasons not related to usb issue). In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops.
1-2 Months later (issue still exists), a new Laptop was purchased (Laptop B) with a factory Windows 7 image. In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops and other laptop. Desktop A was removed from the office and brought to a different office for testing, (without changing anything) and it has worked normally for 2 weeks straight with no usb issues.
Timeline (approximation)
Week 1: New desktops are installed in the office - (now total of 3 computers in office)
Week 4: Desktops experienced usb error (code 38))
Week 16: Laptop A was reformatted)
Week 18: Laptop A experienced same usb error)
Week 22: Laptop B was purchased - (now total of 4 computers in office))
Week 24: Laptop B experienced same usb error)
Week 24: Desktop A removed from office)
Week 28: Desktop B and Laptop A/B still experience same usb error, while Desktop A is functional (outside of office)
Process of elimination
- cannot be hardware, as it has happened to 3 distinct devices
- not an issue with OS image, 3 different installation mediums used
- not an issue with brand/type of flash drive, both USB 2.0 and 3.0 devices have been tried, along with brand new out-of-box devices. Issue occurs on both USB 2.0 and 3.0 ports on the computers
What it could be?
- the software that was installed onto the computers?
- virus/spyware/malware etc. ?
- ...and why does Desktop A work, when nothing was done to it?
Next steps/actions
- bring Desktop A back to office, wait and see what happens
- bring new laptop into office, with bare Windows 7 and no software installed, just networked
Any thoughts on WTF is going on???
windows-7 usb usb-flash-drive
Environment
4 computers: Desktop A, Desktop B, Laptop A, Laptop B
Software (same across all computers): Office 2013, Sage 50 Simply Accounting, Sage Act CRM, Adobe XI Reader, FortiClient 5.x, Meraki Systems Manager (MDM)
OS: Desktop A/B & Laptop B are running Windows 7 x64 Professional, Laptop A Windows 7 x64 Home Premium
Hardware: Desktops are custom built and identical, w/Gigabyte motherboards, 8GB RAM, Core i3. Laptop A is Asus K53E, Laptop B is Lenovo ThinkPad Edge E540,
USB: Desktops A/B and Laptop B have USB 2.0 + 3.0 ports. Laptop A only has USB 2.0
Note: all devices stay in the office at all times, and are left powered on 24/7
Problem
A customer has 4 computers, after a few weeks of use, the brand new desktops A/B experienced usb "issues". The below error would appear when you plug in USB flash drives:
(Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
During this time Laptop A experienced no such issues. If the desktop is restarted, the USB device would function as normal (can be unplugged/plugged back in unlimited number of times) for the rest of the day (approx. 24 hours) until the same error would appear the next morning. The only way to clear the error and use the usb device is to reboot.
3-4 Months later (issue still exists), Laptop A was reformatted (for reasons not related to usb issue). In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops.
1-2 Months later (issue still exists), a new Laptop was purchased (Laptop B) with a factory Windows 7 image. In the first few weeks of use the laptop functioned normally, but after it experienced the same issues as the 2 desktops and other laptop. Desktop A was removed from the office and brought to a different office for testing, (without changing anything) and it has worked normally for 2 weeks straight with no usb issues.
Timeline (approximation)
Week 1: New desktops are installed in the office - (now total of 3 computers in office)
Week 4: Desktops experienced usb error (code 38))
Week 16: Laptop A was reformatted)
Week 18: Laptop A experienced same usb error)
Week 22: Laptop B was purchased - (now total of 4 computers in office))
Week 24: Laptop B experienced same usb error)
Week 24: Desktop A removed from office)
Week 28: Desktop B and Laptop A/B still experience same usb error, while Desktop A is functional (outside of office)
Process of elimination
- cannot be hardware, as it has happened to 3 distinct devices
- not an issue with OS image, 3 different installation mediums used
- not an issue with brand/type of flash drive, both USB 2.0 and 3.0 devices have been tried, along with brand new out-of-box devices. Issue occurs on both USB 2.0 and 3.0 ports on the computers
What it could be?
- the software that was installed onto the computers?
- virus/spyware/malware etc. ?
- ...and why does Desktop A work, when nothing was done to it?
Next steps/actions
- bring Desktop A back to office, wait and see what happens
- bring new laptop into office, with bare Windows 7 and no software installed, just networked
Any thoughts on WTF is going on???
windows-7 usb usb-flash-drive
windows-7 usb usb-flash-drive
edited Oct 11 '14 at 6:32
techfutures
asked Oct 11 '14 at 0:15
techfuturestechfutures
613
613
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13
add a comment |
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13
add a comment |
1 Answer
1
active
oldest
votes
I just had the same issue on Windows 10. It probably won't help with Windows 7, but may with Windows 8+. Windows 10 has a faster boot sequence which takes some shortcuts.
After uninstalling, rebooting and tearing my hair out for a while, I decided to take it at its word and held down on the Shift key while clicking on shutdown to do a complete power off instead of the normal hybrid. Once I did that, the device loaded just fine. I haven't done testing to see if it will continue to load, but that is what did it for me.
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f823738%2fmystifying-usb-mass-storage-device-issue-code-38%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I just had the same issue on Windows 10. It probably won't help with Windows 7, but may with Windows 8+. Windows 10 has a faster boot sequence which takes some shortcuts.
After uninstalling, rebooting and tearing my hair out for a while, I decided to take it at its word and held down on the Shift key while clicking on shutdown to do a complete power off instead of the normal hybrid. Once I did that, the device loaded just fine. I haven't done testing to see if it will continue to load, but that is what did it for me.
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
add a comment |
I just had the same issue on Windows 10. It probably won't help with Windows 7, but may with Windows 8+. Windows 10 has a faster boot sequence which takes some shortcuts.
After uninstalling, rebooting and tearing my hair out for a while, I decided to take it at its word and held down on the Shift key while clicking on shutdown to do a complete power off instead of the normal hybrid. Once I did that, the device loaded just fine. I haven't done testing to see if it will continue to load, but that is what did it for me.
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
add a comment |
I just had the same issue on Windows 10. It probably won't help with Windows 7, but may with Windows 8+. Windows 10 has a faster boot sequence which takes some shortcuts.
After uninstalling, rebooting and tearing my hair out for a while, I decided to take it at its word and held down on the Shift key while clicking on shutdown to do a complete power off instead of the normal hybrid. Once I did that, the device loaded just fine. I haven't done testing to see if it will continue to load, but that is what did it for me.
I just had the same issue on Windows 10. It probably won't help with Windows 7, but may with Windows 8+. Windows 10 has a faster boot sequence which takes some shortcuts.
After uninstalling, rebooting and tearing my hair out for a while, I decided to take it at its word and held down on the Shift key while clicking on shutdown to do a complete power off instead of the normal hybrid. Once I did that, the device loaded just fine. I haven't done testing to see if it will continue to load, but that is what did it for me.
edited Feb 8 at 9:01
Peter Mortensen
8,415166185
8,415166185
answered Oct 18 '15 at 19:52
Ralph TrickeyRalph Trickey
213
213
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
add a comment |
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
That worked for me!! Using USB keyboards and mice (3 different set) with a laptop progressively failed, and this fixed all problems.
– Peter Mortensen
Feb 8 at 9:57
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f823738%2fmystifying-usb-mass-storage-device-issue-code-38%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you (the users) ejecting (as in "safely remove hardware and eject media") the usb flash drives or just removing the device?
– DavidPostill♦
Oct 11 '14 at 7:41
@DavidPostill we tried both, but doesn't really explain why Desktop A is suddenly working. Even without safely removing it.
– techfutures
Oct 11 '14 at 16:02
Hmm. Have you tried error.info/windows/driver-38.html and support2.microsoft.com/kb/310123?
– DavidPostill♦
Oct 11 '14 at 16:09
Tried that at one point in time.
– techfutures
Oct 11 '14 at 16:12
Then I'm out of ideas ...
– DavidPostill♦
Oct 11 '14 at 16:13