Hanging start up


  1. Posts : 103
    Windows 10
       #1

    Hanging start up


    I have a issue with windows 10 taking 30+ seconds to load up. It gets stuck on welcome screen and i never used to have this issue before. Here is my logs. It used to take 2-5 sec tops.

    Bootlog shows multiple times
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys


    my cbs log shows
    CSI 00004f3d@2016/1/5:16:55:18.218 Primitive installers committed for repair
    2016-01-05 11:55:18, Info CSI 00004f3e [SR] Verify complete
    2016-01-05 11:55:18, Info CSI 00004f3f [SR] Repairing 1 components
    2016-01-05 11:55:18, Info CSI 00004f40 [SR] Beginning Verify and Repair transaction
    2016-01-05 11:55:18, Info CSI 00004f41 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 OQMGOYrgIooYUujnrnx7pngg/jYEmCKvWcHRKKRR0VI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-05 11:55:18, Info CSI 00004f42 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-01-05 11:55:18, Info CSI 00004f43@2016/1/5:16:55:18.230 Primitive installers committed for repair
    2016-01-05 11:55:18, Info CSI 00004f44 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 OQMGOYrgIooYUujnrnx7pngg/jYEmCKvWcHRKKRR0VI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-05 11:55:18, Info CSI 00004f45 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-01-05 11:55:18, Info CSI 00004f46 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
    2016-01-05 11:55:18, Info CSI 00004f47 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 OQMGOYrgIooYUujnrnx7pngg/jYEmCKvWcHRKKRR0VI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-05 11:55:18, Info CSI 00004f48 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 OQMGOYrgIooYUujnrnx7pngg/jYEmCKvWcHRKKRR0VI=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-05 11:55:18, Info CSI 00004f49 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2016-01-05 11:55:18, Info CSI 00004f4a@2016/1/5:16:55:18.249 Primitive installers committed for repair


    It is either a opencl.dll issue or dxgkrnl.sys issue but i can not find anything on how to fix either.
      My Computer


  2. Posts : 42,963
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, please see this lengthy thread, which addresses this issue (albeit I think unresolved still).
    Windows 10 10586.3 and slow login problem - Page 13 - Windows 10 Forums
    It's a symptom some have noted since the November 10586 TH2 upgrade build.
    I believe I've seen a comment there about dxgkrnl.sys

    opencl.dll & SFC /Scannow is 'normal' for some unfortunately and is documented here a number of times. It occurs in conjunction with a particular NVIDIA driver build.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:04.
Find Us




Windows 10 Forums