Strange boots! Help me!

[vale]

PC configuration::

1.. AMD AthlonXP 2800+ (Socket A)
2.. motherboard ASUS A7V600-X (versione BIOS 1002)
3.. 512 MB di RAM 400DDR marcata Elisir
4.. HD Maxtor SATA 80GB.
5.. Il SO operativo installato è Windows XP Professional Service Pack 1.
My PC boots or crashes every time I do scandisk, defrag, CDburning from
ISOimages (before boot, it appears the classic blu screen
"Kernel_Stack_Impage_Error").

What can be the problem? The memory? The HD SATA?

 

[Gareth Jones]

My PC boots or crashes every time I do scandisk, defrag, CDburning from
ISOimages (before boot, it appears the classic blu screen
"Kernel_Stack_Impage_Error").

What can be the problem? The memory? The HD SATA?

Update the BIOS and also install the SAME version sata windows drivers.
--
__________________________________________________
Personal email for Gareth Jones can be sent to:
'usenet4gareth' followed by an at symbol
followed by 'uk2' followed by a dot
followed by 'net'
__________________________________________________

 

[Paig Chong Woo]

PC configuration::

1.. AMD AthlonXP 2800+ (Socket A)
2.. motherboard ASUS A7V600-X (versione BIOS 1002)
3.. 512 MB di RAM 400DDR marcata Elisir
4.. HD Maxtor SATA 80GB.
5.. Il SO operativo installato è Windows XP Professional Service Pack 1.
My PC boots or crashes every time I do scandisk, defrag, CDburning from
ISOimages (before boot, it appears the classic blu screen
"Kernel_Stack_Impage_Error").

What can be the problem? The memory? The HD SATA?

Yeah, I'd say the RAM. This Elixir "brand" is pure crap. Test your RAM with
memtest86.

 

[Paul]

Yeah, I'd say the RAM. This Elixir "brand" is pure crap. Test your RAM with
memtest86.

"Kernel_Stack_Impage_Error"
http://www.microsoft.com/windows200...2000/techinfo/reskit/en-us/w2000msgs/6094.asp

"Explanation:

This Stop message indicates that the requested page of kernel data
from the paging file could not be read into memory. It might have
been caused by a bad block (sector) in a paging file, a disk
controller error, a defective motherboard, failing RAM, or because
the stack signature in the kernel stack was not found. In extremely
rare cases, it is caused when nonpaged pool resources run out."

If you have a spare disk around, clone the SATA onto it. Since
your current computer is having a lot of disk trouble, do the
cloning on another computer. I agree with testing the memory, and
if memtest passes your memory, then the disk is the next thing
to consider. Judging by the clustering of errors focused on the
disk, it is possibly a disk problem of some sort. I would try
swapping your SATA drive, for a drive by another manufacturer or
for a PATA drive.

If you are getting errors other than Kernel_Stack_Impage_Error,
please post them, so we can get an idea of where the fault lies.

I don't know if Maxtor's drive testing software handles SATA
drives yet or not. You need to find some kind of drive fitness
test, to verify exactly how healthy the disk is.

HTH,
Paul