Continuous BSOD errors

Matthew_81

Commendable
Apr 30, 2016
6
0
1,510
My apologies if in wrong forum, I'm new to this website. After starting games, joining steam chats, watching videos, ect. my computer will either BSOD or just freeze and bug out until I force restart. I've checked system temps and those are all normal if not under average temps always.
I've tried updating all my drivers (all up to date) and doing a fresh install of windows both from a flash drive and also from the disc.

My specs are:
Windows 10 home 64bit
AMD FX 8350 4.0ghz
EVGA GTX 970 SSC 4GB
1x8GB Corsair Vengeance
Corsair cx 600W
2TB seagate barracuda
ASROCK 970 extreme3
(don't know what other specs needed)


Computer name: DESKTOP-DG5DAV0
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASRock, 970 Extreme3 R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8544579584 bytes total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 1/8/2017 11:02:35 AM your computer crashed
crash dump file: C:\Windows\Minidump\010817-39218-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sun 1/8/2017 11:01:28 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!ReleaseCacheDC+0x31)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802234A3BE2, 0xFFFFAF81B9806170, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
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 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 1/1/2017 5:54:33 PM your computer crashed
crash dump file: C:\Windows\Minidump\010117-20000-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR


On Tue 11/29/2016 2:03:12 AM your computer crashed
crash dump file: C:\Windows\Minidump\112916-18328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80301E35B22, 0xFFFF9180604A3BE0, 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.



*Any and all help is appreciated
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
You have a bad driver, and it's causing corruption of the windows installation itself. That last dump with the NTOSKRNL.EXE isn't a good one. Have you run MemTest on the RAM to make sure it's good? Are you overclocking at all? You can reboot your system into safemode with command prompt, and run SFC /scannow to scan and repair your system files (ntoskrnl.exe, and any others that could be corrupt)
 

Matthew_81

Commendable
Apr 30, 2016
6
0
1,510
I have ran mem test and it shows no issues at all with memory so that's why I'm so confused. I also am not OC-ing and have never OC'd. I'm going to reboot in Safemode and run that cmd prompt.
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Hmmm How about your RAM settings. Can you back your RAM speed off a little? Those errors you showed up above definitely have the telltale signs of corruption of sorts. Have you ran MBAM? Malware Bytes Anti-Malware? to see if you have anything going on? How about using Process Explorer to just see what's going on in your system. Doing a boot trace in Procmon might help shed some light on things too.
 

Matthew_81

Commendable
Apr 30, 2016
6
0
1,510
I tried backing RAM speeds off a little. Also borrowed my friends RAM and tried that, problem still happening even with swapped RAM. I've ran MBAM and it detects no signs of anything. I just keep getting BSOD. I also did another fresh install of windows from disc, still no luck.
 

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Could you possibly re-install after changing your HD settings in BIOS to be IDE instead of AHCI? Just to rule that one little aspect of drivers / bad hardware out? At this point you are really getting into the realm of hardware going bad.