BSOD - I need help!!

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
:Q

I posted my original problem in the Software For Windows section:
Firefox 2.0.0.12 Issues

Now I've had 3 BSODs today.

:(

The first 2 crashed the system to reboot...but the last one just stayed blue.
I took a picture of it.

Can anyone help to tell me what this means?

Is my hardware being strained from my OC (keep in mind that I've been running my current configuration for several months now)??

Here is the BSOD:
BSOD

PS: I took the pic with a phone, sorry for the image quality.

:|
 

bailw

Platinum Member
Oct 30, 2005
2,309
0
76
Check your event viewer to see if you can get anything out of it. It could be software problem but it might be your system instability.
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
I tried that already and was not able to ascertain much.

My rig has been running at these settings for months. Anyway, I have backed my OC down to 2.8GHz (400x7) and running memory now at stock. I'll see if I happens again. I'm kinda worried though.

:(
 

Duvie

Elite Member
Feb 5, 2001
16,215
0
71
I haven't much luck with gskill of late...I suspect perhaps the memory...hold the 430fsb and clock speed and drop the ram multi and see if that cures your BSOD....

Perhaps run memtest as well....Gskill PC2-6400 at 860ddr and only 1.9v? Seems a bit low with my experience...
 

Duvie

Elite Member
Feb 5, 2001
16,215
0
71
I like the idea in one of them to disable the C1E halt state in the bios...I usually do in my ocing of C2D's...
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
Thanks guys.

I'll have to go through those in detail.

Keep in mind that I'm still running my Gigabyte GA-965P-DS3 (Rev. 3.3, F10).
 

Xvys

Senior member
Aug 25, 2006
202
0
0
It seems more often than not, when you get BSOD after the system has been runnig, that it is a memory problem. Usually either not enough ram voltage or too tight of timings in relation to the ram voltage. Running 4 sticks of ram in P965 mb's is sometimes problematic, and more ram voltage, say 2.0 or 2.1v might help stablize your system.
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
Originally posted by: Xvys
It seems more often than not, when you get BSOD after the system has been runnig, that it is a memory problem. Usually either not enough ram voltage or too tight of timings in relation to the ram voltage. Running 4 sticks of ram in P965 mb's is sometimes problematic, and more ram voltage, say 2.0 or 2.1v might help stablize your system.

Thanks for your input but I'm only running 2 sticks of RAM.

They are rated to run @ 800MHz with 1.8V - 1.9V.

I have run them stably as high as 1000 with 2.0V.

So...

Running them @ 860 with 1.9V in my opinion, should be more than enough.

My rig has had these settings (see sig) for months now. The only new change is the memory and they have been tested and have proven to be fine.

So...

I'm starting to think that I have a software issue.


NOTE: It hasn't given me a BSOD since the screenshot I posted last night.
 

myocardia

Diamond Member
Jun 21, 2003
9,291
30
91
How long has it been since you changed your video card's driver, Cheex? If it was fairly recently, that would be the first thing I would look into.
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,103
16,016
136
As Duvie says, I agree. I have RMA'ed 3 pairs of sticks with Gskill in the last 2 months. I see you are running 1.9 vdimm. Is that mfg spec ? if so, and you run it@400, you should be OK. try a memtest boot disk, and run for an hour.
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
Originally posted by: myocardia
How long has it been since you changed your video card's driver, Cheex? If it was fairly recently, that would be the first thing I would look into.

Well, I'm still using Forceware 169.25 WHQL for Vista x64.
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
Originally posted by: Markfw900
As Duvie says, I agree. I have RMA'ed 3 pairs of sticks with Gskill in the last 2 months. I see you are running 1.9 vdimm. Is that mfg spec ? if so, and you run it@400, you should be OK. try a memtest boot disk, and run for an hour.

As I said my memory has been stable @ 1000 with 2.0V but...

I'm not gonna be foolhardy. I'll take your advice and run Memtest for an hour.

(Arnold voice) I'll be back.
 

Build it Myself

Senior member
Oct 24, 2007
333
0
0
I remember hearing, and for the life of me i can't find out where, that people had those BSOD issues with firefox, but i'm looking and i can't find out where or why. I think it had something to do with video not working properly, but i'll keep looking into it, maybe something will turn up, try googling the "STOP:" #'s and the word firefox and try to find something...

Yeah, I found something, you're not the only one it seems, i'm having an issue with this code too, it's something with Nvidia and firefox...

https://forums.microsoft.com/t...=7&ft=11&tf=0&pageid=4

there are many others, but you get the idea.
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,103
16,016
136
Originally posted by: Cheex
Originally posted by: Markfw900
As Duvie says, I agree. I have RMA'ed 3 pairs of sticks with Gskill in the last 2 months. I see you are running 1.9 vdimm. Is that mfg spec ? if so, and you run it@400, you should be OK. try a memtest boot disk, and run for an hour.

As I said my memory has been stable @ 1000 with 2.0V but...

I'm not gonna be foolhardy. I'll take your advice and run Memtest for an hour.

(Arnold voice) I'll be back.

I am just trying to eliminate a possibility. I had stable systems for months, then they wouldn;t even boot. It was bad memory. I couldn;t believe it. I also had a set of Ballistix die on me also.
 

Cheex

Diamond Member
Jul 18, 2006
3,123
0
0
Originally posted by: Markfw900
Originally posted by: Cheex
Originally posted by: Markfw900
As Duvie says, I agree. I have RMA'ed 3 pairs of sticks with Gskill in the last 2 months. I see you are running 1.9 vdimm. Is that mfg spec ? if so, and you run it@400, you should be OK. try a memtest boot disk, and run for an hour.

As I said my memory has been stable @ 1000 with 2.0V but...

I'm not gonna be foolhardy. I'll take your advice and run Memtest for an hour.

(Arnold voice) I'll be back.

I am just trying to eliminate a possibility. I had stable systems for months, then they wouldn;t even boot. It was bad memory. I couldn;t believe it. I also had a set of Ballistix die on me also.

No no no...Don't get me wrong!!

I hope you didn't take any offense to anything I said...I was not meant to be.



On a lighter note:
I ran Memtest for about 1 hour and 10 minutes with the memory at the stock 800 with 1.8V...
The stock range is from 1.8V - 1.9V so...
I'm thinking that my memory is okay...I could be wrong though...I hope I'm right...:p
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,103
16,016
136
OK, so with the same voltage and memory, run the cpu at 2800 then, see what happens.

I didn;t take offense to anything, just trying to help....
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
27,103
16,016
136
Well, then you should be able to run the cpu@ that speed. (memory speed)
 

n7

Elite Member
Jan 4, 2004
21,281
4
81
I don't like Memtest for setups with lots of RAM anymore, since it takes too long to find errors, if it even does.

Try HCI Memtest in Windows as an alternative.

That being said, it doesn't seem like RAM is the issue in your case Cheex.
 

lopri

Elite Member
Jul 27, 2002
13,310
687
126
How long did it take to finish one loop with 8GB, n7? I think it took like an hour and a half with my setup. (8 loops in about 12 hours)
 

JustaGeek

Platinum Member
Jan 27, 2007
2,827
0
71
Originally posted by: Cheex
Yeah. I honestly am thinking software issue.

Should I reload...again??

I wouldn't worry about it too much, Cheex, unless it happens on a regular basis.

I was getting a few of those in the begginning after installing my Ultimate x64. It was almost always a software issue (Defender clashing with Norton clashing with Riva Tuner clashing with the SuperAntiSpyware etc.).

Also, it would happen on "wake-up" from sleep, but after enabling +5VSB it does not happen again.

Do not re-install it. Let the Vista "settle down" on your system, you'll learn what program might be causing it, or other possible software/hardware issues.