wer.dll

Associated Error Codes

Below lists error codes and symbolic names found for this module.

CodeFound inDescription
0x6478.11011Application Crashing Events
0x3e88.110Faulting application name: %1, version: %2, time stamp: 0x%3 Faulting module name: %4, version: %5, time stamp: 0x%6 Exception code: 0x%7 Fault offset: 0x%8 Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 Faulting package full name: %14 Faulting package-relative application ID: %15
0x3e91011Fault bucket %1, type %2 Event Name: %3 Response: %4 Cab Id: %5 Problem signature: P1: %6 P2: %7 P3: %8 P4: %9 P5: %10 P6: %11 P7: %12 P8: %13 P9: %14 P10: %15 Attached files:%16 These files may be available here: %17 Analysis symbol: %18 Rechecking for solution: %19 Report Id: %20 Report Status: %21 Hashed bucket: %22 Cab Guid: %23
0x300000001011Info
0x500000041011Information
0x900000011011Microsoft-Windows-WER-PayloadHealth
0xc00003ed78.11011Windows cannot access the file %1 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 %2 because of this error. Program: %2 File: %1 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: %3 Disk type: %4
0xc000138878.11011EventType %1, P1 %2, P2 %3, P3 %4, P4 %5, P5 %6, P6 %7, P7 %8, P8 %9, P9 %10, P10 %11
0x3e811Faulting application name: %1, version: %2, time stamp: 0x%3 Faulting module name: %4, version: %5, time stamp: 0x%6 Exception code: 0x%7 Fault offset: 0x%8 Faulting process id: %9 Faulting application start time: %10 Faulting application path: %11 Faulting module path: %12 Report Id: %13 Faulting package full name: %14 Faulting package-relative application ID: %15
0x20003ed11Windows cannot access the file %1 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 %2 because of this error. Program: %2 File: %1 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: %3 Disk type: %4
0x5200000211Error
0x9100000111Application
0x3e87Faulting application name: %1, version: %2, time stamp: 0x%3 Faulting module name: %4, version: %5, time stamp: 0x%6 Exception code: 0x%7 Fault offset: 0x%8 Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13
0x3e97Fault bucket %1, type %2 Event Name: %3 Response: %4 Cab Id: %5 Problem signature: P1: %6 P2: %7 P3: %8 P4: %9 P5: %10 P6: %11 P7: %12 P8: %13 P9: %14 P10: %15 Attached files:%16 These files may be available here: %17 Analysis symbol: %18 Rechecking for solution: %19 Report Id: %20 Report Status: %21
0x3e98.1Fault bucket %1, type %2 Event Name: %3 Response: %4 Cab Id: %5 Problem signature: P1: %6 P2: %7 P3: %8 P4: %9 P5: %10 P6: %11 P7: %12 P8: %13 P9: %14 P10: %15 Attached files:%16 These files may be available here: %17 Analysis symbol: %18 Rechecking for solution: %19 Report Id: %20 Report Status: %21 Hashed bucket: %22
15 entries