Hey fags, I've been getting pic related with every single torrent client except
for vuze. It usually happens about 5-8 minutes after starting a torrent, and yet
this only happens to clients besides shitty ass vuze. I've tried qbitorrent,
utorrent 2.2.1, deluge, and transmission qt. I've read that it's a driver issue,
but I recently upgraded my machine with a new mobo, ram, and cpu. This happened
before that upgrade, and still happens now. I kind of doubt it's a problem with my
gpu/harddrives/peripherals. Any ideas on a fix or a torrent client that might work?
I was also wondering if there were any cancer free older versions of Azurues/Vuze,
seeing as it's the only working client I've tried. I guess I could try Tixati?
>>17108928
Step 1: open cmd.
Step 2: delete system 32
Step 3: obtain a good linux distro
Step 4: get linux
Step 5: marvel at how linux has no viruses/bugs
Step 6: marvel at how linux isnt a botnet or used to spy on you by NSA
>>17108958
Bud I'm just a student who got this shit for free, I'd love to use Linux but I don't have the time, tried putting lubuntu on a shitty hp netbook for fun, was pretty cool. But really do you know of any good older versions of azureus?
>>17108928
This error is basically saying something went wrong in memory which shouldn't be even used.
That means something low level went bad:
drivers
OS itself
hardware
So you have few possible solutions:
Reinstall OS aka Windows. This can solve your problem if your drivers are bad.
If it is OS problem, then MS can fix it next Wednesday or most likely never.
If reinstall doesn't help, your hardware is slowly dieing.
My bet (since you told us it is happening when torrent) are drivers for ethernet or wifi card are the cause.
>new mobo (motherboard?)
-> mobo usually have network card integrated, check drivers for that.
>>17109021
Well I have been using pic related for both my old pc and the current one, so this could definitely have something to do with it.
>>17109067
If you'd bothered to use google before posting here, you'd see that this isn't an unusual problem due to bad network drivers on Windows 10.
You can see if there are other drivers you can get that will be more stable, use your on-board ethernet connector on your computer (you can find cheap wifi routers to bridge ethernet to your existing wifi network if you have to use wifi to get to the internet), or try a different wifi adapter.
