Can't install any OS (hardware fault?)

[Paul Richard]

Hi,

I've just bought the components to a new PC and am having problems. Here is
a rundown of the hardware:

- Abit VI7 Mobo (KT800, VT8237 chipset)
- Celeron 2.2 GHz (Northwood core)
- 512 MB memory (Corsair Value)
- Maxtor 80GB ATA-133 HDD
- Lite-On 52x32x52 CDRW
- Enermax 350W EG365P-VE FMA PSU

Also, I recently updated the BIOS to version 1.2 off the Abit website.

Everything boots up fine and I get the machine to boot of the CD. In the
most recent attempt I booted off a Windows XP CD. The installation starts
out fine enough. I get through the initial questions, it asks about the
partitions and I format the drive, etc (oh yeah, I partitionned the disk and
am using the first 20GB to install). Usually around this point is where it
blue screens. In some instances I get further along the process than others,
but eventually I always bluescreen. This last time around the Windows
message looked like this:

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If
this is a new installation,ask your hardware or software manufacturer for
any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If you
need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select Safe
Mode.

Technical information:

*** STOP: 0x00000050 (0xC14EC3F8,0x00000000,0xC14EC3F8,0x00000000)

The blue screen is generally the same except that the "PAGE_FAULT..." bit
can differ and I've also had driver names appear towards the bottom (in the
technical information section; e.g. atapi.sys; dio.sys or something like
that).

Now I've also tried booting up a Debian 3.0 install CD and mostly always run
into a Kernel panic with a message suggesting that I use the init= option at
the boot prompt. Looks like it can't locate the kernel on the CD. In some
other cases, the screen fills up with rubish. Always seem to happen around
the same point too.

In some other cases, I've tried booting to Win98 DOS (off a floppy) with the
atapi driver installed and just tested copying a bunch of files from the
CDRW to the HDD. In one case, the system locked during the copy.

I even tried swapping my CDRW drive for my old 4x Toshiba CD-Rom (which I
now to be working fine in my old Pentium system) and get pretty much the
same type of results.

Given the randomness of it all, I'm thinking hardware fault on the Mobo but
I'd sure like to hear different. Any gurus out there that could lend a
hand? Could this be anything other than the Mobo?

Any help appreciated!

Cheers,
Paul

 

[spodosaurus]

Hi,

I've just bought the components to a new PC and am having problems. Here is
a rundown of the hardware:

- Abit VI7 Mobo (KT800, VT8237 chipset)
- Celeron 2.2 GHz (Northwood core)
- 512 MB memory (Corsair Value)
- Maxtor 80GB ATA-133 HDD
- Lite-On 52x32x52 CDRW
- Enermax 350W EG365P-VE FMA PSU

Also, I recently updated the BIOS to version 1.2 off the Abit website.

Everything boots up fine and I get the machine to boot of the CD. In the
most recent attempt I booted off a Windows XP CD. The installation starts
out fine enough. I get through the initial questions, it asks about the
partitions and I format the drive, etc (oh yeah, I partitionned the disk and
am using the first 20GB to install). Usually around this point is where it
blue screens. In some instances I get further along the process than others,
but eventually I always bluescreen. This last time around the Windows
message looked like this:

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If
this is a new installation,ask your hardware or software manufacturer for
any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If you
need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select Safe
Mode.

Technical information:

*** STOP: 0x00000050 (0xC14EC3F8,0x00000000,0xC14EC3F8,0x00000000)

The blue screen is generally the same except that the "PAGE_FAULT..." bit
can differ and I've also had driver names appear towards the bottom (in the
technical information section; e.g. atapi.sys; dio.sys or something like
that).

Now I've also tried booting up a Debian 3.0 install CD and mostly always run
into a Kernel panic with a message suggesting that I use the init= option at
the boot prompt. Looks like it can't locate the kernel on the CD. In some
other cases, the screen fills up with rubish. Always seem to happen around
the same point too.

In some other cases, I've tried booting to Win98 DOS (off a floppy) with the
atapi driver installed and just tested copying a bunch of files from the
CDRW to the HDD. In one case, the system locked during the copy.

I even tried swapping my CDRW drive for my old 4x Toshiba CD-Rom (which I
now to be working fine in my old Pentium system) and get pretty much the
same type of results.

Given the randomness of it all, I'm thinking hardware fault on the Mobo but
I'd sure like to hear different. Any gurus out there that could lend a
hand? Could this be anything other than the Mobo?

Any help appreciated!

Cheers,
Paul

go and download memtest86 from http://www.memtest86.com/

make a donation to help with the costs of running that site

test your system

report back here

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying

 

[Paul Richard]

Hi,

How crap is that? I responded back yesterday to this post, but using a
different server and the post has still not made it to the first server I
used.

Anyway, here is what I have found:

So the memory seems to be the problem. After only a single pass through all
the tests here is the summary:

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5).

Later in the day, I did further testing and started by swapping the DIMM to
the second slot (bank 2-3) on the board. I powered up and allowed memtest to
do its its thing. No errors found!! A step forward I thought.

I then powered down, moved the DIMM back to bank 0-1 and powered back up.
This time on rebooting, the system failed to boot and the board played a
long continuous beep which suggests an error. I then repeated the steps of
powering down, removing and re-installing the memory to the same slot (bank
0-1) and powering up again. This was necessary a few times before it booted
and memtest was able to run again. Once again, the results were similar to
my initial bank 0-1 test with failures in tests 4, 5 and 6. So
consistent... as long as I am able to boot up.

I then returned the DIMM back to bank 2-3, but failed to boot up again with
that long continuous beep. I've tried this quite a few times now with the
same results. Now it doesn't seem to matter which bank the memory is in, I
just can't get it to boot.

Conclusions: Well I'm not certain which valid conclusions I can draw.
However, given that I did get a successful test cycle of the memory when in
bank 2-3 suggests that the DIMM is ok and that the problem may be with the
mobo (slot connectors, memory bus, etc.??). I'd appreciate your thoughts
and analysis.

Oh, one point in passing. The chipset on the board is the Via PT800 (not
the KT800). Sorry about the confusion.

Cheers,
Paul

I don't know why I didn't think of that given that I have used memtest it in
the past.

So the memory seems to be the problem. Ah the time I could have saved if I'd
just started with this.

Summary :

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

I also noted a few of the logs that appeared as it was doing test 6. The
following memory locations were listed: 57MB, 256.5MB, 408.3MB, 414.0MB,
257.0MB, 257.6MB.

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5). I've
not tried moving it to the other slot on the boards (ran out of time this
morning), but I'll have a go this evening. Guess I'll call the retailler to
ask what to do next. Hope they don't give me a hard time.

Thanks for your help! I'll let you know how it turns out.

Paul

Hi,

I've just bought the components to a new PC and am having problems. Here is
a rundown of the hardware:

- Abit VI7 Mobo (KT800, VT8237 chipset)
- Celeron 2.2 GHz (Northwood core)
- 512 MB memory (Corsair Value)
- Maxtor 80GB ATA-133 HDD
- Lite-On 52x32x52 CDRW
- Enermax 350W EG365P-VE FMA PSU

Also, I recently updated the BIOS to version 1.2 off the Abit website.

Everything boots up fine and I get the machine to boot of the CD. In the
most recent attempt I booted off a Windows XP CD. The installation starts
out fine enough. I get through the initial questions, it asks about the
partitions and I format the drive, etc (oh yeah, I partitionned the disk and
am using the first 20GB to install). Usually around this point is where it
blue screens. In some instances I get further along the process than others,
but eventually I always bluescreen. This last time around the Windows
message looked like this:

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If
this is a new installation,ask your hardware or software manufacturer for
any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If you
need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select Safe
Mode.

Technical information:

*** STOP: 0x00000050 (0xC14EC3F8,0x00000000,0xC14EC3F8,0x00000000)

The blue screen is generally the same except that the "PAGE_FAULT..." bit
can differ and I've also had driver names appear towards the bottom (in the
technical information section; e.g. atapi.sys; dio.sys or something like
that).

Now I've also tried booting up a Debian 3.0 install CD and mostly always run
into a Kernel panic with a message suggesting that I use the init= option at
the boot prompt. Looks like it can't locate the kernel on the CD. In some
other cases, the screen fills up with rubish. Always seem to happen around
the same point too.

In some other cases, I've tried booting to Win98 DOS (off a floppy) with the
atapi driver installed and just tested copying a bunch of files from the
CDRW to the HDD. In one case, the system locked during the copy.

I even tried swapping my CDRW drive for my old 4x Toshiba CD-Rom (which I
now to be working fine in my old Pentium system) and get pretty much the
same type of results.

Given the randomness of it all, I'm thinking hardware fault on the Mobo but
I'd sure like to hear different. Any gurus out there that could lend a
hand? Could this be anything other than the Mobo?

Any help appreciated!

Cheers,
Paul

go and download memtest86 from http://www.memtest86.com/

make a donation to help with the costs of running that site

test your system

report back here

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying

 

[spodosaurus]

Sorry for top posting, but there's a lot of data there I would tend
to agree with your conclusions about there being a problem with the
motherboard. To make ultra sure, you could try a different stick of RAM
in there. However, if you do not have access to another stick of RAM,
then I'd be taking the motherboard back and getting a replacement. I'm
afraid that's the best/most help I can offer. If you were local I'd
bring over one of my memory cards and try it out

Ari

Hi,

How crap is that? I responded back yesterday to this post, but using a
different server and the post has still not made it to the first server I
used.

Anyway, here is what I have found:

So the memory seems to be the problem. After only a single pass through all
the tests here is the summary:

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5).

Later in the day, I did further testing and started by swapping the DIMM to
the second slot (bank 2-3) on the board. I powered up and allowed memtest to
do its its thing. No errors found!! A step forward I thought.

I then powered down, moved the DIMM back to bank 0-1 and powered back up.
This time on rebooting, the system failed to boot and the board played a
long continuous beep which suggests an error. I then repeated the steps of
powering down, removing and re-installing the memory to the same slot (bank
0-1) and powering up again. This was necessary a few times before it booted
and memtest was able to run again. Once again, the results were similar to
my initial bank 0-1 test with failures in tests 4, 5 and 6. So
consistent... as long as I am able to boot up.

I then returned the DIMM back to bank 2-3, but failed to boot up again with
that long continuous beep. I've tried this quite a few times now with the
same results. Now it doesn't seem to matter which bank the memory is in, I
just can't get it to boot.

Conclusions: Well I'm not certain which valid conclusions I can draw.
However, given that I did get a successful test cycle of the memory when in
bank 2-3 suggests that the DIMM is ok and that the problem may be with the
mobo (slot connectors, memory bus, etc.??). I'd appreciate your thoughts
and analysis.

Oh, one point in passing. The chipset on the board is the Via PT800 (not
the KT800). Sorry about the confusion.

Cheers,
Paul

I don't know why I didn't think of that given that I have used memtest it
in

the past.

So the memory seems to be the problem. Ah the time I could have saved if
I'd

just started with this.

Summary :

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

I also noted a few of the logs that appeared as it was doing test 6. The
following memory locations were listed: 57MB, 256.5MB, 408.3MB, 414.0MB,
257.0MB, 257.6MB.

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5).
I've

not tried moving it to the other slot on the boards (ran out of time this
morning), but I'll have a go this evening. Guess I'll call the retailler
to

ask what to do next. Hope they don't give me a hard time.

Thanks for your help! I'll let you know how it turns out.

Paul

Hi,

I've just bought the components to a new PC and am having problems. Here

is

a rundown of the hardware:

- Abit VI7 Mobo (KT800, VT8237 chipset)
- Celeron 2.2 GHz (Northwood core)
- 512 MB memory (Corsair Value)
- Maxtor 80GB ATA-133 HDD
- Lite-On 52x32x52 CDRW
- Enermax 350W EG365P-VE FMA PSU

Also, I recently updated the BIOS to version 1.2 off the Abit website.

Everything boots up fine and I get the machine to boot of the CD. In the
most recent attempt I booted off a Windows XP CD. The installation

starts

out fine enough. I get through the initial questions, it asks about the
partitions and I format the drive, etc (oh yeah, I partitionned the disk

and

am using the first 20GB to install). Usually around this point is where

it

blue screens. In some instances I get further along the process than

others,

but eventually I always bluescreen. This last time around the Windows
message looked like this:

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.

If

this is a new installation,ask your hardware or software manufacturer

for

any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If

you

need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select

Safe

Mode.

Technical information:

*** STOP: 0x00000050 (0xC14EC3F8,0x00000000,0xC14EC3F8,0x00000000)

The blue screen is generally the same except that the "PAGE_FAULT..."

bit

can differ and I've also had driver names appear towards the bottom (in

the

technical information section; e.g. atapi.sys; dio.sys or something like
that).

Now I've also tried booting up a Debian 3.0 install CD and mostly always

run

into a Kernel panic with a message suggesting that I use the init=

option at

some

around

the

I

but


go and download memtest86 from http://www.memtest86.com/

make a donation to help with the costs of running that site

test your system

report back here

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying

 

[Paul Richard]

Why? Is it bad netiquette to top post? Geez, am I a rude bastard and I
don't even know it? So that's what my friends are always on about
I tend to preffer it anyway as the answer is more handy.

Anyway, I guess I'll get in touch with Komplett first thing Monday to get an
RMA. I actually already opened one for the memory after the first test
thinking the memory was bad. Geez, I just want the damn thing to work. Oh
well...

So thanks for your help, much appreciated!!

Paul

Sorry for top posting, but there's a lot of data there I would tend
to agree with your conclusions about there being a problem with the
motherboard. To make ultra sure, you could try a different stick of RAM
in there. However, if you do not have access to another stick of RAM,
then I'd be taking the motherboard back and getting a replacement. I'm
afraid that's the best/most help I can offer. If you were local I'd
bring over one of my memory cards and try it out

Ari

Hi,

How crap is that? I responded back yesterday to this post, but using a
different server and the post has still not made it to the first server I
used.

Anyway, here is what I have found:

So the memory seems to be the problem. After only a single pass through all
the tests here is the summary:

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5).

Later in the day, I did further testing and started by swapping the DIMM to
the second slot (bank 2-3) on the board. I powered up and allowed memtest to
do its its thing. No errors found!! A step forward I thought.

I then powered down, moved the DIMM back to bank 0-1 and powered back up.
This time on rebooting, the system failed to boot and the board played a
long continuous beep which suggests an error. I then repeated the steps of
powering down, removing and re-installing the memory to the same slot (bank
0-1) and powering up again. This was necessary a few times before it booted
and memtest was able to run again. Once again, the results were similar to
my initial bank 0-1 test with failures in tests 4, 5 and 6. So
consistent... as long as I am able to boot up.

I then returned the DIMM back to bank 2-3, but failed to boot up again with
that long continuous beep. I've tried this quite a few times now with the
same results. Now it doesn't seem to matter which bank the memory is in, I
just can't get it to boot.

Conclusions: Well I'm not certain which valid conclusions I can draw.
However, given that I did get a successful test cycle of the memory when in
bank 2-3 suggests that the DIMM is ok and that the problem may be with the
mobo (slot connectors, memory bus, etc.??). I'd appreciate your thoughts
and analysis.

Oh, one point in passing. The chipset on the board is the Via PT800 (not
the KT800). Sorry about the confusion.

Cheers,
Paul

I don't know why I didn't think of that given that I have used memtest

it

in

the past.

So the memory seems to be the problem. Ah the time I could have saved if
I'd

just started with this.

Summary :

Test 0: 0 Errors
Test 1: 0 Errors
Test 2: 0 Errors
Test 3: 0 Errors
Test 4: 1514 Errors
Test 5: 1448 Errors
Test 6: 10 Errors
Test 7: 0 Errors
Test 8: 0 Errors
Test 9: 0 Errors
Test 10: 0 Errors
Test 11: 0 Errors

I also noted a few of the logs that appeared as it was doing test 6. The
following memory locations were listed: 57MB, 256.5MB, 408.3MB, 414.0MB,
257.0MB, 257.6MB.

The main memory is a single Corsair Value Select VS512MB400 (CAS 2.5).
I've

not tried moving it to the other slot on the boards (ran out of time this
morning), but I'll have a go this evening. Guess I'll call the

retailler

to

ask what to do next. Hope they don't give me a hard time.

Thanks for your help! I'll let you know how it turns out.

Paul

Paul Richard wrote:

Hi,

I've just bought the components to a new PC and am having problems.

Here

is

a rundown of the hardware:

- Abit VI7 Mobo (KT800, VT8237 chipset)
- Celeron 2.2 GHz (Northwood core)
- 512 MB memory (Corsair Value)
- Maxtor 80GB ATA-133 HDD
- Lite-On 52x32x52 CDRW
- Enermax 350W EG365P-VE FMA PSU

Also, I recently updated the BIOS to version 1.2 off the Abit website.

Everything boots up fine and I get the machine to boot of the CD. In the
most recent attempt I booted off a Windows XP CD. The installation
starts

out fine enough. I get through the initial questions, it asks about the
partitions and I format the drive, etc (oh yeah, I partitionned the

disk

and

am using the first 20GB to install). Usually around this point is where
it

blue screens. In some instances I get further along the process than
others,

but eventually I always bluescreen. This last time around the Windows
message looked like this:

A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.
If

this is a new installation,ask your hardware or software manufacturer
for

any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If
you

need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select
Safe

Mode.

Technical information:

*** STOP: 0x00000050 (0xC14EC3F8,0x00000000,0xC14EC3F8,0x00000000)

The blue screen is generally the same except that the "PAGE_FAULT..."
bit

can differ and I've also had driver names appear towards the bottom (in
the

technical information section; e.g. atapi.sys; dio.sys or something like
that).

Now I've also tried booting up a Debian 3.0 install CD and mostly

always

run

into a Kernel panic with a message suggesting that I use the init=

option at

the boot prompt. Looks like it can't locate the kernel on the CD. In
some

other cases, the screen fills up with rubish. Always seem to happen
around

the same point too.

In some other cases, I've tried booting to Win98 DOS (off a floppy)

with

the

atapi driver installed and just tested copying a bunch of files from the
CDRW to the HDD. In one case, the system locked during the copy.

I even tried swapping my CDRW drive for my old 4x Toshiba CD-Rom (which
I

now to be working fine in my old Pentium system) and get pretty much the
same type of results.

Given the randomness of it all, I'm thinking hardware fault on the Mobo
but

I'd sure like to hear different. Any gurus out there that could lend a
hand? Could this be anything other than the Mobo?

Any help appreciated!

Cheers,
Paul



go and download memtest86 from http://www.memtest86.com/

make a donation to help with the costs of running that site

test your system

report back here

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying

--

Are you registered as a bone marrow donor? You regenerate what you
donate. You are offered the chance to donate only if you match a person
on the recipient list. Visit www.marrow.org or call your local Red Cross
and ask about registering to be a bone marrow donor.

spam trap: replace shyah_right! with hotmail when replying