在 Windows 10 上右键单击会导致 explorer.exe 崩溃

在 Windows 10 上右键单击会导致 explorer.exe 崩溃

我在使用 Windows 10 时遇到了一些问题。每次我右键单击某些文件时,Explorer.exe 都会完全重新启动。我不知道为什么,但这样使用电脑真的很烦人。在您询问之前,我没有对注册表或组权限进行任何操作。我授予用户对硬盘的完全访问权限,因为我是唯一的用户。

我发现当我右键单击文件时它会崩溃.dll.exe我不知道它是否会因其他文件扩展名而崩溃,我只尝试过那些文件扩展名。

答案1

崩溃是由 2008 年的 Realtek Audio 驱动程序引起的,该驱动程序试图释放包含临界区,这是不允许的:

APPLICATION_VERIFIER_LOCKS_LOCK_IN_FREED_HEAP (202)
Freeing heap block containing an active critical section.
This stop is generated if a heap allocation contains a critical section,
the allocation is freed and the critical section has not been deleted.
To debug this stop use the following debugger commands:
$ !cs -s parameter1 - dump information about this critical section.
$ ln parameter1 - to show symbols near the address of the critical section.
This should help identify the leaked critical section.
$ dps parameter2 - to dump the stack trace for this critical section initialization.
$ parameter3 and parameter4 might help understand where this heap block was
allocated (the size of the allocation is probably significant). 
Arguments:
Arg1: 0f26059c, Critical section address. Run !cs -s <address> to get more information. 
Arg2: 04a2d40c, Critical section initialization stack trace. Run dps <address> to dump the stack trace. 
Arg3: 0f260230, Heap block address. 
Arg4: 000020f8, Heap block size. 

STACK_TEXT: 
00 ntdll!KiFastSystemCallRet
01 ntdll!NtWaitForMultipleObjects
02 ntdll!RtlReportExceptionEx
03 ntdll!RtlReportException
04 verifier!AVrfpVectoredExceptionHandler
05 ntdll!RtlpCallVectoredHandlers
06 ntdll!RtlDispatchException
07 ntdll!KiUserExceptionDispatcher
08 verifier!VerifierStopMessageEx
09 verifier!AVrfpFreeMemLockChecks
0a verifier!AVrfpFreeMemNotify
0b verifier!AVrfpRtlFreeHeap
0c msvcrt!free
0d verifier!AVrfp_delete
WARNING: Stack unwind information not available. Following frames may be wrong.
0e RtkAPO
0f RtkAPO
10 ALSNDMGR!CPlApplet
11 OneDriveSettingSyncProvider!CUserTileProvider::_ValidateStream


-----------------------------------------
Critical section   = 0x0f26059c (+0xF26059C)
DebugInfo          = 0x0eb35358
NOT LOCKED
LockSemaphore      = 0x0
SpinCount          = 0x020007d0


Stack trace for DebugInfo = 0x0eb35358:

0x711d8b53: verifier!AVrfpInitializeCriticalSectionCommon+0xF4
0x711d8cc1: verifier!AVrfpRtlInitializeCriticalSection+0x11
0x65277b05: RtkAPO+0x87B05
0x65278255: RtkAPO+0x88255
0x6527b5d6: RtkAPO+0x8B5D6
0x652738a7: RtkAPO+0x838A7
0x75c2e8e0: combase!CServerContextActivator::CreateInstance+0x1A0
0x75bd8f1a: combase!ActivationPropertiesIn::DelegateCreateInstance+0xBA
0x75c2edc2: combase!CApartmentActivator::CreateInstance+0xA2
0x75c2f105: combase!CProcessActivator::CCICallback+0x65
0x75c2f080: combase!CProcessActivator::AttemptActivation+0x40
0x75c2f37b: combase!CProcessActivator::ActivateByContext+0xDB
0x75c2f1f7: combase!CProcessActivator::CreateInstance+0x67
0x75bd8efb: combase!ActivationPropertiesIn::DelegateCreateInstance+0x9B
0x75bd714d: combase!CClientContextActivator::CreateInstance+0xFD
0x75bd8f02: combase!ActivationPropertiesIn::DelegateCreateInstance+0xA2
0x75c27240: combase!ICoCreateInstanceEx+0xBE0
0x75c26509: combase!CComActivator::DoCreateInstance+0x149
0x75c28332: combase!CoCreateInstance+0x132
0x100078da: ALSNDMGR!CPlApplet+0x32BA

    Image path: C:\Windows\System32\RtkAPO.dll
    Image name: RtkAPO.dll
    Timestamp:        Mon Dec 22 08:50:19 2008 (494F46BB)
    CheckSum:         0026D77A
    ImageSize:        0026C000
    File version:     11.0.6000.85
    Product version:  11.0.6000.85
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Realtek Semiconductor Corp.
    ProductName:      Realtek(r) LFX/GFX DSP component
    InternalName:     RTKAPODll
    OriginalFilename: RTKAPO.Dll
    ProductVersion:   11, 0, 6000, 85
    FileVersion:      11, 0, 6000, 85
    FileDescription:  Realtek(r) LFX/GFX DSP component
    LegalCopyright:   Copyright (c) Realtek Semiconductor Corp. 2008

因此,安装较新的 realtek 驱动程序版本来修复该问题。

相关内容