RaDiKaL_ :
Try reinstalling your NIC drivers.
I'll do this when I can.
bjornl :
First and most important. Stop using Windows XP. Go to Windows 7 or above. Much more stable. And most importantly it is moderately secure. And unlike Windows 10, Windows 7 doesn't spy on you (unless you get click happy while surfing)
I have, this is a dual boot system; XP x64 Pro and 7 x64 Pro - sorry I failed to mention this....
What? Windows 10 spies on you??!! Didn't know that.... I only had win10 for a few months and just didn't like the overall feel of it(two control panels? Really half of the settings is via desktop control panel whilst the remaining half is in metro's system settings? A couple of bugs too, one where it takes forever to load to desktop after login and the other is the startmenu bug where it fails to load startmenu and have to do workarounds to get it working...other than those three complaints, I would have been fine with 10). So went back to 7...skipped 8/8.1 because that felt more targeted towards touchscreens and I don't have one(and yes I've played with 8 and 8.1 for just about a year)....plus I will most likely still use keyboard + mouse over touchscreen if I had one anyways.....
bjornl :
Windows XP is crash prone. The 64bit version you are using is even more so.
Oh well it was perfectly stable with my other XP builds....I didn't think this build would be any different....
bjornl :
64bit on XP is a total crap shoot. Drivers can and do fail for no obvious reason. The requirements to get a driver signed on XP was far easier, and so the quality level was lower. Plus almost no one used 64bit and so very little effort was put in to that by 3rd party developers.
mmmmmmh.... Well 64-bit XP was built from win2k3 x64 OS, rather than XP x86 and just adding bits and pieces to it so that it complies to x64 OS, so it should be just as stable as that server OS.... Hm, well I can see why the complaints, I have a Razer Ouroborus and Razer refused to make Synapse or even a standalone driver for XP 64-bit....so I'm left in the dust with that one...
bjornl :
In this case I suspect that your AV is the cause not the TCP driver. Kaspersky uses a filter driver which interacts with tcpip.sys and given the CRAP OS you are running expecting a modern program on a barely tested platform set up in the worst possible configuration. I'd say you should expect crashes, viruses, loss of personal info and so on. Also you need to disable the kaspersky NDIS 6 filter from your local area connection properties; this will make your PC even less secure but it might make it slightly more stable.
I thought XP was the most stable and liked OS of MS.....is that not the reason why it's lasted the longest in OS history?
Well the modern program has support for XP 64-bit, otherwise I wouldn't have installed it..... I'll try that suggestion if I get another BSOD from that TCPIP.sys driver....
bjornl :
The other possibility is that you have a virus. XP is so ridiculously unsecured that you are prone to any and all virus out there. Perhaps you got one which detected XP and assumed 32bit and damaged your system in some unexpected way as a result.
Impossible, I've scanned the system fully with KIS 2016, Malwarebytes Anti-Malware, SUPERAntiSpyware and Spybot Search and Desotry and it came clean a couple of months ago when I did it, I also haven't used the computer since then to until now when I felt like playing some games on my tower....
I thought 32-bit viruses can't affect 64-bit operating systems........so you're essentially safe until you get hit with one that's made for 64-bit OSs.....
Actually a testimonial on that: I had a 32-bit winXP build that was just bare, no virus/malware protection programs running, nothing - so no bloatware and such, just the bare OS + drivers and that's it(I believe I only had like 25 or so processes running, I also disabled some services and stuff to maximize performance as it was running on fairly old hardware)! It was also connected to the internet and was only meant to play the older games that wouldn't run on newer OSs. It also ran for a few years. Surprisingly, it didn't get hit with a virus/malware, or there was no symptoms that I could see of anyways....and if it did get hit with one, it's got nothing of value, just some save files that I may or may not try to recover and re-install OS. Done, fresh system ready to be infected! hahahaha
bjornl :
The 3rd possibility (and least likely) is the driver. Given that the drivers say 'Microsoft' they are most certainly in box drivers (meaning included with the OS). So you can't re-install THOSE drivers unless you feel like doing a repair install of the OS. But if you use an add-on NIC and happen to still have the drivers for it, might be worth trying to re-install them.
I don't think I use the generic MS drivers, I only use them if there is no proper dedicated ones from the hardware's manufacturer, or if there's a problem with it....
Nah, no addon NIC, just the onboard one which is enough for me. ☺
Facebook
Twitter
Instagram