From: wolverine01@charter.net   
      
   On 11/19/2025 6:57 PM, Paul wrote:   
   > On Wed, 11/19/2025 5:04 PM, sticks wrote:   
   >> On 11/19/2025 8:08 AM, Paul wrote:   
   >>> On Tue, 11/18/2025 11:26 PM, sticks wrote:   
   >>>> The box in question is a rather older machine, but has always been steady   
   and   
   >>>> actually the one I use the most because it is out in my workshop area.    
   That said,   
   >>>> it was originally win 7 that I installed win 10 on several years ago.    
   It runs   
   >>>> all day long usually, and I put it to sleep at night.  Not as fast as my   
   newer   
   >>>> one in my office, but it works nicely with latest Firefox, BBird, Office   
   2019   
   >>>> and most other programs I need.   
   >>>>   
   >>>> So, a couple days ago, I would come to the computer and notice it had   
   rebooted.   
   >>>> The arrangement on my Core Temp taskbar icons were not as I had left   
   them, and   
   >>>> the BBird was closed.  So after a couple of these, I started   
   investigating.   
   >>>>   
   >>>> Event Viewer showed it booted because of a bugcheck error.  This error   
   was the   
   >>>> same for several reboots.  It didn't reboot while I was using it, and   
   otherwise   
   >>>> worked just fine.   
   >>>>   
   >>>> So I did the DISM /restore which couldn't find a source.  It did say the   
   files   
   >>>> were repairable.  So I got an win 10 iso and used it for the source and   
   it did   
   >>>> say it repaired everything.   
   >>>>   
   >>>> I then did an SFC/ scannow and it reported everything OK.   
   >>>> Next I did a chkdsk /f and it reported nothing to fix.   
   >>>>   
   >>>> Used it for awhile and all seemed ok.  Came back later and it had   
   rebooted again.   
   >>>>   
   >>>> Checked on video driver and already had the best one.   
   >>>> Virus check and nothing there   
   >>>>   
   >>>> Rebooted again, so I decided to try a system restore point.  First time,   
   it   
   >>>> rebooted after a short time doing the restore.   
   >>>>   
   >>>> Did a memory check using the windows memory test.  I know it's not the   
   best,   
   >>>> but it said all was good.   
   >>>>   
   >>>> Tried a second time to restore and after over 2 hours I finally shut it   
   down   
   >>>> and restarted.  Hated doing that, but it seemed to be stuck.   
   >>>>   
   >>>> Decided to do a restore, saving my files, and it got to the first reboot   
   at   
   >>>> about 12% and failed, resetting back to before the setup.  I didn't   
   catch the   
   >>>> error on that one before restarting, but when it came back on it said   
   >>>> 0x8007025D - 0x2000C The installation failed in the SAFE_OS phase with an   
   >>>> error during APPLY-IMAGE operation.   
   >>>>   
   >>>> Today, the damn thing ran fine all day until about 5 PM.  The above error   
   >>>> suggested faulty install media, so I got a new usb card and made a new   
   set of   
   >>>> install files and tried again.  This time it rebooted several times and   
   got   
   >>>> to 82% and screen said the stop code was MEMORY MANAGEMENT.  Upon   
   restarting   
   >>>> the screen said 0xC1900101 - 0x4000D The installation failed in the   
   SECOND BOOT   
   >>>> phase with an error during MIGRATE DATA operation.   
   >>>>   
   >>>> It has been running since and I'm typing this on it now.   
   >>>>   
   >>>> My questions:   
   >>>> Am I missing something I should do?   
   >>>> Do you think this is a software issue, or hardware?   
   >>>>   
   >>>> I would like to fix it if it is a screwed up install or corrupted files,   
   but   
   >>>> I don't really want to do something like try new memory on this old box.   
   >>>>   
   >>>> Any help appreciated!   
   >>>>   
   >>>   
   >>> The first observation, is this is a workshop area PC.   
   >>>   
   >>> Do you generate a lot of sawdust in the area ? Do you smoke ?   
   >>> I'm looking for evidence the cooling system is not in good shape,   
   >>> or the HDD breathe-able hepafilter has ingested a solvent   
   >>> in the air, or smoke has gummed up the equipment.   
   >>   
   >> I call it a workshop, but it is actually a small portion of my garage.   
   Originally I wanted a computer in there so I could follow along on repair   
   videos for things I was working on, like my motorcycle.   
   >> I use Core Temp to keep an eye on temperatures as though I heat it, I do   
   not cool it in the summer.  It does get hot for probably about 10 days each   
   year where the fan really kicks up like when watching a video.  But now, it   
   runs very cool.  I did    
   reapply the thermo paste about two years ago, and if you remember I doubled   
   the ram from 4-8 Gig with your help, even though the book on it said four was   
   the limit.   
   >>   
   >>> Your post makes no reference to the storage device, how many   
   >>> years it has been spinning all day.   
   >>   
   >> I Like to keep it running because it filters all the incoming crap in my   
   email so I don't have to deal with it during the day when I look at the   
   phone.  It has been only a few years I keep it running, and I do sleep it   
   when it gets hot.  But I'll    
   explain in a minute why I'm delaying looking into this for now.   
   >>   
   >>> A general idea of make/model of machine would help ascertain   
   >>> what era of memory it uses, and whether we should be concerned   
   >>> about memory. DDR2 seemed to be error prone (I only had one   
   >>> machine which was rock solid on DDR2, and it ran at DDR2-533   
   >>> which tells you "speed makes a difference" there). DDR3 generally   
   >>> seems to be pretty good. I have a couple machines on DDR3 and   
   >>> don't see the failure syndrome you are seeing.   
   >>   
   >> It's a Compaq Presario BM412AA-ABA CQ5600Y   
   >> 8GB of DDR2.  Pegatron Narra5 motherboard.   
   >> AMD Phenom II X2 B59 (CAllisto) processor   
   >> It's pretty "adult" now.   
   >>   
   >> ---snip---   
   >>   
   >> That said, here's where I'm at now.  I read something about a failure on   
   an upgrade perhaps being helped by using the windows upgrade tool.  So I did   
   run it and it found three of what seemed relatively minor fixes. This is after   
   it had been running    
   three hours without any problems today.   
   >>   
   >> I decided to try and reinstall one more time.  (Side Note:  Firefox was   
   minimized just now and I was informed it stopped working and closed Hmmm)    
   Anyways, it finally completed a fresh install taking an hour and a half to   
   complete.  I made a    
   couple adjustments and then immediately imaged the drive.  It has been   
   running now for 8 hours and right up until Firefox just closed, I have had no   
   problems.   
   >>   
   >> I feel I am at least now in a spot where I can decide if it is hardware or   
   software related.  When I step away from now on, I will close my open   
   programs and if it boots on a fresh install, I can figure it is probably   
   hardware related.  If after a    
   couple days I get no problems, I'll leave the mail open and then the browser,   
   both usually minimized, and go from there.   
   >>   
   >> FWIW, I'm not against getting a new system, but with the summer heat this   
   is not the best environment for a computer and if I can keep this one running   
   without wasting a lot of time, I'd prefer to do that.   
   >>   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)