Bugcheck 7F almost daily after Connected Standby

Did you roll back the drivers or have there been no drivers updated?

Code:

2: kd> !irp c35496c0
Irp is active with 7 stacks 5 is current (= 0xc35497c0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 96060030 00000000 8880e952-b7f280e8    
           \Driver\sdbus    ndis!ndisSetDevicePowerOnComplete
            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 b7f28030 00000000 00000000-00000000    pending
          Unable to load image \SystemRoot\system32\DRIVERS\bcmdhd63.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmdhd63.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmdhd63.sys
 \Driver\BCMSDH43XX
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 c352b020 00000000 81f7dbfa-9611f720 Success Error Cancel pending
          *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
 \Driver\vwifibus    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-9611f720    


            Args: 00000000 00000000 00000000 00000000


2: kd> lmvm bcmdhd63
start    end        module name
99490000 995ef000   bcmdhd63 T (no symbols)           
    Loaded symbol image file: bcmdhd63.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmdhd63.sys
    Image name: bcmdhd63.sys
    Timestamp:        Thu Oct 03 04:09:54 2013 (524CD1F2)
    CheckSum:         000541FB
    ImageSize:        0015F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Intel graphics drivers have also been flagged yesterday

Code:

81c3d570  8f461000Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
 igdkmd32+0x11000
2: kd> lmvm igdkmd32
start    end        module name
8f450000 8f747000   igdkmd32 T (no symbols)           
    Loaded symbol image file: igdkmd32.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
    Image name: igdkmd32.sys
    Timestamp:        Mon Aug 17 17:34:15 2015 (55D1FEF7)
    CheckSum:         002EEBFD
    ImageSize:        002F7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'd like to give driver verifier a shot to see if any other driver is causing problems, but I'm not sure how it is with tablets.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Unfortunately is it possible to have no drivers flagged with driver verifier what is the case now, probably because a minidump contains very little data compared to a kernel dump.

Please keep verifier running and be prepared of system freezes.

No, I wouldn't be able to debug a complete dump + a complete dump would contain much of useless data.

I prefer to keep it to minidumps for now :)

An Intel controller driver has been flagged.
Honestly, it looks to me like a bug from updating to Windows 10.
Driver Reference Table - iaioi2ce.sys

Code:

9a8c7210  90f5b3d8Unable to load image \SystemRoot\System32\drivers\iaioi2ce.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaioi2ce.sys
*** ERROR: Module load completed but symbols could not be loaded for iaioi2ce.sys
 iaioi2ce+0xb3d8
2: kd> lmvm iaioi2ce
start    end        module name
90f50000 90f62000   iaioi2ce T (no symbols)           
    Loaded symbol image file: iaioi2ce.sys
    Image path: \SystemRoot\System32\drivers\iaioi2ce.sys
    Image name: iaioi2ce.sys
    Timestamp:        Fri Nov 01 03:24:26 2013 (527310DA)
    CheckSum:         0001C7B5
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4