New build, random BSODs

[hueyz]

Hello everyone. I recently built a new(ish) computer and it is giving me some problems. I keep getting random BSODs, at first I thought it was because of my OC so I went ahead and removed it, but now it still continues to BSOD. All parts are new besides the CPU and the PSU. Parts are listed below, Crash Dump info posted below parts list :

CPU: AMD Phenom II X6 1100T Black Edition Thuban 6-Core 3.3GHz (From an old working build)
MOBO: ASUS M5A99FX PRO R2.0
SSD: SanDisk Ultra II 2.5" 480GB SATA III Internal Solid State Drive (SSD) SDSSDHII-480G-G25
RAM: G.SKILL Ares Series 16GB Model F3-2400C11D-16GAB
CPU COOLER: Corsair Hydro Series™ H80i GT High Performance Water / Liquid CPU Cooler
VGA: EVGA GeForce GTX780 SuperClocked w/EVGA ACX Cooler 3GB GDDR5 384bit
PSU: Rosewill 650w psu from an build i had before.

CRASH DUMP INFO:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 1/22/2016 12:28:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012216-6692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002CD7071, 0xFFFFF8800BBDC130, 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 Fri 1/22/2016 12:28:20 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002CD7071, 0xFFFFF8800BBDC130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Thu 1/21/2016 4:15:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012016-7035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x50 (0xFFFFF1001434F154, 0x1, 0xFFFFF80002F7537E, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/21/2016 4:08:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012016-6973-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF8800331D858, 0xFFFFF8800331D0B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 1/20/2016 1:53:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012016-6692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x9E39E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF80001CB139E, 0xFFFFF880021AD308, 0xFFFFF880021ACB60)
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 that cannot be identified at this time.



On Tue 1/19/2016 3:15:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011916-7035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80001CCEF20, 0xFFFFF8800DF07F80, 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.

 

[Guest]

get this-http://www.resplendence.com/whocrashed

 

[faalin]

The 0xc000001d error is a common yet critical error that can occur when Windows is damaged or fails to work as a result of either missing system files or corrupt system components.


If you haven't done a hole lot on the computer I would recommend just reinstalling and see if that fixes the issue

 

[hueyz]

Hello denis280, the crash dump reports were pulled with WhoCrashed. They are pasted below the parts list. Hi faalin, I suspect that might be an issue. I forgot to mention that during Windows install my computer kept going into BIOS, then I had to manually click the SSD in the UEFI to boot into it to continue the windows install. I figured out the issue causing the problem, my old Alienware keyboard was making the PC go into BIOS every time I booted. I switched it out and continued the install but I believe the damage is already done. I am going to reinstall windows, is there anyway I can check after my new install to make sure the BSOD will not happen again ? On another note, what do you guys think of this build ?

 

[Guest]

Hello denis280, the crash dump reports were pulled with WhoCrashed. They are pasted below the parts list. Hi faalin, I suspect that might be an issue. I forgot to mention that during Windows install my computer kept going into BIOS, then I had to manually click the SSD in the UEFI to boot into it to continue the windows install. I figured out the issue causing the problem, my old Alienware keyboard was making the PC go into BIOS every time I booted. I switched it out and continued the install but I believe the damage is already done. I am going to reinstall windows, is there anyway I can check after my new install to make sure the BSOD will not happen again ? On another note, what do you guys think of this build ?

Good system

 

[hueyz]

Thank you Denis280, I am hoping to upgrade to the new cards AMD is releasing.

 

[hueyz]

I reinstalled Windows 7, and everything went smooth. So far I have had no probelms, ran Prime95 and did 3 Burnin test. But now I have a new problem, I have screen tearing when I play video games and switching out between programs and watching videos online. This was not happening before I had reinstalled windows, what could be causing this now ?

 

[Guest]

I reinstalled Windows 7, and everything went smooth. So far I have had no probelms, ran Prime95 and did 3 Burnin test. But now I have a new problem, I have screen tearing when I play video games and switching out between programs and watching videos online. This was not happening before I had reinstalled windows, what could be causing this now ?

are you running the gpu stock or overclock

 

[hueyz]

stock, since the new windows install I have not OC'ed anything. I installed all the proper drivers and updated windows, installed GTA 5 and other software for pc stats. I can't get it to stop. I already did a clean install of the video card driver.