BSOD while downloading torrents - system crashes every time

[johnjames2]

Dear Administrators,

I am accustomed to downloading torrents, but my computer suddenly crashes every time I try. I didn't install Windows updates or any new software prior to this happening... the only thing is my antivirus (Avast) updates automatically.

I've completely removed Avast, installed MSFT Security Essentials, and have downloaded all new networking drivers. I've also unstalled UTorrent completely and reinstalled. Nothing helps. Any suggestions?

This problem is costing me an incredible amount of time (and insanity) to fix...


Also, WHOCrashed report included below:

[FONT=Segoe UI, Arial]On Mon 7/30/2012 3:02:11 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-15818-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001930675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 3:02:11 AM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]netio.sys[/FONT] (NETIO!NetioCompleteNetBufferAndNetBufferListChain+0x55)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001930675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\drivers\netio.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 2:58:32 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-19562-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 2:36:31 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-14118-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880018BB675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 2:15:55 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-18392-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800179C675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 1:31:55 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-18657-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001797675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 7/30/2012 1:00:26 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-23134-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 11:04:07 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-17019-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001909675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 10:42:00 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-23821-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 10:38:03 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-20264-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001823675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 10:35:19 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-21122-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 10:32:29 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-19359-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800191E675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 10:00:42 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-22838-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001931675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 9:44:05 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-26551-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 7/29/2012 8:24:23 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\072912-23041-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800190C675)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]18 crash dumps have been found and analyzed. Only 15 are included in this report. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
[/FONT]

 

[KimJong]

Can you give example of torrent you downloading so we can make sure not torrent?

 

[johnjames2]

Uh... not sure what you mean. UTorrent, BitTorrent and Vixtrola all cause the system to crash, but from researching similar problems, this seems to be a driver problem and not necessarily related to the torrent software.

 

[KimJong]

No what you download?

 

[johnjames2]

This has absolutely nothing to do with the problem we're discussing. Whether it's freeware or hard to find out-of-print non-copywritable books from the turn of the century, who cares????

 

[KimJong]

Need know if torrent problem...why so defensive?

 

[centaur78]

hi

Your dump all relate to NetIO.sys.... so BSOD's are more related to the networking..

Try reinstalling the latest drivers for the wireless and ethernet...depending on what your connecting to.

 

[johnjames2]

Thanks Centaur,

Drivers are all updated... since this was recommended on a different forum. People who are far more knowledgeable than I am are convinced it's a driver issue. But I've updated them and no luck, so I'm still hunting for the elusive answer.

BTW, I'm using Clearwire.

 

[kegobeer]

At least some of the problems are related to sptd.sys, which belongs to Daemon Tools. I would completely uninstall it and see if you continue to have BSODs.

 

[centaur78]

ok try disabling to IPv6 from your interfaces... you could follow this step...How to disable IP version 6 (IPv6) or its specific components in Windows 7, in Windows Vista, in Windows Server 2008 R2, and in Windows Server 2008

 

[kegobeer]

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.

 

[johnjames2]

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.

 

[centaur78]

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

 

[johnjames2]

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?

 

[centaur78]

Try running with administrative privilege.

if not you could open up even viewer and save the respective Application ans System logs..

 

[johnjames2]

Could've sworn I did that... er, must be 'user error.' :0)

Anyway, here you go. Any advice is really, really appreciated.

 

[centaur78]

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

 

[johnjames2]

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?

 

[centaur78]

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..

 

[johnjames2]

Here's what I see...