Tcpip.sys is a network driver, in many cases it is either of the following that is causing it
- USB network adapter
- Network driver
In 99% of the cases WMD is insufficient to find any errors, for that reason MemTest86+ is recommended.
I ran the windows memory diagnostic and it found no errors.
The last dump, 0x1E, was caused by driver verifier but no driver flagged. This indicates a different cause than drivers.
The 0x1E gives a memory access violation result, run MemTest86+ per below instructions.
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8036a7d7f67, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ needs to be run for at least 8 complete passes
for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero
errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.