Windows 10: sfc fixes file integrity straight after clean install. Bluescreens.

Hey.


I can't for the life of me get Windows 10 Pro to install without corrupted system files. I have tried 6 times now since December. When I have installed by means of removing all partitions from boot drive before new ones are created and are presented with the desktop for the first time I run sfc and it has to fix something. I run DISM scanhealth and that comes up clean.


Later corrupted files in my operating system will cause problems. Now it is causing bluescreens but it has also caused malfunction in applications and startup items that doesn't start up.


Bluescreens are Critical Process Died, once with services.exe and again with svchost.exe. I have ran both memtest and the built in tool in Windows to test my RAM. Two passes of Memtest without any issue. I have also run Prime95 with small FFT's to see if my CPU spat out any errors but not a single error there either nor even as much as a warning. I have also run check disk on both the NVMe and the USB flash drive which by the way the USB flash drive have had one job and that is to be Windows install media and has only been overwritten 3-4 times.


I have tried with stock BIOS, I have tried to turn off CPU Boost as well as taking my RAM down to 2100MHz from JDEC 2400MHZ but none of this helped. I have disconnected all devices not needed for installation and ran my PC with only NVMe boot drive, CPU, video card, memory, mouse, keyboard and one monitor. Memory is installed in slot 2 and 4 counting from the CPU socket.


The PC is a year old.

Asus ROG Strix B450-F Gaming motherboard BIOS is 4007 which is latest that isn't in BETA.

AMD Ryzen 5 3600X 6-Core Processor

Kingston HyperX KHX3200C16D4/8GX 2x set to 2400 and then 2100MHz manually

KINGSTON SA2000M81000G NVMe

Asus ROG-Strix-RTX2060Super

Corsair RM 650x power supply.

Kingston DataTraveller 16GB USB 3.0 connected to USB 3.0 blue on rear IO.



I'll leave lastest crashdump below, both crashes have happened on start up around a second after desktop is loaded. Both SFC and DISM now come out clean. Bluescreen didn't occur prior to driver install so it could be that also but at this stage I'm more curious as to why the Windows install tool makes an install image to my USB that installs corrupted files when stress testing my CPU and RAM doesn't produce errors.


If you need anything else don't hesitate to ask.











Microsoft R Windows Debugger Version 10.0.19041.685 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP 12 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff805`35000000 PsLoadedModuleList = 0xfffff805`35c2a2b0

Debug session time: Sun Jan 10 09:41:37.550 2021 UTC + 1:00

System Uptime: 0 days 0:00:17.180

Loading Kernel Symbols

...............................................................

.........Page 4080da not present in the dump file. Type ".hh dbgerr004" for details

.......................................................

................................................................

.

Loading User Symbols

................................................................

.......................

Loading unloaded module list

...........

For analysis of this file, run !analyze -v

9: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



CRITICAL_PROCESS_DIED ef

A critical system process died

Arguments:

Arg1: ffffb6065e21b0c0, Process object or thread object

Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

------------------



Page 4080da not present in the dump file. Type ".hh dbgerr004" for details



KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 3



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on TURINGMACHINE



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 2



Key : Analysis.Memory.CommitPeak.Mb

Value: 79



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: ef



BUGCHECK_P1: ffffb6065e21b0c0



BUGCHECK_P2: 0



BUGCHECK_P3: 0



BUGCHECK_P4: 0



PROCESS_NAME: svchost.exe



CRITICAL_PROCESS: svchost.exe



ERROR_CODE: NTSTATUS 0x5e340040 - <Unable to get error code text>



CRITICAL_PROCESS_REPORTGUID: {7bd1a1bd-8607-444f-a12d-60a0a2d8d6d4}



IMAGE_NAME: bisrv.dll



MODULE_NAME: bisrv



FAULTING_MODULE: 00007fff24ba0000 bisrv



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXWINLOGON: 1



STACK_TEXT:

fffffb0a`1498a938 fffff805`359068e2 : 00000000`000000ef ffffb606`5e21b0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

fffffb0a`1498a940 fffff805`35849b39 : 00000000`00000000 fffff805`3535971d 00000000`00000002 fffff805`35358d37 : nt!PspCatchCriticalBreak+0x10e

fffffb0a`1498a9e0 fffff805`35709724 : ffffb606`00000000 00000000`00000000 ffffb606`5e21b0c0 ffffb606`5e21b4f8 : nt!PspTerminateAllThreads+0x140b4d

fffffb0a`1498aa50 fffff805`35709a4c : ffffb606`5e21b0c0 00000000`00000000 00000014`9d97f91c fffff805`356358fa : nt!PspTerminateProcess+0xe0

fffffb0a`1498aa90 fffff805`354071b8 : ffffb606`5e21b0c0 ffffb606`5e340040 fffffb0a`1498ab80 ffffb606`5e21b0c0 : nt!NtTerminateProcess+0x9c

fffffb0a`1498ab00 00007fff`2994c534 : 00007fff`299c2a63 00007fff`299f1354 00000014`9d97f8e0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000014`9d97e5a8 00007fff`299c2a63 : 00007fff`299f1354 00000014`9d97f8e0 00000000`00000000 00007fff`298b0000 : ntdll!NtTerminateProcess+0x14

00000014`9d97e5b0 00007fff`2995353e : 00007fff`299f1354 00000000`0000000c 00007fff`298b0000 00007fff`298c276a : ntdll!TppWorkerpInnerExceptionFilter+0x5b

00000014`9d97e5e0 00007fff`2993bb16 : 00000014`9d97e688 00000014`9d97e6c8 00007fff`298c276a 00000000`00000001 : ntdll!TppWorkerThread$filt$5+0x19

00000014`9d97e620 00007fff`2994bb9e : 00007fff`299f1414 00000014`9d97f2f0 00000014`9d97f8e0 00000014`9d97ec40 : ntdll!_C_specific_handler+0x96

00000014`9d97e690 00007fff`2995130f : 00000000`00000000 00000014`9d97ec30 00000014`9d97f2f0 00000000`00000000 : ntdll!_GSHandlerCheck_SEH+0x6a

00000014`9d97e6c0 00007fff`298fb5e4 : 00000000`00000000 00000014`9d97ec30 00000014`9d97f2f0 00000000`00000000 : ntdll!RtlpExecuteHandlerForException+0xf

00000014`9d97e6f0 00007fff`2994fe3e : 00000197`bb2885a0 0000000c`00000028 00000197`bbd24fe0 00007fff`24cb5770 : ntdll!RtlDispatchException+0x244

00000014`9d97ee00 00007fff`24c058b4 : 00007fff`24bea86a 00000000`00000000 00007fff`29918b6a 00000000`00000000 : ntdll!KiUserExceptionDispatch+0x2e

00000014`9d97f528 00007fff`24bea86a : 00000000`00000000 00007fff`29918b6a 00000000`00000000 00000000`00000000 : bisrv!BipCancellationTimerAllocateState

00000014`9d97f530 00007fff`24c16090 : 00000197`bb4c0960 00000197`bbd24fe0 00000197`bbd24fe0 00000000`00000000 : bisrv!BipCancelWorkItem+0x32c1a

00000014`9d97f640 00007fff`24c1def1 : 00000000`00000000 00000000`00000004 00000014`9d97f750 00000014`9d97f780 : bisrv!BiSrvCancelWorkItem+0x13c

00000014`9d97f700 00007fff`24bed57a : 00000000`00004a16 00000197`bc2cfde8 00000197`bb42f530 00000197`bb4c0940 : bisrv!Execution::BackgroundManager::CancelTaskByWorkItem+0x61

00000014`9d97f730 00007fff`24bbc7a6 : 00000197`bb4c0940 00000197`bbd558e4 00000197`bb2d1c80 00007fff`298ef63d : bisrv!Execution::BackgroundManager::ActivityCallback+0x30dc6

00000014`9d97f780 00007fff`24ca8270 : 00000014`9d97f879 00007fff`298c2db8 00000000`00000012 00000197`bb227bc0 : bisrv!Execution::BackgroundManager::HostManagerActivityCallback+0x16

00000014`9d97f7b0 00007fff`24ca80d2 : 00000197`bbce8170 00007fff`298ef006 00000197`bc2cfd20 0000751c`f7882b7c : RMCLIENT!HampConnectionDeliverPayload+0x30

00000014`9d97f820 00007fff`24ca73e4 : 00000197`bbd558d0 00000197`bc2cfde8 00000197`bc2e77d0 00000000`00000000 : RMCLIENT!HampIpcChannelWnfCallback+0xe2

00000014`9d97f860 00007fff`29913bd0 : 00000197`bc2cfd20 00000197`bc2cfde8 00000197`bb299750 00000197`bb202340 : RMCLIENT!RmpClientWnfMessageQueueWorker+0xc4

00000014`9d97f890 00007fff`298c276a : 00000000`00000000 00000000`00000000 00000197`bb202340 00000197`bb254440 : ntdll!TppWorkpExecuteCallback+0x130

00000014`9d97f8e0 00007fff`28cb7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x68a

00000014`9d97fbe0 00007fff`298fd0d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14

00000014`9d97fc10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21





SYMBOL_NAME: bisrv!BipCancelWorkItem+32c1a



IMAGE_VERSION: 10.0.19041.546



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 32c1a



FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_5e340040_bisrv.dll!?BipCancellationTimerAllocateState@@YAJPEAU_BI_ACTIVATED_TASK_INSTANCE@@EW4_BI_CANCEL_REASON_INTERNAL@@PEAE2@Z_bisrv!BipCancelWorkItem



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {04baa501-bc5c-bdda-1cc1-14284a3390b0}



Followup: MachineOwner

---------

:)

 

SFC some corrupt files can not be fixed


1) The next step: install Nvidia driver, reboot and run SFC again (bad surprise).
2) Permanent fix will survive Nvidia driver install or upgrade.
3) Right now if SFC says no integrity violations it means you have obsoleted 32bit opencl.dll and not one from the Nvidia driver. I.e. no integrity violations is bad thing.

 

SFC some corrupt files can not be fixed

What happened during clean install as mentioned, no sfc integrity violations with no driver in, integrity violations once Windows update installed the NVIDIA driver automatically during finishing up the install settings, then sfc can not fix came about. I reinstalled the newest NVIDIA drivers and the can not fix files was still there. Then i used method here they were gone. So basically you feel on next NVIDIA update this error will come back. Not using 32 bit drivers, 64 bit if it makes a difference.

Newest are these
[table][tr][td]Version:[/td] [td] 358.91 WHQL[/td] [/tr] [tr][td] Release Date:[/td] [td] 2015.11.9[/td] [/tr] [tr][td] Operating System:[/td] [td] Windows 10 64-bit[/td] [/tr] [tr][td] Language:[/td] [td] English (US)[/td] [/tr] [tr][td] File Size:[/td] [td] 287.24 MB[/td] [/tr] [tr][td][/td] [td][/td] [/tr] [/table]

 

SFC unable to fix some of Windows Files

HI Ali. I'm Greg, an installation specialist, 10 years awarded Windows MVP, and Volunteer Moderator, here to help you.

Make sure you did everything in this checklist Step 10 for running SFC including confirming the System image by which it checks the files with DISM, then try SFC three separate times to see if it can repair the files:

http://answers.microsoft.com/en-us/windows/wiki...

If not then move on to Step 11 to run a Repair Install, which keeps your files, settings and apps in place while reinstalling WIndows to replace all of the files including the damaged ones. This is NOT a typical Reset or reinstall of WIndows since it saves
everything in place, takes about an hour, solves most problems by the easiest method possible. This is always the next step when SFC cannot repair broken files.

I hope this helps. Based on the results you report back I may have other suggestions if necessary. If you will wait to choose whether the problem is resolved, then I will continue to help until the problem is fixed.

I hope this helps. Based on the results you report back I may have other suggestions if necessary. If you will wait to choose whether the problem is resolved, then I will continue to help until the problem is fixed.

_________________________

Linked tutorial is from a trusted Microsoft MVP