something overwote memory it did not own. It happened to over write a pool header (a tracking data structure for kernel memory) it might be the network driver, or even malware. generally you would just update the motherboard drivers and do a malwarebytes scan and see if you can find the cause of the problem. Otherwise you would have to run verifier.exe and force the system to bugcheck when the header is overwritten. the bugcheck memory dump would name the bad driver that overwrote the pool memory
since the stack is corrupted you can not tell what driver caused the corruption. It could be the network driver or not, some malware will attempt to gain access by corrupting the stack. most of the time it is just the ethernet driver...