View Single Post
  #2  
Old February 9th 05, 09:20 PM
Paul
external usenet poster
 
Posts: n/a
Default

In article , "kris"
wrote:

HELP

Anyone successfuly installed Windows XP on a K8 board? Keeps rebooting just
after it says "Stating Winodw" just after its loaded the drivers right at
the begining of the Windows XP install. Sometimes get errors RE atapi.sys
and sometimes get PAGE_FAULT_IN_NON_PAGEDAREA (or similar wording)

PLZ help


This sounds like a memory problem.

The K8V is a single channel board. If you are running two sticks
at DDR400, the sticks should be installed in slots 1 and 3. If you
have only one stick of memory, try it in slot 3 (furthest from
the processor). (Remember to unplug the computer before moving
the sticks - at the very least, make sure the green LED on the
motherboard is not lit, when moving or changing components of
any type on the motherboard.)

If you are lucky, there will be a Vdimm setting in the BIOS.
To operate memory at DDR400, this should really be set to 2.6V or
higher. Even 2.75V won't hurt, if the motherboard supports it.

It is time to test your memory with memtest86 from memtest.org .
The program will format a blank floppy for you and put a program
on it. You'll need to make the floppy the first device in the
boot order in the BIOS. On the next boot, the floppy will boot
the computer, and the program will display info about the memory
in a 640x480 window. (The floppy does not have a file system on
it, so the floppy cannot be listed in Windows.)

If you get tons of errors in Memtest86, then that is your problem
right there.

You should be able to enter the BIOS and change some of
the settings. The simplest thing to try, would be dropping
the clock settings a bit, as that will give the memory extra
time to respond. If no combination of settings is helping, it
could be the memory is really bad (as in a stuck fault). If
slowing the clock down stops the errors, it could be the memory
just isn't going to work with that processor (but may work on
another board).

I've been through this crap with an Nforce2 board, and a quick
fix is to buy some CAS2 memory. It is either that, or go Googling
for some success stories with your motherboard model number
as a search term. Since the memory controller is inside the
processor, there is even a small chance that the problem is with
the processor itself.

Hope that gives you a few ideas. Try the cheap ideas first.
Paul