Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
I am here after ignoring this issue for about 4 years, as I tried a few things without any success and then gave up. Since then I've just restarted my pc when it would crash (about twice a day, though it's been getting more as of late). I've been having this issue since I bought my pc but I could send it to the shop because I'd not have a pc for two weeks or more.
Firstly, the freeze can be described as follows:
The displays retain the same image, they therefore do not switch to a blue screen of death or anything similar. If sound is playing, it might sometimes be looped into a small segment and be repeated indefinitely.
I've tried disabling fast boot, disabling C-States (BIOS), disabling ram dual mode timings, removing one of the two rams at a time and I wiped the disks (multiple times, f.e. with reinstalling windows.)
I've reinstalled windows yesterday again and tried running chkdsk, which fixed some errors but this did not stop the crashes.
In Event Viewer, I typically get the following errors:
I've not tried running the intel video adapter on my motherboard, so I will give that a go, though I do not think that is an issue because I've replaced my gpu and it kept crashing.
I have enabled safe mode since a few hours and haven't seen any crashes yet.
I've had the PC afk in the BIOS for a few hours and did not experience any crashes. No overclocking and never have.
Windows and my programs (except games) run on my SSD, my HDD is used for storage of large files and games.
This PSU should not have been used anywhere near a computer that had an add on video card and for the following reasons, it is not a good brand, it is not even Bronze efficiency rated, it is old/out of warranty and when independently tested when out of the box new it could only produce 552W, not good I`m afraid
This PSU should not have been used anywhere near a computer that had an add on video card and for the following reasons, it is not a good brand, it is not even Bronze efficiency rated, it is old/out of warranty and when independently tested when out of the box new it could only produce 552W, not good I`m afraid
Thank you for raising the possible issue with the powersupply. For what it is worth, I also used this PSU with the GTX 970 and got the same issues.
I've just used a calculator for the PSU requirements and got to 413W minimum and an advised wattage of >463. With the 970 this is 388 and >438.
I would say that a safety mark of +-100w should be enough for the system and as such, I would like to add that this is the standard PSU that came with the prebuild system (incl. GTX 970).
However, something could very well be broken, as that would indeed give a kernel-power error as well. I suppose testing this would have me replace the PSU by another unit and see if that would result in a crash-free experience? I'd assume that it would be advised to buy a better energy efficient one anyways, as it will save power.
Thanks again for your reply. It is most appreciated.
You should always go by what the manufacturer of the GPU recommends and then add some to allow for additional HDDs etc, PSU calculators also do not take into account old, poor quality or the efficiency rating of any PSU that a person may well use, I wouldn`t use anything less than a Gold efficiency rated PSU with a decent GPU like the one that you have.
You will get the kernel power error whenever the computer powers down before Windows has been closed properly, thermal shutdowns and loss of power are two common causes.
You should always go by what the manufacturer of the GPU recommends and then add some to allow for additional HDDs etc, PSU calculators also do not take into account old, poor quality or the efficiency rating of any PSU that a person may well use, I wouldn`t use anything less than a Gold efficiency rated PSU with a decent GPU like the one that you have.
You will get the kernel power error whenever the computer powers down before Windows has been closed properly, thermal shutdowns and loss of power are two common causes.
Yup, quite sure it isn't thermal tho as I have kept the temps on my monitor once and watched them when they crashes (low temps), wouldn't make sense with the fact of mostly idle crashing the system.
Thanks for the suggestion, ill look into getting a new PSU or at least testing the pc with another PSU. Also, I have ran chkdsk on my HDD again and till now I've not seen any crashes. Could a corrupt bit of HDD cause a kernel power event? I would not say so but wondering if this could be the cause. Would loss of power be able to freeze the windows and retain the current windows (it does not turn off/ lose data on screen) instead of turning the PC off due to lack of power?
Is there anything else you would recommend have me do/ check?
EDIT: For some reason im unable to edit my last post. PC has just crashed again dskchk therefore hasn't solved the issue. It was stable for a few hours until I started playing a game (which is saved on the HDD), giving me a clue towards the harddrive. Ill remove it tonight and see if crashing persists then.
EDIT: It might be worth noting that I'm using Windows 10 Student Edition, though this shouldn't change a lot.
Additional Drive information as it could be of importance (from system information):
All windows related files are on the SSD except the paging file, Downloads and Videos. 1 TB HDD:
Description Disk drive
Manufacturer (Standard disk drives)
Model: ST1000DM003-1CH162 (https://www.hdsentinel.com/storageinfo_details.php?lang=en&model=SEAGATE ST1000DM003)
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 4
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 931.51 GB (1,000,202,273,280 bytes)
Total Cylinders 121,601
Total Sectors 1,953,520,065
Total Tracks 31,008,255
Tracks/Cylinder 255
Partition Disk #0, Partition #0
Partition Size 450.00 MB (471,859,200 bytes)
Partition Starting Offset 1,048,576 bytes
Partition Disk #0, Partition #1
Partition Size 100.00 MB (104,857,600 bytes)
Partition Starting Offset 472,907,776 bytes
Partition Disk #0, Partition #2
Partition Size 930.13 GB (998,716,275,200 bytes)
Partition Starting Offset 594,542,592 bytes
Partition Disk #0, Partition #3
Partition Size 850.00 MB (891,289,600 bytes)
Partition Starting Offset 999,311,802,368 bytes
500 GB SSD:
Description Disk drive
Manufacturer (Standard disk drives)
Model Samsung SSD 860 EVO 500GB
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 2
SCSI Bus 1
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 465.76 GB (500,105,249,280 bytes)
Total Cylinders 60,801
Total Sectors 976,768,065
Total Tracks 15,504,255
Tracks/Cylinder 255
Partition Disk #1, Partition #0
Partition Size 549.00 MB (575,668,224 bytes)
Partition Starting Offset 1,048,576 bytes
Partition Disk #1, Partition #1
Partition Size 465.22 GB (499,530,072,064 bytes)
Partition Starting Offset 576,716,800 bytes
Software Environment/Windows Error Reporting:
19/05/25 19:53 Windows Error Reporting Fault bucket , type 0
Event Name: WinPBRDiag
Response: Not available
Cab Id: 0

Problem signature:
P1: 1
P2: X
P3: 9
P4: 0
P5: X
P6: X
P7: 17134
P8: rs4_release
P9: X
P10: X

Attached files:
\\?\C:\Windows\Panther\SetupAct.log
\\?\C:\Windows\Panther\diagerr.xml
\\?\C:\Windows\inf\setupapi.setup.log
\\?\C:\Windows\inf\setupapi.offline.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6021.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6032.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6040.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6051.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_1_6c1f9c3d3d9d3fde2e0f666f6f146c8e29f676_00000000_cab_11246050

Analysis symbol: 
Rechecking for solution: 0
Report Id: a4b055e8-bc16-4eac-a914-0922b516262c
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/05/25 19:54 Windows Error Reporting Fault bucket , type 0
Event Name: WinPBRDiag
Response: Not available
Cab Id: 0

Problem signature:
P1: 1
P2: X
P3: 9
P4: 0
P5: X
P6: X
P7: 17134
P8: rs4_release
P9: X
P10: X

Attached files:
\\?\C:\Windows\Panther\SetupAct.log
\\?\C:\Windows\Panther\diagerr.xml
\\?\C:\Windows\inf\setupapi.setup.log
\\?\C:\Windows\inf\setupapi.offline.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6021.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6032.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6040.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6051.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_1_6c1f9c3d3d9d3fde2e0f666f6f146c8e29f676_00000000_cab_11246050

Analysis symbol: 
Rechecking for solution: 0
Report Id: a4b055e8-bc16-4eac-a914-0922b516262c
Report Status: 6
Hashed bucket: 
Cab Guid: 0
19/05/25 19:57 Windows Error Reporting Fault bucket , type 0
Event Name: WinPBRDiag
Response: Not available
Cab Id: 0

Problem signature:
P1: 1
P2: X
P3: 9
P4: 0
P5: X
P6: X
P7: 17134
P8: rs4_release
P9: X
P10: X

Attached files:
\\?\C:\Windows\Panther\SetupAct.log
\\?\C:\Windows\Panther\diagerr.xml
\\?\C:\Windows\inf\setupapi.setup.log
\\?\C:\Windows\inf\setupapi.offline.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6021.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6032.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6040.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6051.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_1_6c1f9c3d3d9d3fde2e0f666f6f146c8e29f676_00000000_cab_11246050

Analysis symbol: 
Rechecking for solution: 0
Report Id: a4b055e8-bc16-4eac-a914-0922b516262c
Report Status: 6
Hashed bucket: 
Cab Guid: 0
19/05/25 20:12 Windows Error Reporting Fault bucket INVALID_REQUEST, type 0
Event Name: WinPBRDiag
Response: Not available
Cab Id: 0

Problem signature:
P1: 1
P2: X
P3: 9
P4: 0
P5: X
P6: X
P7: 17134
P8: rs4_release
P9: X
P10: X

Attached files:
\\?\C:\Windows\Panther\SetupAct.log
\\?\C:\Windows\Panther\diagerr.xml
\\?\C:\Windows\inf\setupapi.setup.log
\\?\C:\Windows\inf\setupapi.offline.log
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6021.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6032.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6040.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6051.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_6c1f9c3d3d9d3fde2e0f666f6f146c8e29f676_00000000_1ee95d30

Analysis symbol: 
Rechecking for solution: 0
Report Id: a4b055e8-bc16-4eac-a914-0922b516262c
Report Status: 268435462
Hashed bucket: 
Cab Guid: 0
19/05/25 20:42 Application Error Faulting application name: TBPanel.exe, version: 10.4.0.0, time stamp: 0x59bbad47
Faulting module name: TBPanel.exe, version: 10.4.0.0, time stamp: 0x59bbad47
Exception code: 0xc0000094
Fault offset: 0x00041754
Faulting process id: 0x2af4
Faulting application start time: 0x01d5133a653ee10f
Faulting application path: C:\Program Files (x86)\EXPERTool\TBPanel.exe
Faulting module path: C:\Program Files (x86)\EXPERTool\TBPanel.exe
Report Id: 5a13fb17-c87e-4ea3-8af2-9eeec5f1ff88
Faulting package full name: 
Faulting package-relative application ID:
19/05/25 20:42 Application Error Faulting application name: TBPanel.exe, version: 10.4.0.0, time stamp: 0x59bbad47
Faulting module name: TBPanel.exe, version: 10.4.0.0, time stamp: 0x59bbad47
Exception code: 0xc0000094
Fault offset: 0x00041754
Faulting process id: 0x2fc0
Faulting application start time: 0x01d5133a5a3274da
Faulting application path: C:\Program Files (x86)\EXPERTool\TBPanel.exe
Faulting module path: C:\Program Files (x86)\EXPERTool\TBPanel.exe
Report Id: c132be63-613c-4c2b-8948-74b57a523792
Faulting package full name: 
Faulting package-relative application ID:
19/05/25 20:42 Windows Error Reporting Fault bucket 1818605922070592140, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: TBPanel.exe
P2: 10.4.0.0
P3: 59bbad47
P4: TBPanel.exe
P5: 10.4.0.0
P6: 59bbad47
P7: c0000094
P8: 00041754
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3C0.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF44E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF46E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF48E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TBPanel.exe_f2f9f1eac9ddecaaa108815c3ce6a3872526d_76e97210_1270f883

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5a13fb17-c87e-4ea3-8af2-9eeec5f1ff88
Report Status: 268435456
Hashed bucket: ec2b2d0fb9e0ad8fa93cfc7363707a8c
Cab Guid: 0
19/05/25 20:42 Windows Error Reporting Fault bucket 1818605922070592140, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: TBPanel.exe
P2: 10.4.0.0
P3: 59bbad47
P4: TBPanel.exe
P5: 10.4.0.0
P6: 59bbad47
P7: c0000094
P8: 00041754
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD03.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADAF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADD0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADCE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERADFE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TBPanel.exe_f2f9f1eac9ddecaaa108815c3ce6a3872526d_76e97210_170cb407

Analysis symbol: 
Rechecking for solution: 0
Report Id: c132be63-613c-4c2b-8948-74b57a523792
Report Status: 268435456
Hashed bucket: ec2b2d0fb9e0ad8fa93cfc7363707a8c
Cab Guid: 0
19/05/25 20:47 Application Error Faulting application name: mbamtray.exe, version: 3.1.0.1807, time stamp: 0x5cc0b4e2
Faulting module name: Qt5Core.dll, version: 5.11.1.0, time stamp: 0x5cba0161
Exception code: 0xc0000005
Fault offset: 0x0018dc19
Faulting process id: 0x16a0
Faulting application start time: 0x01d5133afe70aa49
Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe
Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll
Report Id: 64e9ee18-73e0-483e-bc74-6ebc303d183b
Faulting package full name: 
Faulting package-relative application ID:
19/05/25 20:47 Windows Error Reporting Fault bucket 1505372194176755521, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: mbamtray.exe
P2: 3.1.0.1807
P3: 5cc0b4e2
P4: Qt5Core.dll
P5: 5.11.1.0
P6: 5cba0161
P7: c0000005
P8: 0018dc19
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CC6.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mbamtray.exe_40eeb6dfb6343d612b691e093979076daa2547a_2c67c329_17486c85

Analysis symbol: 
Rechecking for solution: 0
Report Id: 64e9ee18-73e0-483e-bc74-6ebc303d183b
Report Status: 268435456
Hashed bucket: 0b3b3ff5fb361ac874e42808e8a7e741
Cab Guid: 0
19/05/25 20:47 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: mbamtray.exe
P2: 3.1.0.1807
P3: 5cc0b4e2
P4: Qt5Core.dll
P5: 5.11.1.0
P6: 5cba0161
P7: c0000005
P8: 0018dc19
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_mbamtray.exe_40eeb6dfb6343d612b691e093979076daa2547a_2c67c329_1d4c5832

Analysis symbol: 
Rechecking for solution: 0
Report Id: 64e9ee18-73e0-483e-bc74-6ebc303d183b
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/05/25 21:16 Windows Error Reporting Fault bucket 2033848167598686498, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: witcher3.exe
P2: 3.0.19.14337
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDRA4C8.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4C9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4E9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA506.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA527.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 69320645-36c6-4ed8-8314-9092341895e5
Report Status: 268435456
Hashed bucket: 9ab9748427bcc5781c39ae21f4cc8122
Cab Guid: 0
19/05/25 21:25 Application Error Faulting application name: Discord.exe, version: 0.0.305.0, time stamp: 0x5c8190a4
Faulting module name: Discord.exe, version: 0.0.305.0, time stamp: 0x5c8190a4
Exception code: 0xc0000005
Fault offset: 0x0007da36
Faulting process id: 0x28d0
Faulting application start time: 0x01d5134047e2bdf4
Faulting application path: C:\Users\Stijn\AppData\Local\Discord\app-0.0.305\Discord.exe
Faulting module path: C:\Users\Stijn\AppData\Local\Discord\app-0.0.305\Discord.exe
Report Id: e2851af4-0f6a-4e92-96b6-68825b0737f3
Faulting package full name: 
Faulting package-relative application ID:
19/05/25 21:25 Windows Error Reporting Fault bucket 1692373355569516288, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Discord.exe
P2: 0.0.305.0
P3: 5c8190a4
P4: Discord.exe
P5: 0.0.305.0
P6: 5c8190a4
P7: c0000005
P8: 0007da36
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFD99.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF6F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF8F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF8D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFFAE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Discord.exe_627a6710fe8d2f956f15aa10d6ee9f9d3296d2_8d23bdb2_2a550375

Analysis symbol: 
Rechecking for solution: 0
Report Id: e2851af4-0f6a-4e92-96b6-68825b0737f3
Report Status: 268435456
Hashed bucket: 303e7942c5bf3c19a77c8499ae0e8f00
Cab Guid: 0
19/05/25 22:30 Windows Error Reporting Fault bucket 1162527887693842388, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem signature:
P1: steamwebhelper.exe
P2: 5.5.99.96
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDR975A.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER975B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97CA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9883.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER994F.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 0de08344-6069-416f-a433-ac68ef0a11f2
Report Status: 268435456
Hashed bucket: b231840ad87a7cef802220f45b7a07d4
Cab Guid: 0
19/05/25 23:55 Windows Error Reporting Fault bucket 2284205016968472552, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeCP.exe
P2: 11.0.17134.765
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDR5846.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5856.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5867.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5891.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER58B1.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: b0f24d97-971d-42ef-882c-20d43c19a49f
Report Status: 268435456
Hashed bucket: 43fc720ba2d730af5fb3205c569227e8
Cab Guid: 0
19/05/26 00:05 Windows Error Reporting Fault bucket 1398403670248554359, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: 3DMarkICFDemo.exe
P2: 1.1.0.0
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDR8038.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8039.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8049.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8060.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8071.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: a0f30ae8-51bd-4411-af03-9bd6ccc72f63
Report Status: 268435456
Hashed bucket: 7d1456b0d2be4df1336820baa1c47f77
Cab Guid: 0
19/05/26 00:10 Windows Error Reporting Fault bucket 1773249858782635763, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: 3DMarkICFWorkload.exe
P2: 1.1.0.0
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDR141B.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER141C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER141D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1431.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1451.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: bb78c93d-439d-4e4b-8cb7-58588cd55409
Report Status: 268435456
Hashed bucket: 055aa074c8e0dc6f889bd959fac026f3
Cab Guid: 0
19/05/26 00:24 Windows Error Reporting Fault bucket 433345071, type 5
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
P1: 4097
P2: Manual
P3: Immediate
P4: Pass
P5: Standard
P6: 0
P7: 0
P8: 270
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER444C.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_4097_27bcd6ca58e6916c31aca37c7d0f5835e938a6_00000000_1b14511d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5e100576-1cfa-462b-94e7-313c2555e524
Report Status: 268435552
Hashed bucket: e57e894642bf06ea8e18c91396352803
Cab Guid: 0
19/05/26 00:24 Windows Error Reporting Fault bucket , type 0
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
P1: 4097
P2: Manual
P3: Immediate
P4: Pass
P5: Standard
P6: 0
P7: 0
P8: 270
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_4097_27bcd6ca58e6916c31aca37c7d0f5835e938a6_00000000_17cc4333

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5e100576-1cfa-462b-94e7-313c2555e524
Report Status: 100
Hashed bucket: 
Cab Guid: 0
19/05/26 00:38 Windows Error Reporting Fault bucket 1381970814187616849, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: eurotrucks2.exe
P2: 1.34.0.17
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDRDBE9.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBEA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBFB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC18.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC38.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 827467f0-47bd-4d07-8740-455140037f3d
Report Status: 268435456
Hashed bucket: 041a846411448e3d932dbf222d9c3a51
Cab Guid: 0
19/05/26 00:40 Windows Error Reporting Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.753
P2: 80073d02
P3: 99ABA0D3-B75E-4AAA-B66B-ADE9E597D686
P4: Install
P5: 1
P6: 0
P7: 0
P8: Update;ScanForUpdates
P9: {855E8A7C-ECB4-4CA3-B045-1DFA50104289}
P10: 0

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE0B7.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_10.0.17134.753_2794cae9a3fb9c5e2a8cd4489d979cae05a353e_00000000_0d7ae52b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 696ad5e8-09c2-4388-870d-c0728d807014
Report Status: 2147491840
Hashed bucket: 
Cab Guid: 0
19/05/26 00:40 Windows Error Reporting Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.753
P2: 80073d02
P3: 99ABA0D3-B75E-4AAA-B66B-ADE9E597D686
P4: Install
P5: 1
P6: 0
P7: 0
P8: Update;ScanForUpdates
P9: {855E8A7C-ECB4-4CA3-B045-1DFA50104289}
P10: 0

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_10.0.17134.753_2794cae9a3fb9c5e2a8cd4489d979cae05a353e_00000000_2cfae088

Analysis symbol: 
Rechecking for solution: 0
Report Id: 696ad5e8-09c2-4388-870d-c0728d807014
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/05/26 00:40 Windows Error Reporting Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.753
P2: 80073d02
P3: 99ABA0D3-B75E-4AAA-B66B-ADE9E597D686
P4: Install
P5: 1
P6: 0
P7: 0
P8: Update;ScanForUpdates
P9: {855E8A7C-ECB4-4CA3-B045-1DFA50104289}
P10: 0

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 696ad5e8-09c2-4388-870d-c0728d807014
Report Status: 1074003968
Hashed bucket: 
Cab Guid: 0
19/05/26 13:20 Windows Error Reporting Fault bucket 1998207031659061142, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Cities.exe
P2: 5.6.7.3267
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\Stijn\AppData\Local\Temp\RDRE281.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE282.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2A2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2DE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE30E.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 5060615b-153c-4c54-ae3f-16dfbacd57cd
Report Status: 268435456
Hashed bucket: d55b05ae8a807a5f4bbb0eb555b9df96
Cab Guid: 0
19/05/26 20:59 Application Error Faulting application name: mbamservice.exe, version: 3.2.0.765, time stamp: 0x5c508d96
Faulting module name: MBAMCore.dll, version: 3.0.0.767, time stamp: 0x5c7d3d3a
Exception code: 0xc0000005
Fault offset: 0x000000000001f266
Faulting process id: 0xeac
Faulting application start time: 0x01d513ff12f93d03
Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe
Faulting module path: C:\PROGRAM FILES\MALWAREBYTES\ANTI-MALWARE\MBAMCore.dll
Report Id: efa3c1cb-91d2-43cc-8af2-9d89b771ce15
Faulting package full name: 
Faulting package-relative application ID:
19/05/26 20:59 Windows Error Reporting Fault bucket 1628233584017260462, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: mbamservice.exe
P2: 3.2.0.765
P3: 5c508d96
P4: MBAMCore.dll
P5: 3.0.0.767
P6: 5c7d3d3a
P7: c0000005
P8: 000000000001f266
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E94.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mbamservice.exe_74dabf5682672c672812566aaaea139d085e426_59b03392_0aa02b36

Analysis symbol: 
Rechecking for solution: 0
Report Id: efa3c1cb-91d2-43cc-8af2-9d89b771ce15
Report Status: 268435456
Hashed bucket: 440c3c772c701d67d698a5d162b5bfae
Cab Guid: 0
19/05/26 20:59 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: mbamservice.exe
P2: 3.2.0.765
P3: 5c508d96
P4: MBAMCore.dll
P5: 3.0.0.767
P6: 5c7d3d3a
P7: c0000005
P8: 000000000001f266
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_mbamservice.exe_74dabf5682672c672812566aaaea139d085e426_59b03392_10fc9256

Analysis symbol: 
Rechecking for solution: 0
Report Id: efa3c1cb-91d2-43cc-8af2-9d89b771ce15
Report Status: 4
Hashed bucket: 
Cab Guid: 0
19/05/26 22:47 Application Error Faulting application name: ctfmon.exe, version: 10.0.17134.1, time stamp: 0x0ac88d37
Faulting module name: InputService.dll, version: 10.0.17134.319, time stamp: 0x9c86695f
Exception code: 0x00000675
Fault offset: 0x00000000000795fe
Faulting process id: 0xb10
Faulting application start time: 0x01d51411b3abe41c
Faulting application path: C:\WINDOWS\system32\ctfmon.exe
Faulting module path: C:\WINDOWS\system32\InputService.dll
Report Id: d20e2ccf-f8e9-46c2-a4e2-afdbb1136161
Faulting package full name: 
Faulting package-relative application ID:
19/05/26 22:47 Windows Error Reporting Fault bucket 1206816424109801294, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ctfmon.exe
P2: 10.0.17134.1
P3: 0ac88d37
P4: InputService.dll
P5: 10.0.17134.319
P6: 9c86695f
P7: 00000675
P8: 00000000000795fe
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9544.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95E2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9611.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER960F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9630.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ctfmon.exe_569118a7d9e3441050af1f31d920c0213079c8be_b6283c8f_200998fd

Analysis symbol: 
Rechecking for solution: 0
Report Id: d20e2ccf-f8e9-46c2-a4e2-afdbb1136161
Report Status: 268435456
Hashed bucket: 746154d26abd9264f0bf7924cc2bff4e
Cab Guid: 0
19/05/27 14:09 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 193
P2: 80b
P3: 0
P4: 0
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190527-1609.dmp
\\?\C:\WINDOWS\TEMP\WER-640921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE562.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE583.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE582.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE592.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_9ca3165d63e5a63de86d269f9c7e6e94a1fb72_00000000_cab_1fcde5ff

Analysis symbol: 
Rechecking for solution: 0
Report Id: 66f24d0c-7245-4489-bbcc-e9ef820551b9
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
19/05/27 14:09 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 193
P2: 80b
P3: 0
P4: 0
P5: 0
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190527-1609.dmp
\\?\C:\WINDOWS\TEMP\WER-640921-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE562.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE583.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE582.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE592.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_9ca3165d63e5a63de86d269f9c7e6e94a1fb72_00000000_1d69e591

Analysis symbol: 
Rechecking for solution: 0
Report Id: 66f24d0c-7245-4489-bbcc-e9ef820551b9
Report Status: 4
Hashed bucket: 
Cab Guid: 0
Yup, quite sure it isn't thermal tho as I have kept the temps on my monitor once and watched them when they crashes (low temps), wouldn't make sense with the fact of mostly idle crashing the system.
Are you not aware that modern PSUs have safe internal operating temperatures, over temperature protection (OTP) the safe operating temperature of your PSU is 40ºC and once it reaches that it will shut down to prevent it from going on fire, there is no means of a motherboard monitoring the PSUs OTP and unfortunately the older and poorer the quality of a PSU the hotter they get.
For clarity, Windows crashes and when enabled a crash dmp will be generated, a computer that shuts down due to overheating is not described as having crashed as overheating is not Windows related and no crash dmp will be generated, the kernel power error as previously mentioned is only telling you that Windows was not shut down correct;y.
Are you not aware that modern PSUs have safe internal operating temperatures, over temperature protection (OTP) the safe operating temperature of your PSU is 40ºC and once it reaches that it will shut down to prevent it from going on fire, there is no means of a motherboard monitoring the PSUs OTP and unfortunately the older and poorer the quality of a PSU the hotter they get.
For clarity, Windows crashes and when enabled a crash dmp will be generated, a computer that shuts down due to overheating is not described as having crashed as overheating is not Windows related and no crash dmp will be generated, the kernel power error as previously mentioned is only telling you that Windows was not shut down correct;y.
But shutting the pc down sounds like the current display image would be lost, which is not the case. I keep seeing the same image as before, showing that power isn't cut. Thanks for explaining the problem at hand. I will get a new PSU.
Not entirely sure what you mean by this.but if you are referring to "The displays retain the same image," info from your OP, overheating causing the system to lock up can cause the video to also freeze and the audio quite often changing to a horrible buzzing sound or looping.
Please note that using a poor quality PSU over a period of time can damage one or more components and it is recommended if at all possible to either have an existing PSU properly tested under load or to swap in an appropriately and adequately powered PSU for testing purposes.
Not entirely sure what you mean by this.but if you are referring to "The displays retain the same image," info from your OP, overheating causing the system to lock up can cause the video to also freeze and the audio quite often changing to a horrible buzzing sound or looping.
Please note that using a poor quality PSU over a period of time can damage one or more components and it is recommended if at all possible to either have an existing PSU properly tested under load or to swap in an appropriately and adequately powered PSU for testing purposes.
This is looking like a power supply issue as Phil stated so I would start with swapping out the PSU with a known good quality brand for testing purposes and see if the crashes continue.
If you need a PSU recommendation you can let us know.