New
#11
I had another BSOD, but this one was a bit different. I occurred when I tried to put the computer to sleep (i didnt actually see the BSOD come up, but it did produce a minidump).
Attachment 101162
I had another BSOD, but this one was a bit different. I occurred when I tried to put the computer to sleep (i didnt actually see the BSOD come up, but it did produce a minidump).
Attachment 101162
Still indicating a possible problem with your Intel Wireless:
As you already have the latest driver for this, I'm not sure where to go.Code:2: kd> !irp ffffbb85c49866f0 Irp is active with 5 stacks 3 is current (= 0xffffbb85c4986850) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. cmd flg cl Device File Completion-Context [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 0 ffffbb85bc4f9050 00000000 00000000-00000000 Unable to load image \SystemRoot\System32\drivers\Netwtw04.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Netwtw04.sys *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys \Driver\Netwtw04 Args: 00014400 00000000 00000004 00000002 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)] 0 e1 ffffbb85bbbab970 00000000 fffff80348647cac-ffffbb85beac5b80 Success Error Cancel pending \Driver\vwifibus nt!PopSystemIrpCompletion Args: 00014400 00000000 00000004 00000002 [N/A(0), N/A(0)] 0 0 00000000 00000000 00000000-ffffbb85beac5b80 Args: 00000000 00000000 00000000 00000000
One thing you can try is look through the Power Options and uncheck any settings that reduce power to the wireless.
Attachment 101291
Thanks for your continued support Ztruker.
I have set the 'On battery' wireless setting to maximum, the 'Plugged In' was already at maximum. I'll just be sure to put the computer to sleep via the start menu instead of just closing the lid, that seemed to be when it occurred.
It does seem to be going well since uninstalling Networx (at least regarding the original BSOD problem), fingers crossed that was it.
I'll keep you updated on how it goes the next few days.
Cheers
Last edited by dominics; 13 Sep 2016 at 21:10.
it has been 4 days now with no BSOD, so it looks as though Networx was to blame. I will give it a few more days before marking it solved but it looks promising.
Cheers
Still no new BSODs after 13 days, its looking good.
Thanks for your help Ztruker