Help, random BSOD on new build

imported_Nap

Member
Oct 30, 2007
33
0
0
:frown:

Specs are Q6600, ABIT IP35-E, Antec P182, 4gigs Patriot (2x2gig), BFG 8800GT, and a Samsung Spinpoint 500GB. I am running Vista Ultimate x64 (I'm thinking this is the problem.) Everything is at stock speeds for the moment, and the BSOD seems pretty random, got it once so far just transferring stuff from an external HDD, once from playing Crysis, and once from just starting Windows. I really have no idea what is wrong, other than maybe x64 Vista is a piece. Please, any help?
 
Jun 4, 2005
19,723
1
0
Mem test. If you get an error, pop one stick out and try again. If no error, replace with the other stick and try again.

Alternatively, you could boot up a linux live CD and stress test that way (not sure if it'll test the hard drive), but I've never actually stressed off a LiveCD so I can't say if it'll work or not.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
Am currently running memtest and so far it's popped up with 10 errors. All were right in a row. Should I just stop the test now and try one stick at a time? I am guessing I'm going to have to RMA this now? How can I even go about this if I already mailed in my UPC from the packaging for a rebate?

Figures the only "Made in the USA" computer component I have ever bought is the only one to have ever failed on me.
 
Jun 4, 2005
19,723
1
0
Yep. Might as well stop now and try a different stick.

You *should* be able to RMA it without the UPC, but you'll have to contact them and mention it first.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
Alright I've been running memtest with only a stick in the first dimm slot. It's made it through one pass with no errors. Is it okay to stop now or should I keep going? And if so for how long? I suppose after this there is no use of putting the other stick back in and just trying it with that one alone.
 
Jun 4, 2005
19,723
1
0
The first one is fucked. An error is an error.

Run the good one through as long as you can (a few hours should be alright), run it overnight if you must.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
K so the first one is screwed but WTF is going on now? The RAM was going on it's 2nd pass and how it's stopped at 18%. Everything else seems to be going normal but now it's hung up on this one spot... This is getting ridiculous. All this in addition to my noisy as hell CPU fan and my clicking DVD drive. :(
 
Jun 4, 2005
19,723
1
0
Just let it keep going. Do you know anyone who might have compatible ram you could test with? Hell, it could be a motherboard problem (definitely not something I'm at all familiar with).

Make sure to switch slots if this one fails too.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
I stopped the test but I will restart it before I go to bed. I know one other person with compatible RAM, but I too am not sure what is up with the whole thing. If it is a motherboard problem how will I be able to tell? Edit: You said to change spots if this one fails. Could the reason the other one failed be the slot too? Or is that one just flat out screwed?
 
Jun 4, 2005
19,723
1
0
Originally posted by: Nap
I stopped the test but I will restart it before I go to bed. I know one other person with compatible RAM, but I too am not sure what is up with the whole thing. If it is a motherboard problem how will I be able to tell?

You'll be able to tell if his ram also fails on your motherboard, or if your ram checks on his.

EDIT: Saw your edit, well, the problem with computers is that any piece of hardware can cause the most unexpected errors. The only way to figure it out would be trial and error.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
I already made a thread about my system BSODing. I ran memtest and found one of the modules was faulty. Now today when I got home I went and popped in the "bad" module just to make sure it was bad and it wasn't the slot it was in (trying a new slot). The night before I was running with the "good" stick and played Crysis for quite a while, all stably and without issue. So when I go to start the system up after putting in the bad RAM and taking out the good one, the computer starts up, everything appears to be working, all fans are going etc. but there is nothing displayed on the screen. I figured this RAM was really screwed up so I tried the other one. Same result. I even tried it using two different monitors. Is something else fucked up now? Please help, this blows hard. This was only my second build so I could have made some really stupid mistake so mention anything that comes to mind.

In addition, I've noticed that when I boot up the computer (this also happened while I the computer was working though so probably not related) that the computer would start up, nothing would be displayed, about 3 seconds later it would shut off, then start right back up again and work this time. Of course it doesn't even work at all anymore. PLEASE offer some advice this thing is really getting on my nerves.

Specs are
ABIT IP35-E
Q6600
4gigs (2x2gig) Patriot DDR2
Corsair 520W
Antec P180
Samsung Spinpoint 500gb
EDIT: Forgot 8800GT
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Thread title edited to remove foul language, since Forum guidelines do not allow foul language in thread titles or summaries.

AnandTech Moderator
mechBgon
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
Originally posted by: Nap
Heh I apologize for the language I am just a bit frustrated right now. ;)

Understandably :D Have you tried boosting the memory voltage a little? Sometimes that can help the RAM run stable. Try maybe 2.7 volts?

 

Agamar

Golden Member
Oct 9, 1999
1,334
0
0
What hard drives are you using... It could be a power issue. I know I can cause a similiar problem with dual raptors in a PC that has a weak power supply.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
I would try boosting the memory voltage but the problem is I cannot see anything. I suppose the system is technically "posting" since it is running (I didn't have a mobo speaker hookup for some reason...) I cannot even get into the BIOS. The computer just sits there with all the fans running, seemingly normal but there is no image diplayed. As for the harddrive it's only one Samsung Spinpoint 500gig, and I doubt that's the problem because I had the system up and running OK just a day earlier. Plus, as far as I know the Corsair 520W is a pretty good PSU. Hopefully this just turns out to be some stupid mistake but I for the life of me can't figure it out.

Edit: I should probably mention I have reset the CMOS to no avail.
 

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
Unplug the computer from the wall, pull the CMOS battery and let it sit for 5 minutes. Put in the one good ram stick, put the CMOS battery back in, plug it in and try and reboot.
 

imported_Nap

Member
Oct 30, 2007
33
0
0
Crossing my fingers and trying the CMOS battery... Only problem is I forgot which was the good stick of RAM cause I figured what the hell and tried to use them both... :confused:
 

imported_Nap

Member
Oct 30, 2007
33
0
0
It appears to be working again. I had used the wrong PCI-E connector on the 8800, I guess it has to be plugged into 2 molex connectors. The one stick of RAM is still screwed though and I can't even get past post with it in. :(
 

GuitarDaddy

Lifer
Nov 9, 2004
11,465
1
0
Have you updated to the latest bios? Some boards need a bios update to play nice with 2gb sticks.

But it does sound like you have a bad stick, RMA it ASAP
 

imported_Nap

Member
Oct 30, 2007
33
0
0
I've already made a couple threads on problems I've been having with this new build. Initially, for about a day the computer seemed to work great. Then around the 2nd day I started getting BSOD and just general crashes all the time. So I ran memtest, got something like 60 errors with my memory. Ok, so that was definitely screwed, but while I waited to get a replacement I was still using my computer for internet, word, etc. It wouldn't USUALLY crash under these circumstances (I say usually because it did once I think, but otherwise it was all when I was trying to play Crysis.) After this the system would come on, all the fans going etc., but no image would be displayed on the screen. Sorted this out, or so I thought because I had my 8800GT plugged in with the wrong connector. So now here I am and of course it's still unstable, it crashed another couple times today, and now it just doesn't turn on period. The fans don't even come on. I really don't know what to think now... Could this be a motherboard problem? Is there something similar to memtest for motherboards? Any response is appreciated because I am about ready to just chuck this thing out of the window.

Specs are: Q6600, ABIT IP35-E, BFG 8800GT, 4gigs (2x2) Patriot DDR2, Corsair 520W, Antec P182.

EDIT: Ok so I looked in the computer and apparently I had plugged a firewire port into what was supposed to be a USB hookup. Unplugged this and the computer booted fine, and it "runs" all fans spinning and the harddrive running and what not, but now I am not even getting an image on the monitor again... I'm guessing I got a FUBARed video card and RAM? Pretty shit luck. :(
 

MarcVenice

Moderator Emeritus <br>
Apr 2, 2007
5,664
0
0
Try removing one stick of ram at a time. Start eliminating factors, like the videocard for example, remove it and see what happens. Do you have a spare PSU that you could try ?
 

imported_Nap

Member
Oct 30, 2007
33
0
0
No spare PSU though I did try to remove one stick of RAM at a time as you said and one was full of errors in memtest the other I couldn't tell because the computer just stopped displaying anything but was still running (Like I said I think this is sorted now because I had the vid card plugged in wrong.) But even if I did have a bad part, like say RAM or a video card, the system would still probably at least start right? In its current state I just push the power button and nothing happens. It's worth noting like I did in my other threads, that since I have had the computer running even when it was relatively stable, the computer would start up, stay on for about 3 seconds with nothing displayed, turn off, then turn right back on again and act as it usually should, booting up in Windows, etc.