Incorrect and partly correct.
The tcpip.sys is a Windows driver, from Windows drivers we can assume they are not the cause. If Windows drivers were the cause many systems running Windows would be very unstable as it is a fact that Windows drivers very often show up in the dumps.
Some Windows drivers do give indications towards possible causes where we come with the 'partly correct'.
When a Windows network driver is flagged there are more possible causes than just the network drivers from the network adapters.
AV programs, AM programs, VPN programs, USB network adapters, etc., all those are also included when Windows network drivers are flagged.
If you're certain your physical network adapters (wifi, lan, usb) are perfectly fine, but crashes keep showing that the network drivers are causing the crashes. There are various reasons why this occurs for which some more analysis and troubleshooting is required, but you need to include all possibilities, else someone would replace the whole system without knowing that a single driver from the AV is causing problems. A simple removal of the program would do the job.
In your case I found the LAN driver being the possible cause, check ASRock for driver updates
1: kd> lmvm e1i63x64
Browse full module list
start end module name
fffff80d`d7400000 fffff80d`d7486000 e1i63x64 T (no symbols)
Loaded symbol image file: e1i63x64.sys
Image path: \SystemRoot\System32\drivers\e1i63x64.sys
Image name: e1i63x64.sys
Browse all global symbols functions data
Timestamp: Fri Mar 04 22:46:29 2016 (56DA0235)
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4