Multiple BSOD on home brew PC - Unexpected_Kernel_Mode_Trap most often

If you had not used Ccleaner you can uninstall it.
If you like it you can continue to use it.
Unknowingly many OP may check boxes that clean files that are needed for troubleshooting.
Please uncheck: memory dumps and Windows log files.
Only use the Windows and applications tabs.
Don't clean the registry. For long periods of time you may be able to clean the registry then all of a sudden there are major problems needing clean install or backup image.
So don't clean the registry unless there is a significant problem that needs to be fixed and in those case make sure that you have made an updated backup image.


Bugcheck 7F on Mon Jan 1 06:17:15.986 2018 debugging displayed misbehaving driver ambakdrv.sys Aomei BackUpper driver. This driver should have already been troubleshooted. This is a recurrent driver BSOD. Can you uninstall this driver?

Bugcheck 133 on Tue Jan 2 03:57:50.530 2018 debugging displayed misbehaving driver athw10x.sys Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
Updating a driver: Updating a driver. - Microsoft Community


What is your progress with:
a) backing up files
b) making a backup image with Macrium
c) creating a brand new restore point?

athw10x.sys

Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter

Official site: http://www.qualcomm.com/drivers Unofficial site: https://www.ath-drivers.eu

ambakdrv.sys

Aomei BackUpper driver

http://www.aomeitech.com/download.html

Code:

athr Qualcomm Atheros Exten Qualcomm Atheros Exten Kernel Manual Running OK TRUE FALSE 0 3,608,576 0          2/08/2017 2:29:50 PM C:\WINDOWS\system32\drivers\athw10x.sys 8,192

Code:

athw10x  athw10x.sys  Tue Aug 01 23:29:50 2017 (5981553E)

Happy New Year.

b) I have created backup image with Macrium and have also set up a schedule for future backups.

a) I have been using File History and I have "Storage Spaces" using currently 2 new WDC 2TB HDDs. These are where my libraries are located (i.e. in E: not C: )

c) I'm not sure whether I correctly understand about "creating a brand new restore point". I have been making restore points quite frequently e.g. deleting apps etc. Is this the same?

I did a search for ambackdrv.sys and found a couple of older copies and these have been deleted.

My PC is definitely becoming more stable with your assistance, again I thank you. I also noticed in one of the HDD tests that my HDD C: had quite a number of CRC errors and suggested it may be a cable fault. I changed the cable and used a different socket.. but have now reverted to the SSD after checking it's health etc.

I have only had 2 BSOD in over 24 hrs. both were the unexpected kernel etc. and both appeared to occur when the system was on the login screen.

I have also noticed that Sytem Interrupts are close if not 100% of CPU when my PC initially sets up after login (see pic) then drops pretty quickly to ~2-5% . Before you started helping me, this would stay around ~35% -60% .

I have now updated my BIOS to the latest version and Windows advises the Qualcomm Driver is the most suitable.

The link for Drivers etc for the ASUS PRIME B350-PRIME Motherboard is:PRIME B350-PLUS Driver & Tools| Motherboards | ASUS Australia


Finally I like how quickly you are able to see the culprit causing a BSOD. Is this some app I can get?

I've included additional stuff below and I'm thinking that in the spirit of the Forum and depending on your advice on the latest info, I should treat this thread as Resolved as I don't appear to be having multple BSODs anymore. However, I wait for your input.

The latest BSOD implicated memory.

For every test there are:
True positives..........................................................The test results indicate it found a problem and there really was a problem.
True negatives........................................................The test results indicate it found no problems and there really were no problems.
False positives........................................................The test results indicate it found a problem and there really were no problems.
False negatives......................................................The test results indicates it found no problems and there really were problems.
Accuracy..................................................................A mathematical result based on the above results.

For Memtest 86+ version 5.01 test results that display pass when there were fewer than 8 passes have a significant number of false negatives.
It sometimes takes passes in the 20's to find malfunctioning RAM.

The test that was done was only done for 3 passes so the testing duration is in the area where there are a significant number of false negatives.

The test should be repeated so that there are 8 or more passes to allow sufficient time to find RAM / DIMM/ MB problems.

Whenever using Windows driver verifier it is important to create a brand new restore point and not rely on any automatic restore points. Sometimes when using Windows driver verifier the typical methods to turn off the tool fail. In these cases a system restore is necessary and having manually created a new one provides a margin of safety.

The WHEA 0 x 124 bugcheck often indicates a hardware problem. Sometimes misbehaving software and hardware drivers can present with a
WHEA 0 x 124 bugcheck. So as a routine all of the hardware needs to be evaluated or checked: CPU, GPU, RAM, Drive, PSU.

The latest windows driver verifier produced BSOD debugging did not display a definitive driver.

The debugging tool that we use is windbg. It has a steep learning curve. It is a free Microsoft tool.

There are software that can provide lower level debugging. You can download and install these now and follow the progress in the thread:

Bluescreenview: Blue screen of death (STOP error) information in dump files.
Whocrashed: http://www.resplendence.com/whocrashed

That's great that the system is becoming more stable. I'm sorry that it was not a quick fix. Sometimes the testing is a lot more rigorous. Progress is being made.

While using Windows driver verifier the drivers are being stressed and there may be computer sluggishness. When you launched the menu there were instructions on the drivers to select as well as the tests to perform. The more tests that are selected the more sluggish the computer may become. The two links that were posted for windows driver verifier had different numbers of tests to perform during its use.

Once the computer is stable (36 hours of no BSOD after the last BSOD) the tool will be turn off. Then the CPU can be evaluated.

Review the earlier post. The hardware components need to be ruled in / ruled out with valid tests.

For Memtest 86+ version 5.01 > 8 or more passes and the more the passes the better the test.
For Prime95 > 3 hours (abort testing as needed)
For FurMark > 1 hour (abort testing as needed)
For HD Tune > Health, Benchmark, and Full error scan
For PSU > check 3.3, 5, and 12 V values with CPU voltage and frequency

For drivers they often can be updated to fix them.
Sometimes they need to be uninstalled and then reinstalled.
Other times they are completely uninstalled.

For the Qualcom the windows driver verifier results will provide information about the stability / instability of the current driver.
If it needs to be uninstalled and replaced that can be performed pending the future debugging results.

Thanks for the info on working with BSOD issues. I will look at your suggestions... I don't mind learning as this is fast becoming my full time hobby.

I had another BSOD and it was when the WiFi showed internet not being connected and the BSOD "DPC_WATCHDOG_VIOLATION" happened when I trouble shooted the Internet connection. I think I have a suspect Qualcom Driver and will look at solutions.

When I started assembling this PC, I purchased the MB, CPU and 8GB DDR4 memory all assembled and tested. I then added what I thought was 2400 DDR4 but is actually at 2133 but the seller said this was by design and could be overclocked easily to 2400.

I hear what you say about Memtest etc. and have decided to remove the additional 8GB memory and will then run Memtest 86+ until at least 8 passes, even though this means I'll be without the use of my PC.

I have a sneaking suspicion that when I run the tests on the original DDR4, I will get no errors, Fingers Crossed.

I will then run again the other tests mentioned in your post. I have also discovered where to load additional system info and this has been updated.

I have learnt so much with your assistance and that's fantastic. I have been making PCs for lots of years and my first few PCs were made of discrete components that I soldered onto the motherboard. For me working with PCs and software is great but also getting "under the hood" is just as interesting and rewarding.

I'll keep you posted on Memtest etc.
cheers,
Rob

It is a well known problem that running with incompatible memory sticks can cause BSOD events (simply using RAM from different manufacturers is often enough to cause errors). I suspect this is the problem in your case. Your memory modules are clearly different:

Code:

[Memory Device (Type 17) - Length 40 - Handle 0032h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      0031h
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM_A1
  Bank Locator                  BANK 0
  Memory Type                   1ah - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         2400MHz
  Manufacturer                  Unknown
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number                   CT8G4DFD824A.C16FDD2


[Memory Device (Type 17) - Length 40 - Handle 0035h]
  Physical Memory Array Handle  002ch
  Memory Error Info Handle      0034h
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM_A2
  Bank Locator                  BANK 1
  Memory Type                   1ah - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         2400MHz
  Manufacturer                  Unknown
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number                   F4-2400C15-8GNT

Try just one memory stick and see if your PC is then free of any BSOD.

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.

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:

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:

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.

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,