Link to home
Start Free TrialLog in
Avatar of ZyncFinger
ZyncFinger

asked on

Problems installing WinXP Pro

I'm having a strange problem trying to do a fresh install of Windows XP Pro (SP2).

Brand new motherboard (ASRock 4CoreDual-VSTA), updated with latest BIOS from April 2007.
Pentium-D-930 3.0 GHz dual core.
Brand new, freshly formatted WD 320 GB EIDE HDD (attempting to install on 40 GB partition).
2 GB RAM.

When I boot to the install CD (brand new, legitimate version), setup starts normally, but soon starts telling me that it is unable to copy a series of files. Here's the complete list:

mdwmdmsp.dll
nikedrv.sys
rio8drv.sys
riodrv.sys
spnike.dll
sprio600.dll
sprio800.dll
srgb.icm
streamci.dll
tosdvd.sys
tsbvcap.sys
tsbyuv.dll
usbcamd.sys
usbcamd2.sys
vdmindvd.sys
wowfax.dll
wowfaxui.dll
fsvga.sys
paqsp.dll
usrcntra.dll
usrcoina.dll
usrdpa.dll
usrdtea.dll
usrfaxa.dll
usrlbva.dll
usrmlnka.exe
usrprbda.exe
usrrtosa.dll
usrsdpia.dll
usrshuta.exe
usrsvpia.dll
usrv42a.dll
usrv80a.dll
usrvoica.dll
usrvpa.dll

Without much choice in the matter, I hit ESC to skip each file. When the machine reboots to continue, it gets past the Windows splash screen, then goes to the blue screen telling me that my C: drive needs to be checked for consistency. Several messages about deleting corrupt fragments follow (sorry, they flash by quickly, so I don't have details), and into another auto-reboot.

On the next reboot, Setup initializes, then I get a popup saying:

"The procedure entry point SetBruslOrgEx could not be located in the dynamic links library GDI32.dll."

I hit OK. Setup tries to continue, but then I get this popup:

"The software you are installing for this hardware:

Battery

has not passed Windows Logo testing to verify its compatibility with Windows XP."

...followed by a warning that I should discontinue the installation.

I then get a bluescreen saying....

PAGE_FAULT_IN_NONPAGED_AREA
.
.
.
.
STOP: 0x00000050 (0xF05C371C, 0x00000000, 0x804E94A2, 0x00000000).

....and then the system hangs. Same thing happened when I tried the whole process a second time.

I also had similar troubles previously, when trying to do a fresh install on my old HDD using a *cough*backup*cough* version of XP (that I'd used successfully in the past), with minor differences in the files that were unable to be copied and the timing of the appearance of the bluescreen.

Any ideas? I've done several installs of various versions of Windows over the years and never run into anything like this.
ASKER CERTIFIED SOLUTION
Avatar of simpswr
simpswr
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Alan Henderson
Try a bootable Linux CD like Ubuntu:
http://www.ubuntu.com/getubuntu/download

If this works your hardware's OK, if it doesn't contact MS on their free phone and ask for a new CD.
simpswr - I remember a post from here a while back that talked about copying the install CD files to the HDD and then running the install from there.
Do you know that procedure?

Vic
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
younghv
"copying the install CD files to the HDD and then running the install from there"
As you'll be aware that's a great way to install Win 98. I've tried it with XP without success, might work from a separate HDD but I doubt it.
vallis - thanks for that.
There is something tickling my memory (what little there is of it) about a way to get past the 'failure to copy' problem.
If I get a chance I'll do some digging around.
Vic
. . "simpswr - I remember a post from here a while back that talked about copying the install CD files to the HDD and then running the install from there.
Do you know that procedure?" . .

Seems like I recall folks wanting to do that, but I don't recall any success story

Rich
Avatar of ZyncFinger
ZyncFinger

ASKER

Yikes.....bad memory, indeed. Tried running MemTest86 and it found over 300 errors. Guess I was putting too much faith in POST's assertion of "2048MB OK."
Yep . . the installation of XP stresses the memory and will show any weaknesses that would not otherwise show up