XP Pro does not boot in safe mode

Toshiba intel / Spm30
January 24, 2009 at 04:39:49
Specs: WinXP Pro SP3, P4 1.8G/512MB
While browsing in normal mode I suddenly got the blue screen of death with the following information:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
Technical Information:
0x000000D1(0x73656CD7, 0x00000002, 0x00000000, 0xF8219678)

The system would then not boot in normal mode and when I tried booting in safe mode, it hung at the following command:

multidisk(0)disk(0)rdisk(0)partition(1)\WINDOWS\SYSTEM32\DRIVERS\agp440.sys

I then boot it from a bootable XP cd for repair and ran the chkdsk command on C:\windows but still it did not boot properly.

I tried all options for booting including the last known good config and debugging mode but could not boot.

Could anyone please advise how can I boot properly without formatting the system? Thanks for any help


See More: XP Pro does not boot in safe mode

Report •


#1
January 24, 2009 at 05:02:09
Find a list of STOP MESSAGES(BSOD) here:
http://aumha.org/win5/kbestop.htm
Then find and click D1 that is on the right side.

Report •

#2
January 24, 2009 at 06:05:20
Thanks for replying Chuck. The website refers to an update installation to overcome DRIVER_IRQL_NOT_LESS_OR_EQUAL error but in the first place how do I boot into safe mode or normal mode as for now I can't even get windows booted.

Report •

#3
January 24, 2009 at 06:17:54
Run a Windows Repair (not the Recovery Console.)

"So won’t you give this man his wings
What a shame
To have to beg you to see
We’re not all the same
What a shame" - Shinedown


Report •

Related Solutions

#4
January 24, 2009 at 07:12:40
I forgot to tell that when the BSOD appeared initially, I was able to reboot in normal mode and then I enabled the chkdsk option on my C:\ drive after which the system re-booted but it started giving the DRIVER IRQL mssg from then onwards and I couldn't boot into any mode.

I've run windows repair from a bootable cd (not using the console recovery option) but upon re-boot it again displays the BSOD and I can't go any further.

Could the chkdsk enable option be disabled from the command prompt or anything fixed in the boot.ini to fix this ?

Any other suggestions......thanks again!


Report •

#5
January 24, 2009 at 11:39:05
The two most common causes are bad RAM or a corrupt driver.

Report •

#6
January 25, 2009 at 03:10:59
How do we fix it if that's a corrupt driver?

Report •

#7
January 25, 2009 at 07:27:57
If it's a driver issue, then a Repair should fix it. You didn't say what happened immediately preceding this problem.

"So won’t you give this man his wings
What a shame
To have to beg you to see
We’re not all the same
What a shame" - Shinedown


Report •


Ask Question