From: nospam@needed.invalid   
      
   On Mon, 11/24/2025 5:54 PM, sticks wrote:   
   > On 11/19/2025 8:52 PM, sticks wrote:   
   >> On 11/19/2025 6:57 PM, Paul wrote:   
   >>> On Wed, 11/19/2025 5:04 PM, sticks wrote:   
   >   
   > ---snip---   
   >   
   >>>>> Your post makes no reference to the storage device, how many   
   >>>>> years it has been spinning all day.   
   >   
   > https://i.postimg.cc/4dyW4QHp/Smart.jpg   
   >   
   >> I bought the thing several years ago, so long I can't remember actually,   
   but I am pretty sure I only gave $50 for it.  I used to go wireless, but it's   
   pretty far from the router so I wired out here for ethernet and that helped   
   with function a lot.     
   For what my original intentions were for having something out in the garage,   
   this damn thing has been pretty good.  This is really the first time I've had   
   an issue, and it appears something got corrupted, but just might have been   
   fixed with the    
   successful reinstall.  All day now with no reboots.  Fingers crossed.   
   >   
   > It started rebooting again, so I reran the chkdsk, sfc, and dism stuff, but   
   it still had problems.  Below were some of the events.  They were not all   
   the same, and I remembered your advice on checking out the disk so I installed   
   HD tune to check it    
   out, and got the results in the link above.  It does look like the drive   
   might be on it's last legs.   
   >   
   > So before I just go and buy a new box, I'm gonna try another drive I have   
   laying around.  It's a 640 Gig laptop drive, but I'm not buying a new desktop   
   drive for this old machine.  I have a brand new 1 TB Samsung 990, but I can't   
   use it since it    
   doesn't have the connectors on the board for it.  If the spinner works   
   without errors, I'll know that was the problem.  Fun fun fun.   
   >   
   > ----------------------   
   > 1.  The computer has rebooted from a bugcheck.  The bugcheck was:   
   0x00000139 (0x0000000000000003, 0xffffb783ade056c0, 0xffffb783ade05618,   
   0x0000000000000000).   
   >   
   > 2.  The computer has rebooted from a bugcheck.  The bugcheck was:   
   0x0000003b (0x00000000c0000005, 0xfffff80627a83518, 0xfffff8062b0ad920,   
   0x0000000000000000).   
   > The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b   
   (0x00000000c0000005, 0xfffff8003fb08db2, 0xffff8e88cd64ba30, 0x0   
   00000000000000).   
   >   
   > 3.  The computer has rebooted from a bugcheck.  The bugcheck was:   
   0x0000003b (0x00000000c0000005, 0xfffff8003fb08db2, 0xffff8e88cd64ba30,   
   0x0000000000000000).   
   >   
   > 4.  The computer has rebooted from a bugcheck.  The bugcheck was:   
   0x0000001e (0xffffffffc0000005, 0xfffff800528d23c5, 0x0000000000000001,   
   0x0000000000000103).   
      
   Your Reallocated Sector Count seems a bit strange.   
   I think it is trying to report "2", at a guess.   
      
   Your bugchecks seem to be in Ring0, which could be memory used   
   for kernel and drivers. That does not have a strong disk drive   
   component to it, directly. And while it could have an indirect   
   effect, you would think there would be more splatter in the   
   form of crashing or erroneous application behavior. Your error   
   behavior seems relatively focused.   
      
   KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139   
      
   SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B    (possibly   
   driver related)   
      
   KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E    
   (status_access_violation as well)   
      
   I had a weird one in WinXP days, that "seemed" to be ram buffer used for   
   disk operation (kernel level). When the RAM was changed out, the problem was   
   gone for   
   a while, but I don't really think it was gone. Now that the machine   
   is dead, no other machine in the room has had such symptoms.   
   Not every one of these problems, "behaves cleanly". They   
   do all sorts of weird stuff.   
      
   *******   
      
   By all means, try another drive. Just don't clone it on   
   that machine, OK ? Take the two disks to a machine that is   
   working, and do your cloning there. You may need to run a   
   CHKDSK using the machine that works well, before setting   
   up to do a clone. If there is a CRC error during cloning, most   
   cloning programs stop if that happens. The attempt to clone,   
   might even be a kind of test.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)