Windows 10: Most likely cause of corrupted system files right after clean install of Windows 10?

Discus and support Most likely cause of corrupted system files right after clean install of Windows 10? in Windows 10 BSOD Crashes and Debugging to solve the problem; I've been getting sporadic BSODs for months and did a complete clean reinstall all partitions wiped from the USB but continued to get BSODs. I suspect... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by HG815, Mar 22, 2021.

  1. HG815 Win User

    Most likely cause of corrupted system files right after clean install of Windows 10?


    I've been getting sporadic BSODs for months and did a complete clean reinstall all partitions wiped from the USB but continued to get BSODs. I suspect it may be one of the connected USB devices, a failing USB port, or some other failing hardware like the SSD. Anyway, I configured the system to generate minidump files but they don't get written there is no minidump folder. The Event Viewer tells me that "windows dump file creation failed due to error during dump creation". I did an SFC scan and it found and repaired corrupted system files.


    1. What is the most likely cause of the SFC scan finding corrupted system files right after a clean install of the OS?


    2. Is it possible they were always corrupt something went wrong during installation and they weren't discovered by the installer during installation? This seems highly unlikely to me.


    3. Is a failing SSD a likely cause of the inability to create minidump files after BSODs?


    For additional reference, the BSODs were either store exception errors or critical process died errors but again no minidump files were ever created. And the machine is a Samsung ultrabook with an i7-6700HQ and an SSD running the latest Windows 10 Pro.

    :)
     
    HG815, Mar 22, 2021
    #1
  2. FreddyAk Win User

    Windows 10 installation file system

    Hello I installed windows 10 on pendrive 3,75 gb with ntfs system file using ultraISO. I read on internet that it is required to use fat32 if you have uefi mobo which I do (msi b85m-g43). So far my system is working just fine except after boot screen the background doesnt dissapear, insted windows 10 loading circle on little black background appears and then it goes to welcome screen. Everythings else is fine so far. May this problem be caused by file system ? Or could it done any other problems I dont see?

    Well Nevermind. It seems like program formatted pendrive to fat32 and I didnt see it.
     
    FreddyAk, Mar 22, 2021
    #2
  3. Corrupted file RAR

    If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:
    • Open WinRAR application in your system.
    • Now click on File tab > Open or simply press Ctrl+O.
    • A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
    • Now click Open button.
    • Click Tools tab > Repair archive or simply press Alt+R.
    • Again a small window "Repairing File name.rar" will pop up.
    • Now click Browse to select a location to save the repaired archive.
    • Check the box "Treat the corrupt archive as RAR" and click OK.
    • WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.
    I hope the above steps will help you repair the corrupted RAR archive.

    Thanks.
     
    Lincoln Dunne, Mar 22, 2021
    #3
  4. trparky Win User

    Most likely cause of corrupted system files right after clean install of Windows 10?

    Why is my machine acting like this?

    It's a clean installation of Windows 10, reinstalled it on April 15th. Both Windows Defender and MalwareBytes have verified that the system is clean of all malware. I have attached a text file with a list of the running processes on my system as of right this moment.
     
    trparky, Mar 22, 2021
    #4
Thema:

Most likely cause of corrupted system files right after clean install of Windows 10?

Loading...
  1. Most likely cause of corrupted system files right after clean install of Windows 10? - Similar Threads - likely cause corrupted

  2. Corrupt system files / clean windows install not working

    in Windows 10 Installation and Upgrade
    Corrupt system files / clean windows install not working: So I recently started to have problems with my windows itself before I decided to go for a full reset to try and fix it. A few applications and games kept on refreshing and crashing, the same with my browser. This all linked in my mind to being a ram issue which I thought...
  3. Corrupt system files / clean windows install not working

    in Windows 10 Gaming
    Corrupt system files / clean windows install not working: So I recently started to have problems with my windows itself before I decided to go for a full reset to try and fix it. A few applications and games kept on refreshing and crashing, the same with my browser. This all linked in my mind to being a ram issue which I thought...
  4. Corrupt system files / clean windows install not working

    in Windows 10 Software and Apps
    Corrupt system files / clean windows install not working: So I recently started to have problems with my windows itself before I decided to go for a full reset to try and fix it. A few applications and games kept on refreshing and crashing, the same with my browser. This all linked in my mind to being a ram issue which I thought...
  5. Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install: After my last topic: Constant BSOD of different types - Microsoft Community I sent the RAM sticks to warranty. No issue found so they sent them back I live in a country with little to no consumer protection okay!. In the meantime I borrowed a pair of sticks from a friend....
  6. Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install

    in Windows 10 Gaming
    Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install: After my last topic: Constant BSOD of different types - Microsoft Community I sent the RAM sticks to warranty. No issue found so they sent them back I live in a country with little to no consumer protection okay!. In the meantime I borrowed a pair of sticks from a friend....
  7. Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install

    in Windows 10 Software and Apps
    Constant BSOD ---- Windows get corrupted --- BSOD/Corruption right after clean install: After my last topic: Constant BSOD of different types - Microsoft Community I sent the RAM sticks to warranty. No issue found so they sent them back I live in a country with little to no consumer protection okay!. In the meantime I borrowed a pair of sticks from a friend....
  8. Cause of corrupt system files?

    in AntiVirus, Firewalls and System Security
    Cause of corrupt system files?: I've been in the process of removing data from a Win 10 machine for several weeks now, during which time it has not been connected to the internet, and no new programs have been installed on it. However, today, when I was trying to run malware checks on the appdata folder,...
  9. System file corruption on clean install

    in Windows 10 BSOD Crashes and Debugging
    System file corruption on clean install: Win10 Pro 1903 Build 18362.267 Here is a guide I have followed and didn't help; https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors I ended up creating a bootable usb with MediaCreationTool1903, deleting all partitions and doing a fresh install. After...
  10. Clean Windows 10 install due to corrupt file system/no boot

    in Windows 10 Installation and Upgrade
    Clean Windows 10 install due to corrupt file system/no boot: Grettings All, I'm currently working on a laptop for a friend that has Windows 10 and is in a non bootable state with missing files, directories, reset options and is stuck in the "Unable to Fix" state. I'm pretty sure the issue is related to BCD and boot options but all...