From: fixitchris on 29 Jan 2010 14:27 About 6months ago we started getting REGISTRY_ERROR BSOD on a couple PCs and I was able to recover them using KB307545. Recently, many more computers have been crashing with this BSOD and become unrecoverable, constantly crashing when attempting to enter the recovery console or even reinstall XP for that matter. Also NTpasswd utility is unable to mount the volume for write due to its own errors it finds. I used the NTpasswd utility to reset the password since none of the passwords that I have recorded worked in the recovery console on the PCs that were able to get into the console. Has anyone been experiencing this lately? any ideas if there are crash dumps that could help point out the culprit? Thanks Chris
From: Andrew E. on 30 Jan 2010 00:15 If multiple installations fail &/or simple files are lost,etc,sounds like hd is on its way out.Try downloading the MS-DOS hd chk utility from the hd mfg web site.Install to MS-DOS formatted floppy,boot pc to floppy,run the test(s).Also,chk youre battery,replace it if over 3 yrs old as it continuously runs the BIOS. "fixitchris" wrote: > About 6months ago we started getting REGISTRY_ERROR BSOD on a couple PCs and > I was able to recover them using KB307545. Recently, many more computers > have been crashing with this BSOD and become unrecoverable, constantly > crashing when attempting to enter the recovery console or even reinstall XP > for that matter. Also NTpasswd utility is unable to mount the volume for > write due to its own errors it finds. I used the NTpasswd utility to reset > the password since none of the passwords that I have recorded worked in the > recovery console on the PCs that were able to get into the console. > > Has anyone been experiencing this lately? any ideas if there are crash > dumps that could help point out the culprit? > > Thanks > Chris
From: Questor on 30 Jan 2010 08:50 Andrew: please note that this is happening to "many more computers" not just one. Also, there aren't many computers nowadays that even HAVE a floppy drive. Fixitchris: Are these computers that are crashing booting remotely from a single source? Running a HD utility on that one console drive may find errors. Questor ---> > If multiple installations fail&/or simple files are lost,etc,sounds like > hd is on its way out.Try downloading the MS-DOS hd chk utility from the > hd mfg web site.Install to MS-DOS formatted floppy,boot pc to floppy,run > the test(s).Also,chk youre battery,replace it if over 3 yrs old as it > continuously > runs the BIOS. > > "fixitchris" wrote: > >> About 6months ago we started getting REGISTRY_ERROR BSOD on a couple PCs and >> I was able to recover them using KB307545. Recently, many more computers >> have been crashing with this BSOD and become unrecoverable, constantly >> crashing when attempting to enter the recovery console or even reinstall XP >> for that matter. Also NTpasswd utility is unable to mount the volume for >> write due to its own errors it finds. I used the NTpasswd utility to reset >> the password since none of the passwords that I have recorded worked in the >> recovery console on the PCs that were able to get into the console. >> >> Has anyone been experiencing this lately? any ideas if there are crash >> dumps that could help point out the culprit? >> >> Thanks >> Chris
From: Ken Blake, MVP on 30 Jan 2010 10:01 On Fri, 29 Jan 2010 21:15:01 -0800, Andrew E. <eckrichco(a)msn.com> wrote: > If multiple installations fail &/or simple files are lost,etc,sounds like > hd is on its way out. More nonsense from Andrew E., one of the main posters of nonsense in these newsgroups. Andrew, he says "many more computers have been crashing with this BSOD." Many computer don't crash because of a single failing HD. Moreover the symptoms (registry errors) are not those of a failing HD. > Try downloading the MS-DOS hd chk utility from the > hd mfg web site.Install to MS-DOS formatted floppy,boot pc to floppy,run And very computers these days even have floppy drives. > the test(s).Also,chk youre battery, And it is not at all a symptom of a failing battery. > replace it if over 3 yrs old Many batteries last considerably longer than three years. And some batteries don't last anywhere near that long. The battery should be replaced when it starts failing, not at a certain age. > as it > continuously > runs the BIOS. It does *not* "run the BIOS." Nothing "runs" the BIOS. The battery's purpose is to prevent the loss of the data stored in it, and to keep the clock going when the computer is powered off. > "fixitchris" wrote: > > > About 6months ago we started getting REGISTRY_ERROR BSOD on a couple PCs and > > I was able to recover them using KB307545. Recently, many more computers > > have been crashing with this BSOD and become unrecoverable, constantly > > crashing when attempting to enter the recovery console or even reinstall XP > > for that matter. Also NTpasswd utility is unable to mount the volume for > > write due to its own errors it finds. I used the NTpasswd utility to reset > > the password since none of the passwords that I have recorded worked in the > > recovery console on the PCs that were able to get into the console. > > > > Has anyone been experiencing this lately? any ideas if there are crash > > dumps that could help point out the culprit? > > > > Thanks > > Chris -- Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003 Please Reply to the Newsgroup
From: fixitchris on 11 Feb 2010 17:02 Sorry, my notifications for this thread weren't on. I ran MHDD and the hdd passes, no issues. Another one happened today, on a 2 year old HP workstation. I wonder if this is relevant: http://www.computerworld.com/s/article/9155419/Windows_patch_cripples_XP_with_blue_screen_users_claim
|
Pages: 1 Prev: SORRY BUT A NEW ERROR MESSAGE Next: Have SP2 Installed - do I need SP3? |