Problema. PC se congela. (SOLUCIONADO)

Hola.
Tengo un i7 950l
Placa base Asus P6T
RAM 4 GB  Kinston
Disco Seagate barracuda 7200 rpm
Gráfica GTX 480.
S.O Windows 7
Todos los drivers actualizados incluyendo la ultima versión de la Bios.
S.O recientemente formateado con fallos antes y después del formateo.
Caja totalmente limpia con disipadores limpios y pasta térmica recién cambiada.
Fuente de alimentación revisada y sin picos.
RAM comprobada módulo por modulo.
CPU crompobado y sin fallos.
VGA revisada y sin fallos.

Mi problema es que según le da a mi PC, se queda congelado o bien me salta un pantallazo azul.
Lo hace aleatoriamente y una vez que la a hecho ya puede estar todo el día encendido que no lo vuelve a hacer.
Las temperaturas son normales y puede congelarse nada más encenderlo o bien hacerlo al rato o no hacerlo en todo el día.
Antes de fallar empieza como a ralentizarse y si coincide que hay algún sonido produciéndose este suena como a lata.
Pero para que falle no tiene por que haber ningún sonido. Incluso estando sin tocarle ni teniendo programas abiertos se puede bloquear.

Como yo no di con el fallo lo llevé al servicio técnico, pero ellos tampoco dieron con el fallo después de analizar todos los componentes.
Lo único que no se puede testear por completo es la placa base.
Que es donde yo pienso que reside el fallo.


Os pongo el reporte de fallos que me proporciona el programa WhorCrashed.

[b]On Wed 27/07/2011 21:01:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-26551-01.dmp
uptime: 00:13:44
This was probably caused by the following module: hal.dll (hal+0x12818) 
Bugcheck code: 0x9C (0x0, 0xFFFFF8800316FC70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Wed 27/07/2011 21:01:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:13:44
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500) 
Bugcheck code: 0x9C (0x0, 0xFFFFF8800316FC70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Wed 27/07/2011 17:43:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-23337-01.dmp
uptime: 00:26:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F63180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Mon 18/07/2011 17:37:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071811-19936-01.dmp
uptime: 00:00:07
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8005129038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sun 17/07/2011 21:32:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071711-28298-01.dmp
uptime: 00:14:51
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F63180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Fri 01/07/2011 9:51:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070111-20108-01.dmp
uptime: 00:10:56
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00) 
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F7180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. [/b]

Me gustaría saber si alguien a tenido este fallo o sabe que puede ser.

Gracias.
EDITADO EL 21-08-2011 / 14:52 (EDITADO 1 VEZ)