Windows registry is damaged. Windows will restart and try to fix the problem.

[Gary]

Posted this over on Velocity but got no response!

Have been chasing this problem for some time. Found an old Win note that
indicates it might be a memory problem. Have reduced the amount of useable
memory from 312 meg to 64 meg to try.

Any one have any more info on this problem? Would appreciate any
suggestions as to what to try.

Thanks

 

[Don Phillipson]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.

"Gary" <gspence@NOSPAMcharter.net> wrote in message
news:OwujwRtKIHA.1188@TK2MSFTNGP04.phx.gbl...

> Have been chasing this problem for some time. Found an old Win note that
> indicates it might be a memory problem. Have reduced the amount of
useable
> memory from 312 meg to 64 meg to try.
>
> Any one have any more info on this problem? Would appreciate any
> suggestions as to what to try.

There is too little information to define the problem.
If this PC ever booted Windows OK in the last week
you should try (DOS reboot and)
SCANREG /RESTORE
and choose the date of a good boot.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)

 

[philo]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"Gary" <gspence@NOSPAMcharter.net> wrote in message
news:OwujwRtKIHA.1188@TK2MSFTNGP04.phx.gbl...
> Posted this over on Velocity but got no response!
>
> Have been chasing this problem for some time. Found an old Win note that
> indicates it might be a memory problem. Have reduced the amount of
useable
> memory from 312 meg to 64 meg to try.
>
> Any one have any more info on this problem? Would appreciate any
> suggestions as to what to try.
>
> Thanks
>


try different memory sticks
or run a memory diagnostic

the 64megs you have in the machine might be flakey

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"philo" <philo@privacy.net> wrote in message
news:%238LjRYvKIHA.280@TK2MSFTNGP03.phx.gbl...
>
> "Gary" <gspence@NOSPAMcharter.net> wrote in message
> news:OwujwRtKIHA.1188@TK2MSFTNGP04.phx.gbl...
>> Posted this over on Velocity but got no response!
>>
>> Have been chasing this problem for some time. Found an old Win note that
>> indicates it might be a memory problem. Have reduced the amount of
> useable
>> memory from 312 meg to 64 meg to try.
>>
>> Any one have any more info on this problem? Would appreciate any
>> suggestions as to what to try.
>>
>> Thanks
>>
>
>
> try different memory sticks
> or run a memory diagnostic
>
> the 64megs you have in the machine might be flakey
>
>
Have two sticks, one 256 meg (added approx 2 yrs ago) and one 64meg
(original i.e. 1995?). Think it is using the 256 stick at the beginning so
am probably running in the bottom 64 megs of the 256 stick.

Have only restarted approx 3 time since I changed the available memory but
no errors yet!

As time progresses I will use one or the other of the sticks if the problem
returns.

Got any links to a memory diagnostic?

Thanks for the quick response.

Gary

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"Don Phillipson" <d.phillipsonSPAMBLOCK@rogers.com> wrote in message
news:%23LwO%23kvKIHA.4584@TK2MSFTNGP03.phx.gbl...
> "Gary" <gspence@NOSPAMcharter.net> wrote in message
> news:OwujwRtKIHA.1188@TK2MSFTNGP04.phx.gbl...
>
>> Have been chasing this problem for some time. Found an old Win note that
>> indicates it might be a memory problem. Have reduced the amount of
> useable
>> memory from 312 meg to 64 meg to try.
>>
>> Any one have any more info on this problem? Would appreciate any
>> suggestions as to what to try.
>
> There is too little information to define the problem.
> If this PC ever booted Windows OK in the last week
> you should try (DOS reboot and)
> SCANREG /RESTORE
> and choose the date of a good boot.
>
> --
> Don Phillipson
> Carlsbad Springs
> (Ottawa, Canada)
>
>
Have done a restore to no avail

Sorry for the lack of thought on my part (after all I know what's going on
why wouldn't you ha ha!) The computer has been restarted many times with no
problem! Only rarely does the problem show up!

I have another problem that may or may not be related. On boot the display
resolution some times (rarely) comes up at 480x640 instead of 1024x768! The
problem is that I can't reset it in control panel, display,settings.
Settings bar is "stuck". Only after rebooting (sometimes several times) can
I reset the display resolution.

Thanks for getting in the discussion.

Gary

 

[philo]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.



> >
> >
> > try different memory sticks
> > or run a memory diagnostic
> >
> > the 64megs you have in the machine might be flakey
> >
> >
> Have two sticks, one 256 meg (added approx 2 yrs ago) and one 64meg
> (original i.e. 1995?). Think it is using the 256 stick at the beginning
so
> am probably running in the bottom 64 megs of the 256 stick.
>
> Have only restarted approx 3 time since I changed the available memory but
> no errors yet!
>
> As time progresses I will use one or the other of the sticks if the
problem
> returns.
>
> Got any links to a memory diagnostic?


check here

http://oca.microsoft.com/en/windiag.asp

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"philo" <philo@privacy.net> wrote in message
news:uWiFpJwKIHA.280@TK2MSFTNGP03.phx.gbl...
>
>
>> >
>> >
>> > try different memory sticks
>> > or run a memory diagnostic
>> >
>> > the 64megs you have in the machine might be flakey
>> >
>> >
>> Have two sticks, one 256 meg (added approx 2 yrs ago) and one 64meg
>> (original i.e. 1995?). Think it is using the 256 stick at the beginning
> so
>> am probably running in the bottom 64 megs of the 256 stick.
>>
>> Have only restarted approx 3 time since I changed the available memory
>> but
>> no errors yet!
>>
>> As time progresses I will use one or the other of the sticks if the
> problem
>> returns.
>>
>> Got any links to a memory diagnostic?
>
>
> check here
>
> http://oca.microsoft.com/en/windiag.asp
>
>
>
Ran the memory extended test several time with no errors. Nuts that would
have been too simple!

No new registry errors though since I ran the scanreg /fix routine. Maybe
its fixed! Will reply if any more problems unless some one has any other
ideas.

Thanks much for the help.

Gary

 

[Buffalo]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"Gary" <gspence@NOSPAMcharter.net> wrote in message
news:%23iGizM7KIHA.748@TK2MSFTNGP04.phx.gbl...
>
> "philo" <philo@privacy.net> wrote in message
> news:uWiFpJwKIHA.280@TK2MSFTNGP03.phx.gbl...
> >
> >
> >> >
> >> >
> >> > try different memory sticks
> >> > or run a memory diagnostic
> >> >
> >> > the 64megs you have in the machine might be flakey
> >> >
> >> >
> >> Have two sticks, one 256 meg (added approx 2 yrs ago) and one 64meg
> >> (original i.e. 1995?). Think it is using the 256 stick at the
beginning
> > so
> >> am probably running in the bottom 64 megs of the 256 stick.
> >>
> >> Have only restarted approx 3 time since I changed the available memory
> >> but
> >> no errors yet!
> >>
> >> As time progresses I will use one or the other of the sticks if the
> > problem
> >> returns.
> >>
> >> Got any links to a memory diagnostic?
> >
> >
> > check here
> >
> > http://oca.microsoft.com/en/windiag.asp
> >
> >
> >
> Ran the memory extended test several time with no errors. Nuts that would
> have been too simple!
>
> No new registry errors though since I ran the scanreg /fix routine. Maybe
> its fixed! Will reply if any more problems unless some one has any other
> ideas.
>
> Thanks much for the help.
>
> Gary

Sometimes simply removing memory sticks and re-inserting them corrects a pin
connecton problem due to oxidation, etc.
If the problem resurfaces, remove and re-insert the sticks several times and
do the same for the video card.

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"Buffalo" <Eric@nada.com.invalid> wrote in message
news:w6udnRleQ5gBLNTanZ2dnUVZ_s6mnZ2d@comcast.com...
>
> "Gary" <gspence@NOSPAMcharter.net> wrote in message
> news:%23iGizM7KIHA.748@TK2MSFTNGP04.phx.gbl...
>>
>> "philo" <philo@privacy.net> wrote in message
>> news:uWiFpJwKIHA.280@TK2MSFTNGP03.phx.gbl...
>> >
>> >
>> >> >
>> >> >
>> >> > try different memory sticks
>> >> > or run a memory diagnostic
>> >> >
>> >> > the 64megs you have in the machine might be flakey
>> >> >
>> >> >
>> >> Have two sticks, one 256 meg (added approx 2 yrs ago) and one 64meg
>> >> (original i.e. 1995?). Think it is using the 256 stick at the
> beginning
>> > so
>> >> am probably running in the bottom 64 megs of the 256 stick.
>> >>
>> >> Have only restarted approx 3 time since I changed the available memory
>> >> but
>> >> no errors yet!
>> >>
>> >> As time progresses I will use one or the other of the sticks if the
>> > problem
>> >> returns.
>> >>
>> >> Got any links to a memory diagnostic?
>> >
>> >
>> > check here
>> >
>> > http://oca.microsoft.com/en/windiag.asp
>> >
>> >
>> >
>> Ran the memory extended test several time with no errors. Nuts that
>> would
>> have been too simple!
>>
>> No new registry errors though since I ran the scanreg /fix routine.
>> Maybe
>> its fixed! Will reply if any more problems unless some one has any other
>> ideas.
>>
>> Thanks much for the help.
>>
>> Gary
>
> Sometimes simply removing memory sticks and re-inserting them corrects a
> pin
> connecton problem due to oxidation, etc.
> If the problem resurfaces, remove and re-insert the sticks several times
> and
> do the same for the video card.
>
>
Did have the cards out so will see? No video card as it is built into the
mother board .

Thanks for the thoughts.

Gary

 

[Franc Zabkar]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.

On Sun, 25 Nov 2007 10:32:26 -0700, "Buffalo" <Eric@nada.com.invalid>
put finger to keyboard and composed:

>Sometimes simply removing memory sticks and re-inserting them corrects a pin
>connecton problem due to oxidation, etc.
>If the problem resurfaces, remove and re-insert the sticks several times and
>do the same for the video card.

I just had this same problem with my own PC. I changed a HD and then
lost about 48MB of RAM. :-(

The solution was to remove the DIMMs, *gently* clean the pins with a
soft eraser, and then spray both the pins and the sockets with contact
cleaning solvent.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.


"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:00njk398eesamcr7n8hq2mqv9i9722a3gf@4ax.com...
> On Sun, 25 Nov 2007 10:32:26 -0700, "Buffalo" <Eric@nada.com.invalid>
> put finger to keyboard and composed:
>
>>Sometimes simply removing memory sticks and re-inserting them corrects a
>>pin
>>connecton problem due to oxidation, etc.
>>If the problem resurfaces, remove and re-insert the sticks several times
>>and
>>do the same for the video card.
>
> I just had this same problem with my own PC. I changed a HD and then
> lost about 48MB of RAM. :-(
>
> The solution was to remove the DIMMs, *gently* clean the pins with a
> soft eraser, and then spray both the pins and the sockets with contact
> cleaning solvent.
>
> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.

Had the DIMM's out but did not clean them! Also did a scanreg /fix and /opt
four times so will have to see if any thing changes. No problems since but
probably too soon to tell! Can try further cleaning if problem reappears!

Thanks so much for trying.

Gary

 

[Gary]

Re: Windows registry is damaged. Windows will restart and try to fix the problem.

No new problems to date 12/7/07!

Thanks to all who responded

Gary
"Gary" <gspence@NOSPAMcharter.net> wrote in message
news:OwujwRtKIHA.1188@TK2MSFTNGP04.phx.gbl...
> Posted this over on Velocity but got no response!
>
> Have been chasing this problem for some time. Found an old Win note that
> indicates it might be a memory problem. Have reduced the amount of
> useable memory from 312 meg to 64 meg to try.
>
> Any one have any more info on this problem? Would appreciate any
> suggestions as to what to try.
>
> Thanks