• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

BSOD at random times in the last 4 days - Help pls

Joined
Dec 30, 2010
Messages
1,221 (0.23/day)
Location
Canada
System Name Brutus
Processor i5 4690k @4.7Ghz (Watercooled)
Motherboard z97 MSI Gaming 5
Cooling NZXT Kraken x61 AIO watercooler
Memory Gskill Ripjaws 8gb (2x4gb) 1600mhz 7-8-7-24
Video Card(s) MSI Gaming GTX 980ti x2 (sli)
Storage 1 SSD 64GB (OS) + 2x500GB WesternDigital RAID 0
Display(s) YAMAKASI Catleap q270 SE 27inch Glossy 2560x1440
Case NZXT Phantom
Audio Device(s) ASUS Xonar DX
Power Supply Antec TPQ 1200w
Software Windows 7 (64 bit)
Hi, I have started getting BSODs twice a day at random moments on my computer in the last 4 days. I've tried to figure out the reason for the BSODs but I'm not sure.

I often get the * Hardware failure * bsod. Now I know these can be caused by a number of things, so that is why I included with this post the SF Diagnostic Tool zip attachement so you can help me figure this out.

I consider my knowledge of computers (overclocking, hardware maintenance and debugging) at a decent level, so it shouldn't take much help before we fix this. I just need someone to point me in the right direction.
 

Attachments

Hi, I have started getting BSODs twice a day at random moments on my computer in the last 4 days. I've tried to figure out the reason for the BSODs but I'm not sure.

I often get the * Hardware failure * bsod. Now I know these can be caused by a number of things, so that is why I included with this post the SF Diagnostic Tool zip attachement so you can help me figure this out.

I consider my knowledge of computers (overclocking, hardware maintenance and debugging) at a decent level, so it shouldn't take much help before we fix this. I just need someone to point me in the right direction.

ur attachment wont really help. Just try to remove hardware and replace with old parts. Or for ram take a stick out and try it and try the other.
 
isn't there a log file I can look at to see what's the culprit?

I don't wanna spend the next 3 days testing each and every hardware piece, toying with settings and whatnot when I could have made my life easier by gaining important knowledge to help me get to the fix
 
It would be easiest to provide an error code. You can use this program for easy access. Or use the Event Viewer and look at the criticals.
 
Run memtest86
 
Here's what you asked for:

==================================================
Dump File : 080912-10561-01.dmp
Crash Time : 09/08/2012 10:32:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71ed0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71ed0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080912-10561-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 275,664
==================================================

==================================================
Dump File : 080712-10155-01.dmp
Crash Time : 07/08/2012 9:31:50 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000040
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02e882d2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080712-10155-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
==================================================
 
Whats the brand of you OS SSD?
 
Remove your overclock, tell us if that fixes it
 
My ssd is a kingston 64gb... I only use it to put windows 7 OS on it...

As for my overclock, it's been running for 2 years now... don't see how that's gonna change anything... but I will try it...

Can you guys determine anything by lookin at the .dmp file I copied earlier ?
 
how can I run memtest without a CD? I don't have CDs right now to boot from
and appearantly I can make a USB drive... but ONLY using linux...
 
no but I did install something similar called "virtual clone drive"... u think that could be the culprit?

because (I'm not 100% sure about this tho) I think I started having BSODs before installing virtual clone drive

I think its software personally.
 
Is the "Windows Memory Diagnostic" any good at detecting RAM problems?
 
Is the "Windows Memory Diagnostic" any good at detecting RAM problems?

Memtest for about 6 loops is enough to find something that will make you BSOD like you are. But I really think its software. Does it BSOD in safe mode?
 
I'm waiting for the next BSOD right now lol... I usually get 1 or 2 every day in the last 4 days
 
I just had another BSOD, of the same type... "hardware failure"...

While playing Asssassin's creed revelaitons... The 2 last I had, were while playing that game and "play catan" which is an online board game (on firefox)...

And I just did a CLEAN windows 7 re install... I'm so lost
 
Did you run Memtest86?
 
I don't have CDs to run it...
 
ok, not sure how to... I was told I can only do it with a flash drive if I have LINUX
 
What do you mean you don't have CDs? Go get some
 
flip the switch and run them as 6950s
 
just take a god damn stick of ram out and run it for a day and see if it bsods, and try the next day with just the other... That will tell you if its bad ram and which is bad
 
Back
Top