Is My Windows 10 Corrupt - Settings Not Being Saved And Possibly More

Page 1 of 6 123 ... LastLast
  1.    06 Mar 2018 #1

    Is My Windows 10 Corrupt - Settings Not Being Saved And Possibly More


    Hi all. Everything was going great until a couple of hours ago. I got up from my computer, came back and it was rebooting itself. When it came back up I couldn't access any windows functions like the start menu, taskbar settings, clock, and so forth. I ran an SFC and DISM scan and both came up clean. I then used this tool and got the function of everything again.

    http://www.thewindowsclub.com/fixwin-for-windows-10

    So then I changed all my taskbar settings back to how they were but now when I reboot they won't save my settings. There's also a couple little issues that I swear weren't like they are now, but I really don't know. For instance, I have the "settings" tab saved to my start menu - I swear it used to say "settings" underneath it like all my other saved tabs - but now it just shows the gear picture. I have a "windows update" tab that now just says windows update but with no picture. Also, when I go into Windows Update and click on "view installed update history", I also could've sworn that it used to list everything right there.

    Maybe I'm wrong about those couple of issues, but the fact that my taskbar settings are not being saved means there's definitely an issue with atleast one thing - and I now can't help but think that there might be other issues.

    Any theories? Is there a way to get my settings to save - but much more importantly - is something now permanently corrupted? I'm just a basic guy who swears at the top of his lungs when computers go awry, and would be scared half to death to do something as drastic as reinstall windows.

    Thanks, Chris

    Edit: Ok, there is more stuff that is wrong. When I tried to take out my usb thumb drive it wouldn't give me the pop up message that it was Ok to do so. When I unplugged my headphones it also usually gives me a message that they were just unplugged, and now I don't get that message.
      My ComputerSystem Spec

  2.    06 Mar 2018 #2

    when I go into Windows Update and click on "view installed update history", I also could've sworn that it used to list everything right there.
    - that suggests you may have received a Windows upgrade to build 1709.

    Do you have a folder called Windows.old on C: ?
    If so, check its properties and creation date.

    However, it should not be that you saw a major loss or change of functions as you report.

    What is your Windows build?
    Windows key + R, winver

    Windows may reboot for other reasons- e.g. if a health check discovers a disk problem.

    Do you have Active Hours set (in Settings) and if so was the reboot within the set period?

    Download a small free utility called BluescreenView and see if that tells you of any event.
      My ComputerSystem Spec

  3. Bree's Avatar
    Posts : 9,631
    10 Home x64 (1809) (10 Pro on 2nd pc)
       06 Mar 2018 #3

    dalchina said: View Post
    ...Download a small free utility called BluescreenView and see if that tells you of any event.
    It's from NirSoft, who have many very useful tools. Get it direct from the author...
    https://www.nirsoft.net/utils/blue_screen_view.html
      My ComputersSystem Spec

  4.    06 Mar 2018 #4

    Since you mentioned an issue with your USB thumb drive you might find these articles interesting.
    And as dalchina mentioned, 1709 is also mentioned in those articles.

    KB4090913 for Windows 10 fixes USB bug
    Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5 - Windows 10 Forums

    Microsoft Releases KB4090913 Update to Fix Critical USB Driver Issue
    Microsoft Releases KB4090913 Update to Fix Critical USB Driver Issue
    Last edited by Brink; 06 Mar 2018 at 13:57. Reason: updated link
      My ComputersSystem Spec

  5.    06 Mar 2018 #5

    Thanks guys. So I'm at work but I did check a bunch of these things on my way out. The only thing I wasn't able to do yet was the nirsoft scan. So these are some of the things I remember.

    My build is the latest - 1709.

    I don't believe my computer was set to reboot at certain hours. I've had 1709 for a month or two now and it's never rebooted before. As of this morning my computer said I was up to date updates wise. The last update was on Feb. 18th though, so nothing from yesterdays USB patch as of yet.

    So even though I haven't run the nirsoft scan yet - and maybe that will tell me something (probably won't understand it if it's too techie though to be honest) - but things like the USB patch, even if I had it installed already, it doesn't seem to me that's a major thing because.........the actual reboot into the "nothing is working" part.........into my taskbar settings won't save after a reboot part.........well.......those things, just aren't right. The USB problem would appear to be one of possibly several collateral damage issues with this reboot. I'm really curious as to what this nirsoft scan will say. I'm not quite sure why an SFC and DISM scan came up clean. Aren't those supposed to detect issues like this???

    Thanks, Chris
      My ComputerSystem Spec


  6. Posts : 22,021
    windows 10 professional version 1607 build 14393.969 64 bit
       06 Mar 2018 #6

    Run the beta version of the log collector and post a zip into this thread:
    log collector v2-beta08.zip
    (extract > open)
    In case there are problems using the beta log collector please use the DM log collector:
    BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec

  7.    06 Mar 2018 #7

    The Nirsoft tool will quickly show you if you have any minidump files- related to a BSOD.

    If you have, see if the date/time relates to a restart. The tool shows you the content too.

    Random restarts can also be caused by hardware problems of course.

    Please try to answer questions posted- it will help you.
      My ComputerSystem Spec

  8.    06 Mar 2018 #8

    Thanks. I'll do these when I get home tonight and report back.
      My ComputerSystem Spec

  9.    06 Mar 2018 #9

    Ok, I couldn't wait, I went home at lunch time, lol.

    DESKTOP-GI4BH7F (2018-03-06 12 09).zip

    I also ran the nirsoft scan, but unless I was doing it wrong, nothing came up on the screen. It did say in the very bottom left corner "0 crashes".

    And as for the Windows Old folder - Yes on February 17th

    Hope some of this helps.
      My ComputerSystem Spec


  10. Posts : 22,021
    windows 10 professional version 1607 build 14393.969 64 bit
       06 Mar 2018 #10

    1) There were no BSOD mini or memory dump files.
    2) There was a BSOD yesterday with bugcheck 50
    3) There have been many drive file system repairs.
    3) The drive file system is corrupt. The master file table is corrupt (MFT).
    4) The RAM is mismatched.

    5) Update the specs in the "My Computer" section:
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    6) For all tests / steps please post images into the thread.
    7) If there are any problems posting images please use one drive or drop box share links.

    8) Open administrative command prompt and type or copy and paste:
    9) sfc /scannow
    10) dism /online /cleanup-image /scanhealth
    11) dism /online /cleanup-image /restorehealth
    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    13) Make sure that there is no over clocking while troubleshooting.

    14) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date Dell Inc. 3.2.4, 6/17/2016
    15) Please check to see if this is the most up to date version.
    (Upgrade the BIOS > Version 3.5.2, 3.5.2)
    http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=GG6PP

    16) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    17) To ensure that there are no improper bios settings please reset the bios.
    18) Sometimes there can be failure to boot after resetting the bios.
    19) Backup the computer files to another drive or to the cloud.
    20) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    21) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    22) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
    23) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
    24) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

    25) Open administrative command prompt and type or copy and paste:
    chkdsk /x /f /r
    This may take many hours so plan to run it overnight.

    C:\Windows\system32>chkdsk /x /f /r
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    26) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste > notepad > save to desktop > post into the thread
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

    27) Run HD Tune:
    http://www.hdtune.com/
    Post images of the results for each of these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    28) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 Tutorials

    29) Uninstall Avast:
    Avast Uninstall Utility | Download aswClear for Avast Removal

    30) Uninstall Supraantispyware:
    SUPERAntiSpyware FAQ - How do I uninstall SUPERAntiSpyware?

    31) Uninstall Malwarebytes
    How do I uninstall Malwarebytes Anti-Malware? | Official Malwarebytes Support

    32) Turn on Windows defender








    Code:
    Event[906]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2018-02-25T21:34:30.657  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: N:, DeviceName: \Device\HarddiskVolume45.(A device which does not exist was specified.)

    Code:
    Event[1099]:  Log Name: System  Source: Ntfs  Date: 2018-03-04T22:23:03.606  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    Event[1102]:  Log Name: System  Source: Ntfs  Date: 2018-03-04T22:24:04.103  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x3d00000000d083.  The name of the file is "\hiberfil.sys".
    Code:
    Event[1103]:  Log Name: System  Source: Ntfs  Date: 2018-03-04T22:24:04.107  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x100000002669a.  The name of the file is "\ProgramData\AVAST Software\Avast\log".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".
    Code:
    Event[1104]:  Log Name: System  Source: Ntfs  Date: 2018-03-04T22:24:04.418  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure.  The file reference number is 0x100000002669a.  The name of the file is "\ProgramData\AVAST Software\Avast\log".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".
    Code:
    Event[1816]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:31:23.984  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume OS.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x3d00000000d083.  The name of the file is "\hiberfil.sys".Event[1817]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:31:24.341  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume OS.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0xa800000001a1a2.  The name of the file is "\System Volume Information\{4e379e33-1c3b-11e8-8afe-945330b69c79}{3808876b-c176-4e48-b7ae-04046e6cc752}".Event[1818]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:31:26.069  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x36000000000281.  The name of the file is "\$Recycle.Bin\S-1-5-21-941664009-1777881967-1004190689-1001\$RJS3NN8.rar".
    Code:
    Event[1802]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:24.439  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume OS.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x3d00000000d083.  The name of the file is "\hiberfil.sys".Event[1803]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:25.879  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: A corruption was discovered in the file system structure on volume OS.The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0xa800000001a1a2.  The name of the file is "\System Volume Information\{4e379e33-1c3b-11e8-8afe-945330b69c79}{3808876b-c176-4e48-b7ae-04046e6cc752}".Event[1804]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:47.630  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1805]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:47.630  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1806]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:47.630  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1807]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2018-03-05T21:30:48.031  Event ID: 98  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: Volume C: (\Device\HarddiskVolume3) needs to be taken offline for a short time to perform a Spot Fix.  Please run "CHKDSK /SPOTFIX" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.Event[1808]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:48.351  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1809]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:48.444  Event ID: 131  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:.Event[1810]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:48.515  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1811]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:48.989  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1812]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:49.021  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1813]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:54.799  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1814]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:54.867  Event ID: 130  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: The file system structure on volume C: has now been repaired.Event[1815]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:30:56.940  Event ID: 132  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: Too many repair events have occurred in a short period of time.Temporarily suspending posting of further repair events.
    Code:
    Event[1819]:  Log Name: System  Source: Ntfs  Date: 2018-03-05T21:32:49.906  Event ID: 133  Task: N/A  Level: Information  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-GI4BH7F  Description: Skipped posting of 14 repair events.  Repair event posting will now be resumed. Here are the skipped posting repair events count by repair verbs: BadFRS:            4 OrphanChildFRS:    1 BadClusters:       0 BadFreeClusters:   0 CrossLink:         0 SDEntry:           0 InvalidSecurityId: 0 IndexAttribute:    0 IndexSubtree:      0 IndexOffset:       0 IndexEntry:        4 IndexOrder:        0 Connect:           0 BreakCycle:        0 FRSAllocate:       5 Others:            0
    Code:
    Event[732]:  Log Name: System  Source: UASPStor  Date: 2018-02-24T00:23:22.893  Event ID: 129  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-GI4BH7F  Description: Reset to device, \Device\RaidPort6, was issued.
    Code:
    Event[1181]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2018-03-05T17:37:51.038  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-GI4BH7F  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffcf0b41b28000, 0x0000000000000000, 0xfffff80034abe85e, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\030518-25187-01.dmp. Report Id: 858e9a02-bae1-44ae-ba77-bc47f98bc565.
    Last edited by zbook; 06 Mar 2018 at 21:57.
      My ComputerSystem Spec


 
Page 1 of 6 123 ... LastLast

Related Threads
I just had my very first WTF (what the f…) moment with Windows Pro 10 (version 1703) x64. I have a legitimate copy. Background: My motherboard (ASUS Sabertooth Z170 Mark 1) released a new revision of BIOS firmware. As always, I upgraded my...
Hi, I've used Windows 10 since day one although I've only just started to use the Calendar App since the AU update. When entering Birthdays and selecting the 'repeat yearly details' they are NOT saved despite the 'Save and Close' being activated....
the file is possibly corrupt the file header checksum does not match the computed checksum" please help me this message pops up when i boot my computer !
This started today and so far I have only detected it with my IRC client. I have normally all the pop-up notification settings turned off for this software. However, ever since today Windows 10 has been turning the notifications back on and it...
OK, so I have here a Windows 10 laptop that had major issues. To start off half the services such as BFE, DHCP, and NLA weren't running. They were giving me access denied. I repaired them using "Tweaking.com - Windows Repair v3.5.0". But now I'm...
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:44.
Find Us