I don't think disabling IPv6 is going to help with the BSOD, especially if it's not being used by his router and/or any other application. If anything, the number of connections may be part of the BSOD problem. Since torrent software can be finicky at best, reducing the active connections to something lower than 100 (probably lower than 50) would be a start, after removing Daemon Tools of course.
Thanks... I tried limiting connections in UTorrent to 20 and tried to DL 1 single file. Still crashes.
This thing is driving me crazy. I've had no problems with torrents for years through 4 separate laptops, then all of a sudden bang - 3 days ago BSOD 100% of the time.
No windows updates or other software installation. It happened literally while I was watching "Where the Red Fern Grows" on YouTube. Before the movie, everything was fine. Afterwords, BSOD every single time.
I ran mem diagnostics too in case RAM was bad - but everything checks out. Doesn't seem to be hardware related at all.
Hi john
All the dumps you have provided here are minidump's pointing to Netio.sys whch is a network related issue.....
The best way to get a more clear picture of the BSOD is to either have a complete dump or a kernel dump.... which would atleast help us to see whats causing the problem.
You can change this by the following steps..
Click Start, and on the search type "view advanced system settings"
Under Startup and recovery select the write debugging information to either a complete memory dump if its available or Kernel memory dump
click ok and reboot for this to take effect..
The recreate the BSOD by using the utorrent and post the memory.dmp file here
Thank you Centaur,
Kernel Mem dump was available. I followed your instructions and tried to use the SF Diag Tool to create a new set of files, based on the kernel mem dump, which I could zip and attach for you. But I ran into significant issues. "Driver List" returned an error as did "Event Log" and some of the others too.
Perhaps I'm not doing this correctly?
Try running with administrative privilege.
if not you could open up even viewer and save the respective Application ans System logs..
Could've sworn I did that... er, must be 'user error.' :0)
Anyway, here you go. Any advice is really, really appreciated.
Hi John
the BSOD dumps you send me where minidumps as before...
you need to go in here %SystemRoot%\MEMORY.DMP
to get you kernel dump
I have the MEMORY.DMP file. It's too big to post here, even if I compress it.
I also have the SF Diagnostic tool. I'd like to use the SF Diagnostic tool on the MEMORY.DMP file, but I can't. I can open the MEMORY.DMP file with SF Diagnostics, but this doesn't allow me to run it as administrator, which means it doesn't work. If I run the SF Diagnostic tool as administrator, I can't specify the MEMORY.DMP file to analyze. It automatically selects minidump files.
Please... how do I get around this?
It sure is...because it would be same as your physical memory.
Try to see if you could open up the memory dump using the Bluescreen view by going into OPTIONS and selecting the first one and browsing to the place where you have the memory.dmp
Let me know what you see there..
Here's what I see...
Quote