Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffd68c778620c0, 2, 0, fffff800425f555f}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,
the above dump file is usually caused by drivers which have incorrect addresses so when placed into memory it gets corrupted and hence the blue screen. Unfortunately the dump file doesn't mention an actual driver but i can see from the Call stack that it's possibly network related.
As you'll recall you recently updated 'one' of your network drivers (2nd in the list below) but you also have several others:
anodlwfx.sys Fri Mar 6 10:10:08 2009: ALPHA Networks Filter Driver
athwbx.sys Thu Oct 17 10:46:01 2013: Qualcomm Atheros AR9485WB-EG Wireless Network Adapter
rt640x64.sys Thu Oct 1 11:34:33 2015: Realtek NICDRV 8169 PCIe GBE Family Controller driver
SeLow_x64.sys Sun Oct 18 12:12:14 2015: SoftEther VPN Driver
If you know which ones your not using then I'd remove them especially the Alpha networks which has suddenly appeared out of the blue. It might be part of a bigger application which your running?
If it's still proving hard to find then do a search.
We could try running the driver verifier which tests each driver on boot up and if any are suspect a blue screen will occur. This can sometimes lead to a bsod boot loop although if one boots to safe mode you can then turn the verifier off. Hopefully the offending driver will be written in the dump file.
This will guide you on how to run the verifier:
Link Removed
Post any new dump files.