In Vista, if I open mmc and add a snapin, it crashes. If I click debug to see the crash message, this is displayed:
Unhandled exception at 0x77b05a20 in mmc.exe: 0xC0000005: Access violation writing location 0x00000e4c.
Printable View
In Vista, if I open mmc and add a snapin, it crashes. If I click debug to see the crash message, this is displayed:
Unhandled exception at 0x77b05a20 in mmc.exe: 0xC0000005: Access violation writing location 0x00000e4c.
That is referencing memory locations I believe. I would say that the app is corrupt. Have a look about for a copy of this file. I'm sure it will be online somewhere. Backup first though remember.
Due to the way vista handles RAM it could also be an indication of a faulty stick. I suggest downloading and running memtest on your machine. Another symptom of this is when installing large programs you get the same error. Have you ever had this error before?
Haven't got Vista installed on this current computer, however I'm under the impression this functionality would be the same as XP. You could try Start > Run > MSConfig, then the "Expand file" option beneath the general tab.
You might need your Windows CD, unless your network admins or PC manufacturer have copied the I386 folder locally. On mine it's:
File To Restore: MMC.exe
Restore From: C:\Windows\I386
Save File In: C:\WINNT\system32
Are you runing the mmc as Administrator? Do you have SP-1 installed for Vista? Some of the mmc stuff was removed with SP-1 and is now a separate download.
If I open an msc file directly, it doesn't crash. It only crashes if I open mmc and then add in any snap-in.
I am running Vista SP1, but the problem also occured prior to loading SP1. When mmc is launched, it prompts for administrative rights, and I allow.
This is further crash data:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: mmc.exe
Application Version: 6.0.6001.18000
Application Timestamp: 47918d09
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a7a6
Exception Code: c0000005
Exception Offset: 000659c3
OS Version: 6.0.6001.2.1.0.256.4
Locale ID: 1033
Works for me. I second the faulty memory idea. Run the extended tests in memtest86+ overnight and see if anything turns up.