Irql_not_less_or_microsoft_sucks

[ShAdOWmoNkX]

Hello, My Master Uber Geeks :D ,

It was suggested that I break my insanely large set of questions into a few posts to make them easier to, er, digest. Again, sorry for all the questions -- but I'm really baffled and you guys are nothing short of brilliant!

Here's the *SECOND* in a three-part series. And the good news -- it's free! No MPAA to bitch and moan! Popcorn is an additional $3.50 per kernel. Otherwise, go with Linux (cough, kernel, cough ... pun).

I can't do a clean install of WinXP on someone's computer. The computer locks up at 89% during the NTFS full format, or if I do the quick NTFS format, it locks up while installing the setup files.

If it miraculously manages to get past that, I get one of two BSOD's:

IRQL_NOT_LESS_OR_EQUAL

or

MEMORY_MANAGEMENT

I know it has to do with the BIOS settings as the RAM is fine and this person had Windows 98 installed successfully before (aside from many driver issues) ... but which BIOS setting is to blame or at least most likely to cause this problem? There are a LOT of options for RAM to the point it's mind-boggling, so it's likely SOMETHING is wrong there, even though the default BIOS settings are being used.

It's worth noting that I personally had a similar problem a long time ago when I had a different BIOS/mobo than this person and was trying to install the then-new Win2K, but MY problem had to do with having ECC enabled in conjunction with a sensitive MRH -- not a good mix. Causes RAM to projectile vomit all over itself.


Many thanks and cheers,

-ShAdOWmoNkX :)

[ski]

Check these for a possible solution:

http://www.memtest86.com

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q311564&

[ShAdOWmoNkX]

Already scannned the RAM, as I may have mentioned ... same program, incidentally.

Not upgrading; instead is a clean format/install. Hardware is compatible afaik and the BIOS is latest revision. Mobo supports ACPI, so it *should* work with XP.

I think it has to do with the RAM/BIOS settings. Not sure which/why, tho ... which are usually responsible for this kinda thing?

Thank you!

-ShAdOWmoNkX :)

[no-mbr]

Just as a "diag" tool, could you copy or backup the current system and try an install over the current OS.

What about trying an install on FAT32? Convert later?

I had a similar problem once, it it turned out to be the modem. I pulled a "working modem" out --and the install completed successfully, later I had to manually add in a Comm port and the modem....

I'd pull hardware and disable ACPI in the BIOS, just for kicks...

Like to hear from you when you diascover the problem..

[ski]

Are you sure all of the hardware components are compatible?

[mjc]

Generally the IRQ_NOT error is a BIOS problem.....the BIOS is not compatible with XP and needs an update or to be installed without ACPI mode....XP wants complete control, it interacts directly with the hardware like the BIOS and if the BIOS is not able to relinquesh control the it pukes....

[ShAdOWmoNkX]

Hmm, I haven't checked the Microsoft Hardware Compatibility List, but it's not to be trusted anyhow -- it's not exhaustive and it's generally outdated (also doesn't take into account slipstreaming the latest Service Pack, but I haven't done that anyways...).

Ack, it's a small board and only like two PCI slots, believe it or not! One card is the add-in video card, the other is the sound card.

ACPI is disabled, and doubt it's the video card since it worked before. Sound shouldn't be a problem as it's not even in during the install (instead, my ethernet card is in this person's computer so as to update/network it easily -- and it's a working, compatible card, I'm sure).

That leaves a conflict, BIOS or hardawre problem. Not sure. Talk about agony!

Will definitely apprise you guys as to the outcome, no-mbr -- please keep the great ideas rolling in! I'm sure they'd help someone else someday! :)

Thanky,

-ShAdOWmoNkX

[sarshad]

Hi there!

I don't know much about IRQ's or bios settings which might cause this problem but I have faced a similar problem with XP. So just a suggestion based on what I had done. Clean install Win 98 and then immediately upgrade to Win XP <from within 98>. Dont bother to install the various peripheral drivers in 98. You can later change your drives to NTFS if required. I have no clue why this might work... but it did work for me.

Good luck!

[ski]

I haven't checked the Microsoft Hardware Compatibility List, but it's not to be trusted anyhow

Base on your replies to your 3 recent posts so far, it appears to me that you do not trust anyone.

[no-mbr]

Why not try a different drive? Try a dir/s of the CDROM from root as disc/file check....see if there are other ways to create disk/IO errors.
Manually set the dirve to P mode....

[gwallen4]

I recently had a WD 40 GB drive on an older computer whose bios wouldn't recognize the large drive. So E-Z bios was installed on the HD by the Western Digital installation software to allow the whole 40 GB to be seen.

When I used the drive in a new computer (one that would recognize the whole 40GB), I had a heck of a time trying to format the drive. It would get to a certain point, then hang. Repartitioning and reformatting using WD installation utilities didn't work either.

I'm still not sure how I fixed it, but a some point I wrote zeroes to the whole drive and later was able to partition it and format the partitions. I'm not sure if zeroing the drive actually did anything or if I just diddled with it until it gave up.

Anyway, the point I'm trying to make is that prior partitioning and changes to the master boot record can make reformatting difficult.

You might try the manufacturer's installation software for the drive and see if you can use that to do a NTFS format. Then do your WinXP install.

[malcore]

My little bit here, and I do mean "little".

Sometimes clearing the CMOS will help. I would also leave out the sound card and the network card until installed.

Have you disabled any comm ports and USB in BIOS? Having these enabled can sometimes cause a Windows install to crash.

[ShAdOWmoNkX]

Hey Guys,

Here's an update that should help anyone with similar problems...

As mentioned before, the computer locked up at 89% during a Full NTFS format. If instead you do a Quick Format (one wherein each write isn't verified, so it thus eliminates extenuating problems), it locks up when Windows is loading the Setup files to begin the installation.

Guess what? -- and I can't believe I didn't see it before:

This computer has TWO problems!

*FIRST PROBLEM*

The 89% "lockup" was NOT a lockup despite my thoughts elsewise -- the Format just slowed down incredibly. Know why? Bad clusters at the end of the hard drive. Tons of them.

I figured this out for myself when I tried to intall Windows 98 as per the computer owner's request instead of putting XP on it.

Heh, a Full Format with the Windows 98 Boot Disk stopped at 89%, too. "Trying to recover allocation resource," or some-such. Cluster after cluster after cluster. It would have taken hours to do (I didn't let it run all the way through, but "hours" might even be generous)!

I wanted to do a Quick Format so that the bad sectors would be ignored until I had a chance to deal with them properly. Incidentally, you can't do a Quick Format with the Windows 98 Boot Disk.

So I got creative and instead did a quick FAT32 format with the Windows XP CD-ROM and immediately shut the computer down when it finished, before it had a chance to begin installing the setup files.

Giggle.

I then booted up from the Windows 98 Boot Disk and started ScanDisk manually ("scandisk C: /autofix /noprompt /surface" etc.).

It whipped through the surface scan. `Til it got to the end. Man, it would have taken hours just to fix this, too! Which isn't surprising since a Full Format essentially does the same thing (mark bad sectors as such) and would have taken just as long.

Well, I came up with a quick `n dirty solution: note where the first bad cluster starts, write it down, clear hard drive with Windows XP CD-ROM, partition drive to "end" right before bad clusters start, and voila! A working drive.

WARNING: Despite the "solution," running a drive that is known to be failing is done at yer own risk! It's entirely probable that anything on it might end up being corrupted and/or lost when it fails completely or as it fails.

I told the computer owner, "You have a bad hard drive, and there are many reasons this could happen. Old age, too much stress, power outa-"

"...Well, actually the power went out here for a few hours while my Son was working on the computer..."

Yip.

Ergo problem. This guy is getting a new drive. He bought it with my help -- online, of course.


*SECOND PROBLEM*

The IRQL_NOT_LESS_OR_EQUAL thing was the "second" problem -- know what caused this? You guessed it; incompatible BIOS. There's a trick to beating this:

Turn off ACPI in the BIOS. When booting the Windows 2000/XP CD and it asks if you would like to load other SCSI drivers by hitting F7, hit F5 instead. Shortly after, it will prompt you to select the kind of computer you have. Pick "Standard PC."

Problem solved.

Sigh, no ACPI, but on the plus side, you can enable APM in Windows, and it is at least better than going back to the good `ol days of AT power supplies/mobos (as opposed to ATX).

That's that. For you geeks, hope this adds to your knowledge store, and for those suffering similarly, I hope this helps fix your problem!

Cheers,

-ShAdOWmoNkX