• 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.

Problems with rebooting on new system

K

Kruzen

Steve's a Dick
Joined
Jan 6, 2002
Messages
4,003
Helping my friend setup his new computer and everything..
we finished putting it together and its acting finnicky while installing everything

every once and awhile, with no warning, rhyme or reason. It reboots.

Abit IC7-Max3-G
Pentium 4 2.8C
1 gig Mushkin pc3200
two SATA WD 80gig 8mb sped ed's.
Saphire Radeon 9800 Pro
Audigy 2 ZS

Temps and voltages are perfectly within range (although, video card voltage is at 1.55 and i heard that it should be at 1.5.. if anyone else agrees, i may give this a shot)
 
HS installed correctly? Reseat your power leads to the board?

What kind of psu? Is it under or overvolting?

Take out vid and soundcards and try?

Test your memory?
 
well i had my friend run memtest.

he said it ran like 50% with no problem,s and then the last half of the test there was TONS of failures and shit.

i told him to try one stick of ram, see what it does, then swap it out.. see what it does, and report back.. if they are both fucked the ni guess we will try sending the ram back to newegg, maybe after trying some other dimm slots.

sound good to you guys? other suggestions?
 
Disable auto-reboot on system failure, its in the Startup & Recovery options in the Advanced tab of my computer properties
 
I'm his friend. I checked each ram stick seperately, and each one ended up having problems. does that mean they are fubar? or...

I heard on here that mushkin ram likes voltage, and in the ram specs, it says 1.5-1.75. I have it at 1.6 right now. Also, the cas latencies for the ram are 2-2-2. The defaults are set at 2.5-6-2-2. Could these things have anything to do with it?
 
Originally posted by chockomonkey
I'm his friend. I checked each ram stick seperately, and each one ended up having problems. does that mean they are fubar? or...

I heard on here that mushkin ram likes voltage, and in the ram specs, it says 1.5-1.75. I have it at 1.6 right now. Also, the cas latencies for the ram are 2-2-2. The defaults are set at 2.5-6-2-2. Could these things have anything to do with it?
Click to expand...

You mean 2.5-2-2-6? Try setting it to default specs and run it again.
 
well, i don't know... in the BIOS, when set to default, it appears as follows:

X - CAS Latency Time 2.5
X - Act to Precharge Delay 6
X - DRAM RAS# to CAS# Delay 2
X - DRAM RAS# Precharge 2

So yeah... whatever that means... and then the ram is suposedly 2-2-2.
 
Well, running it at looser timings than stock won't make errors worse, infact it will probably help reduce errors... So I doubt that's the/a problem...
 
Well, if the ram says that its cas latency is 2-2-2, then what are those settings i put above meant to be at?
 
Well, i ended up RMAing the ram to newegg and i just got the new stuff back. Upon runing memtest, i got 74 errors on the 5th test after running for an hour. Then, i ran memtest on 1 of the sticks, ran it for an hour, and recieved no erors, then on the other, where i recieved 354 errors on the 5th test.

Did i just get another stick of bad ram?
 
Originally posted by chockomonkey
Well, i ended up RMAing the ram to newegg and i just got the new stuff back. Upon runing memtest, i got 74 errors on the 5th test after running for an hour. Then, i ran memtest on 1 of the sticks, ran it for an hour, and recieved no erors, then on the other, where i recieved 354 errors on the 5th test.

Did i just get another stick of bad ram?
Click to expand...

did you use the same slot for each stick? after geting new ram and still getting errors i'd start looking into other components.

did you discharge any static by touching the chasis of the pc as it was plugged in before touching the ram?
 
i did use the same slot for both sticks of ram. And before, when i had 2 sticks of bad ram, i also used the same slot for each one when i tested them individually.

I'm pretty sure that i discharged my static electricity too...

what other components could be causing this?
 
well, remove all your unneeded cards, all your pci cards, etc, might even want to unplug your cd-rom/dvd-rom(unless your using the memtest cd).

i've seen a pci network card cause memory errors, as soon as the network card was removed the memory errors went away, so try testing with as few components as possible.
 
So, should i remove my video card as well, 'cause technically i could run off of the mobo's onboard vid.
 
Originally posted by Xtasy0
well, remove all your unneeded cards, all your pci cards, etc, might even want to unplug your cd-rom/dvd-rom(unless your using the memtest cd).
Click to expand...

why would that only affect 1 stick and not the other?
 
I doubt that even those two sticks in the beginning were both bad unless you managed to do something to them. Its possible but now that you got more sticks that are bad its highly unlikely from Mushkin. Most likely something else is causing. Just because you get errors in memtest it doesn't mean its the RAM. Your running the newest version of memtest too right?

Please be aware that not all errors reported by Memtest86 are due to
bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as
the motherboard. It is impossible for the test to determine what causes
the failure to occur. Most failures will be due to a problem with memory.
When it is not, the only option is to replace parts until the failure is
corrected.

Once a memory error has been detected, determining the failing SIMM/DIMM
module is not a clear cut procedure. With the large number of motherboard
vendors and possible combinations of simm slots it would be difficult if
not impossible to assemble complete information about how a particular
error would map to a failing memory module. However, there are steps
that may be taken to determine the failing module. Here are three
techniques that you may wish to use:

1) Removing modules
This is simplest method for isolating a failing modules, but may only be
employed when one or more modules can be removed from the system. By
selectively removing modules from the system and then running the test
you will be able to find the bad module(s). Be sure to note exactly which
modules are in the system when the test passes and when the test fails.

2) Rotating modules
When none of the modules can be removed then you may wish to rotate modules
to find the failing one. This technique can only be used if there are
three or more modules in the system. Change the location of two modules
at a time. For example put the module from slot 1 into slot 2 and put
the module from slot 2 in slot 1. Run the test and if either the failing
bit or address changes then you know that the failing module is one of the
ones just moved. By using several combinations of module movement you
should be able to determine which module is failing.

3) Replacing modules
If you are unable to use either of the previous techniques then you are
left to selective replacement of modules to find the failure.

4) Avoiding allocation
The printing mode for BadRAM patterns is intended to construct boot time
parameters for a Linux kernel that is compiled with BadRAM support. This
work-around makes it possible for Linux to reliably run on your average damaged
RAM (or clearly panic if it cannot). For more information on BadRAM support
for Linux, sail to

http://home.zonnet.nl/vanrein/badram

Sometimes memory errors show up due to component incompatibility. A memory
DIMM/SIMM may work fine in one system and not in another. This is not
uncommon and is a source of confusion. The components are not necessarily
bad but certain combinations may need to be avoided.
Click to expand...

Doesn't the Abit IC7 series have a problem with RAM that has CH-5 chips? Because your Mushkin RAM has just that. I know the Abit IC7-MAX3 doesn't wanna hardly run with those kind of chips at all. Can anyone else confirm this?
 
doubt that even those two sticks in the beginning were both bad unless you managed to do something to them. Its possible but now that you got more sticks that are bad its highly unlikely from Mushkin. Most likely something else is causing. Just because you get errors in memtest it doesn't mean its the RAM. Your running the newest version of memtest too right?
Click to expand...

but what would explain why one of these 2 sticks works fine and the other doesn't?
 
You must log in or register to reply here.
Back
Top