Windows 10: Occasional red screen and blue screens when playing various games.

Well, since it didn't work when I updated it, I just uninstalled the driver to the USB adapter and plugged the headset straight into the audio jacks instead of using the USB adapter. It didn't crash yesterday, but I'll let you know if it does today.

 

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

just crashed again...no red screen or blue screen. Just a freeze.

 

The only thing I can see that is still happening on your system is the corrected hardware errors:



Code: 2018-02-27T15:45:34.435 A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 3The details view of this entry contains further information. 2018-02-27T16:02:34.435 A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 2The details view of this entry contains further information. 2018-02-27T16:02:34.435 A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 3The details view of this entry contains further information. 2018-02-27T16:08:34.435 A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 2The details view of this entry contains further information. 2018-02-27T16:08:34.435 A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 3The details view of this entry contains further information.[/quote] This is not causing a BSOD but could well be consistent with the freeze as it appears to happening in quick succession.

I'm not sure what is causing this it could be motherboard or CPU. We really need to know all the hardware details for your system. What type of Power supply do you have? What is its rating? Fill in the My Computer section with all these details.

A stress test of your CPU might reveal if there is anything wrong there.
CPU TEST
*Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

My Build was updated with as much information as i could recall. I'm currently testing my CPU with the Torture Test on Prime95. Will get back to you if/when an error pops up.

 

So about 30 minutes in, the computer crashed during the stress testing. Not sure what I'm looking at, though. Here's the results text file.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

Lots of errors:

Code: ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test.[/quote] Code: FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file.[/quote] Code: FATAL ERROR: Final result was 4B1D5CCF, expected: A8289A03. Hardware failure detected, consult stress.txt file[/quote] Code: FATAL ERROR: Resulting sum was -9336282822464126, expected: 6175958643242089 Hardware failure detected, consult stress.txt file.[/quote] Looks like a defective CPU to me.

 

I don't have enough experience of AMD CPUs failing with Prime95 to know whether this is definitive for a defective CPU.

I guess you will only know if you replace the CPU. Considering the history you have a good case for returning it as faulty. It must be within warranty as you only recently upgraded.

 

@MicRouS
Have you updated the mobo bios to recommended (F3) for the FX9590
I suspect you have a cpu heat/voltage issue, the fx9590 requires cooling by water cooling system (some suggest a large top down cpu fan setup will work ?). CPU volts on some 9590s' may also need fine tuning (from what I've read on AMD forum).

 

In addition to the current findings and plans with the CPU:

The bugchecks reported in the files were:
A
3B
1E
F7
139

There were no new BSOD dump files to debug.

In one of the crashes the event reporting displayed: atikmpag.sys
Also the event logs displayed the driver had stopped responding and recovered.

In the event file there were many problems with creation of dump files.
The BSOD mini dump files that were at one time present have disappeared:

Code: Event[3424]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-02-24T11:07:30.248 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Unable to produce a minidump file from the full dump file.[/quote] Code: Event[3400]: Log Name: System Source: volmgr Date: 2018-02-24T11:07:21.593 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Dump file creation failed due to error during dump creation.[/quote]
1) In the left lower corner search type: system > open system control panel > on the left pane > click advanced system settings >
a) under performance > click settings > on performance options > click the advanced tab > under virtual memory > click change > post an image of the virtual memory window into the thread
b) under startup and recovery > click settings > post an image of the startup and recovery window into the thread

2) If Ccleaner is on the computer > click the windows tab > scroll down to system and advanced > post an image into the thread

Code: 2/20/2018 6:24 PM Windows Error Reporting Fault bucket AV_CODE_AV_nt!PpmIdleExecuteTransition, type 0 Event Name: BlueScreen Response: Not available Cab Id: 5916cfbe-5a43-4ae7-9cd6-16e3a957c5f0 Problem signature: P1: a P2: 7ff8b7b7fb58 P3: ff P4: 3b P5: fffff8032a358d8e P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-6687-01.dmp \\?\C:\Windows\TEMP\WER-11484-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F2B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F4B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F5B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_f7498d78d87b4315c225c87f9ee72fe27212f8_00000000_cab_127c6a23 Analysis symbol: Rechecking for solution: 0 Report Id: f9b0360a-5b86-4d4a-8383-41e68d69d405 Report Status: 268435456 Hashed bucket:2/7/2018 3:56 AM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: c95905b9-0ac4-42b8-a078-d1d0364383d1 Problem signature: P1: 141 P2: ffffac051d918010 P3: fffff80017abf654 P4: 0 P5: 3e8 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180206-2256.dmp \\?\C:\Windows\TEMP\WER-10901687-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6809.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6819.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6829.tmp.txt \\?\C:\Windows\Temp\WER7A2B.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_19f8dc7e59ca482db9a17407c68f3155a6fa1_00000000_cab_19527bdf Analysis symbol: Rechecking for solution: 0 Report Id: d22ac2dc-7f0a-492e-a849-de298b2884a5 Report Status: 268435456 Hashed bucket:2/13/2018 3:15 AM Windows Error Reporting Fault bucket LKD_0x144_CONTROLLER_GONE_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_134D8, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 068a7733-bd56-412b-97a0-36b0051b41f6 Problem signature: P1: 144 P2: 100d P3: ffff9f8874e92970 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20180212-2214.dmp \\?\C:\Windows\TEMP\WER-9496015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF754.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF763.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF774.tmp.txt \\?\C:\Windows\Temp\WER155C.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_713588f045758b3158454f42d2f2cfea3f79e7_00000000_cab_212516e2 Analysis symbol: Rechecking for solution: 0 Report Id: 5b6d0ee5-3068-4403-9933-15894df25230 Report Status: 268435456 Hashed bucket:2/13/2018 12:38 AM Windows Error Reporting Fault bucket LKD_0x144_ENDPOINT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_134D8, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 18e6cd1e-64dd-4be5-a54c-6890f96da00c Problem signature: P1: 144 P2: 1003 P3: ffff9f8871de7970 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20180212-1938.dmp \\?\C:\Windows\TEMP\WER-101765-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA071.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA081.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA0A1.tmp.txt \\?\C:\Windows\Temp\WERC02F.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_57eda0f1651ab411f8058a8fe282d5de4bf6c6b_00000000_cab_2b09c251 Analysis symbol: Rechecking for solution: 0 Report Id: f332e74d-4da5-4fc6-9867-6a6651241dcd Report Status: 268435456 Hashed bucket:2/13/2018 12:32 AM Windows Error Reporting Fault bucket LKD_0x144_HOST_SYSTEM_ERROR_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_134D8, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 7b7e2d49-4664-4eb5-a49f-9881f1c8b083 Problem signature: P1: 144 P2: 1001 P3: fffffa00b7bfc970 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20180212-1932.dmp \\?\C:\Windows\TEMP\WER-387015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA55.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA55.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA75.tmp.txt \\?\C:\Windows\Temp\WERDBF.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_67bfc269654f44ecb875906ad2f7bccc229da_00000000_cab_251e0f35 Analysis symbol: Rechecking for solution: 0 Report Id: df7dfbec-ce42-423a-b214-b78f31a3ea2f Report Status: 268435456 Hashed bucket:2/13/2018 3:15 AM Windows Error Reporting Fault bucket LKD_0x144_RESET_RECOVERY_STOP_FAILED_USBXHCI!TelemetryData_CreateReport_VEN_1106_DEV_3483_REV_01_FW_134D8, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: f43e485f-3b12-4d9b-b84e-82d44925e700 Problem signature: P1: 144 P2: 100b P3: ffff9f8874e92970 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20180212-2214-01.dmp \\?\C:\Windows\TEMP\WER-9496125-1.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7A4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7C4.tmp.txt \\?\C:\Windows\Temp\WER2906.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_64df7059255681bd3ec08c2d70166fc772e83af_00000000_cab_21252aa8 Analysis symbol: Rechecking for solution: 0 Report Id: ddb56fb4-50c6-48af-974b-9a6e63e27b80 Report Status: 268435456 Hashed bucket:2/19/2018 8:23 PM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_2109_DEV_3431_REV_0420, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: e7754460-49c6-4a75-898b-650cb5a9b30c Problem signature: P1: 144 P2: 3003 P3: ffffa08e6c86f808 P4: 40010000 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20180219-1523.dmp \\?\C:\Windows\TEMP\WER-318362375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE508.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE508.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE528.tmp.txt \\?\C:\Windows\Temp\WER5DF.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_73df2f6c8b44b2b1a4756a640e691239f5b8aa_00000000_cab_089607a3 Analysis symbol: Rechecking for solution: 0 Report Id: e97e7813-8ec1-4c08-8d22-2778c399beaf Report Status: 268435456 Hashed bucket:2/21/2018 1:25 AM Windows Error Reporting Fault bucket STACK_BUFFER_OVERRUN_nt!KiSwapThread, type 0 Event Name: BlueScreen Response: Not available Cab Id: a08d6c1d-fa40-4272-a70f-acfbbc73af47 Problem signature: P1: f7 P2: 2d594a39e19e P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-7328-01.dmp \\?\C:\Windows\TEMP\WER-12515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48FF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER498D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_f7_50cd7cfd9667348efc154780eac2cc692e46601c_00000000_cab_1b6086e3 Analysis symbol: Rechecking for solution: 0 Report Id: f5250617-cb5b-4892-bd71-dad5327c1bed Report Status: 268435456 Hashed bucket:[/quote] Code: 2/20/2018 4:47 PM Windows Error Reporting Fault bucket 0x1E_c0000005_R_STACKPTR_ERROR_nt!KiBeginCounterAccumulation, type 0 Event Name: BlueScreen Response: Not available Cab Id: cf8c7043-6586-40f3-8e5b-6bacf125eea2 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8000a88777c P4: 0 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-6609-01.dmp \\?\C:\Windows\TEMP\WER-12484-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_b3dae2a56b9b9b8af855e3ba5a5b86449b5e387_00000000_cab_09d288ba Analysis symbol: Rechecking for solution: 0 Report Id: 6d7892e2-f6bf-437c-87c4-0d49c749c515 Report Status: 268435460 Hashed bucket:2/16/2018 3:16 AM Windows Error Reporting Fault bucket 0x3B_nt!KiSearchForNewThreadOnProcessor, type 0 Event Name: BlueScreen Response: Not available Cab Id: a7dfd837-19db-418e-8fc4-1122bc029c8d Problem signature: P1: 3b P2: c0000005 P3: fffff802b411e99e P4: ffffec03050a6560 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021518-6875-01.dmp \\?\C:\Windows\TEMP\WER-23171-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E4A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E79.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E89.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_f79248db829f5c281ff15687656b24f7185ced_00000000_cab_20c89eef Analysis symbol: Rechecking for solution: 0 Report Id: ec8831a1-1e60-499c-863d-58716f5b7f55 Report Status: 268435456 Hashed bucket:2/22/2018 3:18 AM Windows Error Reporting Fault bucket 0x3B_win32kfull!TimersProc, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7d2ba662-f7e3-4c87-a58c-0dce6a7dff6c Problem signature: P1: 3b P2: c0000005 P3: ffffc998dc8916e1 P4: ffffa88788739d50 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022118-6250-01.dmp \\?\C:\Windows\TEMP\WER-11609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FF7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4007.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_01b19a4a6c5492fce1155793f71da8cc6182d67_00000000_cab_0d1484a1 Analysis symbol: Rechecking for solution: 0 Report Id: 921e751b-ce5b-4a8f-88e9-f494be408f72 Report Status: 268435456 Hashed bucket:[/quote] Code: 2/20/2018 4:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8000a88777c P4: 0 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-6609-01.dmp \\?\C:\Windows\TEMP\WER-12484-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_b3dae2a56b9b9b8af855e3ba5a5b86449b5e387_00000000_cab_02dc48c1 Analysis symbol: Rechecking for solution: 0 Report Id: 6d7892e2-f6bf-437c-87c4-0d49c749c515 Report Status: 4 Hashed bucket:2/22/2018 3:18 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffffc998dc8916e1 P4: ffffa88788739d50 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022118-6250-01.dmp \\?\C:\Windows\TEMP\WER-11609-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FF7.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4007.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_01b19a4a6c5492fce1155793f71da8cc6182d67_00000000_cab_02e04016 Analysis symbol: Rechecking for solution: 0 Report Id: 921e751b-ce5b-4a8f-88e9-f494be408f72 Report Status: 4 Hashed bucket:2/16/2018 3:16 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff802b411e99e P4: ffffec03050a6560 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\021518-6875-01.dmp \\?\C:\Windows\TEMP\WER-23171-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E4A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E79.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E89.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_f79248db829f5c281ff15687656b24f7185ced_00000000_cab_02e06e98 Analysis symbol: Rechecking for solution: 0 Report Id: ec8831a1-1e60-499c-863d-58716f5b7f55 Report Status: 4 Hashed bucket:2/20/2018 6:23 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 7ff8b7b7fb58 P3: ff P4: 3b P5: fffff8032a358d8e P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-6687-01.dmp \\?\C:\Windows\TEMP\WER-11484-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F2B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F4B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F5B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_f7498d78d87b4315c225c87f9ee72fe27212f8_00000000_cab_02dc3f5a Analysis symbol: Rechecking for solution: 0 Report Id: f9b0360a-5b86-4d4a-8383-41e68d69d405 Report Status: 4 Hashed bucket:2/21/2018 1:25 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: f7 P2: 2d594a39e19e P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-7328-01.dmp \\?\C:\Windows\TEMP\WER-12515-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48FF.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER497C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER498D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_f7_50cd7cfd9667348efc154780eac2cc692e46601c_00000000_cab_02ec499b Analysis symbol: Rechecking for solution: 0 Report Id: f5250617-cb5b-4892-bd71-dad5327c1bed Report Status: 4 Hashed bucket:2/20/2018 4:40 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: cf8c7043-6586-40f3-8e5b-6bacf125eea2 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff8000a88777c P4: 0 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\022018-6609-01.dmp \\?\C:\Windows\TEMP\WER-12484-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4872.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_b3dae2a56b9b9b8af855e3ba5a5b86449b5e387_00000000_cab_02dc48c1 Analysis symbol: Rechecking for solution: 0 Report Id: 6d7892e2-f6bf-437c-87c4-0d49c749c515 Report Status: 4 Hashed bucket:[/quote] Code: Event[638]: Log Name: System Source: Display Date: 2018-02-06T22:56:23.762 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Display driver amdkmdap stopped responding and has successfully recovered. Event[639]: Log Name: System Source: Display Date: 2018-02-06T22:56:26.060 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote]

 

Here are the picture uploads you requested. Not sure if this helps, but it's my friend's old 9590 and Motherboard, but the Power Supply is brand new...Probably should've mentioned that looking back on it now lol.

 

1) For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files

2) Download and install Whocrashed:
Resplendence Software - WhoCrashed, automatic crash dump analyzer

3) In the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
4) Click analyze > view the report > it may display deaddead
5) Post the report into the thread using a one drive or drop box share link
6) Run the beta version of the log collector using extract then open and post a zip into the thread: (it provides more information)
log collector v2-beta08.zip
In case there are problems running the beta log collector you an run the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums

 

Dropbox - DESKTOP-IRU6EQ2-Tue_03_13_2018_182953_26.zip

here's the beta log collection.

Dropbox - DESKTOP-IRU6EQ2 (2018-03-13 18 38).zip

here's the other log collection.

here's the whocrashed output.

Dropbox - WhoCrashedOutput.htm

I think the reason that the dump files are corrupted sometimes is because it's a red screen and thus, doesn't collect the data properly.

 

Oh and by the way, I fresh installed windows and stress tested the cpu with prime95. No crashes after 4 hours. I then took it home and installed steam, discord, corsair utility engine, chrome, battle.net, audacity, 7zip, and EpicGames Launcher. Also, plugged in my own keyboard, mouse, headset, and monitor instead of my friend's after those tests. I think that may be pertinent information.

 

Since 3/8/2018 these were the new bugchecks:
A) The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A.
3D) The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D.
50) The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050.
1E) The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E.
F7) The DRIVER_OVERRAN_STACK_BUFFER bug check has a value of 0x000000F7.


1) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > un-check automatically restart

With this setting change whenever there is a BSOD you will see the BSOD windows. No longer will there be unexpected restarts for BSOD. There can be unexpected restarts for non-BSOD crashes. When you view the BSOD windows always allow it to go to 100% so that it can create a BSOD dump file. On the BSOD windows you will see a bugcheck. Sometimes you may see the misbehaving driver in the form *.sys. If you see the misbehaving driver please record it and post it into the thread.

2) Uninstall Malwarebytes
3) The AV software can be reinstalled in 1 week if there are no more BSOD. When the software is reinstalled if there is a BSOD then uninstall the software and find an alternative AV product. If there are no new BSOD then continue using the software.

4) Backup all files to another drive or into the cloud

5) Make a backup image using Macrium
Macrium Software | Macrium Reflect Free
Place the backup image onto another drive or into the cloud

6) Make a brand new restore point

7) Read these links on Windows driver verifier:

a) Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

b) Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

Windows driver verifier is a tool that will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off. Each time there is a BSOD a dump file should be created which when debugged can display a misbehaving driver.
The tool will be run for 48 hours. After the last BSOD the tool will be run for an additional 36 hours.

After each BSOD you will see the BSOD window with a bugcheck and sometimes a misbehaving driver. You will then need to turn off Windows driver verifier and this is done using the Windows advanced troubleshooting menu. There are 3 methods used to either turn off or recover from the tool.

Use the information in link b to turn off the tool.
Use the information in link a for the customized test settings.

After each BSOD the tool will be turned off and you will return to the desktop. On the desktop run whocrashed to find the misbehaving driver. Then uninstall the misbehaving driver. At the same time run the beta version of the log collector and post a new zip into the thread for troubleshooting. The debugging tools that we use are more powerful than Whocrashed and if Whocrashed did not find a misbehaving drivers we may be able to find them.

Drivers can be reinstalled after they are uninstalled or after all misbehaving drivers have been uninstalled after multiple runs of Windows driver verifier. The end result should be the same.

When using windows driver verifier some computers may become sluggish or have a very slow boot. If this happens the customized test settings can be modified. In link a there are approximately 19 customized settings. In link b there are 3 customized settings. So with more customized tests active at one time you will more likely have BSOD.

Before using the tool the files must be backed up and a brand new restore point made.
When you are comfortable with the methods to turn off the tool you can start using it.

8) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials

Code: Event[1944]: Log Name: System Source: volmgr Date: 2018-03-13T18:28:10.562 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Dump file creation failed due to error during dump creation.[/quote] Code: Event[1970]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2018-03-13T18:28:19.892 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IRU6EQ2 Description: Unable to produce a minidump file from the full dump file.[/quote] Code: 3/11/2018 7:09 PM Windows Error Reporting Fault bucket STACK_BUFFER_OVERRUN_nt!KiSwapThread, type 0 Event Name: BlueScreen Response: Not available Cab Id: 91ce0126-629d-443c-92d1-c916bf395731 Problem signature: P1: f7 P2: ffff8080d35d92ec P3: e37397879e09 P4: ffff1c8c687861f6 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031118-6171-01.dmp \\?\C:\WINDOWS\TEMP\WER-12859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E6E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EBD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_f7_abfa80a186c457bdd48215418d81fb86d54d1_00000000_cab_1c247668 Analysis symbol: Rechecking for solution: 0 Report Id: b17c6c5c-7c67-4703-a513-2c92777a575b Report Status: 268435456 Hashed bucket:3/8/2018 8:42 PM Windows Error Reporting Fault bucket AV_nt!KeWaitForSingleObject, type 0 Event Name: BlueScreen Response: Not available Cab Id: b80b6b58-d0fb-4cf7-9d7f-6fedc3342759 Problem signature: P1: a P2: 0 P3: 2 P4: 0 P5: fffff80216957501 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030818-7968-01.dmp \\?\C:\WINDOWS\TEMP\WER-15734-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B70.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B80.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B90.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_d3862b00d0f9eaf286c583ea94ad858212b8_00000000_cab_11106ce3 Analysis symbol: Rechecking for solution: 0 Report Id: 3a6f640b-f84a-4435-ae7d-3ad68189ef41 Report Status: 268435456 Hashed bucket:[/quote] Code: 3/13/2018 10:34 PM Windows Error Reporting Fault bucket 0xDEADDEAD_rspCrash64!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: 9056279d-92e6-41cc-a420-db9d6c9f520e Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19bba471 P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031318-8500-01.dmp \\?\C:\WINDOWS\TEMP\WER-16171-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6987.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69C6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69D6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_deaddead_fb4eeee6d2fd63b53eaea1761c52384a4a01c_00000000_cab_1e2c8935 Analysis symbol: Rechecking for solution: 0 Report Id: 1ec1dd22-3485-4e65-82fb-14dcd1bfc84d Report Status: 268435456 Hashed bucket:3/11/2018 1:58 AM Windows Error Reporting Fault bucket 0x1E_c0000005_R_nt!KiSwapThread, type 0 Event Name: BlueScreen Response: Not available Cab Id: b35c6672-36fb-42b6-9547-c45008517542 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff802af6cd43e P4: 0 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031018-5812-01.dmp \\?\C:\WINDOWS\TEMP\WER-12484-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4612.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_fa66c2d9e177fcad14521135f244fcf322ed567_00000000_cab_1704b1bc Analysis symbol: Rechecking for solution: 0 Report Id: 81156c5c-ad96-4ce2-9cc4-d5f02c6922da Report Status: 268435456 Hashed bucket:[/quote] Code: 3/11/2018 7:09 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: f7 P2: ffff8080d35d92ec P3: e37397879e09 P4: ffff1c8c687861f6 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031118-6171-01.dmp \\?\C:\WINDOWS\TEMP\WER-12859-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E6E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EAC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EBD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_f7_abfa80a186c457bdd48215418d81fb86d54d1_00000000_cab_02a04ecb Analysis symbol: Rechecking for solution: 0 Report Id: b17c6c5c-7c67-4703-a513-2c92777a575b Report Status: 4 Hashed bucket:3/13/2018 10:34 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: deaddead P2: 0 P3: 0 P4: 19bba471 P5: 3c2a58ed P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031318-8500-01.dmp \\?\C:\WINDOWS\TEMP\WER-16171-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6987.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69C6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69D6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_deaddead_fb4eeee6d2fd63b53eaea1761c52384a4a01c_00000000_cab_02b469d5 Analysis symbol: Rechecking for solution: 0 Report Id: 1ec1dd22-3485-4e65-82fb-14dcd1bfc84d Report Status: 4 Hashed bucket:3/8/2018 8:42 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 0 P3: 2 P4: 0 P5: fffff80216957501 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\030818-7968-01.dmp \\?\C:\WINDOWS\TEMP\WER-15734-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B70.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B80.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B90.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_d3862b00d0f9eaf286c583ea94ad858212b8_00000000_cab_02cc4b9f Analysis symbol: Rechecking for solution: 0 Report Id: 3a6f640b-f84a-4435-ae7d-3ad68189ef41 Report Status: 4 Hashed bucket:3/11/2018 1:58 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff802af6cd43e P4: 0 P5: ffffffffffffffff P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\031018-5812-01.dmp \\?\C:\WINDOWS\TEMP\WER-12484-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45D3.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4601.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4612.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_fa66c2d9e177fcad14521135f244fcf322ed567_00000000_cab_02ac4621 Analysis symbol: Rechecking for solution: 0 Report Id: 81156c5c-ad96-4ce2-9cc4-d5f02c6922da Report Status: 4 Hashed bucket:[/quote] Code: Event[223]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-03-08T15:32:56.582 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: DESKTOP-IRU6EQ2 Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Cache Hierarchy Error Processor APIC ID: 3 The details view of this entry contains further information.[/quote]

 

So, I uninstalled my AV and proceeded with the driver verifier and on reboot it blue screened and it's been on 100% on the error info collection, but it won't take me to the repair options menu. Can I reboot and disable this or should I just give it more time?