MpCmdRun.exe - Application Error

[Guest]

After installing the updated version of Windows Defender, I keep getting the
following error which looks to kill the program:

MpCmdRun.exe - Application Error

The instruction at "0x0096dc91" referenced memory at "0x00000007". The
memory could not be "read".

I am running WinXP Pro Service Pack 2 on a Dell Lattitude D610.

This sounds like a bug!

Thanks, Steve

 

[Guest]

Hello Steve,


Is this occuring in a corporate environment or on a home system/network?

Any clues in the System events log you can see?

http://search.microsoft.com/results.aspx?mkt=en-US&setlang=en-US&q=0x00000007

 

[Guest]

Yes...it is a corporate environment.

System events log shows the same error, and no additional info.

 

[Bill Sanderson MVP]

Could be--or at least, a software conflict of some kind. I don't have any
clear guideance to offer about how to figure out what this issue might be.
I don't believe it is a straight-out bug that hits lots of people, because
this build has been available for some weeks, and I haven't seen this posted
before. I don't think that it is specific to your hardware, because I
believe I've run Windows Defender on that system--though I'm not absolutely
sure I've run that newest build.

What I'd suggest considering is using some tool like MSCONFIG to temporarily
simplify the software load running to see if you can home in on what the
conflict might be.

There are a number of Google hits on this kind of error--but there doesn't
seem to be any simple common denominator that I've spotted about how to
troubleshoot it in the general case.

 

[Guest]

I'm getting the same error.

Dell XPS system, windows xp pro, sp2 Win2k3 AD environment

Event 26 (Application Popup)
Application popup: MpCmdRun.exe - Application Error : The instruction at
"0x00c0c299" referenced memory at "0x00000007". The memory could not be
"read".

Started after going from beta version that expires in December to latest
build. (I did not uninstall the old one first, but let the updater do its
thing)

Next step is to uninstall windows defender, including a registry/disk sweep
for leftovers and a reinstall of the latest package.

 

[Joe Faulhaber[MSFT]]

I've got a guess what it could be - there's a crash in the WGA control that
Windows Defender uses.

If you go to http://www.microsoft.com/genuine and click on the "Validate
Windows" link, you'll get an updated control that I think may fix this
crash.

Please post if it helps or not.

Regards,
Joe