New computer getting BSOD. Need help.

ltommylel

Reputable
Oct 29, 2015
8
0
4,510
Specs:
i5 4690
hyper cooler 212
gigabyte z97x gaming 7 mobo
gigabyte gtx 960 OC 4gb
corsair vengeance 8gm RAM
crucial 250 gb SSD
WD 1TB HDD
cosair rm850w

My new build computer is getting a random BSOD. I fired up the computer and everything seemed to be fine until installed the software for the GPU. From that point on, the PC was only able to run for a few minutes before greatly slowing down until it turned into the BSOD(1).

I removed the GPU and all software with it and used the onboard graphics. Same issue occurs, PC ran for a few minutes then shut down with another BSOD(2). At this point i might be thinking its the RAM, but can someone guide me through this? First time builder.

BSOD(1)
==================================================
Dump File : 102915-4305-01.dmp
Crash Time : 10/29/2015 12:32:29 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0da43b30
Parameter 3 : fffffa80`0da43e10
Parameter 4 : fffff800`033865d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102915-4305-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 282,160
Dump File Time : 10/29/2015 12:33:04 PM
==================================================


BSOD(2)

==================================================
Dump File : 103015-4383-01.dmp
Crash Time : 10/30/2015 2:40:48 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0ccc64f0
Parameter 3 : fffffa80`0ccc67d0
Parameter 4 : fffff800`0278e5d0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Crash Address : ntoskrnl.exe+70740
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\103015-4383-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 272,632
Dump File Time : 10/30/2015 2:48:37 AM
==================================================

EDIT: ran chkdsk and the volume is clean..

EDIT!: Did a full clean install of OS. The same BSOD as above still appeared the first time. Every boot from this point on just freezes at the windows startup. No more BSOD but the screen is completely frozen and it shuts down completely after.
 
dont rule out cpu..of course your not overclocking right or were you overclocking? everything was set back to default in the bios right..hows the temps? no overheating? download real temps check if you can stay on long enough without the bsod...
my first build i put too much thermal paste on and had a similiar situation. i reapplied the evo 212 and all was good.
food for thought
ps also did you save your comp before you upgraded bios and stuff. i learned to do that..if you did try a restore. if all else fails reinstall OS if you can rule out all the parts are working fine cpu/ram
 
No over clocking is done. Hmm.. Thermal paste does sound like a very plausible issue. I bought new RAM to try and troubleshoot it. And the computer ran for a record of 30 minutes! Within that time I did furmark test for about 5 min and did prime95 for about 10. Nothing seemed to be wrong. So I stopped testing

And then I went on YouTube and it bsod after I pressed play. WHATTTTTT?????????

 
hmm maybe take the evo off and reapply see if that helps..also goto bios and see if your cpu temp can be seen if its around 20c to 30c...idle....stay in bios see if it goes up...might just be a cpu thermal paste issue. goodluck ...i know its frustrating..hang in there its well worth it and feels great to get it done
make sure you know to clean it right with the high content alcohol..qtips etc..watch a quick vid. :)
 
from my experience and its not exstensive bsod is mainly a not enough power or voltage issue..or a shutdown from too much heat. have you checked your temps on bios?
as a last resort try taking off evo, take out the chip look at it and the pins on mobo, clean it properly..make sure your build and mobo is secured down on the motherboard pins in the case proper grounding and all that. make sure the evos bracket is properly fastened. reapply the paste and put it back in.im betting its a cpu thing. maybe a bad cpu.
i cant answer the ssd question as ive never had issues with them and dont know problems they can cause.
trace steps back..after you had it booted up...how long till the first bsod..you said when you installed gpu, but was that like mere minutes and the gpu and driver install mught be coincidental.
dont rule out a power supp issue either and or connectivity issue..double check all wires and make sure they are right. what

 
So what I've done as of now...

1) replaced psu. Same issue.
2) took Evo 212 off. Reapplied artic silver 5. Temp in bios sits around 38 to 40c. 31 to 35c in HWmonitor in Windows until it crashes.
3) took out cmos battery hopefully to reset bios. No results same BSOD.
3)replace ram and set to 1600mhz 10-10-10-27. It was originally on 1333 9 9 9 24. No bsod but computer completely freezes and then shuts down..

I have a new SSD coming in to trouble shoot that tmrw. Thus has been a very frustrating battle lol
 
do you have anyones cpu you can use to put it in your system and see if that solves it?
could be the SSD...make another post of this issue under ssd/harddrive and see if anyone can help.

let me know when you fix it and what solves it ok im curious. if i had to bet at this point id say cpu is defective. i cant see mobo being issue, maybe SSD, but all else you ruled out. good luck
 
Alright guys. It looks like I was able to get this working now. I'm typing this on my new computer now as we speak. I got a new SSD and was able to install all the correct drivers(graphics,mobo drivers, wireless adapter etc) and so far no BSOD.

I came to realize that the problem could be one or both of the following:

1) bad SSD
2) corrupted tp-link WDN4800

1) Reason I believe bad SSD could of been one of the issues is because switching out to a new SSD solved this issue or so it seems. Now on to #2 where the mystery is..

2) Right after I installed the OS onto the new SSD, the next driver I was trying to update was the TP LINK WDN4800. I had the driver saved on my external hard drive. I ran it with the old SSD and it installed without a problem but down the line the computer started freezing, getting the BSOD above and eventually it wouldn't even boot into the windows anymore, it would just get stuck at the start up screen.

When I tried to run the drivers on the new SSD, the same BSOD appeared and thats when I began to notice a bit of a trend...Somehow these driver files and BSOD were connected. So I went to download new drivers off the website and ran those. After a rough but successful installing phase of the wireless adapter...Here I am typing my story to you guys. Which makes me think...maybe the hardware wasn't the problem this whole time and it was just bad drivers that caused all the bluescreen.

I still have my old memory that I thought was corrupted but im about to stick it back in to see if its actually functional.

Any thoughts where the main problem is?

EDIT: old memory is still functional.
 
now your really isolating the issue and all you can do now is test another cpu in your system. just be sure.i know nothing of driver issues and i dont know why know one is writing here for you but id say its gotta be a defective cpu. or a motherboard issue distributing voltage and such. too much/not enough. or a driver issue. id you try a different power supply too that could be a culprit too. although idk. keep posting and update . good luck move this post under systems maybe someone will hit on it.
HOLD on a sec, can you get back to windows after this? if yes check the error code number or reference, check your reliability monitor and see the exact cause ok
 


So far right now there seems to be no BSOD. But if another shows up I will definitely swap out the CPU. Another thing to note, when I changed out the SSD, I noticed the wire a bit damaged and changed it to a new one. I've read somewhere else that a faulty wire could also be the cause of certain BSOD... so... It might be worth noting lol.

 
absolutly a faulty wire or bad connectivity somewhere is almost certain a bsod issue.
did you find out what the exact bsod reason was? like checking event log and/or reliability monitor after it happens to see what caused the freeze or shutdown?
 
As an update, It no longer blue screens when im trying to browse..but rather blue screens when im playing tera and only tera. First session i played, 2 hours no problem. Then for some reason today I tried playing again and it blue screens to CRITICAL_OBJECT_TERMINATION. the same exact BSOD I had an issue with weeks ago. I'm truly stumped.