• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Unexplained BSODs

Status
Not open for further replies.
G

gmreplay

Weaksauce
Joined
Dec 27, 2010
Messages
92
My system
6950 unlocked with 6970 BIOS
2600k OC'd to 4.6 GHz
8gb Gskill Ripjaw
PSU - Corsair CMPSU-650TX 650W
Asus P8P67 Pro mobo

I've been getting periodic BSODs for a few weeks now, and I just can't pin down the cause. I've stress tested my GPU, CPU and ram separately using Furmark, IntelBurnTest and Memtest for 4-12 hours each with no problems whatsoever.

The blue screens occur randomly, and seem to have no connection to what I'm doing. I'll get them gaming in Fallout:New Vegas and Starcraft 2, but also while simply browsing the internet and hardly taxing the system. They probably occur at a rate of 2-5 a week.

If it was a problem with my PSU or overclocks I would assume that they would fail under stress, not just any old time. What can I test next to get me closer to the problem?
 
Last edited:
What about your hard drive?

Have you tried turning the 6950 back to a 6950?
 
What do the blue screens say? They will say what caused it about 4/5 of the way down the screen. If you don't remember, there are freeware programs that will pull the dumps created by your BSODs and display them for you. That should make it easier to pinpoint what driver is causing the problem.

Quick Google search found [ame="http://download.cnet.com/BlueScreenView/3000-2094_4-10965136.html...I"]BlueScreenView - Free software downloads and software reviews - CNET Download.com[/ame] actually used that one in the past, and it was actually quite helpful. I couldn't figure out what was causing random blue screens after I built a PC. It ended up being a USB wireless receiver that I was temporarily using.


edit: I have no idea why the link is showing up like that....I even tried it w/o using the code lol.
 
Danny Bui said:
What about your hard drive?

Have you tried turning the 6950 back to a 6950?
Click to expand...

WD 1TB Caviar Black. Seems to be in good condition.

The BSODs say

KMODE_EXCEPTION_NOT_HANDLED
0x0000001e

Caused by driver: e1c62x64.sys
Crash address: ntoskrnl.exe+7fcd0

Some also report as
Caused by driver: ntoskrnl.exe
or
Caused by driver: tcpip.sys

That covers all of the BSODs I've had this month and last (13 of them recorded).
 
Are there any USB devices connected to that PC other than the mouse and keyboard?

Try updating the NIC driver as well. What mobo do you have BTW?

Have you tried setting the CPU back to stock and using the system at stock speeds for a long period of time?
 
Danny Bui said:
Are there any USB devices connected to that PC other than the mouse and keyboard?

Try updating the NIC driver as well. What mobo do you have BTW?

Have you tried setting the CPU back to stock and using the system at stock speeds for a long period of time?
Click to expand...

Occasionally I have a flash drive or logitech quickcam attached, but they haven't been during most of the BSODs.

I haven't updated the NIC driver. Not even sure where to look to find an updated driver actually.

I haven't tried un-OCing the cpu.
 
gmreplay said:
I haven't updated the NIC driver. Not even sure where to look to find an updated driver actually.
Click to expand...
Find out the maker of the NIC.
Go to that maker's website
?????
Profit
gmreplay said:
I haven't tried un-OCing the cpu.
Click to expand...

Well do so. There's a possibility that the motherboard or other onboard devices can't handle the OC.
 
Danny Bui said:
Find out the maker of the NIC.
Go to that maker's website
?????
Profit
Click to expand...

I'm embarrassed to admit this but I don't even know how to find out the maker. I've never dealt with my NIC, and frankly I don't even know exactly what it does.
 
gmreplay said:
I'm embarrassed to admit this but I don't even know how to find out the maker. I've never dealt with my NIC, and frankly I don't even know exactly what it does.
Click to expand...

NIC = Network Interface Controller or basically the Ethernet controller. Effectively one of those most important item to have on PC if you want internet connectivity, It's basically the LAN port on your motherboard.

Go to your motherboard's (which you havn't told us BTW) manufacturer's webpage for that motherboard. Look up the specs for your motherboard. They should list what NIC you have. It's usually a Realtek.
 
OC has been disabled. No blue screens so far. Will report back in soon to see how it turns out.

If it does turn out to be the OC, any suggestions on why and how to fix it? Whenenever i've had an unstable OC in the past it was because my voltage wasn't high enough or the overlock was too high, and it crashed under load. These BSODs happen as often when the computer isn't being taxed as when it is.
 
Danny Bui said:
NIC = Network Interface Controller or basically the Ethernet controller. Effectively one of those most important item to have on PC if you want internet connectivity, It's basically the LAN port on your motherboard.

Go to your motherboard's (which you havn't told us BTW) manufacturer's webpage for that motherboard. Look up the specs for your motherboard. They should list what NIC you have. It's usually a Realtek.
Click to expand...

I edited my mobo into the original post. It's an Asus P8P67 Pro. Thank you.
 
gmreplay said:
I edited my mobo into the original post. It's an Asus P8P67 Pro. Thank you.
Click to expand...

You see, if you had mentioned that, this thread would have been a lot shorter: It's probably your mobo. That particular model had above average failure/defect rates judging from all those threads about it over in the motherboard subforums.

So I'd RMA that mobo once you know for sure that the OC isn't causing the issues. Maybe a week without a BSOD is a good sign that the OC was the cause.
 
Try updating your mobo drivers to see if it clears it if you can't get a RMA (like Bios Updates, Chip sets, everything)
 
gmreplay said:
OC has been disabled. No blue screens so far. Will report back in soon to see how it turns out.

If it does turn out to be the OC, any suggestions on why and how to fix it? Whenenever i've had an unstable OC in the past it was because my voltage wasn't high enough or the overlock was too high, and it crashed under load. These BSODs happen as often when the computer isn't being taxed as when it is.
Click to expand...

Thats great to hear. that 4.6gig oc is impressive but my first thought was that you were reaching the upper threshold of somthing.

Run it for a couple days and report back. If there are no issues then try a mild oc and run it for a couple days.

Lather, rinse repeat until you find a nice blend of oc and stability.
 
Sorry to bump an old thread but I'm having the same issues as OP and I need some help. Not overclocked so that shouldn't be a problem. I also have an ASUS mobo, could it be dying? I just built this system a few months ago.

Mxcl0.png
 
Make your own thread. Just because you have the same symptoms doesn't mean you ave the same cause. Thread locked.
 
Status
Not open for further replies.
Back
Top