Windows application error can be found below -
Log Name: Application
Source: Application Error
Date: 11/01/2012 10:27:16 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: dwnrdhbas1g.prod.main.ntgov
Description:
Faulting application name: cdm.exe, version: 4.54.0.0, time stamp: 0x4ddc4307
Faulting module name: cdm.exe, version: 4.54.0.0, time stamp: 0x4ddc4307
Exception code: 0xc0000005
Fault offset: 0x0000000000024c71
Faulting process id: 0x13f4
Faulting application start time: 0x01cccffbf508cb38
Faulting application path: C:\Program Files (x86)\Nimsoft\probes\system\cdm\cdm.exe
Faulting module path: C:\Program Files (x86)\Nimsoft\probes\system\cdm\cdm.exe
Report Id: 3445dc31-3bef-11e1-be10-0050569c000e
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-01-11T00:57:16.000000000Z" />
<EventRecordID>34472</EventRecordID>
<Channel>Application</Channel>
<Computer>dwnrdhbas1g.prod.main.ntgov</Computer>
<Security />
</System>
<EventData>
<Data>cdm.exe</Data>
<Data>4.54.0.0</Data>
<Data>4ddc4307</Data>
<Data>cdm.exe</Data>
<Data>4.54.0.0</Data>
<Data>4ddc4307</Data>
<Data>c0000005</Data>
<Data>0000000000024c71</Data>
<Data>13f4</Data>
<Data>01cccffbf508cb38</Data>
<Data>C:\Program Files (x86)\Nimsoft\probes\system\cdm\cdm.exe</Data>
<Data>C:\Program Files (x86)\Nimsoft\probes\system\cdm\cdm.exe</Data>
<Data>3445dc31-3bef-11e1-be10-0050569c000e</Data>
</EventData>
</Event>
Environment:
UIM 7.6 or higher Windows 2008 R2 Server
Cause:
This is most likely due to corrupted Perfmon counters. We use the Windows performance counters to display the values in the cdm probe
Resolution:
If the counters become corrupted you can run this command to fix:
%SYSTEMROOT%\system32\lodctr /R
This command is referenced at http://support.microsoft.com/?kbid=300956
Additional Information:
Be sure you are running command ad Administrator.