Hi. . .
The system has had
41 BSODs according to the Windows app
msinfo32. You can find these in the future in the
msinfo32.nfo file - "Software Environment"; "Windows Error Reporting" (WERCON).
I extracted the 41 BSOD WERCON records: (scroll to the right and look for
BlueScreen -
Code:
27-2-2019 8:34 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\022719-11934-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-197887-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WER1A72.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_121524be Analysis symbol: Rechecking for solution: 0 Report Id: 022719-11934-01 Report Status: 0
21-2-2019 22:28 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\022119-32635-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-169027-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1ce6bc2d Analysis symbol: Rechecking for solution: 0 Report Id: 022119-32635-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\120318-12402-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-2149880-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 120318-12402-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\011719-18267-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-162911-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 011719-18267-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\012819-23025-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-201319-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 012819-23025-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\120518-66128-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-1445411-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 120518-66128-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\112918-10623-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-651428-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 112918-10623-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021019-11996-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-36451209-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 021019-11996-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\013019-12121-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-89609017-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 013019-12121-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\123118-13135-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-118981-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 123118-13135-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\121218-17206-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-145517-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 121218-17206-01 Report Status: 0
12-2-2019 11:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021119-15553-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-162287-0.sysdata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 021119-15553-01 Report Status: 0
12-2-2019 11:04 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\110718-26613-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-180415-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WER962.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 110718-26613-01 Report Status: 0
12-2-2019 11:04 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\111218-10264-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-290661-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WERBA2A.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 111218-10264-01 Report Status: 0
12-2-2019 11:04 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021219-10951-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-305278-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WER8600.tmp.WERInternalMetadata.xml These files may be available here: Analysis symbol: Rechecking for solution: 1 Report Id: 021219-10951-01 Report Status: 0
12-2-2019 11:02 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021219-10951-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-305278-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WER8600.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_18ea904d Analysis symbol: Rechecking for solution: 0 Report Id: 021219-10951-01 Report Status: 0
11-2-2019 9:08 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021119-15553-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-162287-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0ceb0be2 Analysis symbol: Rechecking for solution: 0 Report Id: 021119-15553-01 Report Status: 0
10-2-2019 12:40 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\021019-11996-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-36451209-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_19a4a5fa Analysis symbol: Rechecking for solution: 0 Report Id: 021019-11996-01 Report Status: 0
31-1-2019 9:46 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\013019-12121-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-89609017-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1930137c Analysis symbol: Rechecking for solution: 0 Report Id: 013019-12121-01 Report Status: 2
28-1-2019 9:54 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\012819-23025-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-201319-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1e4b8130 Analysis symbol: Rechecking for solution: 0 Report Id: 012819-23025-01 Report Status: 0
17-1-2019 23:26 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\011719-18267-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-162911-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_2008c497 Analysis symbol: Rechecking for solution: 0 Report Id: 011719-18267-01 Report Status: 0
31-12-2018 21:27 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\123118-13135-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-118981-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_183a6d04 Analysis symbol: Rechecking for solution: 0 Report Id: 123118-13135-01 Report Status: 2
12-12-2018 9:28 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\121218-17206-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-145517-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_16a00f2c Analysis symbol: Rechecking for solution: 0 Report Id: 121218-17206-01 Report Status: 0
5-12-2018 9:01 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\120518-66128-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-1445411-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1c3dd7f7 Analysis symbol: Rechecking for solution: 0 Report Id: 120518-66128-01 Report Status: 0
3-12-2018 9:03 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\120318-12402-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-2149880-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_27bcfb6e Analysis symbol: Rechecking for solution: 0 Report Id: 120318-12402-01 Report Status: 0
29-11-2018 13:55 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\112918-10623-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-651428-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1a9a3091 Analysis symbol: Rechecking for solution: 0 Report Id: 112918-10623-01 Report Status: 0
12-11-2018 8:25 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\111218-10264-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-290661-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WERBA2A.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1d0dc467 Analysis symbol: Rechecking for solution: 0 Report Id: 111218-10264-01 Report Status: 0
7-11-2018 13:03 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\110718-26613-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-180415-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WER962.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1d8313dd Analysis symbol: Rechecking for solution: 0 Report Id: 110718-26613-01 Report Status: 0
13-8-2018 17:51 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\081318-48672-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-191413-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0e3efeb8 Analysis symbol: Rechecking for solution: 0 Report Id: 081318-48672-01 Report Status: 0
13-8-2018 8:09 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\081318-30295-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-1068981-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1fe521b3 Analysis symbol: Rechecking for solution: 0 Report Id: 081318-30295-01 Report Status: 0
24-7-2018 15:31 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\072418-51885-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-137561-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_12525668 Analysis symbol: Rechecking for solution: 0 Report Id: 072418-51885-01 Report Status: 0
16-7-2018 7:50 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\071618-17160-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-219852-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_2193fbbc Analysis symbol: Rechecking for solution: 0 Report Id: 071618-17160-01 Report Status: 0
19-6-2018 20:51 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\061918-13806-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-277806-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1da0644d Analysis symbol: Rechecking for solution: 0 Report Id: 061918-13806-01 Report Status: 0
12-6-2018 13:27 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\061218-25693-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-9236756-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_129e3c95 Analysis symbol: Rechecking for solution: 0 Report Id: 061218-25693-01 Report Status: 0
1-6-2018 9:33 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\060118-12807-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-156079-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0c92a533 Analysis symbol: Rechecking for solution: 0 Report Id: 060118-12807-01 Report Status: 0
11-5-2018 8:41 Windows Error Reporting Fault bucket X64_0xC5_2_nt!ExAllocatePoolWithTag+537, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\051118-11216-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-2737567-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WERB52B.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1f5ed6ee Analysis symbol: X64_0xC5_2_nt!ExAllocatePoolWithTag+537 Rechecking for solution: 0 Report Id: 051118-11216-01 Report Status: 0
26-4-2018 14:42 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\042618-9484-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-883106-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0ee243b3 Analysis symbol: Rechecking for solution: 0 Report Id: 042618-9484-01 Report Status: 0
26-4-2018 7:55 Windows Error Reporting Fault bucket X64_0x4E_7_nt!MiPfnReferenceCountIsZero+83319, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\042518-9032-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-54397080-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WERE86B.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1d09ffc2 Analysis symbol: X64_0x4E_7_nt!MiPfnReferenceCountIsZero+83319 Rechecking for solution: 0 Report Id: 042518-9032-01 Report Status: 0
25-4-2018 7:30 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\042518-12838-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-73148-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1941de3d Analysis symbol: Rechecking for solution: 0 Report Id: 042518-12838-01 Report Status: 2
25-4-2018 6:58 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\042418-9094-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-35646774-0.sysdata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0598f570 Analysis symbol: Rechecking for solution: 0 Report Id: 042418-9094-01 Report Status: 0
9-4-2018 7:25 Windows Error Reporting Fault bucket X64_0x3B_nt!ExDeferredFreePool+1df, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\040918-10296-01.dmp C:\Users\svenv\AppData\Local\Temp\WER-153005-0.sysdata.xml C:\Users\svenv\AppData\Local\Temp\WERAD00.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\svenv\AppData\Local\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_1622c7e0 Analysis symbol: X64_0x3B_nt!ExDeferredFreePool+1df Rechecking for solution: 0 Report Id: 040918-10296-01 Report Status: 0
The earliest date that I see off-hand is January 2018 - some 13 months ago.
You can find the actual WERCON reports (*.wer) and very likely some/many of the mini kernel memory dumps in two locations -
- %programdata%\microsoft\windows\wer
- %userprofile%\appdata\local\microsoft\windows\wer
There will be 2 sub-directories under each directory. You'll just have to go through them 1-by-1 if you wish to. The sub-directories will likely be colored
blue indicating compressed files, but you should be able to open them. If you have problems with Windows Explorer, use Altap Salamander, a 3rd party file manager that I've used in lieu of Windows Explorer for over 12 years now.
Altap is a 30-day trial, but can be used far after that date. Installation is easy and clean (no surprise junk is installed); likewise, uninstallation is easy and complete - no remnants left behind.
Download - Altap Salamander File Manager
Now... on to your 2 mini kernel memory dumps....
Bugchecks:
- 0x1a - severe memory management error; NT Kernel named probable cause. NT can never be the cause. It is named here as a default since the real culprit cannot be identified
- 0xc5 - indicates that the system attempted to access invalid memory at a process IRQL that was too high; so basically invalid memory referenced. The probable cause listed as the Microsoft Windows FileInfo Filter Driver fileinfo.sys. Again, like NT, this driver is not the cause of this BSOD because it is a Microsoft Windows driver and is therefore sacrosanct. The real culprit either got away or could not be identified
Of course, the only other cause besides a <1% chance of a Windows Update driver is unknown hardware failure.
I would highly recommend that you test both RAM and al hard drives. I know you said this is a remote system, but these 2 tests really should be done -
I would start with SeaTools for DOS. Windows does not load for either test, so there is no chance of getting BSODs during the testing.
There are 3 drives listed, including a ~4 GB USB (likely a thumb drive -?), and a 64 GB drive listed as "SDXC Card". If this drive is like an SSD, it could definitely give off memory related bugchecks like the
0x1a memory management error.
I do think your issue here is unknown hardware failure with an indication toward a storage device given that
fileinfo.sys was named, even though it was not the cause.
The other odd item in the dump that named NT were the high number of unloaded drivers, specifically
hiber_iaStor and
hiber_storpo - which are likely actually an Intel storage driver and storport.sys - another storage driver. I don't know why these would constantly be unloaded then reloaded. It is odd to say the least.
As you indicated, you could run Driver Verifier, but with just 2 dumps to work with out of 41 and both having different bugchecks, again, I do believe the cause here is unknown hardware failure.
That is it for now!
Regards. . .
jcgriff2
