[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



At this point, it sounds like there3 is a serious problem with either
the bios clocking setup or the RAM is bad. A third issue could be power
supply. 

Try running the clock speed down on the entire system and run memtest. 
Also, try to run memtest on the same ram installed in another board. Try
different ram in the same board.

Verify that the RAM is actually what you think it is. It does happen
that the store hands out the wrong part. Try looking up chip codes to
see if they match the specs you are trying.

It is also possible that the power supply is only marginally in spec.
Add a motherboard only marginally in spec and the system may be now out
of spec for what the power supply can deliver. If the issue clears up a
bit with nothing plugged in but the mother board and the device used to
run memtest from, change the powersupply.

Best test would be to take to system to where you got the ram. Get them
to produce new ram. Run memtest right there with them watching. If the
new ram fails as well, get a new mother board and test the old ram.

> Jim
> _______________________________________________
> Ale mailing list
> Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO &amp; Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
<a  rel="nofollow" href="http://www.localnetsolutions.com";>http://www.localnetsolutions.com</a>

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
&lt;jkinney at localnetsolutions.com&gt;
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00773" href="msg00773.html">[ale] Hardware problems continue on new system</a></strong>
<ul><li><em>From:</em> bluejay at speedfactory.net (Jim Seymour)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00769" href="msg00769.html">[ale] Hardware problems continue on new system</a></strong>
<ul><li><em>From:</em> bluejay at speedfactory.net (Jim Seymour)</li></ul></li>
<li><strong><a name="00770" href="msg00770.html">[ale] Hardware problems continue on new system</a></strong>
<ul><li><em>From:</em> ezlinux at comcast.net (Liberie F. Cunha-Neto)</li></ul></li>
<li><strong><a name="00771" href="msg00771.html">[ale] Hardware problems continue on new system</a></strong>
<ul><li><em>From:</em> bluejay at speedfactory.net (Jim Seymour)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00771.html">[ale] Hardware problems continue on new system</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00773.html">[ale] Hardware problems continue on new system</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00771.html">[ale] Hardware problems continue on new system</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00773.html">[ale] Hardware problems continue on new system</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00772"><strong>Date</strong></a></li>
<li><a href="threads.html#00772"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>