1.
Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe970068
Faulting process id: 0x6f8
Faulting application start time: 0x01ca87f6548089a9
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report Id: 1ae8844b-f3ea-11de-ab8c-00247e5aa068
2.Faulting application name: MSASCui.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc90c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe9d0068
Faulting process id: 0xc30
Faulting application start time: 0x01ca87f6c8f508b0
Faulting application path: C:\Program Files\Windows Defender\MSASCui.exe
Faulting module path: unknown
Report Id: 12bbce86-f3ea-11de-ab8c-00247e5aa068
3.
Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Windows Explorer because of this error.
Program: Windows Explorer
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
4.Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x000007fefe990068
Faulting process id: 0xfdc
Faulting application start time: 0x01ca87f5258fe25c
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report Id: 83b32e0f-f3e9-11de-ab8c-00247e5aa068
5.Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe9b006d
Faulting process id: 0x260
Faulting application start time: 0x01ca87f510a2d3cb
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report Id: 5fb5b9ed-f3e8-11de-ab8c-00247e5aa068
6.Faulting application name: explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe9d0068
Faulting process id: 0xd40
Faulting application start time: 0x01ca87f50c8091dc
Faulting application path: C:\Windows\explorer.exe
Faulting module path: unknown
Report Id: 4ba8ae64-f3e8-11de-ab8c-00247e5aa068
7.Faulting application name: Explorer.exe, version: 6.1.7600.16404, time stamp: 0x4a765771
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe9b006d
Faulting process id: 0xb38
Faulting application start time: 0x01ca87f4496b5bda
Faulting application path: C:\Windows\Explorer.exe
Faulting module path: unknown
Report Id: 4a275ff0-f3e8-11de-ab8c-00247e5aa068
8.Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Windows Explorer because of this error.
Program: Windows Explorer
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
9.Faulting application name: NOTEPAD.EXE, version: 6.1.7600.16385, time stamp: 0x4a5bc9b3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fefe9c006a
Faulting process id: 0xa8
Faulting application start time: 0x01ca87f3292cd283
Faulting application path: C:\Windows\system32\NOTEPAD.EXE
Faulting module path: unknown
Report Id: 01322f1b-f3e7-11de-ab8c-00247e5aa068
10.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.
11.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.