New
#11
Laptop is still happily streaming away. No BSODs for the last 3 days.
I'm gonna mark this one officially as solved.
Thanks @philc43
Well, maybe I spoke too soon. After 6 days without issue, the same BSOD returned in force today... 4 times already.
*sigh*
Latest dump files attached.
Hello again :)
Well the same driver file is triggering errors but I can see that it is a different date. See below:
Looking at your event log it seems that just prior to the first of the new crashes, you ran the network diagnostic troubleshooter a few times. I am wondering if this has reset your network adaptor in some way and caused the crashes to start. You could try and reset your computer to a system restore point just prior to 25th April when this happened.Code:ffffab00`e5461848 fffff80e`a4beb920Unable to load image \SystemRoot\System32\drivers\athw8x.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athw8x.sys athw8x+0x3eb920 0: kd> lmvm athw8x Browse full module list start end module name fffff80e`a4800000 fffff80e`a4c27000 athw8x T (no symbols) Loaded symbol image file: athw8x.sys Image path: \SystemRoot\System32\drivers\athw8x.sys Image name: athw8x.sys Browse all global symbols functions data Timestamp: Thu Jan 28 09:52:54 2016 (56A9E4F6) CheckSum: 0040EC70 ImageSize: 00427000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
So, after a month of trying every driver available for Windows 10, with no end to the random BSODs in sight, I decided to return to Windows 8.1 on this laptop, and it has been smooth sailing ever since.
Thanks philc43 for all your assistance, but it seems like this model just wasn't cut out for Windows 10, and the Creator's Update actually made things worse. Bluetooth would just continually connect/disconnect.
I'm marking this one as 'solved'.