Re: Loaded SP2 now I'm in a boot loop...Things to try.
From: Ron Sommer (rsommer_at_nospam.ktis.net)
Date: 10/21/04
- Next message: RJK: "MS error message on startup from hibernate state..."
- Previous message: Vanguardx: "Re: Problem boot PC post XP SP2 installation"
- In reply to: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Next in thread: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Reply: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 21 Oct 2004 07:28:43 -0500
Are you deleting before reformatting?
-- Ron Sommer "Wild Flower" <Wild Flower@discussions.microsoft.com> wrote in message news:7D63D9C7-3400-4F25-BFF4-2FF60431E504@microsoft.com... > Chad, Thank you for your posts… > > Please comment. > > I just put together my first computer with all top brand hardware pieces… > nothing OEM .. except the Windows XP with SP2 disk… > > I installed everything okay.. installed all the drivers that came with the > hardware… only one that said it wasn’t MS approved.. was the View sonic > LCD > monitor… Also, I don’t have any printers or scanners hooked up to the > computer… just trying to get it running clean… (Note: I don’t own an Astra > scanner) > > I have creative Sound Blaster Audigy 2zs … but my sound wasn’t working… > so, > I went into device manager and selected the sound card.. updated the > driver > with the disk in the drive.. and it worked, I had sound…. But somewhere > after > that it started that reboot continuously thing… long story short.. I have > wiped the drive and started over 5 times… and found that article on the > UMAX > driver… and searched for it on my system and found the .dll > > I have been racking my brain to figure where I got it.. I scanned all the > disks… except for the Windows XP sp2 disk, and no luck… where I am getting > it… then I checked on the WinXP disk… sure enough it’s on there!! Why?? If > they don’t support the driver why is it in their driver.cab????? > > It has been consistent in failing after I have windows install that one > driver… I don’t require Windows to install any other drivers.. just that > sound card one. > > ALSO … I thought this was weird.. the umax.ini file was created at > 2:55am.. > I went to bed at 2:30am.. (trying to work on this) and I had left it > reformatting the drive and installing XP. When I woke… I had the blue > screen > error message… waiting for me to read it.. I ended up reformatting > again….. > at about 9:30am … so that umax.ini file should have been wiped… I don’t > get > it. .. I did let Windows do the formatting.. and not fdisk… which I > thought > would be the same. > > I am reformatting again… and thinking .. maybe don’t install all the > drivers… OR … maybe let windows do all of them.. OR … update windows as > soon > as possible. > > The service pack in embedded on the disk.. so I can’t tell when it is > installed.. > > I really want my system to run at the best optimum capability it has. I > would think installing the drivers and utilities would do that. ARGHHH!! > > > "Chad Harris" wrote: > >> Guy with late homework-- >> >> See if a UMAX driver could be the problem via this KB: >> >> After you install Windows XP Service Pack 2, your computer restarts >> continuously >> http://support.microsoft.com/default.aspx?scid=kb;en-us;873161&Product=winxp >> >> Over-heating, and a bad stick of RAM have been known to cause this--so if >> software remedies don't do it, look to hardware, memory sticks in place, >> cables, ect. >> >> *Often, booting to the Recovery Console and running chkdsk /r will help >> this >> problem.* I don't know if you have an XP CD, because lately so many >> people >> with boot problems have not had one supplied by their OEM, but if you do >> this would be my first choice to try to ditch the endless loop this way. >> >> Description of the Windows XP Recovery Console >> http://support.microsoft.com/default.aspx?scid=kb;en-us;314058 >> >> Scroll down for instructions on running chkdsk /r. >> >> Using the Recovery Console >> http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmc_str_bjid.asp >> >> RC Overview >> http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_console_overview.mspx >> >> Recovery Console in XP >> http://www.kellys-korner-xp.com/win_xp_rec.htm >> >> I didn't know if you could break the loop to F8 as Will says. In my >> experience, Last Known Good Configuration almost never works >> statistically, >> but if it does and this is gone, more power to you. Keep in mind that >> it's >> a snapshot of your configuration immediately after you booted, so if you >> have been booted up for a long time then you're not going to track >> settings >> changes since that time. >> >> I'd first try to F8 to the Windows Advanced Options menu and use Safe >> Mode >> and then try System Restore from Safe Mode. You will probably be back at >> the version before you installed SP2. There is also this option for >> aborted >> SP2 installs or SP2 installs with the problem like the one you're having, >> but again System Restore may not solve your endless loop problem and Last >> Known Good may not. You may need to run a chkdsk /r or use some of the >> other tools I describe. >> >> Resources for troubleshooting startup problems in Windows XP (Info on F8 >> and >> Advanced Options Menu) >> http://support.microsoft.com/default.aspx?kbid=308041 >> >> How to use the Automatic Recovery feature to recover your computer if the >> Windows XP Service Pack 2 Setup program is not completed successfully >> http://support.microsoft.com/default.aspx?kbid=875355&product=windowsxpsp2 >> >> A description of the Safe Mode Boot options in Windows XP >> http://support.microsoft.com/default.aspx?kbid=315222 >> >> If you were unable to use the Recovery Console because you had no XP CD, >> and >> haven't installed it already but could get back to Windows: >> >> If you can tap F8 to get back to Windows via either Safe Mode or as a >> last >> resort in my opinion, Last Known Good Configuration, then you're still >> faced >> with the possible "endless loop problem." That's why my first suggestion >> was to boot to the Recovery Console and run chkdsk /r from the recovery >> console. >> >> You would be possibly faced with the endless loop proble again or when >> you >> installed SP2 so I would run chkdsk /r from the command prompt or the run >> box. >> >> The reason for the endless loop is often that something has set the >> volume's >> "dirty bit." When a volume's dirty bit is set, autochk automatically >> checks >> the volume for errors the next time the computer is restarted.If a >> volume's >> dirty bit is set, this indicates that the file system may be in an >> inconsistent state. The dirty bit can be set because the volume is online >> and has outstanding changes, because changes were made to the volume and >> the >> computer shutdown before the changes were committed to disk, or because >> corruption was detected on the volume. If the dirty bit is set when the >> computer restarts, chkdsk runs to verify the consistency of the volume. >> >> See if you have any disk corrpution by typing "fsutil dirty query [C]: >> Sub >> any drive you want for "C". If it says the volume isn't dirty, you don't >> need to run chkdsk because there aren't any errors on the disk. But I >> know >> you want to run it to see that it runs properly without this read-only >> error. The KB I'm going to list advises you to run "chkdsk volume_label: >> /v >> /f" to fix this. This will fix any errors on the disk and the "v" causes >> it >> to name each fixed file. Hopefully that will resolve it. >> But if it doesn't then run "chkdsk_volume label: /r", and if that doesn't >> then run the chkdsk /r from the recovery console. >> >> >> If the disk is dirty, then System Restore is not going to fix that. >> >> Every time Windows XP starts, Autochk.exe is called by the Kernel to scan >> all volumes to check if the volume dirty bit is set. If the dirty bit is >> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f >> verifies file system integrity and attempts to fix any problems with the >> volume. >> >> Here's what to do: >> >> Go to Start/Run/CMD and type in: fsutil dirty query c: (or whatever drive >> his XP is on). You'll get back either the drive "is dirty" or "it's not >> dirty." >> >> Info on a "Fsutil Query" in the KB below--also see the Explanation at >> Windows Help and Support--type "helpctr" into your run box: >> >> The Fsutil Query Tool: >> http://techrepublic.com.com/5138-6240-728908.html >> >> An Fsutil Query Does Not Work Properly on FAT or FAT32 Volumes >> http://support.microsoft.com/default.aspx?scid=kb;en-us;322275&Product=winxp >> >> You have 4 choices that may work: >> >> 1) You can run chkdsk /r from the Recovery Console. I think this is the >> fastest and most effective. I've seen it work for this several times. >> >> 2) You can run the chkntfs /d and reboot and chkdsk won't run on the next >> boot. What this does is to restore default settings. Note this is a >> different command than chkdsk. Chkntfs is a command that displays or >> specifies whether automatic checking is schduled to run on a FAT, FAT32, >> or >> NTFS volume when the computer is started. >> >> 3) You should be able to fix this by using "chkntfs/X C" if C were the >> problem drive or whatever letter--this works when the drive is dirty and >> I >> showed you above how to verify this. The advantage of sticking the X in >> the >> command is that it saves time by causing the command to skip checking >> cycles >> within the folder. >> >> 4) You can go to Kelly's XP Tweaks and click line 76 left column and see >> if >> this VB script will stop it. >> >> Kelly's Tweaks >> http://www.kellys-korner-xp.com/xp_tweaks.htm >> >> Troubleshooting Windows XP >> http://www.kellys-korner-xp.com >> >> In addition, When there is improper shutdown, the Autochk program runs >> on >> all NTFS drives in XP, 2K, NT where a disk write was in process at the >> time >> of shutdown. This gets exacerbated if you have write caching enabled on a >> hard drive connected to a standard IDE controller. It improves >> performance, >> by delaying data writing while other work is done, but it ups the risk of >> lost data or corruption. >> >> http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prdh_dmt_cgwi.asp >> >> Open the run box with the Windows Key + "r" and type in diskmgmt.msc. >> From >> the graphical display in the bottom of the Disk Management window, >> right-click the disc icon and chooose Properties. On the policies tab, >> clear >> Enable Write Caching on the Disk. (Note this option, ie. the policies >> tab, >> may not be available if your disk is connected to a High Performance >> ATA-66 >> or ATA-100 IDE controller.) >> >> After you find the cause of the underlying problem if there is improper >> shutdown, re-enable write caching. >> >> Additional references for definitions context: >> >> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart >> your >> computer >> http://support.microsoft.com/default.aspx?scid=kb;en-us;831426&Product=winxp >> >> An Fsutil Query Does Not Work Properly on FAT or FAT32 Volumes >> http://support.microsoft.com/default.aspx?scid=kb;en-us;322275&Product=winxp >> >> hth, >> >> Chad Harris >> ______________________ >> >> "Guy with late home work" <Guy with late home >> work@discussions.microsoft.com> wrote in message >> news:4E8FB6DE-03B8-45DE-B9D5-4E80AE7A723E@microsoft.com... >> While rebooting from loading SP2 I get the error message, "Autochk not >> found-skipping autocheck program", then it reboots and goes through the >> same >> routine indefinitely! HELP >> >> >>
- Next message: RJK: "MS error message on startup from hibernate state..."
- Previous message: Vanguardx: "Re: Problem boot PC post XP SP2 installation"
- In reply to: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Next in thread: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Reply: Wild Flower: "Re: Loaded SP2 now I'm in a boot loop...Things to try."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
