need help in tracking a media playing issue

technically lve asked this before, the problem revolves around the fact that on some mkv files directly after rebooting/starting my system the whole computer will freeze for a few seconds.

now the strange part is this only happens once and only directly after starting windows, now generally l play most through media player classic however it does affect media player itself as well in the same way. the strangest part is like l said it only affects files with the mkv extension.

now lve been wondering if there is a different way to attack the problem, like maybe some way of logging what happens when l get the system freeze, something that will create some sort of crash dump of some sort that could log what happens as the problem is easy to create but hard to pin so it would be easy to run some sort of software prior to creating the issue if there is something out there that could possibly pick up an issue.

on a side note, if anyone is interested l use the cccp codec pack.

the whole PC freezes up for a few seconds on generally the first mkv file l open.. after that its fine. and as l said it only affects files with the mkv file extension and it only happens once per boot, once its happened everything seems ok and runs no problem which is why it makes no sense.

that being said some mkvs dont cause issues others do its hard to pinpoint which one will or not. which is why lm hoping there is a way to start some sort of logging going before l attack the issue.. lve spent so much time thinking about what it could be but not actually thinking of a way to monitor the issue rather than just look for a fix.. after all it makes more sense to find out whats happening before l look into messing around with the settings and hoping for the best.

as for the codec pack l use, its the same version l used last year with no problems whatsoever, and as a point of interest generally lm loading Directvobsub/Hailli and ffdshow.

looked further in the logs, now lm speculating here..

last restart showed an error with distributed Com, other than that l dont see the other two having even a remote link to the issue, as volume shadow copying tho l am confused with PxHelp20 causing errors as its supposedly attached to a burning program l dont have installed (unless its part of imgburn).

managed to get VEW running, seems it didnt like my system locale to cheated by running applocale to save me rebooting.

anywho instead of grabbing the last 20 (as l noticed quite a few dns errors in the error logs) l picked the time frame around the time l last rebooted, and the only issues l can really see are along the lines of the above PxHelp20/Dcom that give the general timeframe of my issue, l covered the whole day when l rebooted and the below is all l could come up with.

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 18/03/2013 19:33:55

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 13/03/2013 00:17:35
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Probe2.exe, version: 0.1.4.75, time stamp: 0x00000000 Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f Exception code: 0xc0000005 Fault offset: 0x00033560 Faulting process id: 0xa40 Faulting application start time: 0x01ce1d671f5c32bb Faulting application path: C:\Program Files (x86)\ASUS\PC Probe II\Probe2.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 677f89cc-8b73-11e2-a14d-5404a6532066

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 13/03/2013 00:27:04
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: PxHelp20

Log: 'System' Date/Time: 13/03/2013 00:26:15
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {E10F6C3A-F1AE-4ADC-AA9D-2FE65525666E} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 13/03/2013 00:24:32
Type: Error Category: 0
Event: 36 Source: volsnap
The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.

Log: 'System' Date/Time: 13/03/2013 00:19:05
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: PxHelp20

Log: 'System' Date/Time: 13/03/2013 00:18:15
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {E10F6C3A-F1AE-4ADC-AA9D-2FE65525666E} did not register with DCOM within the required timeout.