[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 743
  • Last Modified:

XP Home SP2 boot problem

Windows XP Home SP2

I had used the system config utility to set boot.ini to boot to safe mode with networking.

I was downloading Cleanup4, high speed connection. The download process froze.
I closed IE using "task manager". start > shutdown > restart.

At restart, I received the black & white "unexpected shutdown" screen with "safe mode", "safe mode etc", "last known good " & normal mode.
Selecting "normal" causes reboot.
Selecting "safe mode" causes reboot.
Selecting "last known good .. " causes the PC to continue the boot process. After the splash screen, a BSOD appear for less time than I can measure. I have tried to stop the action using "pause / break", but I lack co-ordination.

I slaved the drive into a different PC [ running XP Pro SP2 ], & ran error checking. No errors were reported.

During boot, I pressed F8 which gave me the option to "disable automatic restart . . .", which displayed the stop message.  

Driver_IRQL_Not_less_than_or_equal
If this is the first time Yada yada yada
*** Stop:0x000000d1 (0x00000000,0x00000002,0x00000000,0x00000000)

Booting with the XP CD, repair > chkdsk /r > found & fixed errors.

Slaved drive into a different PC [ running XP Pro SP2 ], defrag > no problems.  

Scanned for viruses / spyware with Panda installed on different PC, no malware found.  

Slaved drive into a different PC [ running XP Pro SP2 ], I noticed no pagefile.sys .

Booting with the XP CD, repair > copy C:\boot.ini pagefile.sys   .  Now, I have C:\pagefile.sys  , 1KB in size.  

During boot, I pressed F8 which gave me the option to "disable automatic restart . . .", which displayed the stop message.
Stop:0x000000d1 (0x00000000,0x00000002,0x00000000,0x00000000)

I ran fdisk /mbr.

This is a Compaq Presario.  It has a hidden partition for system recovery.  F10 is supposed to be the key to access the OEM's system recovery, but the drive won't access the system recovery.  
I contacted Compaq tech support.  They have no useful suggestions.  

If I could offer > 500 points, I would do so.  

Thanks for your help.  

Edx15
0
edx15
Asked:
edx15
  • 9
  • 9
  • 4
  • +1
1 Solution
 
ISoulCommented:
Give this a try. I'm assuming that the network card is built into the motherboard. Go into the BIOS settings and disable it. See if you can boot up.
0
 
Expert4XPCommented:
The outlook for a complete recovery doesn't look good.  But you can TRY a XP Repair Install, which sometimes will get you going again.  You may have to re-install your applications.

Here's information on how to do it when booting from your xp startup cd:

http://www.michaelstevenstech.com/XPrepairinstall.htm

http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx
0
 
Expert4XPCommented:
>> *** Stop:0x000000d1 (0x00000000,0x00000002,0x00000000,0x00000000)

Do you have any USB devices connected?  Try booting without any.  I see several references from Google to this stop code relating to usb.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
edx15Author Commented:
Thanks for the replies.  

NB:  The reason for offering 500 points is because this issue is very difficult.  

I had seen many references to USB devices, also.  

No, there are no USB devices connected.  I am running a HDD [ Seagate ] diag now
[ Seagate diag ].  

If that is negative, I'll go into the bios and try to disable the USB controllers on the motherboard.  I will disable as many items as possible in the bios.  Yes, the USB, sound, video, & network chips are "integrated".  I'll disconnect the power & ribbon cables to the optical drive & FDD.  

I ran ram diags earlier, for hours.  I'll look for a replacement stick.  

No offense, but I don't consider a re-install as a legitimate solution.

Thanks again.  

Edx15
0
 
MereteCommented:
Can you get back into safemode?
Or run the recovery console again.
at the safemode desktop/r/click my computer properties advanced/startup and recovery/settings/edit>
=====================================================
SYMPTOMS
When you attempt to start Windows XP, you may receive one of the following error messages:
Windows could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and disk hardware.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
-or-
Windows NT could not start because the following file is missing or corrupt:

Winnt_root\System32\Ntoskrnl.exe

Please re-install a copy of the above file.
-or-
Winnt_root\System32\Hal.dll missing or corrupt:

Please re-install a copy of the above file.
Additionally, you may experience one or more of the following behaviors: • If you start the computer to the Recovery Console, a command prompt may appear with no option to log on to the Windows installation.
• If you try to access the Windows folder, you may receive the following error message:
Access denied.
• If you try to perform a Repair operation from the Windows XP CD-ROM, the Windows installation is not detected and you cannot repair Windows.

CAUSE
This behavior can occur if any or some of the following conditions are true: • The Default value in the [Boot Loader] section of the Boot.ini file is missing or invalid.
• Windows XP is not installed in the location specified in the Boot.ini file.
• The Ntoskrnl.exe file is missing or damaged.
• The partition path in the Boot.ini file is not set correctly.
• General hardware failure.

RESOLUTION
To resolve this issue, use either of the following methods.
 Back to the top

Method 1
Edit the Boot.ini file to restore or correct the Default entry and to ensure that the other entries in the [Operating Systems] section of the Boot.ini file point to the appropriate directories.

For additional information about how to edit the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
289022 (http://support.microsoft.com/kb/289022/EN-US/) HOW TO: Edit the Boot.ini File in Windows XP
 Back to the top

Method 2
Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file: 1. Use the Windows XP CD-ROM to start your computer.
2. When you receive the message to press R to repair Windows by using the Recovery Console, press the R key.
3. Select the Windows installation that you want, and then type the administrator password when prompted.
4. Type bootcfg /rebuild, and then press ENTER.
5. When the Windows installation is located, the following instructions are displayed:
Add installation to boot list? (Yes/No/All)
[Type Y in response to this message.]

Enter Load Identifier:
[This is the name of the operating system. Type Windows XP Professional or Windows XP Home Edition.]

Enter OS Load options:
[Leave this field blank, and then press ENTER].
After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.

After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.  
For additional information about how to edit the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
289022 (http://support.microsoft.com/kb/289022/EN-US/) HOW TO: Edit the Boot.ini File in Windows XP

Method 3
1. Start the computer by using your Windows XP CD-ROM. Press any key to boot from the CD.
2. After the setup files are finished loading press R to repair using Recovery Console.
3. When you are in the recovery console, select the installation to log on to (usually number 1), and then press ENTER.
4. Login to the Administrator account by typing the password for this account, and then press ENTER.
5. At the recovery console command prompt, type the following command, and then press ENTER:

For Uni-Processor systems:
expand cd-rom:\i386\ntoskrnl.ex_ drive:\Windows\system32
For Multi-Processor systems:
expand cd-rom:\i386\ntkrnlmp.ex_ drive:\Windows\system32\ntoskrnl.exe

Cd-rom is the drive letter of your CD-ROM drive, and drive is the drive letter of the hard disk on which windows is installed.
6. If you receive a prompt to overwrite the file, press Y.
7. Type exit, and press ENTER at the command prompt.

Method 4
Start the computer by using the Recovery Console, and then run theCHKDSK /rcommand.

Note You do not have to include the /p switch in the Chkdsk command-line because the /r switch causes the Chkdsk utility to locate bad sectors and recover readable information. This command implies the /p switch..  

MORE INFORMATION
If the Default value in the [Boot Loader] section of the Boot.ini file is missing, Windows XP displays a new entry, Windows (default), on the OS Loader (boot loader) menu, and then defaults to the new entry. The Windows (default) entry points to the following path to load Windows XP:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
For additional information about the Boot.ini file, click the article number below to view the article in the Microsoft Knowledge Base:
102873 (http://support.microsoft.com/kb/102873/EN-US/) BOOT.INI and ARC Path Naming Conventions and Usage
For additional information about Recovery Console in Windows XP, click the article number below to view the article in the Microsoft Knowledge Base:
307654 (http://support.microsoft.com/kb/307654/EN-US/) HOW TO: Install and Use the Recovery Console in Windows XP
 


--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Windows XP Professional for Itanium-based systems
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition


http://support.microsoft.com/?kbid=314477
0
 
MereteCommented:
oops this may help you better, sorry I missed the fact you were using a Compaq, yeah these services are buggars for help.
Ok this one should solve it for you. Fingers crossed. And good Luck
Merete
======================================================
HP and Compaq Desktop PCs - Error: Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll
Printable version
http://h10025.www1.hp.com/ewfrf/wc/famiDocument?dlc=&lc=en&product=12455&cc=us&docname=c00044897

This document applies to HP and Compaq Desktop PCs that come with Windows XP.
When Windows starts, the following error message appears:
" Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll. Please re-install a copy of the above file."
Use the following steps to resolve this error:
Step 1: Opening a command prompt
This error prevents Windows XP from opening. This problem has to be addressed from a command prompt environment.
Use the following steps to open a command prompt environment:

Turn on the PC and press the F8 key repeatedly when the first screen appears.
The Windows advanced options menu appears.
Use the Up and Down Arrow and Enter keys to select Return to OS choices.
Select Microsoft Windows Recovery Console.
 NOTE:  If "Microsoft Windows XP Recovery Console" is not listed, restart the PC with a Windows XP CD, Recovery Console CD, or Recovery Tools CD in the top CD or DVD drive and open Microsoft Windows Recovery Console. If a Windows XP Setup screen appears when using Recovery Console CDs, press the R key to open the Recovery Console.

 NOTE:  If "Microsoft Windows XP Recovery Console" does not list and you do not have a CD with recovery console, try the following:

Turn on the PC, and press the F10 key repeatedly at the first screen.
At the Recovery screen, click Advanced Options.
Press the Alt + D keys at the same time to open a command prompt window and skip to step 5.
When the login prompt appears, press the number next to the windows version (minint or Windows) and type the logon password. Try pressing Enter if you do not know the password.
At the command prompt, type the following: diskpart
Press Enter, do one the following:
If a table of volume names appears, remember the drive letter next to the main drive volume name (usually D or H next to HP_PAVILION or PRESARIO) and press the Esc key.
If a diskpart prompt appears, type list volume, press Enter, remember the drive letter next to the main drive volume name (usually D or H next to HP_PAVILION or PRESARIO), type exit when done, and then press Enter.
 NOTE:  If the main drive volume name does not appear in the list, the PC needs to be recovered. For more information, refer to Performing a Full System Recovery in XP .  

Step 2: Restoring boot.ini
Use the following steps to replace the boot.ini file with the backup boot.ini file:
Type the following at the command prompt: X: (where X is the drive letter).
At the prompt, type the following: ren boot.ini boot.in2
Press Enter
At the prompt, type the following: ren boot.bak boot.ini
Press Enter
At the prompt, type the following: exit
Press Enter
The system automatically restarts. If Windows XP does not open, continue to the next Step.
Step 3: Editing boot.ini
If the steps above fail to resolve the error, use the following steps:
 NOTE:  The following steps use the recovery partition on the hard drive. If the recovery partition has been removed, these steps will not work and you should recover the PC using recovery discs.

Turn on the PC. When the initial logo screen appears, press the F10 key repeatedly until a message about starting recovery appears.
At the Recovery screen, click Advanced Options and then press the Alt and D keys at the same time to go to a command prompt.
At the command Prompt, type the following: diskpart
Press Enter and type the following at the diskpart prompt: list volume
A table of drive volumes and names appears.
Note the drive letter next to the main drive volume name (usually D or H next to HP_PAVILION or PRESARIO).
Type the following at the diskpart prompt: Exit
Press Enter and type the drive letter followed by a colon ( :) at the command prompt. For example, D:.
Press Enter and type the following at the command prompt: attrib -h -s -r boot.ini
Press Enter and type the following at the command prompt: boot.ini
The file opens for editing in Notepad. Edit the boot.ini file to read exactly as follows:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
 NOTE:  If your PC came with Windows XP Professional, edit the line referring to Home Edition under [operating systems] to read as follows: multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect  

Save and Exit from the menu.
Type the following at the command prompt: attrib +h +s +r boot.ini
Press Enter and type the following at the command prompt: Exit
Click Quit on the recovery screen to restart the computer.
The PC should now restart without the error message. If the error still persists, perform a full system recovery. For more information, see HP and Compaq Desktop PCs - Performing a System Recovery in Microsoft Windows XP " 
0
 
MereteCommented:
The PC should now restart without the error message. If the error still persists, perform a full system recovery. For more information, see HP and Compaq Desktop PCs - Performing a System Recovery in Microsoft Windows XP " 

http://h10025.www1.hp.com/ewfrf/wc/famiDocument?lc=en&cc=us&dlc=&product=12455&docname=bph07145
0
 
edx15Author Commented:
No.  I cannot boot to a desktop.  As I think I stated, I have tried safe mode, sm with networking, sm with command prompt, debugging, last known good .. , "disable automatic restart . . .", which displayed the stop message.  

Merete wrote:  "Turn on the PC, and press the F10 key repeatedly at the first screen.
At the Recovery screen, click Advanced Options".  
Edx15 replies:  See inital post.  "F10 is supposed to be the key to access the OEM's system recovery, but the drive won't access the system recovery."  

Seagate Diags found no problems [ extended test, not quick test ] with the drive.  

I do NOT receive the error message you referenced, M.  "" Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll."

The only error message I receive is "Driver_IRQL_Not_less_than_or_equal
If this is the first time Yada yada yada
*** Stop:0x000000d1 (0x00000000,0x00000002,0x00000000,0x00000000)
" , as I noted in my 1st post of this thread.  

Edx15
















0
 
MereteCommented:
Hi, ok re-reading from the top.
You have slaved this hdd several times, have you put the pin back to master not cable select.
Does the bios boot from HDO first boot or cdrom or floppy.

Please provide the computer specs such as video card internal  plus external add on nvidia ati?
Modem onboard?
Sound card onboard /and card?
 Router
Unplug as many as you can.
Are you networked?

These errors are related to an out of date or windowsxpsp2 incompatible driver.
It must one of your hardware you are using the wrong the drivers as it hits before windows can load.
Unplug everything except for your master hdd and one master cdrom drive.
Have you changed the cdrom from the originl?
Have you changed any significant hardware since you bought the computer.

try setting your computer to factory defaults, ( unplug the power cord out of back first)   then drop out the CMOS battery using a small flat nosed pliers.
Power in again and boot with out it. Then shutdown by holding in the off button. Let it sit for about 20 minutes. Like this.
(Unpower again) as in pull out the power plug, now click in the battery again, numbers facing out of course, one way in really.
Put the power in again and see if you can boot with just master hdd and cdrom.

Driver_IRQL_Not_less_than_or_equal Stop 0x000000D1 Error Message When You Turn Your Computer Off
SYMPTOMS
When you shut down your computer that has one or more universal serial bus (USB) devices attached to it, you may receive the following error message on a blue screen:
Stop 0x000000D1 (0x00000040, 0x00000002, 0x00000000, 0xfc96a9dc)
CAUSE
This problem may occur because the OHCI endpoint is unable to find the transfer descriptor in the list.
 Back to the top

RESOLUTION
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 (http://support.microsoft.com/kb/322389/EN-US/) How to Obtain the Latest Windows XP Service Pack
The English version of this fix should have the following file attributes or later:
   Date       Time   Version      Size    File name
   --------------------------------------------------
   06-Feb-02  18:30  5.1.2600.28  15,616  Usbohci.sys


NTLDR is Missing.
http://www.computerhope.com/issues/ch000465.htm#b
0
 
edx15Author Commented:
Why is something always in the last place you look for it?  

I tried a different stick of DDR 333, in the other memory slot.  

I disabled the onboard LAN device.  

I disabled the onboard audio codec.  

I removed the PCI modem & disconnected the FDD & optical drives.  

After each of the above, I booted; same error.  I reversed the steps, putting thing back to "normal".  

I disabled the onboard serial and parallel ports.  

I made it to safe mode.  

I rebooted, made it to normal mode.  Now, pagefile.sys had grown to > 300,000 KB.  

I turned off the computer, then re-started.  No problem reaching normal mode.    

I turned on the parallel port.  I was able to boot to normal mode.  

I turned off the parallel port.  I turned on the serial port.  I was able to boot to normal mode.  

With the serial port enabled, I enabled the parallel port.  I was able to boot to normal mode.  

Because after you find it, you stop looking.  :)
0
 
edx15Author Commented:
The first thing I did was to turn off the USB capabilities, in the bios.  

Edx15
0
 
MereteCommented:
lol ahahaha lost for words, probably reset everything by now, have to hand it to you you have been a busy lad.
Is it working now? Can you boot ok to windows?

your comment:
made it to safe mode.  

I rebooted, made it to normal mode.  Now, pagefile.sys had grown to > 300,000 KB.  

I turned off the computer, then re-started.  No problem reaching normal mode.    

I turned on the parallel port.  I was able to boot to normal mode.  


0
 
edx15Author Commented:
Yes, I have made it to normal mode, with everything connected & enabled.  

edx15
0
 
Expert4XPCommented:
This was a tough one.  Sounds like Windows XP was not using the normal fastdetect because of your earlier changes?

/fastdetect
[[The /fastdetect parameter disables NTDETECT serial and parallel port device detection at the specified communications ports. If you do not specify a communications port, this parameter disables detection on all serial and parallel ports.]]
http://www.mcse.ms/archive66-2004-10-1169735.html

This may have had an effect as you were making more diagnostic changes.

Glad it's working again!!
0
 
MereteCommented:
ok you now have a couple of easy options  edx15
 thanking us all for our awsome help award points to those you feel helped
split points for assists that helped.
and close as very happy camper.
Well I am happy for you it's been a long hard slug your problem.
Cheers Merete
:)
0
 
edx15Author Commented:
I have decided to reduce the points to 250 and reward those to Expert4XP because that person's suggestion was close to the answer, in that the solution was hardware related.  

Merete, I appreciate your multiple, lengthy postings, but they provided absolutely no help solving my issue.  

Expert4XP, I have decided to award you 250 points because I think it would be bad PR for me to award zero points.  One could argue that your suggestion regarding USB devices was in the ball park because the problem was hardware related, although not related to the USB connections.  

I await your comments.  

Sincerely,
edx15
0
 
Expert4XPCommented:
In all fairness, while I appreciate the recognition, I believe that Merete was also responsible for getting you toward the right direction and resolving (resetting) your pc problem.

The recognition and satisfaction are more important to me than the points per se, so maybe a reasonable solution would be a 50/50 split of points with Merete.

Just glad it's working!
0
 
MereteCommented:
Thank you Expert4XP
Yep just gald your up and running.
0
 
edx15Author Commented:
E:  
I appreciate your sense of fair play.  

No offense to Merete, but the issue was hardware.  

edx15
0
 
MereteCommented:
lol I am not worried or concerned, not every answer has the solution.
have nice day
Merete :)
0
 
edx15Author Commented:
V:  
I did not abandon the issue.  It was my understanding, from correspondence between a moderator and this writer, that I needed to wait for the respondents to reply.  Please see my comments & the comments of NetMinder on 24 May 2006.  

Sincerely,
edx15
0
 
MereteCommented:
I would ask that the points be awarded to  Expert4XP since edx15
has stated this anyway. edx15 did you forget to accept on Expert4XP. lol

Comment from edx15
Date: 05/25/2006 01:59PM EST
 Author Comment  

I have decided to reduce the points to 250 and reward those to Expert4XP because that person's suggestion was close to the answer, in that the solution was hardware related.  
 
Problem solved as I see it. :)
0
 
edx15Author Commented:
Points awarded to Isoul because I found the solution to be disabling, the com ports in the bios.  

Thanks to all who replied.  

Sincerely,
edx15
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 9
  • 9
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now