Flash drive error reported in Event Viewer but no problem found,

Kick

Active Member
Joined
Aug 12, 2014
Messages
266
Location
Dorset, England, UK
Hi,

I run my elderly XP desktop isolated from the internet but use usbflash drives as a means of shifting folders between it and my connected Windows 7 desktop when necessary.

Strangely, whenever I connect a usb flash drive to the XP system, whether it's a USB1.1, USB2 or USB3 device, the Event Viewer reports an error "RSM could not load media in drive Drive 0 of library USB Flash Drive USB Device." However the devices work normally in every way - I can add files, copy or move files between the device and and desktop computer locations and so on. The error log is next to useless and the link included appears no longer to exist presumably because Microsoft gave up supporting domestic versions of XP over a year ago.

As I have suggested, despite the error, I have experienced no problems with usb flash drives, the internal card reader (part of original specifications) and external card readers all of which cause similar Event Viewer errors. External usb hard drives and Esata drives do not cause an error to be generated.

Hopefully this is something I can just ignore but it is a puzzle. I would welcome comments from the experts who contribute to this forum.

Thanks and regards, Kick.
 
Hi Kick,

I've researched what I was able to find and it looks to be a common problem with Windows XP yet even Microsoft didn't seem to have an answer.
From what I am able to tell, most errors like this result in the inability to view or use the flash drive media at all. You seem to be one of the lucky ones.
 
Just out of curiosity, with a flash drive you have finished with its contents, what happens if you use the XP machine to format it?

Nev.
 
Just out of curiosity, with a flash drive you have finished with its contents, what happens if you use the XP machine to format it?

Nev.

Hi Nev,

I'm not sure if I have ever formatted the flash drives via the XP machine - at the moment they all contain data but it is something I could try some time. As I said, I get a similar situation with the built in SD card reader when a card is inserted and similarly with an external usb SD card reader when a card is inserted. I'll get back to you if and when I have an update.

Cindy,

Thanks for your reply, I guess I am a lucky one because at least they work despite the error message from Event Viewer. I wondered if it might be something to do with the USB driver and Windows becoming muddled but I have no USB problems.

Cheers and regards to you both, Kick.

P.S. apologies for tardy reply.
 
Last edited:
Hi Cindy, Nev and DSTM,

First an update for Nev: I copied the files of my oldest and smallest flash drive to my desktop (the drive is only 32mb and is a USB 1.1 type) and then reformatted it in XP. Having safely disconnected it, I reinserted it into the usb socket and a few seconds later the same error message appeared in Event Viewer. The flash drive is still working normally and I was able to replace the files lost in the reformatting process. All these errors have happened in the front panel of the desktop where the inbuilt card reader is also located. (I've also just confirmed that the Event Viewer error is generated on both the front panel USB sockets and rear USB sockets).

Cindy and DSTM: Your comments are reassuring in a way - one could easily get paranoid about Event Viewer errors - I tend to get more in Windows 7 but they are usually occurring on startup, don't cause any problems and as likely as not, do not happen at the next startup. It's as if Windows sometimes get confused and can't always keep apace of events during the startup process. I've developed what might be construed as a bad habit, I look at the Event Viewer after each fresh start of the system - I suppose that's asking for trouble or possibly a nervous breakdown. There are probably millions of Windows computer users who never look at the Event Viewer and have got hundreds of error reports stored away, however they are probably still sane.

Regards to all, Kick.
 
I only look at any fault logs if something stops working, it is pointless looking in them otherwise as all sorts of odd errors happen, quite often due to simple time out errors as you said while the system is booting up. Windows is clever enough to sort most of them out once fully booted up any way.

Nev.
 
Back
Top