The mini dumps are automatically collected using V2 and when available are debugged.
The memory dump availability is typically seen in the logs and when available is collected manually.
For any BSOD:
a) run the V2 log collector to collect new log files
b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
Latest V2 logs and memory dump attached.
Attachment 266437
MEMORY.7z - Google Drive
The last BSOD was on 2/8 and today is 2/10.
The bugcheck was KERNEL_SECURITY_CHECK_FAILURE (139)
When available please update the thread with the results of hardware tests.
Started doing the OCCT stress test and again it caused a BSOD less than 7 minutes into the test. Logs attached:
Attachment 266489
Managed to complete Intel CPU Diagnostic. Brandstring seems to indicate that the exact processor model can't be identified.
Attachment 266492
Furmark 1.5 hour stress test result:
Attachment 266515
Last edited by slickochet; 10 Feb 2020 at 12:06.
Update:
Silicon Image SATALink driver - https://www.catalog.update.microsoft...+Silicon+Image (Attention though! It can do nothing. It does not seem that the SATA controller you have is compatible with Windows 10)
Callback file system driver by EIDoS Corporation - Download Center | Callback Technologies
You can reinstall this driver, although it is from 2004, and there were quite a lot of updates to Windows, so maybe this compatibility is lost because the driver uses an API that the system no longer supports?
Ah yes I see. Although the driver in use is from 2008 and I have been using this device for over a year without issue.
Attachment 266519
I know this is not the exact driver name but it is the device with the closest name to it,.
See if you can find a friend, neighbor, relative, or local computer store to swap the CPU.
Alternatively replace the CPU.
Quote