Solved BSOD when dowloading Drivers. Sysdata and Minidump

So I've just done a clean install of Windows 8 64bit. After my computer crashed previously. The issue I'm having now is that whenever I attempt to install a driver, or perhaps particular drivers, my system will either crash and reset, or allow the drivers to download then during the Restart bring up the same error.

The Files that are apparently the issue are as follows.

C:\Windows\Minidump\011915-5694-01.dmp
C:\Users\USER\AppData\Local\Temp\WER-16754.sysdata.xml
C:\Windows\MEMORY.DUMP

Assistance will be greatly appreciated. As I've little to no idea what's causing this, especially after it's been working without issues for months.

-Dredelas.

Get all available Windows updates. Update your drivers using 3dp Chip software.

Rt630x64.sys Wed Oct 19 14:12:55 2011 (4E9EBEC7)
Realtek PCI/PCIe Adapters
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

dump_storahci.sys Thu Jul 26 04:30:35 2012 (5010ABCB)
driver created to provide disk access during crash dump file generation
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys

nvlddmkm.sys Wed Jul 2 19:42:02 2014 (53B4446A)
nVidia Video drivers
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys



Debug session time: Mon Jan 19 14:05:07.990 2015 (UTC + 1:00)
Loading Dump File [C:\Users\Mihael\SysnativeBSODApps\011915-5694-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:05:43.677
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+15393c )
BugCheck 116, {fffffa8006fe54d0, fffff8800c59193c, 0, 2}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Bugcheck code 00000116
Arguments:
Arg1: fffffa8006fe54d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800c59193c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
BUGCHECK_STR: 0x116
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BiosVersion = FB
BiosReleaseDate = 01/23/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Jan 19 13:48:41.178 2015 (UTC + 1:00)
Loading Dump File [C:\Users\Mihael\SysnativeBSODApps\011915-5397-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:03:38.865
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+3782fd )
BugCheck 133, {0, 283, 282, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Bugcheck code 00000133
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000283, The DPC time count (in ticks).
Arg3: 0000000000000282, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR: 0x133
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MsMpEng.exe
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm+3782fd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Jan 19 13:44:23.712 2015 (UTC + 1:00)
Loading Dump File [C:\Users\Mihael\SysnativeBSODApps\011915-5428-01.dmp]
Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
System Uptime: 0 days 0:11:58.399
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+3782fd )
BugCheck 133, {0, 283, 282, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Bugcheck code 00000133
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000283, The DPC time count (in ticks).
Arg3: 0000000000000282, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR: 0x133
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm+3782fd
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




--- E O J --- 2015 Jan 20 13:14:35 PM _88-dbug Copyright 2012 Sysnative Forums
--- E O J --- 2015 Jan 20 13:14:35 PM _88-dbug Copyright 2012 Sysnative Forums
--- E O J --- 2015 Jan 20 13:14:35 PM _88-dbug Copyright 2012 Sysnative Forums

Thanks for the information. I'm currently putting it to the test, but I seem to be having issues downloading the Microsoft Updates themselves, strangely enough. I'll be sure to get back to you should I not find a solution to the issue.