[SOLVED] [Win10v1511Build10586 x64] Corrupt Sytem Files causing Win. upgrade to give me BSOD

Adamsavage79

Adamsavage79

Well-known member
Joined
Nov 3, 2017
Posts
132
Location
Ottawa
Ok, so computer is running a Windows 10 Upgrade from Windows 7. For the last 2 years or so, the computer has been randomly crashing on me. I have no been able to find a pattern to this at well.. I can go days, or even months without a crash. I can crash twice in a day, or be fine for months. It doesn't matter if I'm gaming, or the computer has been idle for several hours. When I ran who crashed, the number 1 reason given for the crashes in my log, was "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" I just ran a display driver unistaller, and did a clean install of my graphics driver. The thought it, that the graphics driver was corrupt somehow. I've ran a few file sytem scanners, like SFC, and they come back saying I have corrupt system files, but fail to tell me what they are, and are not able to fix them.

My current set up is listed below:
· OS - Windows 10, 64 bit (upgraded from Windows 7)

· What was original installed OS on system? Windows 7 I would guess, if I'm understanding the question.

· full retail version
· Age of system (hardware) - Varies, as the hardware has been upgraded, several times over the years.
· Age of OS installation - have you re-installed the OS? It's about 2 years and I have no done a re-install yet, as I'm trying to avoid one.

· CPU - AMD FX 8150
· Video Card - Geforce GTX 60
· MotherBoard - M5A97 LE R2.0
· Power Supply - brand & wattage - Corsair 750 watt, modular

· System Manufacturer - Me.
It's a Desktop

Hard drive error scan came back clean, and I also have ran a Ram test with 6 passes on Memtest plus. The ram test passed, and came back error free.
 

Attachments

Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named softwaremaniac. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

Hi again :)

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

The forum is not letting me attach either the .txt file or the .txt file in a zip format, so I had to put the cbs.txt as a zip in my dropbox. Link is here: Dropbox - cbs.zip


Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2017-11-06 21:25:32.795
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\John\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\wow64_microsoft-windows-media-streaming-ps_31bf3856ad364e35_10.0.10586.1045_none_7bc7235648fd751d\Windows.Media.Streaming.ps.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7
Successfully took permissions for file or folder C:\WINDOWS\winsxs\wow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_714dede8f3cfe571\iSCSITargetPortal.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-powerdiagnostic_31bf3856ad364e35_10.0.10586.0_none_c6e59647f7fbfcf9\TS_Balanced.ps1
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-m..s-mdac-odbcconf-dll_31bf3856ad364e35_10.0.10586.0_none_945e8401a018dcd5\odbcconf.dll
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_66f94396bf6f2376\iSCSITargetPortal.cdxml


Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-media-streaming-ps_31bf3856ad364e35_10.0.10586.1045_none_7bc7235648fd751d\Windows.Media.Streaming.ps.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-media-streaming-ps_31bf3856ad364e35_10.0.10586.1045_none_7bc7235648fd751d\Windows.Media.Streaming.ps.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\BingOnlineServices.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\BingOnlineServices.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\MapsBtSvc.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\MapsBtSvc.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MapControls.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MapControls.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MosHost.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MosHost.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MosTrace.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\Microsoft-Windows-MosTrace.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\MosResource.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\MosResource.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\NMAA.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\NMAA.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\NmaDirect.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7\NmaDirect.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_714dede8f3cfe571\iSCSITargetPortal.cdxml to C:\WINDOWS\winsxs\wow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_714dede8f3cfe571\iSCSITargetPortal.cdxml.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-powerdiagnostic_31bf3856ad364e35_10.0.10586.0_none_c6e59647f7fbfcf9\TS_Balanced.ps1 to C:\WINDOWS\winsxs\amd64_microsoft-windows-powerdiagnostic_31bf3856ad364e35_10.0.10586.0_none_c6e59647f7fbfcf9\TS_Balanced.ps1.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-m..s-mdac-odbcconf-dll_31bf3856ad364e35_10.0.10586.0_none_945e8401a018dcd5\odbcconf.dll to C:\WINDOWS\winsxs\amd64_microsoft-windows-m..s-mdac-odbcconf-dll_31bf3856ad364e35_10.0.10586.0_none_945e8401a018dcd5\odbcconf.dll.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_66f94396bf6f2376\iSCSITargetPortal.cdxml to C:\WINDOWS\winsxs\amd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_66f94396bf6f2376\iSCSITargetPortal.cdxml.


Successfully restored ownership for C:\WINDOWS\winsxs\wow64_microsoft-windows-media-streaming-ps_31bf3856ad364e35_10.0.10586.1045_none_7bc7235648fd751d\Windows.Media.Streaming.ps.dll
Successfully restored permissions on C:\WINDOWS\winsxs\wow64_microsoft-windows-media-streaming-ps_31bf3856ad364e35_10.0.10586.1045_none_7bc7235648fd751d\Windows.Media.Streaming.ps.dll
Successfully restored ownership for C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7
Successfully restored permissions on C:\WINDOWS\winsxs\wow64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.10586.71_none_a1d87199ef9193d7
Successfully restored ownership for C:\WINDOWS\winsxs\wow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_714dede8f3cfe571\iSCSITargetPortal.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\wow64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_714dede8f3cfe571\iSCSITargetPortal.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-powerdiagnostic_31bf3856ad364e35_10.0.10586.0_none_c6e59647f7fbfcf9\TS_Balanced.ps1
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-powerdiagnostic_31bf3856ad364e35_10.0.10586.0_none_c6e59647f7fbfcf9\TS_Balanced.ps1
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-m..s-mdac-odbcconf-dll_31bf3856ad364e35_10.0.10586.0_none_945e8401a018dcd5\odbcconf.dll
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-m..s-mdac-odbcconf-dll_31bf3856ad364e35_10.0.10586.0_none_945e8401a018dcd5\odbcconf.dll
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_66f94396bf6f2376\iSCSITargetPortal.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-i..i_initiator_service_31bf3856ad364e35_10.0.10586.0_none_66f94396bf6f2376\iSCSITargetPortal.cdxml
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2017-11-06 21:25:37.628
Script hash: P4rVDIf0qnLLzaCkRHDNLcNM6JvsCq/wPxylk2njV7A=
----------------------EOF-----------------------
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.





SFC Scan



  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

You already asked me to do those, and I did. Not sure why I would need to do them again.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

These are not the same files. You have more corruption to fix. That's why I've given you these instructions. Kindly follow them and report back with the log I've requested.

Thanks.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

I will do it after work. My CBS log is going to get pretty large. Should I delete it, so it creats a brand new one, vs adding to the current one ?
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

I did the scan as requested, and it said the end "Windows resource protection did not find any Integrity violations" I also attached the files requested.

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2017-11-08 15:09:28.275
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\John\Desktop\SFCFix.zip [0]








PowerCopy::
Line blocked (invalid colon position): "C:\Users\John\AppData\Local\niemiro\Archive\iSCSI\iSCSITargetPortal.cdxml" C\iSCSITargetPortal.cdxml.
PowerCopy:: directive completed successfully.








PowerCopy::
Successfully created directory tree \\?\C:\WIND.


Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\iSCSI\iSCSITargetPortal.cdxml to C:\WIND\iSCSITargetPortal.cdxml.
PowerCopy:: directive completed successfully.








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml


Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\ActionFiles\Cleanup.xml to C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\ActionFiles\Generalize.xml to C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\ActionFiles\Respecialize.xml to C:\Windows\System32\Sysprep\ActionFiles\Respecialize.xml.
Successfully copied file C:\Users\John\AppData\Local\niemiro\Archive\ActionFiles\Specialize.xml to C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml.


Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2017-11-08 15:09:30.841
Script hash: xv7myj2UH0VF5mMsc3o+NK3Cvnb3cproimwLRU5/hsE=
----------------------EOF-----------------------
 

Attachments

Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

Please try upgrading your system using MCT now.

1. Download the Media Creation Tool to your desktop. Go ahead and run this. Note: Click the Download tool now button when you are at this link.
2. Accept the license agreement
3. Keep the default which is to Upgrade your PC and click Next.
4. Go ahead and run this through and let me know when complete.

Doing it this way will keep all your data and programs intact. As always though, make sure you have a backup of any critical data in case something unexpected happens.

Let me know how it goes.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

It's checking for updates currently, and labled Windows 10 set up. Is this how Windows 10 does a soft install ? Windows all the way up to 7, would delete the windows folder and such, but keep your programs "intact"... If you chose that route.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

It will ask you whether you want to keep your personal files at a later stage, first it must do all the downloading and checking. This is all expected.
Let me know how it all turns out.
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

I'm starting to wonder if it's "stuck" at this point.. I went through checking for updates, checking to make sure I'm ready, and then it wanted to make sure I had enough storage space.. I told it to keep my personal files and programs, and then it repeated itself all over again, with checking for updates, making sure I'm ready to install..
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

softwaremaniac said:
It BSOD-ed during the upgrade again? If so, at which exact point?
Click to expand...

It was not very far, I was not watching. I was watching tv. I would say before 20%.

I did find an article that points to this being a not so uncommon thing. This could be unrelated to my crashes before hand. Title is called "Confusion reigns over Windows 10 update that causes blue screen of death". I'm going to avoid doing a clean install for now, as the system is still somewhat stable. I still would like to see if I will still get crashes. If I don't, then indications are that this new update/upgrade are bugged somehow. As mentioned, this waiting time frame could take quite some time. If a month goes by, and no crashes. Then it's a good indication I have a system that is more stable.

 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

I'm leaning towards something else being the culprit here, and not the installation. Would you like me to dig deeper now or would you like me to wait until you're certain your system is stable?
 
Re: Corrupt Sytem Files causing Windows upgrade to give me BSOD

I think the best option is to wait and see if my system is stable.. I tried making a fresh Windows install on a usb, but the media creation tool was giving me a hard time. It kept giving me Error Code: 0x80072f76 - 0x20017... So I went ahead and did it with the ISO image, using Rufus. I was able to find a older version I made over a year on, using the Media creation tool. I also still have my Windows 7 DVD, worst comes to worst.

I could use the break from all this troubleshooting. I'm curios though, while I wait to see if Windows is stable. What you think the problem might be ?
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top