computer problems

goingganzo

well guys i have a computer problem that my new comp 2 months old will boot up then less than 1 min later will die aka frese. my network card was giveing me blue screen of death sence i bult it

my system consists of
asus an8 sli premoum
msi 7800 gt sli dual setup
amd 64 3800
2 gig cosar 2-3-3-6
antec super alumi bou
with a 430 antec true power 2.0


what would be best thing to look at?

i am thinking eather power suply or network card or i fried the os with allmost 40 blue screen of death

Sami

What does the BSOD say?

Mike682

In my experience, Antec makes excellent power supplies that last a long time. If it was the power supply, most times the system would just shut off or restart with no prior warning.

Since you stated an issue with the network card, I would first take out the nic card and boot up. See if it runs stable.

Mazeroth

That is a very small power supply for your system, however, if you're not gaming when it's freezing I doubt that's the problem.

Go over to www.anandtech.com and go to the General Hardware forum. LOTS of intelligent computer guys over there that can help you out, much better than an audio forum can.

michael_w

Try and boot it in safe mode and see if it freezes still. That way you'll know whether it's a hardware problem or not. This is asuming you have tried swapping out the network card and are still having problems.

goingganzo

i am thinking it is the mobo the bsod is for the network card the 64 bit prossor dont like the network card or the mo bo dont like it or the network card is dieing. i took everything out but the ps mobo and 1 vid card and the hd and it is still craping out

SCompRacer

goingganzo wrote:

i took everything out but the ps mobo and 1 vid card and the hd and it is still craping out

That include trying different memory sticks?

Sami

SCompRacer wrote:

That include trying different memory sticks?

Well, running memtest86 would be a better option IMO. Even if there aren't any problems it is good to run memory test. (actually, a must in my book)

SCompRacer

You say to-ma-to, I say tom-a-to..... I've done it both ways. I was never one for mem testing everything. Put a first person shooter up and that finds weak links real fast. But I don't do that anymore.

McLoki

I would blame memory or drivers. Make sure you have the latest drivers loaded for all your hardware. (All motherboard drivers, video card, Nic Card, etc.)

If you have multiple memory sticks in the machine, pull 1/2 of them, see if it dies. If it does, pull the other 1/2 and put the first 1/2 back in. see if it dies again.

The drivers are always suspect in a new machine, but it sounds like it may be memory to me.

Michael

goingganzo

thanks guys i do have memory laying around i can try. but i custom set up the mob and will have to re set the cas timeing for the other memory.

i have seen aot of things but this a first for this. i do have the latest drivers for everything. but the thing that gets me is the starting up shut off and it wont start up for a while? it wont even display anything. i had a mem slot problem on a mobo and this is nothing like it.

Mike682

Setting the ram's latency incorrectly in the BIOS (bumping it up or overclocking) can cause problems like you have. What is the mem rated at? Did you try to adjust the timing to the Ram's rated specs? (ex. CL to 2.5)

goingganzo wrote:

thanks guys i do have memory laying around i can try. but i custom set up the mob and will have to re set the cas timeing for the other memory.

i have seen aot of things but this a first for this. i do have the latest drivers for everything. but the thing that gets me is the starting up shut off and it wont start up for a while? it wont even display anything. i had a mem slot problem on a mobo and this is nothing like it.

bobman1235

If you're setting your own RAS/CAS settings on memory that could easily cause frequent and random BSODs. I wouldn't mess with those settings unless you know EXACTLY what you're doing. While I hate to dobut your computer proficiency, you really have no reason to be messing aroudn with memory speed settings aside from sheer tinkering factor, but you hav eto expect some ramifications.

Really sounds like a motherboard or memory problem though. But the most obvious solution to start with seems to be reinstalling the OS from scratch. That would eliminate almost any kind of driver conflict or software issue.

Sami

SCompRacer wrote:

You say to-ma-to, I say tom-a-to..... I've done it both ways. I was never one for mem testing everything. Put a first person shooter up and that finds weak links real fast. But I don't do that anymore.

People experience "random" crashes and can't figure out why because they can't reproduce them. Most of the time it's a memory issue, they haven't tested it. Even if the computer runs "fine" sometimes they lose important data to corruption. Why? Again, memory. Computer runs but those incorrect memory addresses cause unpredictable behaviour once in a while. IMO (maybe I'm biased because I'm a software engineer) memory needs to be tested every time a system is installed, and preferably frequently after that as well. It is the most critical part of your system.

mrbigbluelight

to kill the memory, (J1), put a fresh battery in, and give 'er a whirl.

Depending on your MOBO, this might help you. The above is a trick for a PcChips MOBO I got a while back off of NewEgg. It was going for real cheap, and the question raised on Newegg was: "How come so cheap ?".
The answer was the cmos battery on 90% of the MOBO's were crappy and by the time the end-user got the MOBO installed, BSOD were in bloom.

May not help, probably won't help, but having a fresh battery for $3.50 isn't going to kill you.

SCompRacer

Sami wrote:

People experience "random" crashes and can't figure out why because they can't reproduce them. Most of the time it's a memory issue, they haven't tested it. Even if the computer runs "fine" sometimes they lose important data to corruption. Why? Again, memory. Computer runs but those incorrect memory addresses cause unpredictable behaviour once in a while. IMO (maybe I'm biased because I'm a software engineer) memory needs to be tested every time a system is installed, and preferably frequently after that as well. It is the most critical part of your system.

Then do it Sami, the biased software engineer. But when you get a PC crashing right off the bat how the hell are you gonna run mem test? Swap out memory and leave the BIOS set to default.

goingganzo wrote:

boot up then less than 1 min later will die aka frese.

It wasn't a bad suggestion by a gearhead so just concentrate on helping gonzo.

Sami

SCompRacer wrote:

But when you get a PC crashing right off the bat how the hell are you gonna run mem test?

He's getting BSOD...

Anyways, just saying to run memtest even if the computer seems to run fine. If it isn't booting then it's time to swap the memory.