在过去的几天里,由我制造的Windows 7台式机开始表现异常。我经常使用它,大约有一半的时间是通过TeamViewer使用的。资源管理器将崩溃并随机重启,几乎总是通过TeamViewer进行。这使我怀疑TeamViewer是问题所在,但是无论是否使用TeamViewer,我都多次复制了它。我似乎无法解决问题的唯一方法是启动到安全模式。
我用的CCleaner和的Malwarebytes,以确保它是不是造成问题的原因注册表错误或恶意软件,我已经试图在相宜相关的问题修复在这里以及所有其他修复我已经在网上找到包括拆除安全更新KB980408和KB2926765以及使用“ sfc / scannow”和其他我不记得的东西。
最近,当我尝试启动资源管理器时,它弹出一个小窗口,上面显示“个性化设置”,但它完全是空的并立即崩溃。我可以使它消失的唯一方法是杀死explorer.exe进程。我希望可以截取屏幕截图,但似乎无法打开画笔甚至找不到该exe。我尝试重新启动它,我尝试在个性化设置窗口打开时启动它。
我提供了两个进程列表,第一个是当我启动时safe mode
资源管理器似乎可以正常工作的活动进程列表。第二个是进程列表,我可以将其缩小到正常引导状态,并且仍然可以复制问题。我似乎无法关闭一个过程。NisSrv.exe,被描述为“ Microsoft网络实时检查服务”。当我尝试关闭进程NisSrv.exe时,提示“操作无法完成。访问被拒绝。” 当我尝试关闭相关服务时,它会显示相同的消息。
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
System Idle Process 0 Services 0 24 K
System 4 Services 0 2,660 K
smss.exe 304 Services 0 1,196 K
csrss.exe 408 Services 0 4,156 K
wininit.exe 444 Services 0 4,608 K
csrss.exe 452 Console 1 8,700 K
services.exe 492 Services 0 7,700 K
winlogon.exe 524 Console 1 5,756 K
lsass.exe 536 Services 0 10,644 K
lsm.exe 544 Services 0 4,316 K
svchost.exe 652 Services 0 8,976 K
MsMpEng.exe 804 Services 0 40,696 K
explorer.exe 1332 Console 1 85,220 K
ctfmon.exe 1376 Console 1 3,680 K
dllhost.exe 1624 Console 1 8,656 K
chrome.exe 1408 Console 1 98,504 K
WmiPrvSE.exe 2352 Services 0 6,472 K
chrome.exe 1744 Console 1 65,116 K
taskmgr.exe 372 Console 1 14,948 K
cmd.exe 2776 Console 1 2,960 K
conhost.exe 1816 Console 1 3,580 K
tasklist.exe 2308 Console 1 5,868 K
以及我已将其范围缩小到的进程列表。
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
System Idle Process 0 Services 0 24 K
System 4 Services 0 2,808 K
smss.exe 316 Services 0 1,216 K
csrss.exe 484 Services 0 4,532 K
wininit.exe 596 Services 0 4,604 K
csrss.exe 604 Console 1 23,676 K
services.exe 652 Services 0 11,344 K
lsass.exe 668 Services 0 12,692 K
lsm.exe 676 Services 0 4,464 K
MsMpEng.exe 972 Services 0 68,436 K
winlogon.exe 168 Console 1 7,784 K
svchost.exe 496 Services 0 19,140 K
NisSrv.exe 3176 Services 0 808 K
svchost.exe 1684 Services 0 11,260 K
taskmgr.exe 4524 Console 1 20,696 K
cmd.exe 4764 Console 1 7,224 K
conhost.exe 4772 Console 1 6,916 K
sublime_text.exe 2340 Console 1 45,012 K
dllhost.exe 4476 Console 1 8,736 K
tasklist.exe 3796 Console 1 5,768 K
WmiPrvSE.exe 1768 Services 0 6,344 K
这是来自事件查看器的事件数据xml,该错误是我遇到的错误。
<EventData>
<Data>explorer.exe</Data>
<Data>6.1.7601.17567</Data>
<Data>4d672ee4</Data>
<Data>vrfcore.dll</Data>
<Data>6.3.9600.16384</Data>
<Data>5215f8f5</Data>
<Data>80000003</Data>
<Data>0000000000003a00</Data>
<Data>12e4</Data>
<Data>01cfb84fa70f89dc</Data>
<Data>C:\Windows\system32\explorer.exe</Data>
<Data>C:\Windows\SYSTEM32\vrfcore.dll</Data>
<Data>e5957093-2442-11e4-9f8a-94de806ed9cb</Data>
</EventData>
我再次浏览了eventvwr日志,发现了这一点,可能与
<EventData>
<Data>runonce.exe</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7a253</Data>
<Data>MSVCR100.dll</Data>
<Data>10.0.40219.325</Data>
<Data>4df2bcac</Data>
<Data>c0000005</Data>
<Data>000000000003c145</Data>
<Data>670</Data>
<Data>01cfb8dabbd85942</Data>
<Data>C:\Windows\system32\runonce.exe</Data>
<Data>C:\Windows\system32\MSVCR100.dll</Data>
<Data>fa6f82b9-24cd-11e4-80a8-94de806ed9cb</Data>
</EventData>
以及一般错误的详细信息
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: vrfcore.dll, version: 6.3.9600.16384, time stamp: 0x5215f8f5
Exception code: 0x80000003
Fault offset: 0x0000000000003a00
Faulting process id: 0xc38
Faulting application start time: 0x01cfb84e5e852c5f
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\SYSTEM32\vrfcore.dll
Report Id: 9dc19e6d-2441-11e4-9f8a-94de806ed9cb
我似乎经常遇到的另一个可能无关的错误。
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60
WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99"
could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003.
Events cannot be delivered through this filter until the problem is corrected.
尝试取消选中某项时,在“自动运行”中的“我的资源管理器”选项卡与错误一起显示如下。我应该补充一点,我似乎能够使用ShellExView禁用Shell扩展,但仍然无法使Explorer正确启动。
EXPLORER SHELL UPDATE-参见下面的屏幕截图,我可以通过我下载的名为NexusFile的文件管理器访问资源管理器右键菜单,但是启动资源管理器仍然没有运气。
关于Windows Search Service的另一轮错误
The search service has detected corrupted data files in the index {id=4700}.
The service will attempt to automatically correct this problem by rebuilding the index.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
其次是
The Windows Search Service is being stopped because there is a problem with the
indexer: The catalog is corrupt.
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801
和
The plug-in in <Search.JetPropStore> cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
和
The gatherer object cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)
和
The Windows Search Service cannot load the property store information.
Context: Windows Application, SystemIndex Catalog
Details:
The content index database is corrupt. (HRESULT : 0xc0041800) (0xc0041800)
世卫组织日志
The problem turned out to be Visual Studio trying to debug the explorer crash that caused it to never be able to start. I uninstalled Visual Studio and rebooted and explorer then crashed on boot but immediately restarted and worked fine. I have isolated the crash on boot and traced it to an error with Synergy found here http://synergy-project.org/spit/issues/details/3980/
Thank you to everyone for being patient and helping me, and I will be accepting @and31415 as the answer since he pointed out that the vrfcore.dll was a Visual Studio dll.
The vrfcore.dll
library file mentioned in the log is related to the Microsoft Application Verifier tool, which is part of the Windows 8.1 SDK/WDK (in fact, the file version is 6.3.9600.16384
) and is also included with Visual Studio 2013.
Quoting the documentation:
Application Verifier assists developers in quickly finding subtle programming errors that can be extremely difficult to identify with normal application testing. Using Application Verifier in Visual Studio makes it easier to create reliable applications by identifying errors caused by heap corruption, incorrect handle and critical section usage.
Source: Application Verifier
Although it's not an actual solution, uninstalling Visual Studio can serve as a temporary workaround. Before doing so, you might try to remove just the Application Verifier by following these steps:
Open an elevated command prompt.
Run one of the following commands depending on the Windows version you're running:
x86 (32-bit)
msiexec /uninstall {13A3E02D-36D4-BBD6-0BBD-D0BFDBEA0079}
x64 (64-bit)
msiexec /uninstall {77F3D72C-465F-BD51-890E-CC3914B1365F}
Restart Windows.
注意您可能要确保已安装所有Visual Studio更新,其中可能包括针对特定问题的错误修复。
本文收集自互联网,转载请注明来源。
如有侵权,请联系 [email protected] 删除。
我来说两句