Sporadic BSOD No Obvious Cause Or Pattern

Okay. So far there has only been the test crash in the mini dumps.

In post #8 what was step #14 attachment. It could not be opened.

The logs and image displayed failure to upgrade from 1703 > 1709.
Did you want to upgrade?

I couldn't find it in the upload selector but I think this was it: Attachment 170780

I didn't attempt to upgrade myself but it's probably worth it?

To troubleshoot the upgrade failure look for the hidden Panther logs:
Download and install Everything search: voidtools
Search for these Panther logs and post any that you find into the thread using one drive or drop box share links:

C:\Windows\Panther
setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup


If there are no BSOD with the current Windows driver verifier settings count the number of test boxes that were checked and the number that are now checked. Add 1 test box every 1 hour until you have a boot problem. Then un-check the last test. Then for the next hour add a new test and remove one test. This way all of the drivers will have been exposed to all of the Windows driver verifier tests as were in the first link.

zbook said:

To troubleshoot the upgrade failure look for the hidden Panther logs:
Download and install Everything search: voidtools
Search for these Panther logs and post any that you find into the thread using one drive or drop box share links:

C:\Windows\Panther
setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup


If there are no BSOD with the current Windows driver verifier settings count the number of test boxes that were checked and the number that are now checked. Add 1 test box every 1 hour until you have a boot problem. Then un-check the last test. Then for the next hour add a new test and remove one test.

These are the files that I could find: BSOD - Google Drive

Create a bootable windows 10 iso:
Download Windows 10
Once the BSOD have been fixed you will attempt an upgrade.
If it works then no further troubleshooting is needed.
If it fails it will generate fresh logs that can be troubleshooted.

Uninstall and install Vbox software to update its drivers.
These boot-start drivers failed to load:

Code:

Event[31013]:  Log Name: System  Source: Service Control Manager  Date: 2018-01-04T11:49:14.603  Event ID: 7026  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Composer  Description: The following boot-start or system-start driver(s) did not load: AFDCSCdamDfscFileCryptGpuEnergyDrvNetBIOSNetBTnpsvctrignsiproxyPschedrdbsstdxVBoxDrvVBoxNetLwfVBoxUSBMonvwififltWdFilter

VBoxDrv.sys

VirtualBox

http://www.virtualbox.org/wiki/Downloads

VBoxNetLwf.sys

Oracle VirtualBox NDIS 6.0 Lightweight Filter Driver

http://www.virtualbox.org/wiki/Downloads

VBoxUSBMon.sys

VirtualBox USB driver

http://www.virtualbox.org/wiki/Downloads

So I had several BSOD with 'Special Pool' enabled with the verifier.

Here is the WhoCrashed:
Attachment 170783


Here is the .zip:
Attachment 170784

This was the first debugged misbehaving driver:
diginet.sys (diginet Avid ICON, C|24 Ethernet)
Updating a driver: Updating a driver. - Microsoft Community

Code:

diginet	Avid ICON, C|24 Ethernet Support	c:\windows\system32\drivers\diginet.sys	Kernel Driver	Yes	Auto	Running	OK	Normal	No	Yes

diginet.sys

Avid Technology Pro Tools

http://www.avid.com/US/products/family/Pro-Tools

Code:

4/01/2018 1:59 AM	Windows Error Reporting	Fault bucket 0xC1_24_VRF_diginet!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 69ddb528-892b-42c0-afb8-53c755a4004a

Problem signature:
P1: c1
P2: ffff810b90fd6f90
P3: ffff810b90fd6ffc
P4: b7006c
P5: 24
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\010418-8968-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10062-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AA7.tmp.WERInternalMetadata.xml

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

Analysis symbol: 
Rechecking for solution: 0
Report ID: 405c286d-60e0-4c8a-ac68-096b770be170
Report Status: 268435456
Hashed bucket: