My guess is that either the drive or the memory is going bad on you. It is hard to tell which without testing. You can get errors like that, have the drive test as good so you clean install windows. A week or two later, errors start coming back. That is from bad memory modules.yep. normally that is my 'oh crap' go to and always at least number 2 on my fix it list. This time I just got a slew of errors, different every time I tried including the dreaded registry error. That was my first clue I was in deep doodoo this time. Just tried one last time "what the heck just in case" after all the other changes I've tried, going all the way back behind all of the recent critical updates. This time the message was basically "have no idea why it didn't work but it failed'.Oh well, can't complain. Just wasn't ready to concede defeat, hoping someone knew something I didn't about the new OS. I hardly used it at first but it's still roughly 7 yrs old, this fn thing is just the last quirk it''s recently developed and the battery is completely DOA (only holds a charge for less than 20 min.) soit's time to transfer to the new one while I still can tho i do have everything up in several clouds![]()
See you all hopefully by Monday if the net isn't drug down too much by the weekenders.
Thanks again Ron for trying to help. verymuch appreciated.
The solid state drives are coming way down in cost. I upgraded my work drive ant two laptops to solid state drives last summer.
It might be better to move to the new computer you have though. When computers like the old one start doing stuff like this, it is often an indication that the system board is failing and you would need to rebuild. Since new computers are always much faster and capable than the old ones, spending a bunch on them is not often very economical.
