Kernelbase.dll crashing multiple programs on Windows 10 x64

[overnight22]

Yesterday a couple of programs started crashing when I try to open them.
In all cases the fault module is kernelbase.dll
I tried running sfc /scannow with no difference, and regsvr32 KERNELBASE.dll gives me the following error: The module "kernelbase.dll" was loaded but the entry-point DllRegisterServer was not found.
Make sure that "kernelbase.dll" is a valid DLL or OCX file and then try again.

Here is the crash report for Display Driver Uninstaller:
From Event viewer:
Nombre de la aplicación con errores: Display Driver Uninstaller.exe, versión: 17.0.3.0, marca de tiempo: 0x580fa2bf
Nombre del módulo con errores: KERNELBASE.dll, versión: 10.0.14393.321, marca de tiempo: 0x57f4c4f0
Código de excepción: 0xe0434352
Desplazamiento de errores: 0x0000000000017788
Identificador del proceso con errores: 0xb88
Hora de inicio de la aplicación con errores: 0x01d233e971afa759
Ruta de acceso de la aplicación con errores: C:\Users\Leandro1\Desktop\Display Driver Uninstaller.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\KERNELBASE.dll
Identificador del informe: 9717a54c-400d-4177-9f61-981737f4c2b0
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:

Aplicación: Display Driver Uninstaller.exe
Versión de Framework: v4.0.30319
Descripción: el proceso terminó debido a una excepción no controlada.
Información de la excepción: System.IO.FileNotFoundException
en Display_Driver_Uninstaller.Application..ctor()
en Display_Driver_Uninstaller.Application.Main()



From AppCrashView:
Version=1
EventType=CLR20r3
EventTime=131224416878737295
ReportType=2
Consent=1
UploadTime=131224416879307672
ReportIdentifier=af87185c-9fdc-11e6-826e-386077c726ad
IntegratorReportIdentifier=9717a54c-400d-4177-9f61-981737f4c2b0
NsAppName=Display Driver Uninstaller.exe
AppSessionGuid=00000b88-0001-0022-59a7-af71e933d201
TargetAppId=W:0006b4d7a8c76617292bbea5e19478e10f8b00000000!0000db0f3a53b461fef997edfe9612ebddfcf521e4ce!Display Driver Uninstaller.exe
TargetAppVer=2016//10//25:18:21:51!0!Display Driver Uninstaller.exe
BootId=4294967295
Response.BucketId=0392065c64e977e2445328055ec7e175
Response.BucketTable=5
Response.LegacyBucketId=129257150065
Response.type=4
Sig[0].Name=Firma del problema 01
Sig[0].Value=Display Driver Uninstaller.exe
Sig[1].Name=Firma del problema 02
Sig[1].Value=17.0.3.0
Sig[2].Name=Firma del problema 03
Sig[2].Value=580fa2bf
Sig[3].Name=Firma del problema 04
Sig[3].Value=Display Driver Uninstaller
Sig[4].Name=Firma del problema 05
Sig[4].Value=17.0.3.0
Sig[5].Name=Firma del problema 06
Sig[5].Value=580fa2bf
Sig[6].Name=Firma del problema 07
Sig[6].Value=49
Sig[7].Name=Firma del problema 08
Sig[7].Value=6
Sig[8].Name=Firma del problema 09
Sig[8].Value=System.IO.FileNotFoundException
DynamicSig[1].Name=Versión del sistema operativo
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Id. de configuración regional
DynamicSig[2].Value=3082
DynamicSig[22].Name=Información adicional 1
DynamicSig[22].Value=1dc9
DynamicSig[23].Name=Información adicional 2
DynamicSig[23].Value=1dc9443092663b1ba267e86923267d52
DynamicSig[24].Name=Información adicional 3
DynamicSig[24].Value=2dbd
DynamicSig[25].Name=Información adicional 4
DynamicSig[25].Value=2dbdc66a40172687aa9bfb1d20e2a231
UI[2]=C:\Users\Leandro1\Desktop\Display Driver Uninstaller.exe
UI[3]=Display_Driver_Uninstaller dejó de funcionar
UI[4]=Windows puede buscar una solución en línea al problema.
UI[5]=Buscar una solución en línea y cerrar el programa
UI[6]=Buscar una solución en línea más tarde y cerrar el programa
UI[7]=Cerrar el programa
LoadedModule[0]=C:\Users\Leandro1\Desktop\Display Driver Uninstaller.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\sechost.dll
LoadedModule[9]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[12]=C:\WINDOWS\System32\combase.dll
LoadedModule[13]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[15]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\USER32.dll
LoadedModule[18]=C:\WINDOWS\System32\win32u.dll
LoadedModule[19]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[20]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[22]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[24]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\e96b4590c579d08edc2e60cc3e5ae997\mscorlib.ni.dll
LoadedModule[25]=C:\WINDOWS\System32\ole32.dll
LoadedModule[26]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[28]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[31]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\ee1c3ea3e0049df6d53b35e21c2247e4\System.ni.dll
LoadedModule[32]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\46ebe2b057622677cfc3fd04f47081c0\System.Core.ni.dll
LoadedModule[33]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\61103ac73bccca74b102807a0baf3495\WindowsBase.ni.dll
LoadedModule[34]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\db1726d3f4aef60e7fc01ed9879d9870\System.Xaml.ni.dll
LoadedModule[35]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[36]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[37]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[38]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[40]=C:\WINDOWS\System32\shcore.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[43]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[44]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[45]=C:\WINDOWS\System32\profapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Dejó de funcionar
ConsentKey=CLR20r3
AppName=Display_Driver_Uninstaller
AppPath=C:\Users\Leandro1\Desktop\Display Driver Uninstaller.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=738A8C2378D1C1A124CF821E23C0DE66
MetadataHash=2129412734

 

[Colif]

try running dism
open command prompt {Admin)
Copy/paste this command in - needs to be exact
DISM /Online /Cleanup-Image /RestoreHealth

if it comes back asking for source info, and you are on the anniversary edition of windows 10 (Build 1607) then follow this:

Download a copy of the win 10 iso from Here - create ISO by telling it you want to make DVD - and then mount that ISO in file explorer (see Here) and then copy paste the below command into command prompt (admin)

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
Where "X" is the drive letter where the ISO is located. Simply change the "X" to the correct drive letter

DISM cleans the image reset would use. Try running sfc /scannow after and see if it still finds nothing wrong.

 

[overnight22]

try running dism
open command prompt {Admin)
Copy/paste this command in - needs to be exact
DISM /Online /Cleanup-Image /RestoreHealth

if it comes back asking for source info, and you are on the anniversary edition of windows 10 (Build 1607) then follow this:

Download a copy of the win 10 iso from Here - create ISO by telling it you want to make DVD - and then mount that ISO in file explorer (see Here) and then copy paste the below command into command prompt (admin)

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
Where "X" is the drive letter where the ISO is located. Simply change the "X" to the correct drive letter

DISM cleans the image reset would use. Try running sfc /scannow after and see if it still finds nothing wrong.

Hello, thanks for your answer.
DSIM gave me this error around 50%: The remote procedure call failed error

Here is the log dism.log

 

[overnight22]

I'm creating the ISO now.

 

[Colif]

Method 1:
Check if the Remote Procedure Call (RPC) services are started.
a. Press Windows Key + R, type services.msc, press ENTER.
b. Search for service named Remote Procedure Call (RPC).
c. You will find two services with the same name first one should be automatic and the second one which is Remote Procedure Call (RPC) locator should be manual.
d. Check if it is started, if not right click on the service and click on Start.


Method 2:
From Start screen, open Command Prompt, and Run as administrator.
Now, type the following commands. Press Enter after each command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

are you running MSI Afterburner?

I've found the problem with the help of Process Explorer: it is MSI afterburner + riva statistics server, they have locked the "dxgi.dll" file (found in CBS.log) in system32 folder. So I've exited the apps and the process went fine.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/dismexe-online-cleanup-image-startcomponentcleanup/4f8f9da1-8f29-406b-af23-314b8fb11199

 

[overnight22]

Method 1:
Check if the Remote Procedure Call (RPC) services are started.
a. Press Windows Key + R, type services.msc, press ENTER.
b. Search for service named Remote Procedure Call (RPC).
c. You will find two services with the same name first one should be automatic and the second one which is Remote Procedure Call (RPC) locator should be manual.
d. Check if it is started, if not right click on the service and click on Start.


Method 2:
From Start screen, open Command Prompt, and Run as administrator.
Now, type the following commands. Press Enter after each command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth

are you running MSI Afterburner?

I've found the problem with the help of Process Explorer: it is MSI afterburner + riva statistics server, they have locked the "dxgi.dll" file (found in CBS.log) in system32 folder. So I've exited the apps and the process went fine.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/dismexe-online-cleanup-image-startcomponentcleanup/4f8f9da1-8f29-406b-af23-314b8fb11199

I had MSI installed but it wasn't running, I deleted it just in case but it didn't change anything. Both RPC services are running. Running DISM.exe /Online /Cleanup-image /Scanhealth now gives me Error 1910. The object exporter specified was not found

 

[Colif]

I can't say I have seen that error before

http://www.techezone.com/question/running-dism-tool-giving-error-code-1910-object-exporter-specified-not-found-on-windows-10/

Microsoft suggest you do this: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

 

[overnight22]

That's gonna have to wait until tomorrow because it's getting late here. Thanks for your help, I will post again when I'm done.

 

[overnight22]

I can't say I have seen that error before

http://www.techezone.com/question/running-dism-tool-giving-error-code-1910-object-exporter-specified-not-found-on-windows-10/

Microsoft suggest you do this: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

Seems like Microsoft doesn't like me very much.
I got error 0x8007042B - 0x4000D during in-place upgrade
The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

I might just have to format the partition.

 

[Colif]

If win 10 isn't booting now, try this and copy any info off the hdd you want to save: http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer/

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB

I feel a fresh install is sanest way to go on, once DISM starts to not work and a repair also doesn't, you left with no choice. Cannot run reset as it uses the image DISM fixes.

 

[overnight22]

If win 10 isn't booting now, try this and copy any info off the hdd you want to save: http://www.howtogeek.com/howto/windows-vista/use-ubuntu-live-cd-to-backup-files-from-your-dead-windows-computer/

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB

I feel a fresh install is sanest way to go on, once DISM starts to not work and a repair also doesn't, you left with no choice. Cannot run reset as it uses the image DISM fixes.

It does boot. It automatically rolled back to the moment before the upgrade started. The fresh install is going to have to wait until next week, but thanks for your help anyway.