Re: first attempt ot OC
- From: "timO'" <timothy.w.oleary@xxxxxxxxxxx>
- Date: Wed, 1 Oct 2008 19:32:31 -0700 (PDT)
On Sep 30, 11:37 pm, Paul <nos...@xxxxxxxxxx> wrote:
timO' wrote:
On Sep 29, 10:35 pm, Paul <nos...@xxxxxxxxxx> wrote:
timO' wrote:
On Sep 28, 11:23 pm, Paul <nos...@xxxxxxxxxx> wrote:The voltage setting is visible in the BIOS. It may not be tied to
timO' wrote:the pc started OK today.
i started having this new problem where the BIOS locks up on the ramSo are you at stock speed right now ?
line. i've been able to reboot until the system statrs then all is
well again, but it is really bugging me. Corsair tech said to run
memtest. i created a boot cd but after many passes no errors occurred.
when i posted this result back to the tech on the firum someone on the
corsair forum advised me to go into bios and i did some tweaking i
reset my dram v to 2.1 and the ram to 5-5-5-5-18
i was not able to set the dram to ddr800, as only 400 qnd 533 were
offered. this corresponds with what you were saying about resetting
the cpu frequency.
i'm still unsure what is the deal with the bios locking up. i have not
had a chance to retest the ram with the new settings yet. Corsair said
if the ram made errors they'd replace it.
i have not backed up my c drive yet either.
i might increase the clock like you suggested to see what happens.
Perhaps you can return to stock, and do a few tests there.
You can also use CPUZ, to verify while in Windows, that the
settings you think have been applied, are actually there.
Maybe something is mis-adjusted.
Paul
what are the stock settings anyway?
right now they are 5-5-5-18
I thought I set the DRAM voltage to 2.1, but where can I see that
number in cpuid?
set to DDR2 533. i'd like to bump i up to DDR2 800
any monitoring device. The hardware monitor has a limited number
of inputs on it for voltage.
The DRAM clock, is a combination of the "visible" value shown
in the BIOS (effectively a certain divider ratio between the
CPU clock and the memory clock), and how much you've turned
up the CPU clock above nominal.
Paul
right. the DRAM voltage is visible in BIOS. I haven't messed with the
CPU clock
yet
i am still having intermittant POST problems. POST stops at the line
which lists the RAM.
During a successful POST, my system usually stops a few seconds at
that line then the rest of the POST routine bursts by.
when it screws up it just hangs there indefinitely.
Is it testing the RAM or testing the USB which comes right after the
RAM test?
right now I'm corresponding with ENERMAX and they're saying to reset
CMOS and to send the power supply back.
NO and NO
at least not yet.
maybe i should start a new thead.
the system has yet to crash while running in Windows, and produced no
errors during the memtests.
Stock settings would be FSB533 for the front side bus and DDR2-533
for the RAM. The CPU clock would be 133MHz (133*4 = 533).
FSB533 would be stock for the Pentium D 805. The user manual for
the P5WD2-E Premium shows that there isn't a divider for
DDR2-800 setting, when the FSB is at FSB533. DDR2-533 is as fast
as the nominal setting will go.
http://processorfinder.intel.com/details.aspx?sSpec=SL8ZH
I would test each memory stick individually, and see if any of the
memory is more prone to the problem, than the rest of it.
An additional interface available on motherboards, is the PCI Port 80
function. You can get a debugging card, and it is plugged into
PCI Slot 1 (the PCI slot which is closest to the processor). The
BIOS dumps two digit hex codes, and the codes are "progress" codes
and not error codes as such. I have yet to have a problem which
was made more definite, or easier to find, when one of those cards
was used. But you asked the question, as to what other means there
are of figuring out what is going on, and that is another diagnostic
tool. The cards cost $20 to $100, with the cheapest ones coming from
Hong Kong via Ebay.
One of the problems with the codes, is the quality of the documentation
for the hex codes. There are examples here, and for the most part,
they don't tell me much. Many times, a USENET poster will mention
a code seen on the display, and the documentation will say
"reserved". So if custom entries are used in the BIOS, they're of
no use to anyone.
http://www.bioscentral.com/postcodes/amibios.htm
Part substitution is a frequent debugging means on home computers,
and in this case, testing the RAM a stick at a time, is the cheapest
way to test. That doesn't require buying any more RAM. At this point,
we don't know if this is a motherboard or a RAM issue, and it may
turn out that the problem is with the motherboard. You need to try
as many "free" tests as possible, to try to distinguish where the
problem is.
Paul
thankyou for the detailed and thoughtful response. i will decide how
to proceed.
.
- References:
- Re: first attempt ot OC
- From: timO'
- Re: first attempt ot OC
- From: Paul
- Re: first attempt ot OC
- Prev by Date: Re: New build locking up Asus PKQ Pro
- Next by Date: Re: Help me fix a system that I can't afford to replace right now
- Previous by thread: Re: first attempt ot OC
- Next by thread: Help me fix a system that I can't afford to replace right now
- Index(es):
Relevant Pages
|
