Hi Younggrr,
This is likely being caused by your VirtualBox network adapter.
[CODE]0: kd> !irp fffffa801445ae10
Irp is active with 3 stacks 2 is current (= 0xfffffa801445af28)
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
>[IRP_MJ_POWER(16), IRP_MN_QUERY_POWER(3)]
0 e1 fffffa8010ad9050 00000000 fffff800030cf210-fffffa800cad2350 Success Error Cancel pending
[COLOR=#ff0000]\Driver\VBoxNetAdp nt!PopSystemIrpCompletion[/COLOR]
Args: 00016600 00000000 00000006 00000005
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-fffffa800cad2350
Args: 00000000 00000000 00000000 00000000[/CODE]
[CODE]0: kd> lmvm vboxnetadp6
Browse full module list
start end module name
fffff880`01c00000 fffff880`01c2f000 VBoxNetAdp6 T (no symbols)
Loaded symbol image file: VBoxNetAdp6.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys
Image name: VBoxNetAdp6.sys
Browse all global symbols functions data
Timestamp: Mon Nov 21 11:44:34 2016 (58332472)
CheckSum: 00020DEF
ImageSize: 0002F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/CODE]
You can try either disabling the virtual adapter from Device Manager (or Network Connections), and if that doesn't work, try uninstalling VirtualBox. If that corrects the issue and you still need the software, try doing a fresh installation of the most up-to-date version of VirtualBox. Presumably if you put the computer into sleep mode, the same issue would occur.
