Can't restart. Re-start circle(?) just goes round and round endlessly

Page 13 of 14 FirstFirst ... 311121314 LastLast

  1. Posts : 219
    Windows 10 Pro
    Thread Starter
       #121

    Marie SWE said:
    Yes i use Linux as daily driver, so i only boot in to windows if i need to run software that dont work on linux.
    I just finished one install a few hours ago and posted a picture in the thread Show Us Your Desktop [11]

    I had never heard of uWin.. .
    uWin is authored by the dev of korn shell. It predates WSL and was useful for testing scripts when the only machine available was Windows.
      My Computer


  2. Posts : 2,884
    Windows 10 Pro for the Bro
       #122

    bofhlusr said:
    Here are the event viewer files from the 2019 disk image:

    Dropbox - Eventviewer.zip - Simplify your life

    And a video:
    Tech troubleshooting demo of Re-start and Shutdown - YouTube

    I hope it helps.
    Hi, so a few updates. I took a glance at the Event Viewer logs you posted.
    I think they're logged in System.

    So what I was able to get out of the difference from the picture from earlier, in the first page:
    https://www.tenforums.com/attachment...tart-error.jpg

    Is that there's a bunch of "disk" warnings and the NTFS 140 event.
    I looked online on how to fix the 140 event, and saw there's the checkdisk thing we can try.

    See if you can run this command from an Administrator Command Prompt:
    CHKDSK /F /R /X

    (Source: Run CHKDSK /F /R /X Command to Fix Hard Drive Errors Windows 10 [Full Guide 2023] - EaseUS. )
      My Computer


  3. Posts : 219
    Windows 10 Pro
    Thread Starter
       #123

    pepanee said:
    Hi, so a few updates. I took a glance at the Event Viewer logs you posted.
    I think they're logged in System.

    So what I was able to get out of the difference from the picture from earlier, in the first page:
    https://www.tenforums.com/attachment...tart-error.jpg

    Is that there's a bunch of "disk" warnings and the NTFS 140 event.
    I looked online on how to fix the 140 event, and saw there's the checkdisk thing we can try.

    See if you can run this command from an Administrator Command Prompt:
    CHKDSK /F /R /X

    (Source: Run CHKDSK /F /R /X Command to Fix Hard Drive Errors Windows 10 [Full Guide 2023] - EaseUS. )
    I was under the impression that chkdsk does not apply to NVMe drives?
      My Computer


  4. Posts : 2,884
    Windows 10 Pro for the Bro
       #124

    bofhlusr said:
    I was under the impression that chkdsk does not apply to NVMe drives?
    Honestly, I have no clue about anything regarding that neither. But I'm really sure there won't be any harm done. Who knows, there's a small chance this may fix things? I honestly have no clue.
    But the reason why I mentioned this idea is because one of the main differences I saw between the broken computer log and the working computer log was Event 140.
    Online solutions to Event 140 is that certain checkdisk command I stated in the previous post. So.. I'm really hoping this could come out with a positive outcome? Let's hope so!! Cross our fingers!

    PS if what you're saying is if it applies to SSDs in general, right?
    > does checkdisk apply to ssds - Search
    So that could be good news.
    Over time, small sectors of SSDs become corrupt and unusable anymore. So Windows would "re-write in the MFT of an SSD" that a certain sector is unreadable, and never let any other computer write to those certain sectors. (Not sure if "sector" is the right term".)


    For example: [all my drives are SSDs]
    In this picture, I took a picture of my main drive in this app. Notice it's at 90% with a number bigger than zero for bad blocks?
    Can't restart. Re-start circle(?) just goes round and round endlessly-image.png

    Here's a picture of a drive that I ONLY send files to, and almost never EVER modify any file. I open the files a lot on this drive, but almost never EVER edit any files there; it's like a "read-only" drive:
    Can't restart. Re-start circle(?) just goes round and round endlessly-image.png

    99% good.
    I cannot find the "bad block" count or whatever.
    But I'm sure you see the idea I'm getting at: SSDs do get damaged over time when you erase/modify files on them.
    Don't let that worry you though. I write/erase/modify stuff on my main drive (Windows also does, a LOT more than I do). I've had this drive for probably at least a few years, and it runs perfect.
      My Computer


  5. Posts : 219
    Windows 10 Pro
    Thread Starter
       #125

    Didn't work. Chkdsk requires a re-start but the problem is the re-start does not work.
      My Computer


  6. Posts : 2,884
    Windows 10 Pro for the Bro
       #126

    bofhlusr said:
    Didn't work. Chkdsk requires a re-start but the problem is the re-start does not work.
    You right.
    That idea came across my head as well as a possibility.

    So, let's try it out from Safe Mode.
      My Computer


  7. Posts : 6,194
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #127

    bofhlusr said:
    Didn't work. Chkdsk requires a re-start but the problem is the re-start does not work.
    I think you can shutdown and then start.

    For sure you can boot a Win 10 installation drive, launch a CMD window (Shift+F10 simultaneously) and run from Win PE
      My Computers


  8. Posts : 219
    Windows 10 Pro
    Thread Starter
       #128

    pepanee said:
    You right.
    That idea came across my head as well as a possibility.

    So, let's try it out from Safe Mode.
    In Safemode, chkdsk ran for the system drive but it was going to take at least an hour. I let it run overnight. I checked the PC this morning and apparently chkdsk completed. Unfortunately, the problems persist. Software-based Re-start and Shutdown never completes. :-(

    - - - Updated - - -

    Megahertz said:
    I think you can shutdown and then start.

    For sure you can boot a Win 10 installation drive, launch a CMD window (Shift+F10 simultaneously) and run from Win PE
    Thank you. I would have tried that but chkdsk ran thanks to @pepanee's suggestion.

    - - - Updated - - -

    chkdsk log:


    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is SYS.

    A disk check has been scheduled.
    Windows will now check the disk.

    Stage 1: Examining basic file system structure ...
    1488640 file records processed.
    File verification completed.
    Phase duration (File record verification): 6.31 seconds.
    14353 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 0.81 milliseconds.

    Stage 2: Examining file name linkage ...
    6146 reparse records processed.
    2093756 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 18.96 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 9.91 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.49 seconds.
    6146 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 14.18 milliseconds.

    Stage 3: Examining security descriptors ...
    Cleaning up 3353 unused index entries from index $SII of file 0x9.
    Cleaning up 3353 unused index entries from index $SDH of file 0x9.
    Cleaning up 3353 unused security descriptors.
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 35.53 milliseconds.
    302559 data files processed.
    Phase duration (Data attribute verification): 0.89 milliseconds.
    CHKDSK is verifying Usn Journal...
    36777856 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 90.78 milliseconds.

    Stage 4: Looking for bad clusters in user file data ...
    1488624 files processed.
    File data verification completed.
    Phase duration (User file recovery): 15.97 minutes.

    Stage 5: Looking for bad, free clusters ...
    246721112 free clusters processed.
    Free space verification is complete.
    Phase duration (Free space recovery): 0.00 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1952871750 KB total disk space.
    963730220 KB in 1098938 files.
    600408 KB in 302560 indexes.
    0 KB in bad sectors.
    1656670 KB in use by the system.
    65536 KB occupied by the log file.
    986884452 KB available on disk.

    4096 bytes in each allocation unit.
    488217937 total allocation units on disk.
    246721113 allocation units available on disk.
    Total duration: 16.59 minutes (995679 ms).

    Internal Info:
    00 b7 16 00 9d 62 15 00 d1 0b 24 00 00 00 00 00 .....b....$.....
    67 03 00 00 9b 14 00 00 00 00 00 00 00 00 00 00 g...............
      My Computer


  9. Posts : 2,884
    Windows 10 Pro for the Bro
       #129

    bofhlusr said:
    ... Unfortunately, the problems persist. Software-based Re-start and Shutdown never completes. :-(
    Ooof, I was really hoping this was it.
    So I've been giving it a little thought, and from those Warning logs in Event Viewer, I am thinking of the possibility that one or more of the "powering down" files of your computer have become corrupt, and the computer is saving those corrupt files, as "valid" normal files.

    Example: Say the file is supposed to look like: "abcdefghijklmnop"
    Yet it is was originally placed on a "weird" corrupt block in the drive where your computer has that file saved as: "abc__fg__jk__nop"

    So every time you restore the image, the corrupt-looking file is the one that is placed wherever Windows decides to place it, thinking that "abc__fg__jk__nop" is how the file is supposed to look like. But it's not.

    SO, I found this video containing a bunch of suggestions. I'd try all the ones that you haven't tried yet:
    How to Fix Windows 10 Won't Shut down Issue? [8 Solutions] - YouTube

    But FIRST, try the suggestion before the last one, which is the "sfc /scannow" command. This command finds corrupt files, like in the example I just stated, and replaces those files with the original one that's supposed to be working. I am really hoping that's what those "disk" warnings your Event Viewer is listing, but way more likely is that 140 Event, and that command would fix them. Let's REALLY REALLY hope so. We can all cross our fingers together =)

    But here's the thing. Start the computer up in Safe Mode again, and in the Command Prompt, use this command:
    sfc /scannow

    Let's really Really REALLY REALLY hope this fixes it. =)

    And, worst case scenario, if it didn't work, then go through the checklist of the suggestions in that video.
    Keep note that the last suggestion is an advertisement for you to get their program. You don't want that. I didn't even watch it, I just noticed "ohhh it's a commercial, lol"

    Let's really pray your computer got fixed by then, if not, you can browse around the results of this in YouTube. Look at other suggestions:
    https://www.youtube.com/results?sear...hut+down+issue


    I really hope we can figure this one out.
    This is one of the most nastiest bugs that I've ever encountered.
    =)
      My Computer


  10. Posts : 219
    Windows 10 Pro
    Thread Starter
       #130

    pepanee said:
    ...This is one of the most nastiest bugs that I've ever encountered...
    Thanks, but here's somethings though that you might be forgetting?

    The hardware (including the system drive) has been tested as fine. Additionally, an almost new install of Windows from restoring my 2019 disk image did not show the errors. This likely leads to the conclusion that the error is not in the hardware.

    Nor is the error in software (I did a "Repair Install". And, I did SFC /scannow several times).

    Nonetheless, I'll go on safe mode and do sfc /scannow.

    - - - Updated - - -

    Another dead end.

    In safemode it wouldn't allow me to do "sfc /scannow". Reason: "Windows Resource Protection".

    I also could NOT get out of Safe Mode. After many attempts, I was able to exit Safe Mode and go to my normal desktop but had problems. No audio and ethernet device regardless of what I did.

    Instead of troubleshooting endlessly, I instead restored from a image back up again. This is probably already 3-4 restores since the last backup. At this point, I'm missing my 20 GB system drive from way back when (probably when the OS had a small footprint: Win 7 or Win XP). The restores on those were quick. The issue of long restore times is making me think twice about upgrading to a 4 TB NVMe drive if and when they come out to the market.

    I'm betting if I called Microsoft now, their tech support will likely just say "re-install Windows".
    Last edited by bofhlusr; 09 May 2023 at 23:00.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:02.
Find Us




Windows 10 Forums