Welcome to the forums Deadliver,
Code:
BugCheck A, {fffff7d002e9ab38, 2, 1, fffff8000368dd69}
Probably caused by : hardware ( nt!KiInsertTimerTable+1b9 )
Code:
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bugcheck suggests that drivers have been attempting to access invalid memory addresses and perform write operations, whilst the IRQL level is too high for the driver to interrupt.
It seems to point to a hardware related cause, but looking at the other dumps, I was able to identify some more findings:
Code:
BugCheck FC, {fffff8a000008930, bb8000041c878963, fffff8800ad33530, 0}
*** WARNING: Unable to verify timestamp for cfosspeed.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed.sys
Probably caused by : pacer.sys ( pacer!PcFilterRequestComplete+68 )
Code:
Usual causes: Device driver
This bugcheck indicates that a driver has attempted to access invalid memory again, and execute a region of non-executable memory.
Code:
3: kd> lmvm cfosspeed
start end module name
fffff880`0822e000 fffff880`08399000 cfosspeed T (no symbols)
Loaded symbol image file: cfosspeed.sys
Image path: \SystemRoot\system32\DRIVERS\cfosspeed.sys
Image name: cfosspeed.sys
Timestamp: Mon Oct 12 15:48:49 2009 (4AD341D1)
CheckSum: 00163315
ImageSize: 0016B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your cFosSpeed Miniport driver seems to be a possible cause, please update the software for this driver (Download Page - cfosSpeed - cFos IPv6 Link - cFos - hrping - Skins - cFos Software) or remove it completely using Revo Uninstaller Pro - Uninstall Software, Remove Programs easily, Forced Uninstall, Leftovers Uninstaller
I'll post some more information in a few minutes.