WTF Asrock?

I have started this blog to figure out what is causing my rig to Blue Screen on me, about once a day.
It always seems to happen when I am doing something. Playing a game, doing a Google+ Hangout, etc.

Here is the Blue Screen.
On Sun 1/1/2012 12:04:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010112-22869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 12/30/2011 10:42:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-17862-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x92746)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EE0746, 0xFFFFF88003584FD8, 0xFFFFF88003584830)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 12/30/2011 10:08:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123011-19562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003389180, 0x7)
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. 


That is the last 3 crashes.
A search for CLOCK_WATCHDOG_TIMEOUT and My Asrock board turns up a lot of results. Too many to be a coincidence I think.

Then there is this thread.
http://forums.tweaktown.com/asrock/44772-asrock-z68-extreme-4-bsod-clock-interrupt-not-received.html
which is 38 pages long FULL of people having the same problem with the extreme 4. What give Asrock?