Hello! I built a computer a few months ago and after about a week I started to get repeated BSOD errors. It happens mostly when I am playing video games or watching netlfix, but it also happens when I am simply listening to music or browsing the internet. I've tried just about everything I can think to fix this including reinstalling my OS. Here is my build :
Intel Core i5-3570K, Asus GeForce GTX 670, Thermaltake Chaser A31 - My Custom Build - Spoonerj24's Saved Part List - PCPartPicker
and here are the BSOD errors copy and pasted off Who Crashed: On Wed 11/20/2013 3:05:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-10748-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFB8011E552F0, 0x2, 0x1, 0xFFFFF80003294F6D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
On Wed 11/20/2013 3:05:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x77BC)
Bugcheck code: 0xA (0xFFFFFB8011E552F0, 0x2, 0x1, 0xFFFFF80003294F6D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
On Tue 11/19/2013 11:39:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-6864-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xBF4F1)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/12/2013 2:16:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111213-9952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFFA84112DEBE0, 0x2, 0x1, 0xFFFFF80003283740)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.
On Mon 11/11/2013 9:53:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-6957-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88005A1D40F)
Bugcheck code: 0x50 (0xFFFFF8A045234BA0, 0x0, 0xFFFFF88005A1D40F, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
On Sun 11/10/2013 5:34:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-8673-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033AC123, 0xFFFFF8800AC26A50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Mon 11/4/2013 10:25:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110413-6739-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000AE0C8)
Bugcheck code: 0x50 (0xFFFFF900D068BFA0, 0x0, 0xFFFFF960000AE0C8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.
On Wed 10/30/2013 6:39:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103013-6208-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00575C530, 0x3, 0x4804)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 that cannot be identified at this time.
On Wed 10/30/2013 5:47:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103013-6988-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A005D3ACB0, 0x0, 0x7746F)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 that cannot be identified at this time
Any help would be greatly appreciated. Thank you in advance!