Windows 7: BSOD with differet crashes while installing updates on SWTOR

Hello, I am new to the forums here and am having great difficulty with my new computer. It is only a month old and has been crashing since I got it. I have done a full windows wipe twice. It seldom crashes when I am just on the internet, but will always crash when I try to install updates from SWTOR (Star Wars the Old Republic).

My Ethernet controller and USB need drivers, yet when I try to windows update them it says they cannot find the drivers. Not sure if this is what is causing the crash.

Also included the latest data from WhoCrashed:
On Wed 5/9/2012 2:43:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-10623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 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 Wed 5/9/2012 2:15:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050912-10592-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88006DDD912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED




On Wed 5/9/2012 1:53:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-10873-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xEFC08)
Bugcheck code: 0xD1 (0xFFFFF88001326C08, 0x0, 0x8, 0xFFFFF88001326C08)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 5/9/2012 12:18:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050812-10498-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 5/4/2012 11:02:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-10389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC80)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002FD7180, 0x3)
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 Wed 5/2/2012 1:49:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-10701-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007186912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED

One of the BSOD team members will stop by soon to analyze your .dmps. For now, you can find all of the updates you need for your MoBo(ethernet controller and USB) here.

There is also BIOS updates available, click the download type and select BIOS.

Also, if you are using any of the Gigabyte Utilities, such as EasyTune and Smart6, please stop using them and uninstall them. After doing the updates and removing the utilities, you may find stability. Post back with results.

Updated usb and ethernet controllers, as well as the BIOS through @BIOS. Tried to install SWTOR and got blue screened again. A clock interrupt on a secondary processor.

You did not respond to this. Are you using EasyTune or any of the other Gigabyte utilities. The Fault you mention is common with overclocking.

My latest dumps after updating my bios and ethernet/usb controllers:

Sorry, no I am not overclocked or using Easytune6 or any other utility.

Okay, until your .dmps get analyzed, I would like for you to download CoreTemp, and Hardware Monitor and post snips of your min and max temps please. Specifically your CPU and Motherboard temps.

Hope I got this right

Okay, I would actually like just a snip of the HWMonitor window with the minimum and maximum temps showing. I want to see the temps on the Motherboard sensors. BTW, you have great processor temps.

To use the Sniping tool, in the Windows search box, type "snip" and you will see the snipping tool. Once it opens, click on one corner of the are you want to capture and release it on the opposing corner. After doing so, select "save as" name the file what ever you would like. Then upload that image.