STOP error right after Setup is finished copying files

  • Thread starter Thread starter michas_pi
  • Start date Start date
M

michas_pi

I get a stop error after Setup is finished copying files
(the first time, not the second). the contents of this
error is this:

STOP 0x0000000A
(0xFFE0F80C,0x0000001E,0x00000000,0x8042CB47)
IRQL_NOT_LESS_OR_EQUAL
Address 8042CB47 base at 80400000 DateStamp 304d5a76 -
ntoskrnl.exe

I have read the Knowledge Base article and it doesn't
help :-(. I really don't want to pay for support, so I'm
asking the community.

Thanks!
 
To do a clean install, either boot the Windows 2000 install CD-Rom or setup
disks. The set of four install disks can be created from your Windows 2000
CD-Rom; change to the \bootdisk directory on the CD-Rom and execute
makeboot.exe (from dos) or makebt32.exe (from 32 bit) and follow the
prompts.

When you get to the point, delete the existing NTFS and or other partitions
found. After you delete the partition(s) abort the install, then again
restart the pc booting the CD-Rom or setup disks to avoid unexpected drive
letter assignments with your new install.

You didn't mention the drive controller (possibly SCSI, or ultra DMA, or
ATA100, or raid, or serial ATA), but you may need to boot the Windows 2000
setup disks or CD-Rom and *F6* very early and very important (at setup is
inspecting your system) in the setup to prevent drive controller detection,
and select S to specify additional drivers. Then later you'll be prompted to
insert the manufacturer supplied Windows 2000 driver for your drive's
controller in drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows 2000 Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

:
| I get a stop error after Setup is finished copying files
| (the first time, not the second). the contents of this
| error is this:
|
| STOP 0x0000000A
| (0xFFE0F80C,0x0000001E,0x00000000,0x8042CB47)
| IRQL_NOT_LESS_OR_EQUAL
| Address 8042CB47 base at 80400000 DateStamp 304d5a76 -
| ntoskrnl.exe
|
| I have read the Knowledge Base article and it doesn't
| help :-(. I really don't want to pay for support, so I'm
| asking the community.
|
| Thanks!
 
I don't use any controller cards except the one that's
already on the hard drive. I use the built-in UDMA/133
already in the motherboard. I hope this helps (I also
hope I didn't contradict myself).
 
Yes, you'll need to F6 and install the driver.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

:
| I don't use any controller cards except the one that's
| already on the hard drive. I use the built-in UDMA/133
| already in the motherboard. I hope this helps (I also
| hope I didn't contradict myself).
| >-----Original Message-----
| >To do a clean install, either boot the Windows 2000
| install CD-Rom or setup
| >disks. The set of four install disks can be created from
| your Windows 2000
| >CD-Rom; change to the \bootdisk directory on the CD-Rom
| and execute
| >makeboot.exe (from dos) or makebt32.exe (from 32 bit)
| and follow the
| >prompts.
| >
| >When you get to the point, delete the existing NTFS and
| or other partitions
| >found. After you delete the partition(s) abort the
| install, then again
| >restart the pc booting the CD-Rom or setup disks to
| avoid unexpected drive
| >letter assignments with your new install.
| >
| >You didn't mention the drive controller (possibly SCSI,
| or ultra DMA, or
| >ATA100, or raid, or serial ATA), but you may need to
| boot the Windows 2000
| >setup disks or CD-Rom and *F6* very early and very
| important (at setup is
| >inspecting your system) in the setup to prevent drive
| controller detection,
| >and select S to specify additional drivers. Then later
| you'll be prompted to
| >insert the manufacturer supplied Windows 2000 driver for
| your drive's
| >controller in drive "A"
| >
| >If you wait and then S to specify additional drivers,
| then it may be too
| >late as Windows 2000 Setup at this point may have
| already assigned the
| >resources your drive's controller is wanting to use.
| >
| >--
| >Regards,
| >
| >Dave Patrick ....Please no email replies - reply in
| newsgroup.
| >Microsoft MVP [Windows NT/2000 Operating Systems]
| >http://www.microsoft.com/protect.
| >
| >"michas_pi" wrote:
| >| I get a stop error after Setup is finished copying
| files
| >| (the first time, not the second). the contents of this
| >| error is this:
| >|
| >| STOP 0x0000000A
| >| (0xFFE0F80C,0x0000001E,0x00000000,0x8042CB47)
| >| IRQL_NOT_LESS_OR_EQUAL
| >| Address 8042CB47 base at 80400000 DateStamp 304d5a76 -
| >| ntoskrnl.exe
| >|
| >| I have read the Knowledge Base article and it doesn't
| >| help :-(. I really don't want to pay for support, so
| I'm
| >| asking the community.
| >|
| >| Thanks!
| >
| >
| >.
| >
 
Three things:

1. My motherboard is a Gigabyte GA-7N400V Pro2. The link is this:
http://tw.giga-byte.com/motherboard/products/products_ga-7n400v pro2.htm
It came with only a CD and no floppy, so I can't install any controller card driver. I also have a Maxtor 80GB 7200RPM 8MB cache EIDE hard drive, an ATI Radeon 9600SE AGP X8 video card, Dual Channel 512MB PC3200 RAM, and an AMD Athlon XP 2600+ processor (actual speed is between 1.9 and 2.3 Ghz). I hope this clarifies the topic.
2. In the BIOS (AWARD and it the very latest BIOS update already installed), I selected Fail-Safe Settings. This changed the FSB to 100Mhz. I also turned the built-in sound off, just in the case of any conflicts.
3. I found a KB article (171003) that said that the STOP error could be caused by faulty RAM (any kind of memory, like CPU L1 and L2 cache, DDR, video memory, etc). So i replaced the DDR RAM with the same kind. Same problem. Then I replaced the ATI video card (it had 128MB DDR memory, that's a lot of space for error) with a 3dfx Voodoo3 3000 16MB PCI video card. Now, Windows 2000 Pro installed without a problem!

The morale:
Could it have been the video card and/or the BIOS settings?

Conclusion:

I would love to know the answer to the morale, because I don't want to be stuck with a crappy video card and crappy FSB (the motherboard is capable of 400Mhz).

Any help is appreciated!

Thanks!
 
Nevermind, the same error appeared after I tried to repair Windows 2000 (using the setup CD) because the PC just started to restart repeatedly. Man, I thought this was really gonna work :-(.

Any help is still welcome!

Thanks!
 
Back
Top