MRxSmb Event ID 3019 warning causes lockup

March 10, 2010 at 04:16:48
Specs: XPHomeSP3, 3.0/1gig
Problem is with the computer freezing for anything up to 10 minutes. The only clue I can find is a warning in Event Viewer about MRxSmb code 3019. The computer does have a link to a shared folder on another pc and the problems seem to start when this folder is accessed. I've had a look at a number of fixes for the problem, unfortunately the general concensus is to ignore it and most posts seem to be from a number of years ago. The problem has only just started - the only thing that has changed recently is a few Windows updates last week but doing a System Restore to a prior point had no effect on the problem.
Anyone else come across this issue? & any suggestions please.

"I've always been mad, I know I've been mad, like the most of us..."


See More: MRxSmb Event ID 3019 warning causes lockup

Report •


#1
March 10, 2010 at 04:31:29
johnr, SWAG, possible it's some sort of worm/trojan calling home? Scan?
HTH.
Ed in Texas.

Report •

#2
March 10, 2010 at 04:42:04
Thanks for reply. Already did a full scan with resident Kaspersky. I'd been asked to look at system because of general slowness/freezing so I'd already done the scan, removed loads of rubbish etc. & this event viewer warning is the only thing left. System works 100% until I try connecting to the networked folder & unfortunately networking is not my forte beyond the basics. As it's only a warning, rather than an error, & there's nothing else listed I'm still not absolutely certain that this is the root problem, but I want to get rid of it - even Microsoft's 'fix' is to ignore it!!

"I've always been mad, I know I've been mad, like the most of us..."


Report •

#3
March 10, 2010 at 07:08:26
"The computer does have a link to a shared folder on another pc and the problems seem to start when this folder is accessed."

"System works 100% until I try connecting to the networked folder ...."

That's probably your best clue.

I searched with: MRxSmb code 3019

Have you checked out this:

Event ID 3019 Source MRxSmb
http://www.eventid.net/display.asp?...


Report •

Related Solutions

#4
March 10, 2010 at 07:51:19
Yes, I've been through as many of the solutions on there that are relevant - we haven't got the IE add-on mentioned; the guest account has never been enabled; changing the IsDomainMaster key did nothing; RDC isn't enabled & never has been. Unfortunately most responses are 5+ years old and nothing current seems to be relevant. I'll see about subscribing to Eventid.net (that costs money!!!) to get their 'hidden' responses & see where I go from there, it would just be nice to find a more recent, ie post SP3, comment.

"I've always been mad, I know I've been mad, like the most of us..."


Report •

#5
March 10, 2010 at 12:41:04
There are lots of things that have NOT changed at all since XP was first released.
Old info about MRxSmb and that particular error may still be relevant - that certainly applies to many other things in XP, and even some info about similar in 2000 still applies to XP.

Ask yourself -
When did the error first occur ?
Were you accessing the shared folder previous to that?
Did it occur after you installed something yourself , or after something was installed automatically by Automatic Update, or by an anti-malware or other program program updating itself ?

Can you pin down an approximate date ?

Look in the same place you found the Event error about MRxSmb and that particular error - that log goes back in time (if you have the newest Restore Point loaded) - scroll down and see when you first got the error - if that's not before the beginning of the log, that yields you a date or an approximate date .

You can look up your Microsoft Updates history (which updates were loaded, when) when you access the Microsoft Update page on the Microsoft site.

Look for clues in the "hits" you find for your error.

E.g.
Apparently your error has happened in the past
- after SP2 updates were loaded
- after a particular update to certain anti-malware software was loaded

Search for files with the same date as when you first got the error.

Etc., etc. .


Report •

#6
March 10, 2010 at 13:20:28
Thanks for reply. The problem is that I'm not certain that the MRxSmb warnings are, on their own, the whole problem. The warnings have been occurring for sometime, but have now been more common, coinciding with the system freezing problem. There wasn't a specific date after which the problem occurred, all I have been able to establish is that: the freezing only happens after we've tried to access the remote folder; the only event shown is the warning about MRxSmb (which does seem to have a bearing upon network folders); no actual error about MRxSmb is listed; Googling the problem does not come up with a definitive answer, or even a comparable problem, and the proposed fixes I've tried have had no effect. Hence I surmise that it is a combination of the MRxSmb warning, together with some other update/system change that is causing the lock-up.

I'm just hoping that this is not the only system in the world with these symptoms and we can find some common denominator that will establish where the problem lies & how I can fix a MRxSmb warning (...........that has not actually manifested itself as an actual error.....................even though the error occurs!!...)

When is Windows8/Cloud Computing coming, so I can leave this to someone else to sort out? ;-)

"I've always been mad, I know I've been mad, like the most of us..."


Report •

#7
March 10, 2010 at 14:38:28
I'd bet your nic card is going bad.

Religion is what keeps the poor from murdering the rich.

Napoleon


Report •

#8
March 10, 2010 at 23:37:57
Hmmm, that's a possibility, could be the card on the 2nd pc as well I suppose.

"I've always been mad, I know I've been mad, like the most of us..."


Report •

#9
April 28, 2010 at 04:34:36
I have the exact same problem as you describe. It seems to be explorer.exe that is hanging. The PC hangs when I open a UNC shortcut from my desktop. However, if the same UNC shortcut is opened in Word everything works fine eventhough the PC is currently hanging from opening the UNC shortcut.

The PC does not always hang for when opening UNC shortcuts, but most often.

This does not happen to all PCs in the network !!


Have you had any luck ?


Report •

#10
April 28, 2010 at 05:08:39
No cure I'm afraid, the problem seems to have gone away
(famous last words!) and I have no idea if it was a recent update
or just a change in the wind...

Just a thought, can you end explorer.exe and then restart it just
to confirm that it is the issue?

"I've always been mad, I know I've been mad, like the most of us..."


Report •

#11
April 28, 2010 at 08:36:28
explorer.exe is what loads the desktop.
Lots of things can cause it to hang, yet there's nothing wrong with explorer.exe itself.

Windows Explorer, the alternative to My Computer, is merely a second instance of explorer.exe running with some added switches.
E.g. for my Win 98SE computer
C:\WINDOWS\EXPLORER.EXE /n,/e,C:\

If these computers are connected via network cables.....

- make sure all end connectors are "latched" into the network ports - the plastic lever on them fatigues more the more it has been used, and eventually it won't "latch" into the port or it breaks off, and then you need to replace the end connectors.
The end connectors are easy to replace if you have the right tool to install them - that tool can be bought for as little as $20 or less if you search , and the end connectors can be bought in bulk.
- the cable sheath should be clamped inside the end connectors - it that was sloppily done (too much of the cable sheath was removed) or the cable sheath has pulled out, you're more likely to have problems with that end of the cable.
- I've noticed that some cheap network cables don't actually have the matched twisted pairs of wires hooked up properly - that could certainly cause problems even when the cable still works. When you look at the end connectors, there should be matched pairs beside each other - e.g. blue, white with blue stripe, orange, white with orange stripe, green, white with green stripe, brown, white with brown stripe. If the white with (color) stripe wire doesn't match the (color) of the wire beside it on one side or the other, you're more likely to have problems, the more likely the longer the cable is.

- some routers have a cable test feature in their configuration. You merely connect the cable between the router and a live network port (the device with the port must be on), run the test, you know right away whether it's a good connection or an iffy one.


Report •


Ask Question