Winxp Dell Dimension 9100 will not boot

  • Thread starter Thread starter Richard
  • Start date Start date
R

Richard

I have a Dell Dimension 9100 desktop which will not boot.
Instead, I get a blue screen with this information:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical Information:
STOP: 0x000000D1 (0x00000018,0x00000002,0x00000000,0xF722F261)
iastor.sys - Address F722F261 base at F7220000, DateStamp 426d0c8c

Also, I cannot boot into Safe mode, nor Safe mode with Network nor
Command Prompt. I get a long list of drivers being loaded, and then
it freezes. The last loaded driver is Mup.sys. The iastor.sys
driver, referenced in the STOP code, is loaded 13 drivers from the end
of the list.

I tried Last "Last Known Good Configuration", but that did not help
either.
 
Richard said:
I have a Dell Dimension 9100 desktop which will not boot.
Instead, I get a blue screen with this information:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical Information:
STOP: 0x000000D1 (0x00000018,0x00000002,0x00000000,0xF722F261)
iastor.sys - Address F722F261 base at F7220000, DateStamp
426d0c8c

Also, I cannot boot into Safe mode, nor Safe mode with Network nor
Command Prompt. I get a long list of drivers being loaded, and then
it freezes. The last loaded driver is Mup.sys. The iastor.sys
driver, referenced in the STOP code, is loaded 13 drivers from the
end of the list.

I tried Last "Last Known Good Configuration", but that did not help
either.
Click to expand...

What happened before this started happening?

Updates?
Repair install?
Fresh install?
Drive update?
Software install?
Power surge?
Service Pack install?
 
Richard said:
I have a Dell Dimension 9100 desktop which will not boot.
Instead, I get a blue screen with this information:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical Information:
STOP: 0x000000D1 (0x00000018,0x00000002,0x00000000,0xF722F261)
iastor.sys - Address F722F261 base at F7220000, DateStamp 426d0c8c

Also, I cannot boot into Safe mode, nor Safe mode with Network nor
Command Prompt. I get a long list of drivers being loaded, and then
it freezes. The last loaded driver is Mup.sys. The iastor.sys
driver, referenced in the STOP code, is loaded 13 drivers from the end
of the list.

I tried Last "Last Known Good Configuration", but that did not help
either.
Click to expand...

http://www.intel.com/support/chipsets/imst/sb/cs-020825.htm

Mup.sys is the driver for the Multiple UNC Provider. It selects which
network client protocol to use when the target server is specified by a
UNC path (ex., \\hostname). Have you tried rebooting into Safe Mode but
*without* network support (in which mup.sys is involved)?

What have you recently installed that might affect the networking
components within Windows? A software firewall, HIPS (host intrusion
protection system), antivirus, antimalware, other security products,
network drivers, chipset drivers, firmware updates, etc?

Did you try reinstalling the chipset drivers for your motherboard?

Did you try booting in "last known good configuration"? If that doesn't
work and since you cannot otherwise get into Windows, the next step is
to perform an in-place upgrade (Repair install) to step atop your
current Windows installation.

Have a read at:

http://www.aitechsolutions.net/mupdotsysXPhang.html
 
Richard said:
I have a Dell Dimension 9100 desktop which will not boot.
Instead, I get a blue screen with this information:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical Information:
STOP: 0x000000D1 (0x00000018,0x00000002,0x00000000,0xF722F261)
iastor.sys - Address F722F261 base at F7220000, DateStamp 426d0c8c

Also, I cannot boot into Safe mode, nor Safe mode with Network nor
Command Prompt. I get a long list of drivers being loaded, and then
it freezes. The last loaded driver is Mup.sys. The iastor.sys
driver, referenced in the STOP code, is loaded 13 drivers from the end
of the list.

I tried Last "Last Known Good Configuration", but that did not help
either.
Click to expand...
You will find some interesting info about these two drivers by searching the
internet.

iastor.sys is supposed to be an intel file.
mup.sys can cause a hang if there is anything wrong with the previous
drivers

I would first read all of the discussions of iastor.sys and its assorted
problems. In all likelihood, I would conclude that the copy on my system is
corrupted, and I would download a new version from intel.

Then, I would reboot the system to see if it will complete the boot.

And, you ask, how can I do this if the system won't boot?

Since it is clear from all this that you are now using some other system for
posting, you should download the driver file to the desktop of this
computer.

Then, you remove the system disk from the problem computer and install the
disk in a USB enclosure. Install the now portable drive to your working
system. Determine where all of the copies of iastor.sys lie on the disk
from the problem computer. Install the new version of iastor.sys to all of
these locations. You ought to make a backup of the system disk before doing
all of these actions.

Now, restore the system disk back into your Dimension and see if it will
boot. Yes, it is a lot of work.

I my case, if my systems have this problem, I would restore the entire disk
from an ATI archive which predates the existence of this problem. Such
problems as this are a very good reason for making backups on a regular
basis.

Jim
 
Jim said:
You will find some interesting info about these two drivers by searching
the internet.

iastor.sys is supposed to be an intel file.
mup.sys can cause a hang if there is anything wrong with the previous
drivers

I would first read all of the discussions of iastor.sys and its assorted
problems. In all likelihood, I would conclude that the copy on my system
is corrupted, and I would download a new version from intel.

Then, I would reboot the system to see if it will complete the boot.

And, you ask, how can I do this if the system won't boot?

Since it is clear from all this that you are now using some other system
for posting, you should download the driver file to the desktop of this
computer.

Then, you remove the system disk from the problem computer and install the
disk in a USB enclosure. Install the now portable drive to your working
system. Determine where all of the copies of iastor.sys lie on the disk
from the problem computer. Install the new version of iastor.sys to all
of these locations. You ought to make a backup of the system disk before
doing all of these actions.

Now, restore the system disk back into your Dimension and see if it will
boot. Yes, it is a lot of work.

I my case, if my systems have this problem, I would restore the entire
disk from an ATI archive which predates the existence of this problem.
Such problems as this are a very good reason for making backups on a
regular basis.

Jim
Click to expand...
Also, sometimes this error is associated to bad memory. There is a free
memory tester on the internet.
Jim
 
Back
Top