Tuesday, March 13, 2012 5:01 PM
When I try to run Performance Monitor in Windows 7 I get the error "Microsoft Management Console has stopped working".
Problem Event Name: BEX64
Application Name: mmc.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc808
Fault Module Name: MSVCR80.dll
Fault Module Version: 8.0.50727.4940
Fault Module Timestamp: 4ca2b4dd
Exception Offset: 000000000001da44
Exception Code: c000000d
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: fbb0
Additional Information 2: fbb06339a11baf5fffd402414452d8bd
Additional Information 3: 7964
Additional Information 4: 7964d26bc274ba75f5af276a2727cebe
Any help on how to fix this problem is appreciated.
Wednesday, March 14, 2012 9:22 AM
As MMC related crash issues might be related to incompatible application DLLs attached to the mmc.exe process. I suggest you follow the steps below to troubleshoot it.
1. Make sure the system is up to date with the latest security patch and Service Pack.
2. Try to run "sfc /scannow" to fix files
3. If the problem continues, I suggest you perform a clean boot to troubleshoot it. Please also check if there is any relevant error in event log.
Hope this helps.
- Marked As Answer by Dan Randolph Saturday, March 17, 2012 7:16 PM
Thursday, March 15, 2012 6:42 PM
I tried step 2 (no problems found) and the clean boot but it didn't help.
I have some additional information from when I try to run this with >perfmon /sys
It starts, but as soon as I hit the '+' to add counters, it crashes when this message from the application event logs:
Faulting application name: perfmon.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3e0
Faulting module name: MSVCR80.dll, version: 8.0.50727.4927, time stamp: 0x4a27427d
Exception code: 0xc000000d
Fault offset: 0x000000000001da44
Faulting process id: 0x13fc
Faulting application start time: 0x01cd02d9283ee5ff
Faulting application path: C:\Windows\system32\perfmon.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_88dce9872fb18caf\MSVCR80.dll
Report Id: 6c20cbbe-6ecc-11e1-b13e-00219b24b65c
Could this be a problem with the copy of MSVCR80.dll in the WinSxS folder?
Saturday, March 17, 2012 7:34 PM
Problem solved... I'm not sure if it was my printer driver that caused the problem, but I reinstalled the driver for my Samsung CLP-510 printer and Perfmon works now. I actually downgraded the driver since I wanted the 64-bit version to match with a 32-bit version on my 64-bit system so I could share the printer with a 32-bit Vista system. When you do printer sharing under Print Management it lets you add additional drivers to support different version of Windows. I'm now running Driver Version 3.1.0. I think the newer drivers are messed up. The only two brands of printers I've used with good driver support are HP and Cannon.
I had the print-sharing working before, but when I did an in-place install to try to get Perfmon working again, my print sharing got messed up.
It is also slightly possible, but doubtful, that the last round of Windows updates I installed fixed the problem.
- Edited by Dan Randolph Sunday, March 18, 2012 4:16 AM grammer
Sunday, March 18, 2012 4:14 AM
Now I had to upgrade the pair of Samsung printer drivers to version 3.4.25 (which is an unsigned driver) before it would work with the 32-bit Vista system. I'm not too happy about that. Last time I buy a Samsung printer. This problem has cost me at least $300 in wasted time.
Thursday, March 22, 2012 6:10 PM
There was one more annoying problem with the Samsung setup.
I kept getting this error in my System Event logs on start-up:
The DgiVecp service failed to start due to the following error:
The filename, directory name, or volume label syntax is incorrect.
I did some research and found that DgiVecp is only used to create a virtual parallel port.
I'm running my printer on "Virtual Printer Port for USB". So I disabled the service by running
>SC CONFIG dgivecp start= disable
At the least, it was making my system take longer to start.
Now that my performance counters are working and I fixed all the other event viewer errors my system is running extremely fast and it starts in seconds instead of minutes. Before, when I logged in, it would take another minute before I could do anything. Now it even gets its network connection in less than ten seconds after start-up.
The last thing I did was install a small second hard drive that I had on the shelf. I moved the PageFile.sys over to this hard drive. It is supposed to make your system faster to have the PageFile on a separate physical drive, but I haven't noticed much difference so far.
Working performance counters make a much bigger difference because the OS needs these to optimize memory usage, etc. I could not even shut down the system before. It would get hung up on shut-down so I just had to power it off.
I've experienced numerous problems with other Windows 7 systems too. Windows 7 reminds me of the old Pontiac Trans Am. It drove great, but it need constant repairs to keep it going.
- Edited by Dan Randolph Thursday, March 22, 2012 6:15 PM spelling