Problem Setting Up Windows

[mrmann14]

I started reformating by brother's computer, and in the reformat phase, it froze at 20%. I restarted the computer and I kept getting the message, "The file I386/Ntkrnlmp.exe could not be loaded. The error code is 7". I searched on google and found the Microsoft Knoledge Base article on it. I followed the solution, but still got the same error.

I went into Fdisk and deleted all the partitions and reformated into FAT32.

So I decided to try and replace the CD Drive. I put in a new CD-ROM Drive, and ran the reformat again. This time it went past the Ntkrnlmp error, so I went into the rescure center, and ran chkdsk /r and it just said "The Volume appears to contain one or more unrecoverable problems." But I ran the reformat just to see what happened.

This time it completed the reformat phase, but when it started the setup right after, it said "Setup cannot access the CD containing the Windows XP Installation Files."

I'm almost positive it is not the the Windows XP disk because I reformated my other computer the day before I started this one. I'm just wondering if it is a faulty HD or if it's something else?

 

[mrmann14]

No one?

 

[thescreensavers]

plug it in ur desktop and in my computer find the drive right click it and format,Also You should Try to copy your xp cd and try the copied version, Is the cd scratched up? your cd is probly screwed up so if you can copy the disc it can sometimes it will work. did you try cleaning the cd?

 

[mrmann14]

I did a full low-level format from the maxtor diagnostic tool, but I was still unable to install 2 seperate disks of XP (mine, and my uncle's). So I decided to install Windows 98 to see if that would install and it did. So I guess I narrowed the problem down to the XP CD.

 

[ElFenix]

sounds like a bad cd to me

 

[Bozo Galora]

Yet again - another post with no system or O/S info.
there ought to be a rule here: no info - no answer

There is prob nothing wrong with your CD, it could be mobo bios/bios ACPI setting (and APIC) and SP vers of your O/S. Win 98 has no advanced ACPI or multi-core. NT Kernal Multi Proccessor could mean you are trying to load dual core or multi ACPI for non multi ready mobo.

There is also the new bug - have to set HDD (SATAI??SATAII??IDE??) in bios as "large", not auto or LBA on some mobo. I am also unclear if you checked Maxtor for bad sectors.

(Quote)
NTKRNLMP.EXE "The error code is 7"
http://tooh.blogspot.com/2006/01/ntkrnlmpexe-error-code-is-7.html

You said you had dual processors? NTKRNLMP.EXE is a special version of the Windows NT kernel that allows you to use more than one processor if your version of Windows permits -- and currently all versions of Windows except Windows XP Home Edition permit it.
Chances are, the copy of the multiprocessor kernel on the floppy disk got corrupted. That's what a 7 error usually means. So how to bypass this? At the beginning of the setup process, it asks you if you need to use any special SCSI drivers (scuzzy of them, I know ) by hitting F6. Two almost-entirely undocumented other features can be activated at that point. If you hit F7, then Windows Setup doesn't do any special detecting at all: it assumes your computer is single processor with no power saving features (you can change this later on from Device Manager) and no "wierd" SCSI drivers, just "normal" ones, and uses the appropriate kernel and drivers. If you hit F5, then you can select a specific Hardware Abstraction Layer and Kernel to use for the install.
When you start Setup and it asks you for SCSI drivers, hit F7. NTOSKRNL.EXE will get loaded instead of NTKRNLMP.EXE, and only a single processor will be used. Once Windows Setup is successful, and assuming you've got a Windows 2000 CD, you then open Device Manager, select the Computer object, select the item under it, and update the drivers to "ACPI-compliant Multiprocessor Computer." You will now regain your previous dual processor goodness

You also have to rum memtest86+ from floppy
http://www.trap17.com/index.php/error-i...ws-xp-error-7-ntkrnlmp-exe_t27488.html

Turn on ACPI on your unknown mobo bios, slipstream XP SP2 into your unknown XP CD, using a SP2 pak you download now, not one you downloaded 2 years ago

I guess you have seen these.
http://support.microsoft.com/default.aspx?scid=kb;en-us;812580&Product=winxp
http://support.microsoft.com/kb/318729/EN-US/


bleh

 

[mrmann14]

Sorry about that. The specs for his ultra savings comp are:
Asus P4S800-MX
512MB of Ram
Celeron D 2.26ghz
Asus FX-5200 128mb

What else do you need to know?

 

[Bozo Galora]

O.K. I'll repeat it all again.....

What are and where are ALL HDD's in system - exactly, especially Maxtor (Maxtor tells me nothing)
What XP version exactly
Did you test RAM? How many sticks?
Are your XP's burnt by you or retail pressed?
Did you try reset CMOS for one hour, unplugged?
Have you overclocked system before?
Did you try bios failsafe defaults?
Have you changed CDR cable? Is it firmly down in mobo molex?
Is your CDR on cable alone as master?
What BIOS are you using on your SIS chipset mobo?
Did you reformat because of previous problems? What were they?
Do you have APCI on or off in bios, APIC?
Is your Maxtor detection set to "Auto" "large" or "LBA" in bios?
Have you tried using 6 floppy XP setup disks?
Can you create a second partition on your Maxtor and try a new install with XP CD to make a multi-boot - XP on that partition with the 98 already on "C"?

 

[mrmann14]

Originally posted by: Bozo Galora
O.K. I'll repeat it all again.....

What are and where are ALL HDD's in system - exactly, especially Maxtor (Maxtor tells me nothing) One Internal Maxtor 40gb ATA133 IDE HD
What XP version exactly Windows XP Pro, not with service pack 2
Did you test RAM? How many sticks? 2 sticks of 256 pc-3200 infineon. Not tested
Are your XP's burnt by you or retail pressed? Burnt
Did you try reset CMOS for one hour, unplugged? No
Have you overclocked system before? No
Did you try bios failsafe defaults? No
Have you changed CDR cable? Is it firmly down in mobo molex? The Cables are fine.
Is your CDR on cable alone as master? Yes
What BIOS are you using on your SIS chipset mobo? How do I check, it is just the default.
Did you reformat because of previous problems? What were they? Just some slight system hanging, nothing to serious.
Do you have APCI on or off in bios, APIC? I looked for APCI or APIC and all I saw was the option to set it to APIC or PIC
Is your Maxtor detection set to "Auto" "large" or "LBA" in bios? I couldn't find this option.
Have you tried using 6 floppy XP setup disks? No
Can you create a second partition on your Maxtor and try a new install with XP CD to make a multi-boot - XP on that partition with the 98 already on "C"? I can Try

Heres where I'm at now. I replaced the memory with a stick of 512mb from my current computer and tried the windows XP installation with my uncle's CD (again burnt). This time it got through the whole reformat process, copied all the files to the HD, but when it restarted to run the installation from my HD, I got the message

"STOP: c0000221 {Bad image checksum}
THe image wow32.ddl is possibly corrupt. The Header does not match the computer checksum"

 

[Nocturnal]

Have you tried running Memtest? If not, download and burn the ISO to a CD. If that it goes through for a few passes with no errors then go to Maxtor's website and download and burn their diagnostic software which can also be burnt as an ISO to create a bootable CD. Use that software to rule out the hard drive. When you use the Maxtor diag, make sure you do an advance test. That will take a little longer than the quick test but it's more thorough.

 

[Bozo Galora]

wow allows for 16bit applications to run in 32 windows. Either the 16bit app/driver has become corrupt and is crashing wow32.dll or it is the dll itself that is corrupt. Known bug when upgrading from 98 to XP.

In your case, I would not use XP to partition, format - use the maxtor install utility from floppy - and make sure "C" is active.

40GB Maxtor means an ooold drive - I would use it for a doorstop.

You really should just go to Fry's for a legit pressed copy of XP WITH SP2 in it.
http://www.newegg.com/Product/Product.asp?Item=N82E16837102062
Download and install BIOS 1011C (9-22-05)
http://dlsvr03.asus.com/pub/ASUS/mb/sock478/p4s800-mx/1011C.zip
May or may not help - you loaded Win98 O.K. with the celeron D CPU
heres ASUS d/l search page to double check my link...........
http://support.asus.com/download/download.aspx?SLanguage=en-us
The current loaded bios code version is on the first boot up black screen at the bottom
Or, in your Win98, SiSoftSandra (free vers.) can tell you.

Edit: I think if you downloaded SP2 from MS and used nlite to slipstream it into your XP Pro it may fix all your coruuption probs, assuming you dont wish to buy a new XP.

http://www.nliteos.com/nlite.html
http://www.tacktech.com/display.cfm?ttid=297

 

[JimPhelpsMI]

Hi, Sounds like a bad CD reader or Disk. Reader or Disk can have reading problems anywhere on the disk. Usually works great until you reach that spot. Jim

 

[Bozo Galora]

Quote from orig post:

"So I decided to try and replace the CD Drive. I put in a new CD-ROM Drive"

 

[pkrush]

Almost EVERY time I've had a problem with an XP install, it's been bad RAM. The Windows 98 setup's probably working because it doesn't use as much RAM for copying files. Go to Memtest.org, download the ISO, burn it to a CD, boot the machine off of it, and let it run for a few hours to see if any errors come up.

 

[mrmann14]

I've ran Memtest on the current RAM i'm using = No errors
I've tried multiple XP disks
I've ran the Maxtor diagnostic, which came back with no errors (and I've tried a couple different pieces)
I used the software to low level format it
I've slipstreamed SP2 into my XP Home disk using nlite. (When I try to get the XP source files from any of the Pro disks, I get erros when trying to get files from the i386 folder.)
I updated the bios
I tried pressing F7 to bypass the ACPI thing
I tried setting the HDD to Large instead of auto/LBA.
When I try to install windows with the XP Home disk I get "file \i386\vgaoem.fon could not be loaded. The error code is 7", but the file that gets the error seems to change some times. This comes up before you get the to do the partitioning thing.
The XP Pro disks will go past the format, but during the part where it copies the files onto the hard drive, I get _______ file could not be copied and I get the option to retry or skip the file. Someitmes when I retry the files, they'll work, but some times, I'll have to skip them.

This was the next thing I tried... I went with the pro diks, made a 5 gig partition, did the installation while retrying, skipping the files that didn't work. After I installed it, I got a very minimal version of XP, there were no themes or desktops to choose from or basicly anything in the programs menu. But this allowed me to go put in the XP Home (slipstreamed w/SP2) disk and installed it from there, I chose new installation, and then it went and installed it like normal from the disk and it read all the files and everything. When I got the computer set up, I installed partition magic to delete the partition that was there for the XP Pro, but when I reset it, I got an error message in PM saying "Cannot lock drive, error 27," and then it reset the computer and the problem came back and I couldn't get into windows again and I get the same problems again.

 

[Bozo Galora]

cannot lock drive means just that - you have some process running and part magic cannot establish current situation - you cant fix a transmission while its running.
You could try safe mode, but first run cntrl-alt-del to see what proccesses are running now, and how much CPU usage. Many backup software has some sort of locking "freezing" O/S in place option. Always run PM from CD or floppy, not windows.
Iam also curious as to what OEM means to you - Windows OEM or a prebuilt PC with its OWN OEM disc with windows and all its drivers???
How and where did you get the disc?? Was your brothers PC a prebuilt?
Since your brothers system is old, I am also wondering if its a boot sector virus.
After trying everything else, as a last resort, to wipe partition table, you can load win98 boot floppy and type fdisk_/mbr [ENTER] twice
I really think if you buy a new HDD, not ATA133, not Matrox, your probs will go away.
Maxtor also has (had) a utility to cut back ATA133 to ATA100 on drive

Note: You can also set BIOS to "halt on no errors" which may give you BSD or logs in event viewer to explain things.

Edit: Doing a "new install" over an old one always puts an additional O/S entry in boot.ini
Always best to do Repair install.

You will have to go to recov console and do a C: bootcfg_/rebuild
http://support.microsoft.com/kb/q291980/

Note that boot.cfg does not wipe the mbr, boot.ini, ntdetect, - just rebuilds it.



Kinda funny - another thread here almost exact same thing.

 

[mrmann14]

Originally posted by: Bozo Galora
cannot lock drive means just that - you have some process running and part magic cannot establish current situation - you cant fix a transmission while its running.
You could try safe mode, but first run cntrl-alt-del to see what proccesses are running now, and how much CPU usage. Many backup software has some sort of locking "freezing" O/S in place option.
Iam also curious as to what OEM means to you - Windows OEM or a prebuilt PC with its OWN OEM disc with windows and all its drivers???
How and where did you get the disc?? Was your brothers PC a prebuilt?
Since your brothers system is old, I am also wondering if its a boot sector virus.
Try win98 boot floppy and type fdisk_/mbr [ENTER] twice
I really think if you buy a new HDD, not ATA133, not Matrox, your probs will go away.
Maxtor also has (had) a utility to cut back ATA133 to ATA100 on drive

Note: You can also set BIOS to "halt on no errors" which may give you BSD or logs in event viewer to explain things.

Edit: Doing a "new install" over an old one always puts an additional O/S entry in boot.ini

You will have to go to recov console and do a C: bootcfg_/rebuild
http://support.microsoft.com/kb/q291980/



Kinda funny - another thread here almost exact same thing.

I built his comp. It's not that old, maybe old technology, but not old like life of the parts.

I don't get what you mean by the OEM comment...

If I were to get a new hard drive, should I get just a ATA100 drive? (obv not maxtor this time round )

I'm running memtest on the ram in there, and it's had 3 passes right now with no errors.

I guess I'll try the /mbr thing and see if that does anything.

 

[Bozo Galora]

dont do the mbr thing yet - I edited my post while you were posting - see the bootcfg_/rebuild thingy

Buy a seagate 160-200GB ATA100 7200.7 drive for around $40 in hot deals forum.
Dont buy a 7200.8 or 7200.9
Or you can wait 2 weeks for the seagate 7200.10 perpendicular drives

 

[Minerva]

Seagate 7200.10's are out now.

They're the flagship model (750GB). I have two enroute and am curious as to how well it performs. My 300GB 7200.9 died after three weeks of light use.

 

[Bozo Galora]

Yeah, I know the 750's are out, but I'm sure poster doesnt want to spend $520
AFAIK the low end job will be $108
Since the magnetic domains are packed a lot closer for same 7200 RPM - they should be lots faster.

 

[mrmann14]

Now, I put the troubled HDD in my healthy computer to see if I could get it to install Windows. It installed fine, using the Windows XP Pro and XP Home edition CDs. I guess I've kinda ruled out the possibility that it is the HDD, the CD drive and CD, and the memory because I've used the memory that from my healthy computer on the troubled PC and it still doesn't work.

What is left to test out? The Mobo and the CPU? My healthy and troubled PC both use the same intel socket 478. Would it be best to swap out the CPU and Mobo one at a time from the healthy PC to see if that is the problem, or is there something else I should test out too?

 

[Bozo Galora]

I would go for the mobo, SIS is oddball stuff
the only thing left after that is the PSU - last thing I would think of is CPU.

Edit: could be mobo shorting out on case

(But you just know its gonna be something really stupid - LOL)

 

[mrmann14]

I put my good mobo in there and voila it worked
Sol I took the mobo back to the shop that I bought it at, and now they're going to send it back to asus and they'll either repair it or send a new one, which will take 2-3 weeks apparently. :disgust:

BTW, thanks a lot for the help everybody, in particular bozo

 

[Billb2]

Originally posted by: Bozo Galora
O.K. I'll repeat it all again.....

http://www.ocforums.com/showthread.php?p=4481354#post4481354
Post #9