blue screen scanning registry

  • Thread starter Thread starter santashelper
  • Start date Start date
S

santashelper

Guest
Whenever my registry is scanned either by regedit or AVG i get a blue screen
of death. The error code is:0x00000050 (address error). The parameters are:
1 0xfdfffff8, 2 0x00000000 3 0x8054aa32B5B2, 4 0x00000000. Have tried taking
out all hardware and drivers except AGP display card with same results.
Removed AGP card and driver and used a known good pci graphics card with same
results. Put in new memory and it checked good with mem86 3.4A. Still get
blue scren of death when registry is scanned. Tried runnig PC PITSTOP full
tests and still get blue screen. If I run in safe mode it runs everything
fine. Does anyone know what to do to solve this problem?
 
Re: blue screen scanning registry


"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:1B07D48F-1A77-41E1-88A5-88C63FDBFAD2@microsoft.com...
> Whenever my registry is scanned either by regedit or AVG i get a blue
> screen
> of death. The error code is:0x00000050 (address error). The parameters
> are:
> 1 0xfdfffff8, 2 0x00000000 3 0x8054aa32B5B2, 4 0x00000000. Have tried
> taking
> out all hardware and drivers except AGP display card with same results.
> Removed AGP card and driver and used a known good pci graphics card with
> same
> results. Put in new memory and it checked good with mem86 3.4A. Still get
> blue scren of death when registry is scanned. Tried runnig PC PITSTOP
> full
> tests and still get blue screen. If I run in safe mode it runs everything
> fine. Does anyone know what to do to solve this problem?

I don't know about AVG but the native regedit.exe utility does not "scan"
the registry - it opens it for viewing or for editing. Make sure to run the
real thing by typing "c:\windows\regedit.exe" in the Run box, not some
malware look-alike program.

Since the problem does not occur in Safe Mode, you need to perform the usual
elimination process:
1. Physically disconnect your machine from the Internet.
2. Boot into Safe Mode.
3. Run msconfig.exe.
4. Disable each and every task under the Startup tab.
5. Reboot normally. If this fixes the problem then you can restore the
various startup tasks until you find the culprit.

Do not restore your Internet connection until you have re-enabled your virus
scanner and your software firewall (if you have one).
 
Re: blue screen scanning registry

I am running the real regedit looking for an item that does not exist
(xyz123) so that it scans the whole registry. I did this because of the
bluescreen in PC PITSTOP, Spyware Doctor, and AVG.

"Pegasus (MVP)" wrote:

>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:1B07D48F-1A77-41E1-88A5-88C63FDBFAD2@microsoft.com...
> > Whenever my registry is scanned either by regedit or AVG i get a blue
> > screen
> > of death. The error code is:0x00000050 (address error). The parameters
> > are:
> > 1 0xfdfffff8, 2 0x00000000 3 0x8054aa32B5B2, 4 0x00000000. Have tried
> > taking
> > out all hardware and drivers except AGP display card with same results.
> > Removed AGP card and driver and used a known good pci graphics card with
> > same
> > results. Put in new memory and it checked good with mem86 3.4A. Still get
> > blue scren of death when registry is scanned. Tried runnig PC PITSTOP
> > full
> > tests and still get blue screen. If I run in safe mode it runs everything
> > fine. Does anyone know what to do to solve this problem?
>
> I don't know about AVG but the native regedit.exe utility does not "scan"
> the registry - it opens it for viewing or for editing. Make sure to run the
> real thing by typing "c:\windows\regedit.exe" in the Run box, not some
> malware look-alike program.
>
> Since the problem does not occur in Safe Mode, you need to perform the usual
> elimination process:
> 1. Physically disconnect your machine from the Internet.
> 2. Boot into Safe Mode.
> 3. Run msconfig.exe.
> 4. Disable each and every task under the Startup tab.
> 5. Reboot normally. If this fixes the problem then you can restore the
> various startup tasks until you find the culprit.
>
> Do not restore your Internet connection until you have re-enabled your virus
> scanner and your software firewall (if you have one).
>
>
>
 
Re: blue screen scanning registry

"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
>I am running the real regedit looking for an item that does not exist
> (xyz123) so that it scans the whole registry. I did this because of
> the
> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.

What exactly do you mean by "real regedit"? Do you have another
(malware) program also called regedit? What do you mean by "looking for
an item that does not exist"?
 
Re: blue screen scanning registry

"Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> "santashelper" <santashelper@discussions.microsoft.com> wrote in
> message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
>>I am running the real regedit looking for an item that does not exist
>> (xyz123) so that it scans the whole registry. I did this because of
>> the
>> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
>
> What exactly do you mean by "real regedit"? Do you have another
> (malware) program also called regedit? What do you mean by "looking
> for an item that does not exist"?

Okay, I now see the context of "real." Pegasus had brought that up.

You really should follow his advice about using the process of
elimination. Here it is again:

<quote>
Since the problem does not occur in Safe Mode, you need to perform the
usual
elimination process:
1. Physically disconnect your machine from the Internet.
2. Boot into Safe Mode.
3. Run msconfig.exe.
4. Disable each and every task under the Startup tab.
5. Reboot normally. If this fixes the problem then you can restore the
various startup tasks until you find the culprit.

Do not restore your Internet connection until you have re-enabled your
virus
scanner and your software firewall (if you have one).
</quote>

My guess is that it's one of the three programs above you mentioned.
 
Re: blue screen scanning registry

Did as you suggested with same results. Uninstalled AVG and repeated process
with diagnostic mode which automatically reset all startup items. Still
getting blue screen. Do you know of any diagnostics for an AMD atlon 1400
processor?



"Daave" wrote:

> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
> >>I am running the real regedit looking for an item that does not exist
> >> (xyz123) so that it scans the whole registry. I did this because of
> >> the
> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
> >
> > What exactly do you mean by "real regedit"? Do you have another
> > (malware) program also called regedit? What do you mean by "looking
> > for an item that does not exist"?
>
> Okay, I now see the context of "real." Pegasus had brought that up.
>
> You really should follow his advice about using the process of
> elimination. Here it is again:
>
> <quote>
> Since the problem does not occur in Safe Mode, you need to perform the
> usual
> elimination process:
> 1. Physically disconnect your machine from the Internet.
> 2. Boot into Safe Mode.
> 3. Run msconfig.exe.
> 4. Disable each and every task under the Startup tab.
> 5. Reboot normally. If this fixes the problem then you can restore the
> various startup tasks until you find the culprit.
>
> Do not restore your Internet connection until you have re-enabled your
> virus
> scanner and your software firewall (if you have one).
> </quote>
>
> My guess is that it's one of the three programs above you mentioned.
>
>
>
 
Re: blue screen scanning registry

You now need to take this process one step further by doing this while in
Safe Mode:
1. Launch msconfig.exe.
2. Click the "Services" tab.
3. Hide all Microsoft services.
4. Untick the remaining services.
5. Reboot in Normal Mode and check again.

If this is a recent problem then performing a System Restore might help. Do
this ***after*** checking the effect of Steps 1..5 above.


"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
> Did as you suggested with same results. Uninstalled AVG and repeated
> process
> with diagnostic mode which automatically reset all startup items. Still
> getting blue screen. Do you know of any diagnostics for an AMD atlon 1400
> processor?
>
>
>
> "Daave" wrote:
>
>> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
>> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
>> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
>> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
>> >>I am running the real regedit looking for an item that does not exist
>> >> (xyz123) so that it scans the whole registry. I did this because of
>> >> the
>> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
>> >
>> > What exactly do you mean by "real regedit"? Do you have another
>> > (malware) program also called regedit? What do you mean by "looking
>> > for an item that does not exist"?
>>
>> Okay, I now see the context of "real." Pegasus had brought that up.
>>
>> You really should follow his advice about using the process of
>> elimination. Here it is again:
>>
>> <quote>
>> Since the problem does not occur in Safe Mode, you need to perform the
>> usual
>> elimination process:
>> 1. Physically disconnect your machine from the Internet.
>> 2. Boot into Safe Mode.
>> 3. Run msconfig.exe.
>> 4. Disable each and every task under the Startup tab.
>> 5. Reboot normally. If this fixes the problem then you can restore the
>> various startup tasks until you find the culprit.
>>
>> Do not restore your Internet connection until you have re-enabled your
>> virus
>> scanner and your software firewall (if you have one).
>> </quote>
>>
>> My guess is that it's one of the three programs above you mentioned.
>>
>>
>>
 
Re: blue screen scanning registry

Ran without system services as suggested. Still getting blue screen. Have
already tried to restore back to the earliest possible date and still got the
blue screen.

"Pegasus (MVP)" wrote:

> You now need to take this process one step further by doing this while in
> Safe Mode:
> 1. Launch msconfig.exe.
> 2. Click the "Services" tab.
> 3. Hide all Microsoft services.
> 4. Untick the remaining services.
> 5. Reboot in Normal Mode and check again.
>
> If this is a recent problem then performing a System Restore might help. Do
> this ***after*** checking the effect of Steps 1..5 above.
>
>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
> > Did as you suggested with same results. Uninstalled AVG and repeated
> > process
> > with diagnostic mode which automatically reset all startup items. Still
> > getting blue screen. Do you know of any diagnostics for an AMD atlon 1400
> > processor?
> >
> >
> >
> > "Daave" wrote:
> >
> >> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
> >> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> >> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
> >> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
> >> >>I am running the real regedit looking for an item that does not exist
> >> >> (xyz123) so that it scans the whole registry. I did this because of
> >> >> the
> >> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
> >> >
> >> > What exactly do you mean by "real regedit"? Do you have another
> >> > (malware) program also called regedit? What do you mean by "looking
> >> > for an item that does not exist"?
> >>
> >> Okay, I now see the context of "real." Pegasus had brought that up.
> >>
> >> You really should follow his advice about using the process of
> >> elimination. Here it is again:
> >>
> >> <quote>
> >> Since the problem does not occur in Safe Mode, you need to perform the
> >> usual
> >> elimination process:
> >> 1. Physically disconnect your machine from the Internet.
> >> 2. Boot into Safe Mode.
> >> 3. Run msconfig.exe.
> >> 4. Disable each and every task under the Startup tab.
> >> 5. Reboot normally. If this fixes the problem then you can restore the
> >> various startup tasks until you find the culprit.
> >>
> >> Do not restore your Internet connection until you have re-enabled your
> >> virus
> >> scanner and your software firewall (if you have one).
> >> </quote>
> >>
> >> My guess is that it's one of the three programs above you mentioned.
> >>
> >>
> >>
>
>
>
 
Re: blue screen scanning registry

This is getting suspicious. If you had a hardware or driver problem then
your machine would crash in many different applications, not just with
regedit. Perhaps the problem is with regedit, not with your machine. If so
then a clean copy of regedit.exe would resolve the issue.

Pop in your WinXP installation CD, then open a Command Prompt and type these
commands:
expand X:\i386\regedit.ex_ c:\regedit.exe{Enter}
c:\regedit.exe{Enter}

Replace "X:" with the correct drive letter for your CD drive.


"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:7AF7BF47-C343-45D6-8483-33B4F9CE885E@microsoft.com...
> Ran without system services as suggested. Still getting blue screen. Have
> already tried to restore back to the earliest possible date and still got
> the
> blue screen.
>
> "Pegasus (MVP)" wrote:
>
>> You now need to take this process one step further by doing this while in
>> Safe Mode:
>> 1. Launch msconfig.exe.
>> 2. Click the "Services" tab.
>> 3. Hide all Microsoft services.
>> 4. Untick the remaining services.
>> 5. Reboot in Normal Mode and check again.
>>
>> If this is a recent problem then performing a System Restore might help.
>> Do
>> this ***after*** checking the effect of Steps 1..5 above.
>>
>>
>> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
>> news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
>> > Did as you suggested with same results. Uninstalled AVG and repeated
>> > process
>> > with diagnostic mode which automatically reset all startup items.
>> > Still
>> > getting blue screen. Do you know of any diagnostics for an AMD atlon
>> > 1400
>> > processor?
>> >
>> >
>> >
>> > "Daave" wrote:
>> >
>> >> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
>> >> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
>> >> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
>> >> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
>> >> >>I am running the real regedit looking for an item that does not
>> >> >>exist
>> >> >> (xyz123) so that it scans the whole registry. I did this because
>> >> >> of
>> >> >> the
>> >> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
>> >> >
>> >> > What exactly do you mean by "real regedit"? Do you have another
>> >> > (malware) program also called regedit? What do you mean by "looking
>> >> > for an item that does not exist"?
>> >>
>> >> Okay, I now see the context of "real." Pegasus had brought that up.
>> >>
>> >> You really should follow his advice about using the process of
>> >> elimination. Here it is again:
>> >>
>> >> <quote>
>> >> Since the problem does not occur in Safe Mode, you need to perform the
>> >> usual
>> >> elimination process:
>> >> 1. Physically disconnect your machine from the Internet.
>> >> 2. Boot into Safe Mode.
>> >> 3. Run msconfig.exe.
>> >> 4. Disable each and every task under the Startup tab.
>> >> 5. Reboot normally. If this fixes the problem then you can restore the
>> >> various startup tasks until you find the culprit.
>> >>
>> >> Do not restore your Internet connection until you have re-enabled your
>> >> virus
>> >> scanner and your software firewall (if you have one).
>> >> </quote>
>> >>
>> >> My guess is that it's one of the three programs above you mentioned.
>> >>
>> >>
>> >>
>>
>>
>>
 
Re: blue screen scanning registry

Used command line:
c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_ c:\regedit.exe

received msg.:
Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
copyright (C) Microsoft Corp. 1998-1999. All rights reserved.

Can't open input file: d:\i386\regedit.ex_.

Looked at CD contents and found regedit.exe in the i386 folder .




"Pegasus (MVP)" wrote:

> This is getting suspicious. If you had a hardware or driver problem then
> your machine would crash in many different applications, not just with
> regedit. Perhaps the problem is with regedit, not with your machine. If so
> then a clean copy of regedit.exe would resolve the issue.
>
> Pop in your WinXP installation CD, then open a Command Prompt and type these
> commands:
> expand X:\i386\regedit.ex_ c:\regedit.exe{Enter}
> c:\regedit.exe{Enter}
>
> Replace "X:" with the correct drive letter for your CD drive.
>
>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:7AF7BF47-C343-45D6-8483-33B4F9CE885E@microsoft.com...
> > Ran without system services as suggested. Still getting blue screen. Have
> > already tried to restore back to the earliest possible date and still got
> > the
> > blue screen.
> >
> > "Pegasus (MVP)" wrote:
> >
> >> You now need to take this process one step further by doing this while in
> >> Safe Mode:
> >> 1. Launch msconfig.exe.
> >> 2. Click the "Services" tab.
> >> 3. Hide all Microsoft services.
> >> 4. Untick the remaining services.
> >> 5. Reboot in Normal Mode and check again.
> >>
> >> If this is a recent problem then performing a System Restore might help.
> >> Do
> >> this ***after*** checking the effect of Steps 1..5 above.
> >>
> >>
> >> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> >> news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
> >> > Did as you suggested with same results. Uninstalled AVG and repeated
> >> > process
> >> > with diagnostic mode which automatically reset all startup items.
> >> > Still
> >> > getting blue screen. Do you know of any diagnostics for an AMD atlon
> >> > 1400
> >> > processor?
> >> >
> >> >
> >> >
> >> > "Daave" wrote:
> >> >
> >> >> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
> >> >> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> >> >> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
> >> >> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
> >> >> >>I am running the real regedit looking for an item that does not
> >> >> >>exist
> >> >> >> (xyz123) so that it scans the whole registry. I did this because
> >> >> >> of
> >> >> >> the
> >> >> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
> >> >> >
> >> >> > What exactly do you mean by "real regedit"? Do you have another
> >> >> > (malware) program also called regedit? What do you mean by "looking
> >> >> > for an item that does not exist"?
> >> >>
> >> >> Okay, I now see the context of "real." Pegasus had brought that up.
> >> >>
> >> >> You really should follow his advice about using the process of
> >> >> elimination. Here it is again:
> >> >>
> >> >> <quote>
> >> >> Since the problem does not occur in Safe Mode, you need to perform the
> >> >> usual
> >> >> elimination process:
> >> >> 1. Physically disconnect your machine from the Internet.
> >> >> 2. Boot into Safe Mode.
> >> >> 3. Run msconfig.exe.
> >> >> 4. Disable each and every task under the Startup tab.
> >> >> 5. Reboot normally. If this fixes the problem then you can restore the
> >> >> various startup tasks until you find the culprit.
> >> >>
> >> >> Do not restore your Internet connection until you have re-enabled your
> >> >> virus
> >> >> scanner and your software firewall (if you have one).
> >> >> </quote>
> >> >>
> >> >> My guess is that it's one of the three programs above you mentioned.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
 
Re: blue screen scanning registry


"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
> Used command line:
> c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_ c:\regedit.exe
>
> received msg.:
> Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
> copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
>
> Can't open input file: d:\i386\regedit.ex_.
>
> Looked at CD contents and found regedit.exe in the i386 folder .

Mhm. Well. This means that the file is not compressed on the CD and does not
need expanding. Just execute it as it is: D:\i386\regedit.exe.
 
Re: blue screen scanning registry

Couple thoughts here.

Try running regedt32 instead.

and

When doing a Registry search using a single non-multi-core
processor (which I'm pretty sure the Athlon is), Task Mgr.
shows Regedit using 100% CPU continuously for
the duration of the search. Not many apps do this
in day-to-day operations. Major stress.

That being the case, you may be overheating. Check
your CPU fan(s), etc. Also could be PSU problem.


"Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
news:un0aqJRLJHA.5660@TK2MSFTNGP03.phx.gbl...
> This is getting suspicious. If you had a hardware or driver problem then
> your machine would crash in many different applications, not just with
> regedit. Perhaps the problem is with regedit, not with your machine. If so
> then a clean copy of regedit.exe would resolve the issue.
>
> Pop in your WinXP installation CD, then open a Command Prompt and type these
> commands:
> expand X:\i386\regedit.ex_ c:\regedit.exe{Enter}
> c:\regedit.exe{Enter}
>
> Replace "X:" with the correct drive letter for your CD drive.
>
>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:7AF7BF47-C343-45D6-8483-33B4F9CE885E@microsoft.com...
> > Ran without system services as suggested. Still getting blue screen. Have
> > already tried to restore back to the earliest possible date and still got
> > the
> > blue screen.
> >
> > "Pegasus (MVP)" wrote:
> >
> >> You now need to take this process one step further by doing this while in
> >> Safe Mode:
> >> 1. Launch msconfig.exe.
> >> 2. Click the "Services" tab.
> >> 3. Hide all Microsoft services.
> >> 4. Untick the remaining services.
> >> 5. Reboot in Normal Mode and check again.
> >>
> >> If this is a recent problem then performing a System Restore might help.
> >> Do
> >> this ***after*** checking the effect of Steps 1..5 above.
> >>
> >>
> >> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> >> news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
> >> > Did as you suggested with same results. Uninstalled AVG and repeated
> >> > process
> >> > with diagnostic mode which automatically reset all startup items.
> >> > Still
> >> > getting blue screen. Do you know of any diagnostics for an AMD atlon
> >> > 1400
> >> > processor?
> >> >
> >> >
> >> >
> >> > "Daave" wrote:
> >> >
> >> >> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
> >> >> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> >> >> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
> >> >> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
> >> >> >>I am running the real regedit looking for an item that does not
> >> >> >>exist
> >> >> >> (xyz123) so that it scans the whole registry. I did this because
> >> >> >> of
> >> >> >> the
> >> >> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
> >> >> >
> >> >> > What exactly do you mean by "real regedit"? Do you have another
> >> >> > (malware) program also called regedit? What do you mean by "looking
> >> >> > for an item that does not exist"?
> >> >>
> >> >> Okay, I now see the context of "real." Pegasus had brought that up.
> >> >>
> >> >> You really should follow his advice about using the process of
> >> >> elimination. Here it is again:
> >> >>
> >> >> <quote>
> >> >> Since the problem does not occur in Safe Mode, you need to perform the
> >> >> usual
> >> >> elimination process:
> >> >> 1. Physically disconnect your machine from the Internet.
> >> >> 2. Boot into Safe Mode.
> >> >> 3. Run msconfig.exe.
> >> >> 4. Disable each and every task under the Startup tab.
> >> >> 5. Reboot normally. If this fixes the problem then you can restore the
> >> >> various startup tasks until you find the culprit.
> >> >>
> >> >> Do not restore your Internet connection until you have re-enabled your
> >> >> virus
> >> >> scanner and your software firewall (if you have one).
> >> >> </quote>
> >> >>
> >> >> My guess is that it's one of the three programs above you mentioned.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
 
Re: blue screen scanning registry

tried what you suggested by loading regedit from the XP cd. no luck. It
does fail with any program that scans the registry. I.E. Spyware Doctor, AVG,
PC Pitstop.


"Pegasus (MVP)" wrote:

>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
> > Used command line:
> > c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_ c:\regedit.exe
> >
> > received msg.:
> > Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
> > copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
> >
> > Can't open input file: d:\i386\regedit.ex_.
> >
> > Looked at CD contents and found regedit.exe in the i386 folder .
>
> Mhm. Well. This means that the file is not compressed on the CD and does not
> need expanding. Just execute it as it is: D:\i386\regedit.exe.
>
>
>
 
Re: blue screen scanning registry

Regedit32 runs the same program (regedit.exe) according to microsoft..
CPU temp and fan speed are OK. CPU Temp=102 degrees F, System Temp=77
degrees F, CPU Fam Speed=4818 rpm, System Fan=2776.

"V Green" wrote:

> Couple thoughts here.
>
> Try running regedt32 instead.
>
> and
>
> When doing a Registry search using a single non-multi-core
> processor (which I'm pretty sure the Athlon is), Task Mgr.
> shows Regedit using 100% CPU continuously for
> the duration of the search. Not many apps do this
> in day-to-day operations. Major stress.
>
> That being the case, you may be overheating. Check
> your CPU fan(s), etc. Also could be PSU problem.
>
>
> "Pegasus (MVP)" <I.can@fly.com.oz> wrote in message
> news:un0aqJRLJHA.5660@TK2MSFTNGP03.phx.gbl...
> > This is getting suspicious. If you had a hardware or driver problem then
> > your machine would crash in many different applications, not just with
> > regedit. Perhaps the problem is with regedit, not with your machine. If so
> > then a clean copy of regedit.exe would resolve the issue.
> >
> > Pop in your WinXP installation CD, then open a Command Prompt and type these
> > commands:
> > expand X:\i386\regedit.ex_ c:\regedit.exe{Enter}
> > c:\regedit.exe{Enter}
> >
> > Replace "X:" with the correct drive letter for your CD drive.
> >
> >
> > "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> > news:7AF7BF47-C343-45D6-8483-33B4F9CE885E@microsoft.com...
> > > Ran without system services as suggested. Still getting blue screen. Have
> > > already tried to restore back to the earliest possible date and still got
> > > the
> > > blue screen.
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > >> You now need to take this process one step further by doing this while in
> > >> Safe Mode:
> > >> 1. Launch msconfig.exe.
> > >> 2. Click the "Services" tab.
> > >> 3. Hide all Microsoft services.
> > >> 4. Untick the remaining services.
> > >> 5. Reboot in Normal Mode and check again.
> > >>
> > >> If this is a recent problem then performing a System Restore might help.
> > >> Do
> > >> this ***after*** checking the effect of Steps 1..5 above.
> > >>
> > >>
> > >> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> > >> news:4DDB2662-32B8-46A1-A692-A1411418DA6E@microsoft.com...
> > >> > Did as you suggested with same results. Uninstalled AVG and repeated
> > >> > process
> > >> > with diagnostic mode which automatically reset all startup items.
> > >> > Still
> > >> > getting blue screen. Do you know of any diagnostics for an AMD atlon
> > >> > 1400
> > >> > processor?
> > >> >
> > >> >
> > >> >
> > >> > "Daave" wrote:
> > >> >
> > >> >> "Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
> > >> >> news:ulcmMoHLJHA.5232@TK2MSFTNGP05.phx.gbl...
> > >> >> > "santashelper" <santashelper@discussions.microsoft.com> wrote in
> > >> >> > message news:3EA95FCB-0940-4AF9-9165-EE05F3869AEB@microsoft.com...
> > >> >> >>I am running the real regedit looking for an item that does not
> > >> >> >>exist
> > >> >> >> (xyz123) so that it scans the whole registry. I did this because
> > >> >> >> of
> > >> >> >> the
> > >> >> >> bluescreen in PC PITSTOP, Spyware Doctor, and AVG.
> > >> >> >
> > >> >> > What exactly do you mean by "real regedit"? Do you have another
> > >> >> > (malware) program also called regedit? What do you mean by "looking
> > >> >> > for an item that does not exist"?
> > >> >>
> > >> >> Okay, I now see the context of "real." Pegasus had brought that up.
> > >> >>
> > >> >> You really should follow his advice about using the process of
> > >> >> elimination. Here it is again:
> > >> >>
> > >> >> <quote>
> > >> >> Since the problem does not occur in Safe Mode, you need to perform the
> > >> >> usual
> > >> >> elimination process:
> > >> >> 1. Physically disconnect your machine from the Internet.
> > >> >> 2. Boot into Safe Mode.
> > >> >> 3. Run msconfig.exe.
> > >> >> 4. Disable each and every task under the Startup tab.
> > >> >> 5. Reboot normally. If this fixes the problem then you can restore the
> > >> >> various startup tasks until you find the culprit.
> > >> >>
> > >> >> Do not restore your Internet connection until you have re-enabled your
> > >> >> virus
> > >> >> scanner and your software firewall (if you have one).
> > >> >> </quote>
> > >> >>
> > >> >> My guess is that it's one of the three programs above you mentioned.
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
> >
>
>
>
 
Re: blue screen scanning registry

See if line 35 helps:
http://www.kellys-korner-xp.com/xp_tweaks.htm

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm

SupportSpace
www.supportspace.com/pages?aiu=kellyskorner

"santashelper" <santashelper@discussions.microsoft.com> wrote in message
news:37218FB8-629F-4975-ACFB-E48ADEB52C94@microsoft.com...
> tried what you suggested by loading regedit from the XP cd. no luck. It
> does fail with any program that scans the registry. I.E. Spyware Doctor,
> AVG,
> PC Pitstop.
>
>
> "Pegasus (MVP)" wrote:
>
>>
>> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
>> news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
>> > Used command line:
>> > c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_
>> > c:\regedit.exe
>> >
>> > received msg.:
>> > Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
>> > copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
>> >
>> > Can't open input file: d:\i386\regedit.ex_.
>> >
>> > Looked at CD contents and found regedit.exe in the i386 folder .
>>
>> Mhm. Well. This means that the file is not compressed on the CD and does
>> not
>> need expanding. Just execute it as it is: D:\i386\regedit.exe.
>>
>>
>>
 
Re: blue screen scanning registry

First of all I have tried everything that was suggested.
Second, what do you mean by line 35?


"Kelly" wrote:

> See if line 35 helps:
> http://www.kellys-korner-xp.com/xp_tweaks.htm
>
> --
>
> All the Best,
> Kelly (MS-MVP/DTS&XP)
>
> Taskbar Repair Tool Plus!
> http://www.kellys-korner-xp.com/taskbarplus!.htm
>
> SupportSpace
> www.supportspace.com/pages?aiu=kellyskorner
>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:37218FB8-629F-4975-ACFB-E48ADEB52C94@microsoft.com...
> > tried what you suggested by loading regedit from the XP cd. no luck. It
> > does fail with any program that scans the registry. I.E. Spyware Doctor,
> > AVG,
> > PC Pitstop.
> >
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> >> news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
> >> > Used command line:
> >> > c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_
> >> > c:\regedit.exe
> >> >
> >> > received msg.:
> >> > Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
> >> > copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
> >> >
> >> > Can't open input file: d:\i386\regedit.ex_.
> >> >
> >> > Looked at CD contents and found regedit.exe in the i386 folder .
> >>
> >> Mhm. Well. This means that the file is not compressed on the CD and does
> >> not
> >> need expanding. Just execute it as it is: D:\i386\regedit.exe.
> >>
> >>
> >>
>
>
 
Re: blue screen scanning registry

Have tried everything suggested and no cure. Is there any hardware
dianostics for an AMD athlon Thunderbird or perhaps bios updates for an FDI
AK76-SN mother board

"Pegasus (MVP)" wrote:

>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
> > Used command line:
> > c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_ c:\regedit.exe
> >
> > received msg.:
> > Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
> > copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
> >
> > Can't open input file: d:\i386\regedit.ex_.
> >
> > Looked at CD contents and found regedit.exe in the i386 folder .
>
> Mhm. Well. This means that the file is not compressed on the CD and does not
> need expanding. Just execute it as it is: D:\i386\regedit.exe.
>
>
>
 
Re: blue screen scanning registry

Need some clarification first.

Does the blue screen *only* occur if you are scanning the registry? If
so, this is surely a software issue.

Does it *ever* occur in Safe Mode? If not, one of your programs such as
PC Pitstop is probably to blame.


santashelper wrote:
> Have tried everything suggested and no cure. Is there any hardware
> dianostics for an AMD athlon Thunderbird or perhaps bios updates for
> an FDI AK76-SN mother board
>
> "Pegasus (MVP)" wrote:
>
>>
>> "santashelper" <santashelper@discussions.microsoft.com> wrote in
>> message news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
>>> Used command line:
>>> c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_
>>> c:\regedit.exe
>>>
>>> received msg.:
>>> Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
>>> copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
>>>
>>> Can't open input file: d:\i386\regedit.ex_.
>>>
>>> Looked at CD contents and found regedit.exe in the i386 folder .
>>
>> Mhm. Well. This means that the file is not compressed on the CD and
>> does not need expanding. Just execute it as it is:
>> D:\i386\regedit.exe.
 
Re: blue screen scanning registry

I have had a few random blue screens when online. All of the scans work in
safe mode. None of the scans work in normal mode. Pcpitstop.com runs test
over the internet through an activex control. Regedit has been reloaded from
the orginal Microsoft XP Home CD. AVG is a virus check program and I have
been using it for several years.



"Daave" wrote:

> Need some clarification first.
>
> Does the blue screen *only* occur if you are scanning the registry? If
> so, this is surely a software issue.
>
> Does it *ever* occur in Safe Mode? If not, one of your programs such as
> PC Pitstop is probably to blame.
>
>
> santashelper wrote:
> > Have tried everything suggested and no cure. Is there any hardware
> > dianostics for an AMD athlon Thunderbird or perhaps bios updates for
> > an FDI AK76-SN mother board
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "santashelper" <santashelper@discussions.microsoft.com> wrote in
> >> message news:408A82B1-2B8C-4183-8315-D6BB7BA7961F@microsoft.com...
> >>> Used command line:
> >>> c:\Documents and Settigns\Owner> expand d:\i386\regedit.ex_
> >>> c:\regedit.exe
> >>>
> >>> received msg.:
> >>> Microsoft (R) E\File Expansion Utility Version 5.1.2600.0
> >>> copyright (C) Microsoft Corp. 1998-1999. All rights reserved.
> >>>
> >>> Can't open input file: d:\i386\regedit.ex_.
> >>>
> >>> Looked at CD contents and found regedit.exe in the i386 folder .
> >>
> >> Mhm. Well. This means that the file is not compressed on the CD and
> >> does not need expanding. Just execute it as it is:
> >> D:\i386\regedit.exe.
>
>
>
 
Re: blue screen scanning registry

What is the difference between running regedit in normal mode vs safe mode?

"Pegasus (MVP)" wrote:

>
> "santashelper" <santashelper@discussions.microsoft.com> wrote in message
> news:1B07D48F-1A77-41E1-88A5-88C63FDBFAD2@microsoft.com...
> > Whenever my registry is scanned either by regedit or AVG i get a blue
> > screen
> > of death. The error code is:0x00000050 (address error). The parameters
> > are:
> > 1 0xfdfffff8, 2 0x00000000 3 0x8054aa32B5B2, 4 0x00000000. Have tried
> > taking
> > out all hardware and drivers except AGP display card with same results.
> > Removed AGP card and driver and used a known good pci graphics card with
> > same
> > results. Put in new memory and it checked good with mem86 3.4A. Still get
> > blue scren of death when registry is scanned. Tried runnig PC PITSTOP
> > full
> > tests and still get blue screen. If I run in safe mode it runs everything
> > fine. Does anyone know what to do to solve this problem?
>
> I don't know about AVG but the native regedit.exe utility does not "scan"
> the registry - it opens it for viewing or for editing. Make sure to run the
> real thing by typing "c:\windows\regedit.exe" in the Run box, not some
> malware look-alike program.
>
> Since the problem does not occur in Safe Mode, you need to perform the usual
> elimination process:
> 1. Physically disconnect your machine from the Internet.
> 2. Boot into Safe Mode.
> 3. Run msconfig.exe.
> 4. Disable each and every task under the Startup tab.
> 5. Reboot normally. If this fixes the problem then you can restore the
> various startup tasks until you find the culprit.
>
> Do not restore your Internet connection until you have re-enabled your virus
> scanner and your software firewall (if you have one).
>
>
>
 

Similar threads

S
Fileless Registry Trojan
Replies
0
Views
103
Sevyrr
S
B
ZTE Axon Pro review: A killer flagship that won’t break the bank
Replies
0
Views
165
Brad Ward
B
AWS
LG Thrill 4G review
Replies
0
Views
342
AWS
AWS
V
Windows Vista Blue Screen Error
Replies
2
Views
160
Malke
M
AWS
Samsung Infuse 4G review
Replies
0
Views
286
AWS
AWS
Back
Top