A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » Motherboards » Asus Motherboards
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

K8V SE DELUX cant install OS



 
 
Thread Tools Display Modes
  #1  
Old February 9th 05, 09:46 PM
kris
external usenet poster
 
Posts: n/a
Default K8V SE DELUX cant install OS

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


  #2  
Old February 9th 05, 10: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
  #3  
Old February 10th 05, 12:05 AM
Kris
external usenet poster
 
Posts: n/a
Default

On Wed, 09 Feb 2005 16:20:15 -0500, (Paul) wrote:

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



Cheers Paul,

I havent run that mem test s/w you mentioned BUT I have tried DocMem
which is supposed to be pretty godd and has indeed served me well.

I have taken all the cards out except the graphics which does apparent
work 100%. I say apparently since this isnt my PC. A friend went and
bought the bits last week and has just given up and asked me to get
windows on it.

The mem in I have checked agained ASUS recommened for this board and
it is there. So you would think its should pop in and run!!!

I my self have the P4 775 P5AD2 Premiumn ASUS board and work like a
dream so I trust ASUS :S with what they say.

I have gone right though BIOS setup and disabled ALL onboard h/w
except the main ATA controller and still get the same probs.

Kris
  #4  
Old February 10th 05, 12:59 AM
Paul
external usenet poster
 
Posts: n/a
Default

In article , Kris
wrote:

On Wed, 09 Feb 2005 16:20:15 -0500, (Paul) wrote:

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



Cheers Paul,

I havent run that mem test s/w you mentioned BUT I have tried DocMem
which is supposed to be pretty godd and has indeed served me well.

I have taken all the cards out except the graphics which does apparent
work 100%. I say apparently since this isnt my PC. A friend went and
bought the bits last week and has just given up and asked me to get
windows on it.

The mem in I have checked agained ASUS recommened for this board and
it is there. So you would think its should pop in and run!!!

I my self have the P4 775 P5AD2 Premiumn ASUS board and work like a
dream so I trust ASUS :S with what they say.

I have gone right though BIOS setup and disabled ALL onboard h/w
except the main ATA controller and still get the same probs.

Kris


The difference is, memtest86 tests the entire memory. The
program actually moves itself out of the way, and tests even
the memory that originally held the code segment. No other memory
test program I've read about, does that. Memtest86 is not a
perfect testing program, and a further test is required once
the OS is installed. That is Prime95 (torture test option)
from mersenne.org . Prime95 is good for testing with more
heat and electrical noise in the system, as sometimes memory
that passes memtest86, still gets errors when the OS is
running. (I have some memory that does that - Prime95 finds
trouble in 30 minutes or less.)

With respect to the Asus recommended list, we don't know what
method they use to determine that a memory is recommended. If
they only own four sticks of memory for one brand/model number,
to do their testing, then that would not be a statistically
significant sample. They do not document how they do the test.
The results in some cases are ridiculous (like when 1 stick
works, 4 sticks work, but a 2 stick configuration doesn't work).
Asus also has a habit of listing memory that is no longer
manufactured (such as Winbond BH-5 chips) or they list part
numbers that are simply not in circulation (engineering
samples). Many other suppliers of lists, will tell you what
their qualification criterion is, but not Asus. (Intel, for
example, qualifies memory based on specifications, rather than
trying to test quality into their DDR400 memory list.)

I hate to generalize, but both the Nforce2 motherboards, and
the Athlon64 boards are picky about memory. Empirically, it
would seem than not just any company can design good memory
controllers. In your current situation, what this means, is
either you get lucky and find a cheap memory that just happens
to work with the Athlon64, or you buy some CAS2 memory and
pay extra.

About all I can suggest, is buy your memory from a retailer
that allows exchange within a reasonable period, so that if
you are having problems with a picky motherboard/CPU combo,
you can find something that works. This newsgroup is not really
a good place to collect RAM recommendations, as the active
membership is not large enough to get a good answer in a
short time. A better place to look, would be the private
forums, like pcper.com, abxzone.com, nforcershq.com and so
on. Occasionally, you can find a thread on one of those
forums, where they conduct a poll of the users as to what
works and what doesn't work. That kind of a thread is
gold, because it reduces your research time a lot.

Paul
  #5  
Old February 11th 05, 04:16 PM
Kris
external usenet poster
 
Posts: n/a
Default

On Wed, 09 Feb 2005 18:59:28 -0500, (Paul) wrote:

In article , Kris
wrote:

On Wed, 09 Feb 2005 16:20:15 -0500,
(Paul) wrote:

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



Cheers Paul,

I havent run that mem test s/w you mentioned BUT I have tried DocMem
which is supposed to be pretty godd and has indeed served me well.

I have taken all the cards out except the graphics which does apparent
work 100%. I say apparently since this isnt my PC. A friend went and
bought the bits last week and has just given up and asked me to get
windows on it.

The mem in I have checked agained ASUS recommened for this board and
it is there. So you would think its should pop in and run!!!

I my self have the P4 775 P5AD2 Premiumn ASUS board and work like a
dream so I trust ASUS :S with what they say.

I have gone right though BIOS setup and disabled ALL onboard h/w
except the main ATA controller and still get the same probs.

Kris


The difference is, memtest86 tests the entire memory. The
program actually moves itself out of the way, and tests even
the memory that originally held the code segment. No other memory
test program I've read about, does that. Memtest86 is not a
perfect testing program, and a further test is required once
the OS is installed. That is Prime95 (torture test option)
from mersenne.org . Prime95 is good for testing with more
heat and electrical noise in the system, as sometimes memory
that passes memtest86, still gets errors when the OS is
running. (I have some memory that does that - Prime95 finds
trouble in 30 minutes or less.)

With respect to the Asus recommended list, we don't know what
method they use to determine that a memory is recommended. If
they only own four sticks of memory for one brand/model number,
to do their testing, then that would not be a statistically
significant sample. They do not document how they do the test.
The results in some cases are ridiculous (like when 1 stick
works, 4 sticks work, but a 2 stick configuration doesn't work).
Asus also has a habit of listing memory that is no longer
manufactured (such as Winbond BH-5 chips) or they list part
numbers that are simply not in circulation (engineering
samples). Many other suppliers of lists, will tell you what
their qualification criterion is, but not Asus. (Intel, for
example, qualifies memory based on specifications, rather than
trying to test quality into their DDR400 memory list.)

I hate to generalize, but both the Nforce2 motherboards, and
the Athlon64 boards are picky about memory. Empirically, it
would seem than not just any company can design good memory
controllers. In your current situation, what this means, is
either you get lucky and find a cheap memory that just happens
to work with the Athlon64, or you buy some CAS2 memory and
pay extra.

About all I can suggest, is buy your memory from a retailer
that allows exchange within a reasonable period, so that if
you are having problems with a picky motherboard/CPU combo,
you can find something that works. This newsgroup is not really
a good place to collect RAM recommendations, as the active
membership is not large enough to get a good answer in a
short time. A better place to look, would be the private
forums, like pcper.com, abxzone.com, nforcershq.com and so
on. Occasionally, you can find a thread on one of those
forums, where they conduct a poll of the users as to what
works and what doesn't work. That kind of a thread is
gold, because it reduces your research time a lot.

Paul


aye, twos the mem has failled with the memtest86.

Is worrying how odd blocks came up though. The dude who owns the PC
is gonna try and get an exchange. I seem to remember from pasted
encounters with the shop that they have a device for testing mem.

Cheers Paul....Hope this is my last post regaring this problem
  #6  
Old February 13th 05, 12:44 AM
external usenet poster
 
Posts: n/a
Default

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


If it is not a memory problem, then see http://tinyurl.com/6yhsp about

i changed the bios settings for advanced
jumperFree Configuration
Performance mode [auto]
[standard]
[turbo]
--
"As a thinker and planner, the ant is the equal of any savage race of men; as a self-educated
specialist in several arts she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
/\___/\
/ /\ /\ \ Ant @ The Ant Farm: http://antfarm.ma.cx
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Asus A7N8X V1.04 - won't install Windows XP Pro SP-2 OEM Bill Drake Asus Motherboards 4 December 3rd 04 09:28 AM
Can't install Nero 6 James Cdr 1 September 13th 04 11:22 PM
First Build Computer - Need Checklists and Other Tracking Documents Rob Homebuilt PC's 5 July 25th 04 12:03 AM
Fedora Core 2 install dies NBK Asus Motherboards 6 May 24th 04 03:07 AM
Install Problems with an Adaptec 2400a RAID Controller! Starz_Kid General 1 June 24th 03 03:44 AM


All times are GMT +1. The time now is 10:20 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.