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?

"santashelper" <(E-Mail Removed)> wrote in message
news:1B07D48F-1A77-41E1-88A5-(E-Mail Removed)...
> 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).

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" <(E-Mail Removed)> wrote in message
> news:1B07D48F-1A77-41E1-88A5-(E-Mail Removed)...
> > 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).
>
>
>

"santashelper" <(E-Mail Removed)> wrote in message
news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
>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"?

"Daave" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "santashelper" <(E-Mail Removed)> wrote in
> message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
>>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.

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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > "santashelper" <(E-Mail Removed)> wrote in
> > message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
> >>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.
>
>
>

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" <(E-Mail Removed)> wrote in message
news:4DDB2662-32B8-46A1-A692-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > "santashelper" <(E-Mail Removed)> wrote in
>> > message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
>> >>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.
>>
>>
>>

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" <(E-Mail Removed)> wrote in message
> news:4DDB2662-32B8-46A1-A692-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >> > "santashelper" <(E-Mail Removed)> wrote in
> >> > message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
> >> >>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.
> >>
> >>
> >>
>
>
>

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" <(E-Mail Removed)> wrote in message
news:7AF7BF47-C343-45D6-8483-(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
>> news:4DDB2662-32B8-46A1-A692-(E-Mail Removed)...
>> > 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" <(E-Mail Removed)> wrote in message
>> >> news:(E-Mail Removed)...
>> >> > "santashelper" <(E-Mail Removed)> wrote in
>> >> > message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
>> >> >>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.
>> >>
>> >>
>> >>
>>
>>
>>

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" <(E-Mail Removed)> wrote in message
> news:7AF7BF47-C343-45D6-8483-(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> >> news:4DDB2662-32B8-46A1-A692-(E-Mail Removed)...
> >> > 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" <(E-Mail Removed)> wrote in message
> >> >> news:(E-Mail Removed)...
> >> >> > "santashelper" <(E-Mail Removed)> wrote in
> >> >> > message news:3EA95FCB-0940-4AF9-9165-(E-Mail Removed)...
> >> >> >>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.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>