Windows 10: AcePC T11 - Lots of BSODs doing stuff - Atom X5-Z8350

Hi,

I attached the logs from your dumper and additional minidumps.

It's a Chinese minipc (ACEPC T11 (Black) Fanless Mini Desktop Computer Intel Cherry Trail Z8350 Quad Core 4GB RAM 32GB eMMC,2.4G/5G Dual-Band Wi-Fi,Support 4K HD,Bluetooth 4.0,Dual Output VGA/HDMI | Best Mini PC Review 2017-2018). I don't see anything relevant with BlueScreenView. Some of the minidumps crashes with a Microsoft Driver, USBXHCI.SYS, others directly with the Windows kernel.

The PC passes successfully the Intel Processor Diagnostic Tool and at least one pass of an extended Windows Memory Diagnostic test (I didn't have time to try the second pass). Given these tests, it seems odd there is a hardware issue, but anyway I can believe it exists something odd in the motherboard or it's just the BIOS, but I don't have any BIOS update available (There's one but it's ridden of viruses).

Most of the time the PC is stable, but sometimes there are BSODs, almost always related to graphics stuff. For example, when I changed the screen resolution.

Thanks.

:)

 

more space on c:/ drive

thanks for the help

It is a laptop, microsoft windows laptop

I will be using it at home

version 1703

OS build 16063.540

intel(R) Atom (TM) x5-z8350

CPU @1.44GHz

4.00 gb ram

64 bit

 

I now have Windows 10 and Windows Audio Endpoint Driver Device is not producing Sound

Name Intel Atom x5

Code Name Cherry Trail

Package Socket 1380 BGA

Technology 14nm

Specification Intel Atom x5-Z8350 CPU @ 1.44GHz

Intel SST Audio Device (WDM)

Windows 10 64bit 1709

I had same problem, To fix needed to download and run realtek update

https://downloads.dell.com/FOLDER03131031M/1/Audio_Driver_XVXP8_WN32_6.0.1.7544_A01.EXE

Intel SST Audio Device (WDM) version 604.10135.6766.9995 loaded and audioendpoints installed in device manager now, horay!!!!!!

 

The log files are in a foreign language and cannot be scanned or read.
Please use English as the default language and post a new zip so that the files can be troubleshooted:
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials
log collector v2-beta06.zip

Please update the system specs in the "My Computer" section:
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

 

Oops, sorry, here's an English dump.

Edit: these logs weren't taken with the beta log collector, but your non-beta one in the tutorial. Do you need me to use the beta one instead?

 

There was 1 BSOD mini dump file.
When it was debugged it did not display a definitive misbehaving drivers.
The logs indicated prior BSOD with bugchecks:
D1
A
50
139
3B

Windows failed fast startup.
There were multiple drivers that failed to load:
BCMSDH43XX
IntelSST

There was insufficient virtual memory.
There was dump file deletion cause by insufficient free space on the drive.
There was crash dump failure.
There were graphic problems reported.

For all tests / steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

7 If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

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

9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
9a) > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
9b) > 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

10) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

11) To ensure that there are no improper bios settings please reset the bios.

12) Sometimes there can be failure to boot after resetting the bios.

13) So please make sure your files are backed up.

14) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

15) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

16) 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.
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 4 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.
When Memtest86+ 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 BSOD Tutorials

17) Update these drivers:
17a) igdkmd64lp.sys Intel Graphics Kernel Mode Driver
17b) BCMSDH43XX Broadcom 802.11 SDIO Network Adapter Driver
17c) IntelSST Intel SST Audio Device
Updating a driver: Updating a driver. - Microsoft Community

18) Read these links on Windows drive verifier (do not use the tool until it is communicated in the thread)
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Code: Event[77]: Log Name: System Source: Display Date: 2017-12-28T14:12:15.106 Event ID: 4115 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-VR9JQGH Description: Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver.[/quote] Code: Event[786]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-12-29T11:56:16.032 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: COMEDOR Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[853]: Log Name: System Source: volmgr Date: 2017-12-29T11:58:37.260 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: COMEDOR Description: Crash dump initialization failed![/quote] Code: Event[3467]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2018-01-02T19:30:30.089 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: COMEDOR Description: The driver \Driver\BCMSDH43XX failed to load for the device SD\VID_02d0&PID_a9bf&FN_1\4&32d17375&0&0.[/quote] Code: Event[3606]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2018-01-02T19:33:04.953 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: COMEDOR Description: The driver \Driver\IntelSST failed to load for the device ACPI\808622A8\1.[/quote] Code: Event[73]: Log Name: System Source: Application Popup Date: 2017-12-28T14:08:30.834 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-VR9JQGH Description: Application pop-up: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.[/quote] Code: Event[67]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-12-28T13:12:03.954 Event ID: 1018 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-VR9JQGH Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.[/quote] Code: Event[75]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-28T14:12:08.716 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-VR9JQGH Description: The driver \Driver\NdisWan failed to load for the device SWD\MSRRAS\MS_NDISWANIP.[/quote] Code: Event[72]: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Date: 2017-12-28T14:08:26.081 Event ID: 2004 Task: Resource Exhaustion Diagnosis Events Level: Warning Opcode: Contains the results of the diagnosis. Keyword: Events related to exhaustion of system commit limit (virtual memory). User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-VR9JQGH Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: MicrosoftEdgeCP.exe (9584) consumed 5011148800 bytes, MicrosoftEdgeCP.exe (8876) consumed 130662400 bytes, and MsMpEng.exe (3584) consumed 127545344 bytes.[/quote]


Code: 29/12/2017 12:24 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffffe9835d7548d0 P4: ffffe9835d754828 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11890-01.dmp \\?\C:\WINDOWS\TEMP\WER-15015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7E1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD8DC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_81be7b27941524a2852b2c5ee9cc9fba9c9a57_00000000_cab_0350d8eb Analysis symbol: Rechecking for solution: 0 Report ID: d5512239-3b28-47ba-acb7-25968b56424d Report Status: 4 Hashed bucket:29/12/2017 09:47 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff806c487e4656 P4: fffff6053f498fe0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11781-01.dmp \\?\C:\WINDOWS\TEMP\WER-14843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE241.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2AF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE32D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_39a487e17f6d054cae349f6141885e8618fe3ef_00000000_cab_034ce33b Analysis symbol: Rechecking for solution: 0 Report ID: 443faa04-9c33-4965-ad41-395d6ea8e9fd Report Status: 100 Hashed bucket:29/12/2017 09:47 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: ffff806c487e4656 P4: fffff6053f498fe0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11781-01.dmp \\?\C:\WINDOWS\TEMP\WER-14843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE241.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2AF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE32D.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_39a487e17f6d054cae349f6141885e8618fe3ef_00000000_cab_034ce33b Analysis symbol: Rechecking for solution: 0 Report ID: 443faa04-9c33-4965-ad41-395d6ea8e9fd Report Status: 4 Hashed bucket:01/01/2018 01:45 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffff9801e053dc54 P3: 0 P4: fffff8000652720e P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-15718-01.dmp \\?\C:\WINDOWS\TEMP\WER-18843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC37.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCA4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD03.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_5554324fbd877e7940d957f864feead612b1362_00000000_cab_0344dd11 Analysis symbol: Rechecking for solution: 0 Report ID: 7f5e94b5-fdfe-4eb8-a5ba-fabb4eb65a38 Report Status: 100 Hashed bucket:01/01/2018 01:44 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 50 P2: ffff9801e053dc54 P3: 0 P4: fffff8000652720e P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-15718-01.dmp \\?\C:\WINDOWS\TEMP\WER-18843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC37.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCA4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD03.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_5554324fbd877e7940d957f864feead612b1362_00000000_cab_0344dd11 Analysis symbol: Rechecking for solution: 0 Report ID: 7f5e94b5-fdfe-4eb8-a5ba-fabb4eb65a38 Report Status: 4 Hashed bucket:29/12/2017 10:30 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: fffff801db09e51c P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11781-02.dmp \\?\C:\WINDOWS\TEMP\WER-14906-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEE6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDFD1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_e226de9b2d794fa1133fef34569f05d604729c2_00000000_cab_0340dfff Analysis symbol: Rechecking for solution: 0 Report ID: ced731ea-82d8-4e5a-b2f0-672fe8600c73 Report Status: 4 Hashed bucket:01/01/2018 08:33 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: a P2: 10000000698 P3: 2 P4: 0 P5: fffff801d56fd640 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-12437-01.dmp \\?\C:\WINDOWS\TEMP\WER-15531-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE3C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCEAA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF09.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_c292c6dc15499e655573650bbf0c53b67541189_00000000_cab_034ccf17 Analysis symbol: Rechecking for solution: 0 Report ID: f87af26c-6001-4d6c-8c67-b564960d6a3a Report Status: 4 Hashed bucket:31/12/2017 19:11 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 0 P3: 2 P4: 0 P5: fffff803971361cb P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\123117-11656-01.dmp \\?\C:\WINDOWS\TEMP\WER-14750-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD65B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6D8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD736.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_b7cb235d93cd94e2d84b331d3bb4b716f28facf_00000000_cab_034cd755 Analysis symbol: Rechecking for solution: 0 Report ID: 9acd4d90-709b-4eab-a0c6-5d07a84f0ef1 Report Status: 4 Hashed bucket:28/12/2017 22:13 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff8058df8f461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122817-11546-01.dmp \\?\C:\WINDOWS\TEMP\WER-14703-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE61A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE697.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE705.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_03e61c5a4f2f34f63af22195738b88e5d8b75_00000000_cab_2060f349 Analysis symbol: Rechecking for solution: 0 Report ID: a67116cd-b97e-4adb-9e06-181bdd7eb281 Report Status: 2049 Hashed bucket:28/12/2017 22:13 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff8058df8f461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122817-11546-01.dmp \\?\C:\WINDOWS\TEMP\WER-14703-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE61A.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE697.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE705.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_03e61c5a4f2f34f63af22195738b88e5d8b75_00000000_0330e714 Analysis symbol: Rechecking for solution: 0 Report ID: a67116cd-b97e-4adb-9e06-181bdd7eb281 Report Status: 4 Hashed bucket:28/12/2017 13:12 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff809876af461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122817-20984-01.dmp \\?\C:\WINDOWS\TEMP\WER-53406-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2006.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20A2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2111.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_f0a202af6e9fb3669aa4ddb263df34aff123a_00000000_cab_1f292361 Analysis symbol: Rechecking for solution: 0 Report ID: be4de68c-1025-4a72-b0fd-597d00e7ef26 Report Status: 2049 Hashed bucket:28/12/2017 13:12 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff809876af461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122817-20984-01.dmp \\?\C:\WINDOWS\TEMP\WER-53406-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2006.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20A2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2111.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_f0a202af6e9fb3669aa4ddb263df34aff123a_00000000_0321212f Analysis symbol: Rechecking for solution: 0 Report ID: be4de68c-1025-4a72-b0fd-597d00e7ef26 Report Status: 4 Hashed bucket:02/01/2018 20:05 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff80ff30df461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-11406-01.dmp \\?\C:\WINDOWS\TEMP\WER-14546-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD52.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDB0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE0F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_6bfeae6b89f045445348b8c63ec8c69c9858882_00000000_cab_0344ce1d Analysis symbol: Rechecking for solution: 0 Report ID: 5dae8b53-3cdf-4010-ae85-0e75908e9473 Report Status: 4 Hashed bucket:02/01/2018 18:09 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: 3d P3: 2 P4: 0 P5: fffff80cc86af461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-12609-01.dmp \\?\C:\WINDOWS\TEMP\WER-15734-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER14BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1577.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1604.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_bba589a9b6257ebb5cd62f89cf79b316902477_00000000_cab_03491613 Analysis symbol: Rechecking for solution: 0 Report ID: 8ac7593b-d823-4f7b-a6c3-c762b676d031 Report Status: 4 Hashed bucket:02/01/2018 19:01 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: ffff9b0cf40f4d90 P3: 2 P4: 0 P5: fffff80801c8f45e P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-11656-01.dmp \\?\C:\WINDOWS\TEMP\WER-14750-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER70F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_91dbd75d5ba9c11db67829bb16d5123fa5f26_00000000_cab_03410829 Analysis symbol: Rechecking for solution: 0 Report ID: 14c0fc6c-d761-4153-abcb-a04804b436e7 Report Status: 4 Hashed bucket:[/quote] Code: 29/12/2017 12:24 Windows Error Reporting Fault bucket 0x139_3_CORRUPT_LIST_ENTRY_nt!ExAllocatePoolWithTag, type 0 Event Name: BlueScreen Response: Not available Cab Id: be6c8926-21bc-44ef-b0cd-db884a9a5561 Problem signature: P1: 139 P2: 3 P3: ffffe9835d7548d0 P4: ffffe9835d754828 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11890-01.dmp \\?\C:\WINDOWS\TEMP\WER-15015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD7E1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD8DC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_81be7b27941524a2852b2c5ee9cc9fba9c9a57_00000000_cab_1fb10d88 Analysis symbol: Rechecking for solution: 0 Report ID: d5512239-3b28-47ba-acb7-25968b56424d Report Status: 268435456 Hashed bucket:29/12/2017 09:52 Windows Error Reporting Fault bucket 0x3B_win32kbase!HmgShareLockCheck, type 0 Event Name: BlueScreen Response: Not available Cab Id: 5bc40781-c750-472e-af78-c0da7acea62a Problem signature: P1: 3b P2: c0000005 P3: ffff806c487e4656 P4: fffff6053f498fe0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11781-01.dmp \\?\C:\WINDOWS\TEMP\WER-14843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE241.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE2AF.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE32D.tmp.txt \\?\C:\Windows\Temp\WER4D7C.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_39a487e17f6d054cae349f6141885e8618fe3ef_00000000_cab_155957bc Analysis symbol: Rechecking for solution: 0 Report ID: 443faa04-9c33-4965-ad41-395d6ea8e9fd Report Status: 268435556 Hashed bucket:[/quote] Code: 29/12/2017 10:30 Windows Error Reporting Fault bucket AV_nt!NtAssociateWaitCompletionPacket, type 0 Event Name: BlueScreen Response: Not available Cab Id: ca14403e-fcaa-446e-a3d4-f074c6e2437d Problem signature: P1: a P2: 0 P3: 2 P4: 0 P5: fffff801db09e51c P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\122917-11781-02.dmp \\?\C:\WINDOWS\TEMP\WER-14906-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEE6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF53.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDFD1.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_e226de9b2d794fa1133fef34569f05d604729c2_00000000_cab_14dd01a1 Analysis symbol: Rechecking for solution: 0 Report ID: ced731ea-82d8-4e5a-b2f0-672fe8600c73 Report Status: 268435456 Hashed bucket:01/01/2018 01:47 Windows Error Reporting Fault bucket AV_R_INVALID_igdkmd64lp!OSAllocateMemWrapper, type 0 Event Name: BlueScreen Response: Not available Cab Id: 5c09fe69-f823-4d65-80b3-98d58d266847 Problem signature: P1: 50 P2: ffff9801e053dc54 P3: 0 P4: fffff8000652720e P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-15718-01.dmp \\?\C:\WINDOWS\TEMP\WER-18843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC37.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCA4.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD03.tmp.txt \\?\C:\Windows\Temp\WER4A3A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_5554324fbd877e7940d957f864feead612b1362_00000000_cab_06ab4f1b Analysis symbol: Rechecking for solution: 0 Report ID: 7f5e94b5-fdfe-4eb8-a5ba-fabb4eb65a38 Report Status: 268435556 Hashed bucket:02/01/2018 18:09 Windows Error Reporting Fault bucket AV_USBXHCI!Bulk_ProcessTransferEventWithED1, type 0 Event Name: BlueScreen Response: Not available Cab Id: a6cd99dd-f7a1-489d-8448-3f787ebff26a Problem signature: P1: d1 P2: 3d P3: 2 P4: 0 P5: fffff80cc86af461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-12609-01.dmp \\?\C:\WINDOWS\TEMP\WER-15734-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER14BB.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1577.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1604.tmp.txt \\?\C:\Windows\Temp\WER3A55.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_bba589a9b6257ebb5cd62f89cf79b316902477_00000000_cab_24c13f94 Analysis symbol: Rechecking for solution: 0 Report ID: 8ac7593b-d823-4f7b-a6c3-c762b676d031 Report Status: 268435456 Hashed bucket:02/01/2018 20:05 Windows Error Reporting Fault bucket AV_USBXHCI!Bulk_ProcessTransferEventWithED1, type 0 Event Name: BlueScreen Response: Not available Cab Id: deee5bf6-8e15-4c0b-8624-ed5aac9b2b97 Problem signature: P1: d1 P2: 38 P3: 2 P4: 0 P5: fffff80ff30df461 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-11406-01.dmp \\?\C:\WINDOWS\TEMP\WER-14546-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD52.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCDB0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE0F.tmp.txt \\?\C:\Windows\Temp\WERF638.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_6bfeae6b89f045445348b8c63ec8c69c9858882_00000000_cab_1408fb28 Analysis symbol: Rechecking for solution: 0 Report ID: 5dae8b53-3cdf-4010-ae85-0e75908e9473 Report Status: 268435456 Hashed bucket:02/01/2018 19:01 Windows Error Reporting Fault bucket AV_usbxhci!Interrupter_DeferredWorkProcessor, type 0 Event Name: BlueScreen Response: Not available Cab Id: 3f09e3b0-0b4e-434a-bff5-72ca6f944ad5 Problem signature: P1: d1 P2: ffff9b0cf40f4d90 P3: 2 P4: 0 P5: fffff80801c8f45e P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010218-11656-01.dmp \\?\C:\WINDOWS\TEMP\WER-14750-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER70F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_91dbd75d5ba9c11db67829bb16d5123fa5f26_00000000_cab_29fd4c46 Analysis symbol: Rechecking for solution: 0 Report ID: 14c0fc6c-d761-4153-abcb-a04804b436e7 Report Status: 268435456 Hashed bucket:31/12/2017 19:12 Windows Error Reporting Fault bucket AV_USBXHCI!RootHub_DetectAndAcknowledgePortResume, type 0 Event Name: BlueScreen Response: Not available Cab Id: 2bbcb315-1e62-4c29-8844-96ef5157384c Problem signature: P1: d1 P2: 0 P3: 2 P4: 0 P5: fffff803971361cb P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\123117-11656-01.dmp \\?\C:\WINDOWS\TEMP\WER-14750-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD65B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6D8.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD736.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_b7cb235d93cd94e2d84b331d3bb4b716f28facf_00000000_cab_0d0d4438 Analysis symbol: Rechecking for solution: 0 Report ID: 9acd4d90-709b-4eab-a0c6-5d07a84f0ef1 Report Status: 268435456 Hashed bucket:01/01/2018 08:33 Windows Error Reporting Fault bucket AV_win32kbase!UserSessionSwitchLeaveCrit, type 0 Event Name: BlueScreen Response: Not available Cab Id: 8b513583-df5c-491b-a9e4-f39eedda4451 Problem signature: P1: a P2: 10000000698 P3: 2 P4: 0 P5: fffff801d56fd640 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010118-12437-01.dmp \\?\C:\WINDOWS\TEMP\WER-15531-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE3C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCEAA.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF09.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_c292c6dc15499e655573650bbf0c53b67541189_00000000_cab_27f110f3 Analysis symbol: Rechecking for solution: 0 Report ID: f87af26c-6001-4d6c-8c67-b564960d6a3a Report Status: 268435456 Hashed bucket:29/12/2017 13:14 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_igdkmd64lp.sys_GEN8CHV_0_0x141, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 296eaef2-bd78-4245-be2b-45135e15933d Problem signature: P1: 141 P2: ffffab0efeaae010 P3: fffff80a12722410 P4: 0 P5: 1db8 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171229-1314.dmp \\?\C:\WINDOWS\TEMP\WER-3022593-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FD1.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6FF0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER706E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_63ff6b86a786c8777fe86e95b94e9c70ad9b118_00000000_cab_03968d3c Analysis symbol: Rechecking for solution: 0 Report ID: fb508bce-d259-48a2-b4f8-8325c979bd0f Report Status: 268435456 Hashed bucket:29/12/2017 15:44 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_igdkmd64lp.sys_GEN8CHV_0_0x141, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 53871208-6a9e-46b7-b487-b378efbe6b0a Problem signature: P1: 141 P2: ffff98856a65f4a0 P3: fffff8090de22410 P4: 0 P5: 29c P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171229-1543.dmp \\?\C:\WINDOWS\TEMP\WER-1022765-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34CD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34FC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER357A.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8a8ce72a31c3759146b28988b421525fc7577_00000000_cab_236c520a Analysis symbol: Rechecking for solution: 0 Report ID: 67daaf5d-b2d3-4721-9b56-f301421ee14f Report Status: 268435456 Hashed bucket:[/quote] Code: Name [00000001] Broadcom 802.11ac WDI SDIO AdapterAdapter Type Ethernet 802.3Product Type Broadcom 802.11ac WDI SDIO AdapterInstalled YesPNP Device ID SD\VID_02D0&PID_A9BF&FN_1\4&32D17375&0&0Last Reset 02/01/2018 22:33Index 1Service Name BCMSDH43XXIP Address Not AvailableIP Subnet Not AvailableDefault IP Gateway Not AvailableDHCP Enabled YesDHCP Server Not AvailableDHCP Lease Expires Not AvailableDHCP Lease Obtained Not AvailableMAC Address ‪B0:F1:ECC:8B:4A‬IRQ Channel IRQ 1037Driver c:\windows\system32\drivers\bcmdhd63.sys (1.596.0.0, 1.78 MB (1,869,104 bytes), 15/05/2017 00:33)[/quote] Code: bcmsdh43xx Broadcom 802.11 SDIO Network Adapter Driver c:\windows\system32\drivers\bcmdhd63.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] Code: intelsst Intel SST Audio Device (WDM) c:\windows\system32\drivers\isstrtc.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote] igdkmd64lp.sys Intel Graphics Kernel Mode Driver Drivers & Software

 

Thanks, zbook!

I tried several graphic drivers. Last one I'm using is the one which comes from Windows Update. I don't think there's an alternative for the audio one. I'll try to find one for the WiFi driver.

In the coming days I'll all do that stuff but can you tell me something about the other minidumps? The log dumper didn't get the other minidumps, but I attached them in the other_minidumps.7z file . Is there anything useful you can extract from them?

Thanks!

 

Windows BSOD dumps are useful to find misbehaving drivers or malfunctioning hardware.
There can be problems with dump creation and there are troubleshooting steps in the above post.
And there can be problems with dump deletion and there are troubleshooting steps in the above post.
Once these are troubleshooted Windows driver verifier will be used to test the drivers that you have replaced and find drivers that were not replaced that may be misbehaving.

 

With the driver verifier I had the latest minidump you'll find in the dump. It seems your beta log collector now captured the rest of the minidumps.

With MEMTEST86+ 5.0.1 I've got a blank screen, so I did 8 passes with the free version of Passmark's MEMTEST.

I couldn't find good driver substitutions unfortunately. I got some new drivers from Snappy but lost functionality or the system felt slower at shutting down, so I left what I had.

Thanks!

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.125

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

PS C:\WINDOWS\system32> chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
386304 file records processed.
File verification completed.
13799 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
28704 reparse records processed.
460884 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
28704 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
37291 data files processed.
CHKDSK is verifying Usn Journal...
35437064 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

29808639 KB total disk space.
16486168 KB in 137361 files.
110824 KB in 37292 indexes.
0 KB in bad sectors.
467947 KB in use by the system.
41472 KB occupied by the log file.
12743700 KB available on disk.

4096 bytes in each allocation unit.
7452159 total allocation units on disk.
3185925 allocation units available on disk.

 

1) For startup and recovery > system failure > un-check automatically restart
2) For Windows error reporting > change start up type to automatic, click start, click ok, reboot
3) For RAM /DIMM /MB testing all of the software use different algorithms.
The software product Memtest86+ version 5.01 is preferred as each software has false positives, false negatives, and accuracy.

These are the troubleshooting steps for Memtest86+ version 5.01:

Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials: Boot from USB Drive on Windows 10 PC Installation Upgrade Tutorials

Note
If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.
How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows: Enable or Disable Fast Boot in UEFI Firmware Settings for Windows Performance Maintenance Tutorials

1. Try another USB stick
2. Try all USB ports (2.0 and 3.0)
3. Maybe when using UEFI Bios you have to temporarily switch to Legacy in BIOS settings
4. Turn off temporarily fast boot, secure boot, CSM if enabled

 

Done those first steps.

Unfortunately MEMTEST86+ is too old and it's just incompatible with Cherry Trail I guess. I already had "Fast boot" disabled. Tried to run MEMTEST86+ from the official ISO and from SystemRescueCD, which runs ok, but MEMTEST86+ does not.





MEMTEST from Passmark should suffice since it's updated and with UEFI support, and MEMTEST86+ being a fork of this one. If you think I should run another one, Windows Memory Diagnostics works too.

By the way, RAM is solded into the SoC here, so I cannot test RAM modules in isolation.

Can you tell me something about the last log dump I uploaded in the post? Thanks.

 

There were no new BSOD mini dump files since 1/4 /2018.

The software tools have different algorithms.
We use exclusively Memtest86+ version 5.01.
The other software products may have more recent updates. They are using different algorithms and we have had threads with conflicing results.
There have been tests where is has take passes into the 20s to find malfunctioning RAM.

These were the modifications made in another thread for Memtest86+ version 5.01 (the computer manufacturers may have differed)
1. I disabled the fast boot
2. I diasbled the secure boot control to get into CSM
3. I enabled the CSM and F10 to save and exit
4. Press F2 and in the boot menu we will find 4 options:
a) 2 for UEFI: boot manager, UEFI Flash disk
b) 2 for bios: boot manager, flash disk
5. Select the bios flash disk which will be the last option(fourth) and set it as primary boot device.
6. Press F10 to save and exit and wait for the memtest86+ to run.

 

Besides secure boot which was already disabled, I don't have any of those options in my BIOS, sorry. I'm doing the correct procedure to boot stuff from a pendrive: I managed to boot PASSMARK's MEMTEST succesfully, so the only conclusion is that MEMTEST86+ is just incompatible with this motherboard (which could be pretty normal since MEMTEST86+ is not updated since 2013).

Didn't you see the attached file in AcePC T11 - Lots of BSODs doing stuff - Atom X5-Z8350 - Windows 10 Forums ?

The attached filename is COMEDOR (06-01-2018 09 49).zip

It has quite a lot of minidump files inside, unlike the first log dump I uploaded here.

 

Crashes on the computer can occur as BSOD or without BSOD.
The crashes are recorded in several files.
Today is 1/6/2018. The last crashes of any type that were recorded were on 1/4/2018.
When there are crashes there can be problems with creation of the reports and accidental deletion of the files.
The steps in post #4 were to evaluate and fix these types of problems.
Some steps were already made to optimize the creation and prevent the deletion of the files.

The last crashes were bugcheck A
The misbehaving driver was igdkmd64lp
This should have already been fixed.


For the RAM testing see what happens if you try legacy instead of UEFI.
Give that some trial and error testing.
Within the last few months we had had a thread where memtest was used instead of memtest86+ version 5.01.
The results were different.
The memtest is regularly updated whereas the memtest86+ is older and has been the better caliber test.
In the references that were posted from the Microsoft zigzag team and from Ten Forums the Memtest86+ version 5.01 is used.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials
So please see what you can do to perform the better test using Memtest86+ vesion 5.01 for 8 or more passes.
Memtest86+ - Advanced Memory Diagnostic Tool

 

I know that even Microsoft community recommends that version. But I can help it. I managed to run MEMTEST86+ thanks to an EFI enabled multiboot pendrive since the BIOS doesn't have a legacy mode option to boot USB drives. It's just it shows a blank screen unfortunately. There's something more I can try whenever I can.

Just in case, I found that Intel has a compute stick pretty similar in hardware than this minipc. I downloaded its drivers (graphics and chipset ones). I installed them, and now it seems that things are more stable. I'll see if I don't find a BSOD again in the coming days.