WERInternalMetadata.xml (Computer freezes when playing games "APB")

Well, it just crashed agian..

The program mmc.exe version 6.1.7600.16385 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: f80
Start Time: 01cd146862ce4622
Termination Time: 0
Application Path: C:\Windows\system32\mmc.exe
Report Id: c2f7a0d4-805b-11e1-a589-d4856411a13b
I think thats it...

Or then its Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.



- <Event xmlns="Error">
- <System>
<Provider Name="EventLog" />

<EventID Qualifiers="32768">6008</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-04-07T02:39:03.000000000Z" />

<EventRecordID>46614495</EventRecordID>

<Channel>System</Channel>

<Computer>Augeson-HP</Computer>

<Security />

</System>


- <EventData>
<Data>9:37:40 PM</Data>

<Data>‎4/‎6/‎2012</Data>

<Data />

<Data />

<Data>4628</Data>

<Data />

<Data />

<Binary>DC070400050006001500250028000F03DC070400060007000200250028000F03080700003C000000010000000807 000000000000840300000100000000000000</Binary>

</EventData>


</Event>

Event ID 4107 or Event ID 11 is logged in the Application log in Windows and in Windows Server should solve that error.

Do you think thats the cause of the crash?

That's a pretty common error, so I do not think it would be the cause. See how the system responds for a bit, though. Anything is possible.

So basicly the crashes had something to do with a macro that I was using in my built in Naga razor epic.. and for some reason it caused my comp to crash

The macro may have been written to use resources in a way that Windows did not intend for them to be used. Basically, it was probably writing to memory that it was not supposed to and causing Windows to freeze. Glad you narrowed it down. Nice troubleshooting. That may help others in the future with similar problems.

Would there be a way to change that? So I could use my macro?

Do you know who developed the macro? I would recommend you pose the question in the forums related to either the software itself or for the macro that was causing problems.