At least your errors are consistent. 4 of 5 point to NVTcp.sys
They are all either 0xd1 or 0xc2.
• Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
• A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
• A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
I would suggest...
1. Make sure your mb chipset drivers, and graphics drivers are updated.
2. In April, Route44 made this note... "NVTcp.sys driver which belongs to the process NVIDIA Networking Protocol Driver belonging to the software NVIDIA TCP/IP Protocol Driver. Many, many people have had issues with this driver. Several places, including Nvidia's own forums recommend to Uninstall Network Access Manager."
3. You said ... "BSOD when running P2P programs, online games, etc" - P2P and online games are notoriously problematic. If you must use such software, I would suggest you look into doing it inside a virtual machine such as sandboxie. I prefer to get rid of P2P. you are just asking for trouble. Because of typical problems, I would stongly urge you to consider the possibility that you have become infected, and pursue the 8 steps. Because of the way P2P functions, you may have malware! So, here is a good place to start reading.
Start with the three stickies by Julio at the top...
https://www.techspot.com/vb/menu28.html
If you decide to try to clean, please, very carefully follow the instructions here...
https://www.techspot.com/community/...lware-removal-preliminary-instructions.58138/
For more debug information see below...
===========
Windows XP Kernel Version 2600 (Service Pack 3)
Mini062809-01.dmp
BugCheck 100000D1, {38, 2, 1, adc1dab6}
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
BUGCHECK_STR: 0xD1
PROCESS_NAME: Engine.exe
IMAGE_NAME: NVTcp.sys
---------
Mini062609-01.dmp
BugCheck 100000D1, {210001c, 2, 1, ac4a01d1}
Probably caused by : NVTcp.sys ( NVTcp+41d1 )
PROCESS_NAME: Idle
IMAGE_NAME: NVTcp.sys
---------
Mini062409-01.dmp
BugCheck C2, {7, cd4, 1004f, 88e16e68}
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
PROCESS_NAME: Idle
IMAGE_NAME: NVTcp.sys
---------
Mini061809-01.dmp
BAD_POOL_CALLER (c2)
PROCESS_NAME: Idle
IMAGE_NAME: NVTcp.sys
---------
Mini061409-01.dmp
BugCheck 100000D1, {ffffff20, 2, 0, ba4dd62f}
BUGCHECK_STR: 0xD1 (see above)
PROCESS_NAME: System
IMAGE_NAME: Ntfs.sys
