View Full Version : XP 2100+ B Problem
Nomad64
06-26-2003, 05:37 PM
My Friend recenlty purchased an Anthlon XP 2100+ B from Newegg.com and I had the pleasure of installing it yesterday. I wanted to O/C it at the time, but due to time constraints, I couldn't, and left it set at 133 x 13.0 with the Vcore at 1.600 (which I believe is default).
This morning, my friend was complaining about the computer restarting and/or freezing on him at random intervals, so I went over to investigate the problem. After working on it a bit, I saw that even at stock speeds with the Vcore at 1.600, the processor was hitting 45 deg C. So I thought that because I did a hurried job on applying the thermal compound, that I might have goofed on it; so I redid that. Afterwords the problem still persisted, and I am baffled. Anyone have any ideas/suggestions? (espically since this is a folding rig)
His computer layout is as follows:
Leadtek WinFast K7NCR18D-Pro
AMD Athlon XP 2100+B (currently underclocked at 120 x 13.0)
SLK-700 Heat sink w/ YS Tech CMD 36CFM fan
I don't think it's the CPU itself, even at 45c it shouldn't be hanging. Maybe IRQ conflicts? is APIC enabled?
A bad PSU can also lead to random restarts.
Regards,
KODE.
amdrules770
06-26-2003, 11:24 PM
are you sure 1.6 is the vcore? maybe bump it up a bit and see if it gets stable. just go over and play with it a bit.
Nomad64
06-27-2003, 01:45 AM
Originally posted by KODE
Maybe IRQ conflicts? is APIC enabled?...A bad PSU can also lead to random restarts...
Well, I am pretty sure there aren't any IRQ conflicts, because it (besides having all of the serial ports disabled) It dosen't hang/restart right away, I left it on while my friend and I went out and got lunch, we were gone for a good 30 min, and the computer was still running fine when I got back. After opening a window to check the F@H log, it froze though. :\
As for APIC...that is one thing that I didn't check out, but I will have to in the future.
Bad PSU? I built his computer about Feb.-March of this year with an Antec 430W TRUE PSU...but I should probably watch the voltages in the BIOS and invistigate that as well.
Originally posted by amdrules770
are you sure 1.6 is the vcore? maybe bump it up a bit and see if it gets stable. just go over and play with it a bit.
I set the Vcore in the BIOS to 1.600V...so unless the BIOS is a bit screwy, it should be set to that. Plus mine runs just fine at 2.17GHz (166 x 13) at ~1.7v...so the Vcore may be the problem. I will go over there tomorrow and check it out, and then post an update.
One thing I noticed is that I can't set the CPU multipler, also when I set the FSB to 166MHz, it won't even POST...blarg :notgood:
amdrules770
06-27-2003, 02:02 AM
yeah, a little extra voltage couldn't hurt.
dicki
06-27-2003, 08:58 AM
i noticed on my NF7-s that the Vcore ofteb runs a little low up to 0.1 of a volt off under load so i'd definatly bumb it up a bit
dicki
Nomad64
07-02-2003, 10:55 PM
I was over at my friends house working on his computer, again with little luck and little gain. He said that the computer was suffering from random crashes again, but this time Windows stated that it was the display driver for this ATi Radeon 8500LE. I had updated the video drivers to the Catilyst 3.5's when I was there last, but the crashes didn't make much sense to me.
I ran a windows update, and found that he was still running WinXP Pro without SP1 installed! After installing that, as well as about 10 other updates, I restarted and reinstalled the CAT 3.5 drivers. I also upped the Vcore voltage to 1.675...but as I watched the Vcore voltage output from a system monitor in Windows, it registered an average of 1.642V, which distrubes me a bit.
It appears that his system is stable, but we shall see over the next few days. The only real problem I had was the fact that the computer kept shutting down because the CPU temp got up to 60 deg C...than again, it was about 90 deg F in his room.
vBulletin® v3.6.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.