1) Sorunun ana kaynağı Samsung Android cihazınızı bilgisayara bağlamanız. Telefonunuzu bağlamayın.
2) Tencent oyunlarınız var ise Anti-Cheat yazılımını kaldırın.
3) Vanguard'ı kaldırın.
4) Aşağıdaki rehberin ilk 3 adımını uygulayın.
Herkese iyi günler. Bu rehberde sizlere DISM komutunun ne işe yaradığını, ne tarz durumlarda kullanılacağını ve nasıl kullanılacağını göstereceğim. İlk önce DISM nedir onu öğrenelim. DISM aracı yani “Deployment Image Servicing and Management” aracı sistemde tıpkı SFC komutunun yaptığı işlev...
www.technopat.net
Sorun çözülürse lütfen bildirmeyi unutmayın.
[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)
A lock tracked by AutoBoost was released by a thread that did not own the lock.
This is typically caused when some thread releases a lock on behalf of another
thread (which is not legal with AutoBoost tracking enabled) or when some thread
tries to release a lock it no longer owns.
Arguments:
Arg1: ffffe50fcae32380, The address of the thread
Arg2: ffffe50fc7530d40, The lock address
Arg3: 00000000ffffffff, The session ID of the thread
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6156
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12054
Key : Analysis.Init.CPU.mSec
Value: 1530
Key : Analysis.Init.Elapsed.mSec
Value: 18037
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 162
BUGCHECK_P1: ffffe50fcae32380
BUGCHECK_P2: ffffe50fc7530d40
BUGCHECK_P3: ffffffff
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LightingServic
STACK_TEXT:
ffffe388`7a1337c8 fffff800`63a32bca : 00000000`00000162 ffffe50f`cae32380 ffffe50f`c7530d40 00000000`ffffffff : nt!KeBugCheckEx
ffffe388`7a1337d0 fffff800`63bfd9da : ffffe388`00000000 ffffe50f`00000000 00000000`00000009 00000000`00000000 : nt!IopReleaseFileObjectLock+0x1d3d0a
ffffe388`7a133840 fffff800`63bfd1f5 : 00000000`80102050 ffffe388`7a133b80 00000000`00000005 ffffe388`7a133b80 : nt!IopSynchronousServiceTail+0x25a
ffffe388`7a1338e0 fffff800`63bfcbf6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5e5
ffffe388`7a133a20 fffff800`63a077b8 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe50f`c6e5bc60 : nt!NtDeviceIoControlFile+0x56
ffffe388`7a133a90 00000000`77911cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`01c4ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77911cfc
SYMBOL_NAME: nt!IopReleaseFileObjectLock+1d3d0a
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.928
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d3d0a
FAILURE_BUCKET_ID: 0x162_nt!IopReleaseFileObjectLock
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {149090d4-fa3f-70ae-13ca-cb0734eb49c6}
Followup: MachineOwner
---------[/CODE]