[SOLVED] [Win10v1703Build15063 x64] System service exception BSOD, SFC and DISM didn't work

[tibernero]

Hey guys. Just got a new mobo and reinstalled Windows 10, and I've been getting system service exception BSODs consistently. Tried running SFC and DISM to no avail. DISM /RestoreHealth gave me error 0x800f081f and said the source files could not be found. Also just tried running the SFCFix, which only crashes over and over again, I attached the generated text log, as well as the CBS folder. I'm at my wits end and desperately need help! Thank you!

 

[BrianDrab]

Hi and welcome to Sysnative. Sorry for the delay. Are you still in need of assistance?

 

[tibernero]

Yes I am

 

[tibernero]

And the issue has somewhat escalated. Now some of my apps, like Chrome, crash when trying to use the "Save as" dialog box.

 

[BrianDrab]

Please start with the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
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

Step#2 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[tibernero]

Thanks for your help!

Here are the contents of SFCFix:

SFCFix version 3.0.0.0 by niemiro.Start time: 2017-05-05 13:36:45.350
Microsoft Windows 10 Build 15063 - amd64
Using .zip script file at C:\Users\Nicolas Nogueira\Desktop\SFCFix.zip [0]










Successfully took permissions for file or folder C:\WINDOWS\Winsxs\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.15063.0_none_e4e3457246197eaf\mstscax.dll


Successfully copied file C:\Users\Nicolas Nogueira\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.15063.0_none_e4e3457246197eaf\mstscax.dll to C:\WINDOWS\Winsxs\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.15063.0_none_e4e3457246197eaf\mstscax.dll.


Successfully restored ownership for C:\WINDOWS\Winsxs\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.15063.0_none_e4e3457246197eaf\mstscax.dll
Successfully restored permissions on C:\WINDOWS\Winsxs\x86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.15063.0_none_e4e3457246197eaf\mstscax.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-05-05 13:36:46.778
Script hash: Tvly9N0/+nkgZXJ1PQEQpEsLwbBJQMyAEQNtOREn7+k=
----------------------EOF-----------------------

Here's the fixlog from FRST64:

Fix result of Farbar Recovery Scan Tool (x64) Version: 05-05-2017 02Ran by Nicolas Nogueira (05-05-2017 13:39:40) Run:1
Running from C:\Users\Nicolas Nogueira\Desktop
Loaded Profiles: Nicolas Nogueira (Available Profiles: defaultuser0 & Nicolas Nogueira)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]  
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
*****************


Restore point was successfully created.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0 => key removed successfully
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 => key removed successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat => moved successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum => moved successfully


==== End of Fixlog 13:40:05 ====

 

[BrianDrab]

Please do the following.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Step#2 - DISM /RestoreHealth Scan
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. Right-click on the Start button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
   Dism /Online /Cleanup-Image /RestoreHealth
3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
   copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
   
4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
   Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

 

[tibernero]

Here's the fixlog from the second FRST64 run:

Fix result of Farbar Recovery Scan Tool (x64) Version: 05-05-2017 02
Ran by Nicolas Nogueira (05-05-2017 14:19:06) Run:2
Running from C:\Users\Nicolas Nogueira\Desktop
Loaded Profiles: Nicolas Nogueira (Available Profiles: defaultuser0 & Nicolas Nogueira)
Boot Mode: Normal
==============================================
fixlist content:
*****************
CreateRestorePoint:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0]  
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum
*****************
Restore point was successfully created.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 => key removed successfully
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0 => key removed successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat => moved successfully
c:\windows\servicing\packages\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum => moved successfully
==== End of Fixlog 14:19:34 ====

Here's the CBS log on dropbox:

Dropbox - cbs.txt

 

[BrianDrab]

Log looks good. Are you having issues with SFC or DISM completing anymore?

 

[tibernero]

DISM completed fine when you told me to run it again. SFC also did not find any integrity violation. However, I'm still getting crashes when trying to use the "save as" dialog. Should I restart?

 

[BrianDrab]

Please do the following.

Step#1 - BSOD Log
1. Please download the 64-bit version of Bluescreenview from here and save it to your desktop.
2. Right-click on the downloaded file (bluescreenview-x64.zip) and select Extract All. Click the Extract button and a folder will open with the contents that were extracted.
3. Right-click on BlueScreenView.exe and select Run as administrator. If prompted to Allow, please answer yes.
4. Once the program opens and finishes scanning, click on the Edit menu and choose Select All.
5. Then click on the file menu...Save selected Items...and save it to your desktop named BSOD.txt.
6. Open the BSOD.txt file in notepad (you can simply double-click on the file from the desktop to do this) and copy/paste the contents of this in your next reply.

 

[tibernero]

When I select Save selected Items, BlueScreenViewer just crashes. I tried to copy the contents of the 3 blue screens it found; but when I tried to hit Save or Save as in the notepad app i opened, notepad would just stop working.

 

[BrianDrab]

Can you zip/attach the following file if it exists?
c:\windows\memory.dmp

 

[tibernero]

Just discovered another issue. I went on the C:\Windows folder properties, and when I clicked on the previous version tab, COM Surrogate stopped working.

Attached the memory.dmp zip file.

Dropbox - MEMORY.zip

Also attached screenshots of the BlueScreenViewer app, if it helps.

 

[BrianDrab]

Can you provide me information on your computer? Make/Model, etc. Also what was your old motherboard and what is the info on your new one? The BSOD points to not having the updated drivers installed.

 

[tibernero]

It's a custom built system:
Mobo: ASUS Z170-a
CPU: i5-6500
GPU: Gigabyte Nvidia GTX 1070
RAM: 16gb G.Skill Ripjaw V

The old motherboard was a Gigabyte H110M-A

 

[BrianDrab]

Thanks. Can you make sure that your BIOS and drivers are all up-to-date for your new motherboard (i.e. chipset, video, network)?

 

[tibernero]

What would be the easiest and simplest way to do that?

 

[BrianDrab]

Going to the following link.
Z170-A | Motherboards | ASUS USA

 

[tibernero]

Okay, so my BIOS was fine. I stupidly didn't check versions on my other drivers, but I installed the most updated chipset, LAN and audio drivers.