Windows 10: Multiple BSOD on home brew PC - Unexpected_Kernel_Mode_Trap most often

I agree philc43, that mismatched memory may be the problem... although it's taken me much longer to realise it. As posted earlier, I have removed the recently added 8GB memory and have run Memtest86+ again but this time for 9 passes, with no errors.

As I mentioned to zbook, I believe most of the multiple BSODs have gone, but I still have the occasional one. In fact I had two UNEXPECTED_KERNEL_MODE_TRAP this evening. And the info I have from BlueScreenView is that it was the ntoskrnl.exe driver, which from what I have researched is only the messenger, not the real culprit.

Anyway I will keep working to try and find out what's causing these crashes. But it's fair to say that thanks to zbook, I no longer have multiple BSODs and will therefore wait at least 24hours before marking this thread as resolved.

I've included the memtest results and the latest log.
cheers,

 

There were 2 BSOD mini dump files debugged that did not display a definitive misbehaving driver.

1) For the next BSOD please run the DM log collector and also find the memory dump:
Sometimes this file can be large.
C:\windows\memory.dmp

2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread


3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

4) Please update the progress with tests /steps in post #3: Prime95 test images, max temp, test duration, images of HD Tune health, benchmark, full error scan, and chkdsk /x /f /r testing.



Code: Event[16445]: Log Name: System Source: volmgr Date: 2018-01-06T00:35:18.952 Event ID: 49 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ROB64-AMD Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.[/quote] Code: 5/01/2018 10:39 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80225006370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-28109-01.dmp \\?\C:\WINDOWS\TEMP\WER-350093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA4E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCCFD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD8C6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_c0601687d9d722d65a42efe69dcaed02a51_00000000_cab_02f0dc7e Analysis symbol: Rechecking for solution: 0 Report ID: 9d13bc0a-6270-4648-84a3-8b1579ae5d33 Report Status: 4 Hashed bucket:3/01/2018 1:41 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8038e47f370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-59453-01.dmp \\?\C:\WINDOWS\TEMP\WER-750281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF955.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA31.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER389.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_d123599f1f42ec90575b71554f1fa81239537ca_00000000_cab_031a048f Analysis symbol: Rechecking for solution: 0 Report ID: 12797491-4be7-4c67-8b33-1f61858da205 Report Status: 100 Hashed bucket:2/01/2018 1:02 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8038e47f370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-59453-01.dmp \\?\C:\WINDOWS\TEMP\WER-750281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF955.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA31.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER389.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_d123599f1f42ec90575b71554f1fa81239537ca_00000000_cab_031a048f Analysis symbol: Rechecking for solution: 0 Report ID: 12797491-4be7-4c67-8b33-1f61858da205 Report Status: 4 Hashed bucket:6/01/2018 7:18 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: ffff8400d5769ef0 P4: ffff828038750fe0 P5: fffff802db8df213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010618-41953-01.dmp \\?\C:\WINDOWS\TEMP\WER-370312-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB4B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_38854cf4ee9253c3b2a3a36263095d6d573124d_00000000_cab_02fb0be4 Analysis symbol: Rechecking for solution: 0 Report ID: 0d510f74-1dbc-4afe-a6c2-d8893008c319 Report Status: 4 Hashed bucket:4/01/2018 8:48 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: ffffc680d41689b0 P4: ffff9d85f3ecbff0 P5: fffff800c2fa7187 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-53078-01.dmp \\?\C:\WINDOWS\TEMP\WER-793984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DCD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5715.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_54f2ef7d5298e46772c87b81e33dca5fa95574_00000000_cab_031257ef Analysis symbol: Rechecking for solution: 0 Report ID: 8c096fb2-c74a-4311-bada-dc6c496ab940 Report Status: 4 Hashed bucket:1/01/2018 7:08 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: fffff801ed66ce70 P4: ffffbb83e39ac000 P5: fffff801eb590213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-53781-01.dmp \\?\C:\WINDOWS\TEMP\WER-311187-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E94.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER304A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34B0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_ab576f2eab1c395581314b8485538ac36b43fa_00000000_cab_034e354b Analysis symbol: Rechecking for solution: 0 Report ID: c7e231d4-d813-406a-bb72-8991f158a5b4 Report Status: 4 Hashed bucket:6/01/2018 8:48 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: fffff8031446de70 P4: ffffeb06e9996fe0 P5: fffff803122e3213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010618-29203-01.dmp \\?\C:\WINDOWS\TEMP\WER-123984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B6B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F92.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_908627e717c66b65374ce39d2cb59406a9b3170_00000000_cab_0307802d Analysis symbol: Rechecking for solution: 0 Report ID: edd9b127-a155-40a2-8896-d1457f0ea922 Report Status: 4 Hashed bucket:4/01/2018 4:47 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 7f P2: 8 P3: fffff8032826ce70 P4: ffff9d05c8318ff0 P5: fffff803260eab4d P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010418-45296-01.dmp \\?\C:\WINDOWS\TEMP\WER-914734-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD583.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD651.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD38.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_63c9317f9312bcc5c7bcd14d5050d59bff2a3f7c_00000000_cab_036cddee Analysis symbol: Rechecking for solution: 0 Report ID: 2a7778a3-17c0-487b-81f0-41507dd20347 Report Status: 4 Hashed bucket:3/01/2018 2:07 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 8fedb97c-56bf-4be1-baf0-0c8021e10258 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8038e47f370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-59453-01.dmp \\?\C:\WINDOWS\TEMP\WER-750281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF955.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA31.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER389.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_d123599f1f42ec90575b71554f1fa81239537ca_00000000_cab_031a048f Analysis symbol: Rechecking for solution: 0 Report ID: 12797491-4be7-4c67-8b33-1f61858da205 Report Status: 100 Hashed bucket:[/quote] Code: 3/01/2018 2:34 AM Windows Error Reporting Fault bucket 0x133_VRF_ISR_athw10x!readPlatformRegOnce, type 0 Event Name: BlueScreen Response: Not available Cab Id: 8fedb97c-56bf-4be1-baf0-0c8021e10258 Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff8038e47f370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-59453-01.dmp \\?\C:\WINDOWS\TEMP\WER-750281-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF955.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFA31.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER389.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_d123599f1f42ec90575b71554f1fa81239537ca_00000000_cab_0a6f0fc7 Analysis symbol: Rechecking for solution: 0 Report ID: 12797491-4be7-4c67-8b33-1f61858da205 Report Status: 268435556 Hashed bucket:5/01/2018 10:42 AM Windows Error Reporting Fault bucket 0x133_VRF_ISR_athw10x!readPlatformRegOnce, type 0 Event Name: BlueScreen Response: Not available Cab Id: 94978623-0665-4da1-a6f8-de17b705390a Problem signature: P1: 133 P2: 1 P3: 1e00 P4: fffff80225006370 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-28109-01.dmp \\?\C:\WINDOWS\TEMP\WER-350093-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA4E.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCCFD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD8C6.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_c0601687d9d722d65a42efe69dcaed02a51_00000000_cab_1f0c4b37 Analysis symbol: Rechecking for solution: 0 Report ID: 9d13bc0a-6270-4648-84a3-8b1579ae5d33 Report Status: 268435456 Hashed bucket:6/01/2018 7:19 AM Windows Error Reporting Fault bucket 0x7f_8_STACK_USAGE_RECURSION, type 0 Event Name: BlueScreen Response: Not available Cab Id: 6064611f-5712-4a85-a3c6-63f512690abb Problem signature: P1: 7f P2: 8 P3: ffff8400d5769ef0 P4: ffff828038750fe0 P5: fffff802db8df213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010618-41953-01.dmp \\?\C:\WINDOWS\TEMP\WER-370312-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB4B.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_38854cf4ee9253c3b2a3a36263095d6d573124d_00000000_cab_0f5b513a Analysis symbol: Rechecking for solution: 0 Report ID: 0d510f74-1dbc-4afe-a6c2-d8893008c319 Report Status: 268435456 Hashed bucket:6/01/2018 8:48 AM Windows Error Reporting Fault bucket 0x7f_8_STACK_USAGE_RECURSION, type 0 Event Name: BlueScreen Response: Not available Cab Id: c66014f4-b649-4f13-969c-9573410a3227 Problem signature: P1: 7f P2: 8 P3: fffff8031446de70 P4: ffffeb06e9996fe0 P5: fffff803122e3213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010618-29203-01.dmp \\?\C:\WINDOWS\TEMP\WER-123984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER79A6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B6B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F92.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_908627e717c66b65374ce39d2cb59406a9b3170_00000000_cab_0ab7bdf2 Analysis symbol: Rechecking for solution: 0 Report ID: edd9b127-a155-40a2-8896-d1457f0ea922 Report Status: 268435456 Hashed bucket:4/01/2018 4:47 AM Windows Error Reporting Fault bucket 0x7f_8_STACK_USAGE_RECURSION, type 0 Event Name: BlueScreen Response: Not available Cab Id: c90782f3-2dab-4c95-9ae9-b07f270355ff Problem signature: P1: 7f P2: 8 P3: fffff8032826ce70 P4: ffff9d05c8318ff0 P5: fffff803260eab4d P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010418-45296-01.dmp \\?\C:\WINDOWS\TEMP\WER-914734-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD583.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD651.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD38.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_63c9317f9312bcc5c7bcd14d5050d59bff2a3f7c_00000000_cab_0cb932b5 Analysis symbol: Rechecking for solution: 0 Report ID: 2a7778a3-17c0-487b-81f0-41507dd20347 Report Status: 268435456 Hashed bucket:1/01/2018 11:18 AM Windows Error Reporting Fault bucket 0x7f_8_STACK_USAGE_RECURSION, type 0 Event Name: BlueScreen Response: Not available Cab Id: ca2f7b29-a3dc-4fc9-a568-10170f6592e6 Problem signature: P1: 7f P2: 8 P3: fffff801ed66ce70 P4: ffffbb83e39ac000 P5: fffff801eb590213 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-53781-01.dmp \\?\C:\WINDOWS\TEMP\WER-311187-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E94.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER304A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34B0.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_ab576f2eab1c395581314b8485538ac36b43fa_00000000_cab_0ffdeeef Analysis symbol: Rechecking for solution: 0 Report ID: c7e231d4-d813-406a-bb72-8991f158a5b4 Report Status: 268435456 Hashed bucket:4/01/2018 8:48 PM Windows Error Reporting Fault bucket 0x7f_8_VRF_partmgr!PartitionIo, type 0 Event Name: BlueScreen Response: Not available Cab Id: da442ead-9152-4779-868a-99e176dfa855 Problem signature: P1: 7f P2: 8 P3: ffffc680d41689b0 P4: ffff9d85f3ecbff0 P5: fffff800c2fa7187 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010518-53078-01.dmp \\?\C:\WINDOWS\TEMP\WER-793984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DCD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FE1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5715.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_54f2ef7d5298e46772c87b81e33dca5fa95574_00000000_cab_0552b4a6 Analysis symbol: Rechecking for solution: 0 Report ID: 8c096fb2-c74a-4311-bada-dc6c496ab940 Report Status: 268435456 Hashed bucket:[/quote]

 

Hi zbook,
I think we have a real breakthrough. Thanks for pushing me with longer tests. I must admit I've put some of them off because either the time involved or that I need to be in front of the PC monitoring the temp etc.

Anyway, I've completed all the chkdsk tests and used chkdsk /x /f /r on all but the SSD where I limited it to /f. The Storage Spaces confused me as although I have twin 2TB drives, it didn't test them individually, but gave me a pass for the Storage Spaces.

The most surprising part was when I tested the SSD system drive. Although it was a clone of the original 500GB HDD, it came up with a massive number of file errors. I have taken pics and as best I could tried to name them correctly but I may have misnamed some. When I tested the original HDD, it had some errors but nothing like the SSD
I am now giving my PC a heavy workout to see if a BSOD occurs. So far for the last 14 hours, all is good.

I've attached some of the pics and can submit more if you think something is missing. I maybe an optimist, but I'm feeling pretty confident.

 

Nice progress.
For the drive file structure there were errors corrected in the MFT and volume Bitmap.
When available please post 3 images of each drive using HD Tune:
Health (SMART)
Benchmark
Full error scan

 

Hi Zbook,
I'm pleased to report that I haven't had a BSOD for at least 48hrs of virtually continuous use. *Biggrin

I have completed Health and Benchmark scans on the drives and at this stage only quick Error Checking. I started the full error checking on one drive and I estimate it will take around 6+ hours to complete each drive. I will this progressively over the next couple of days as I need to catch up on stuff on my PC now that it's more stable.

The quick scan show all green for all drives.

I will now mark this thread as resolved but will post the results of the detail scans wheb I have them./
Thanks,

 

That's great news.
Wondering what happened with the WHEA errors.
Run this log collector and post a zip into the thread:
log collector v2-beta06.zip

 

Hi zbook,
I've run the log collector and it's attached. I should point out that I can't leave well enough alone and at least a day ago, I added back the 2nd 8GB DDR4 memory and set the clock speed to 2400. *Redface

I have only run 3.5 passes of memtest+ on this combination but with no errors. Also system is still stable. All still seems to be good but I'm noting what I change if something should occur and from what I learnt over the past week or so, I now use Restore Points and the Apps you identified.

Please let me know if the log shows something requiring attention. PS what app do I need to view the Log?
regards & thanks

 

Hi zbook,

I agree that the RAM different part numbers but since adding the 2nd memory I've been monitoring for any adverse changes, with nothing to report yet. I will run a full many pass Memtest on both banks as soon as I can. I'm prepared to scrap the 2nd 8GB ram if any problems occur and will then look at the benefits of adding additional Ram over 8GB.

As suggested, I have now completely removed DriverMax and rely on Windows etc. to update drivers (Fingers crossed)

As for the Dumps and WHEA, I have not intentionally done any cleaning. Although I have CCleaner installed, I don't use it, even when it says there is some cleaning it can do. I've attached the info as requested.
cheers,

 

See post #3 step #15.
See post #11 > top paragraph.
How come these steps were not done when posted?

For Ccleaner:
a) un-check memory dumps
b) un-check Windows log files

For system failure > write debugging information
a) change to automatic memory dump

When you complete the above steps > post images into the thread displaying the changes.
When available please post the images of the Memtest86+ version 5.01 test for 8 or more passes.

On post #3 report the progress with each step.

Post a zip after all of the above changes and if there are any new BSOD:
log collector v2-beta06.zip

 

Well I suppose I'm just a mere mortal and may have somehow lost sight of this request amongst the 31 requested!

I have freely admitted all along that when it comes to the stuff we have been dealing with that I'm definitely a Pleb. I suppose if I wasn't, then maybe I wouldn't be asking help from this forum.

For instance I mentioned that I haven't used or even installed CCleaner before this thread... I didn't expect it to clean my system without permission.. but in this regard, I'm a Newby otherwise maybe it should have been obvious to me. I have now made the changes recommended and these are attached. I will be uninstalling CCleaner as soon as I finish this post.

I said I would do a 8+ pass of Memtest+ and will do so when time permits. If in the meantime if get a BSOD, I will remove the 2nd DDR4 immediately.

At this stage I do not have the time or inclination to provide you with documentary evidence of action on post #3. I have done my best to complete these and I really do appreciate you assistance, but if something wasn't completed or missing, then I would expect you would have told me.

Otherwise, why am I doing all these 31 steps if you are not monitoring the outcome?

Thanks for your excellent help and have a good day

 

Hello Rob,

There is no requirement that you have to follow every single piece of advice you are given here - you are free to make your own mind up and do what you are comfortable with. Analysts will sometimes insist on certain items but they should make it clear when this is required. In this case I think you have found the most probably causes (drivers and mismatched memory) for your original BSOD. Your approach to test this out is quite valid. Memtest86+ may not show up any errors associated with mismatched memory and it will only be by using the system that any problems will manifest themselves.

You asked about how to read the crash dump files. I will point you to an excellent tutorial here:
WinDBG - The Basics for Debugging Crash Dumps in Windows 10

 

Thanks philac43,
what you wrote makes sense. I suppose I over reacted a little earlier as I really do appreciate the help I have received. I will check out the tutorial.
cheers,
Rob

 

Hi zbook and philc43,
thanks heaps with your help and support with fixing my PC. I have now decided to remove the mismatched memory as I believe it is still the cause of some instability. All seems OK without.

I will now research to see if there is any great benefit in increasing the RAM above 8GB, giving I;m using a dedicated Graphics. Also my next goal is to understand more generally about BSODs.
cheers,
Rob