Windows 10: BSOD Caused by driver tcip.sys Caused by address: tcpip+1eae20

I couldn't fit the error code in the title. It's: 0x000000c2

The full dump info from blue screen viewer is:

121418-5656-01.dmp 14/12/2018 10:53:39 BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`63526442 00000000`04110005 ffffa80a`507a9370 tcpip.sys tcpip.sys+1eae20 x64 ntoskrnl.exe+1aa0a0 C:\Users\Brandon\Desktop\121418-5656-01.dmp 6 15 17134 1,068,812 14/12/2018 11:00:25

I have all my drivers up to date. I am using a network card (antennas are on). I have two antivirus programs running (bullgaurd and malwarebytes). I usually frequent on games and applications like chrome, firefox and discord.


I hope this is enough info,

thanks.

:)

 

Getting Critical_structure_corruption (tcpip/sys) BSOD on Windows 10 computer

Old title: critical_structure_corruption (tcpip/sys)

Hi,

I keeping getting a random BSOD with "critical_structure_corruption (tcpip/sys)" as the reason. I then have to wait approximately 10 seconds during which time Microsoft are collecting information about the error. This seemed to be introduced after the last
Windows update Tuesday. I couldn't find the cause so did a system restore and all was fine again until the following morning when Microsoft automatically installed the updates again. A rollback doesn't fix the problem now.

When are Microsoft going to fix it for me?

I have got an old-ish motherboard who's latest BIOS update was 2010 so I can't help but think this may be the reason. I've tried everything else.

Any ideas?

 

wdf01000.sys and ntoskrnl.exe BSOD

I'm on Windows 10, 64bit

Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

Have no idea which driver is causing them

Please help!

Here are my list of drivers and system info: Documents

 

BSOD errors without an identifiable cause

Okay I may or may not be onto something now. Since, from what I've read, it seems that most ntoskrnl.exe BSODs are not actually caused by ntoskrnl, but by another driver that takes up the krnl's space. When ntoskrnl.exe finds it, it throws the system into
a BSOD to prevent damage. Looking the the dump files, I found that there was a driver called hal.dll, but the crash address was different from the driver address. The crash address was ntoskrnl.exe+14ec00, the same as my above post. There is also another driver
called dxgmms2.sys who's crash address was ntoskrnl.exe+14ec00. I'm not sure if this will help or if it means anything but I'm looking for anything at this point.