BSOD while downloading torrents - system crashes every time

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 7 x64
       #1

    BSOD while downloading torrents - system crashes every time


    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:

    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001930675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: netio.sys (NETIO!NetioCompleteNetBufferAndNetBufferListChain+0x55)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001930675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\drivers\netio.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880018BB675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800179C675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001797675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001909675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001823675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800191E675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001931675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001808675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    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: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800190C675)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    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.


    Conclusion
    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.
      My Computer


  2. Posts : 245
    Win7
       #2

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


  3. Posts : 11
    Windows 7 x64
    Thread Starter
       #3

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


  4. Posts : 245
    Win7
       #4

    No what you download?
      My Computer


  5. Posts : 11
    Windows 7 x64
    Thread Starter
       #5

    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????
      My Computer


  6. Posts : 245
    Win7
       #6

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


  7. Posts : 1,454
    Windows 7 ultimate x64
       #7

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


  8. Posts : 11
    Windows 7 x64
    Thread Starter
       #8

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


  9. Posts : 2,913
    Windows 7 Ultimate x64 SP1
       #9

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


  10. Posts : 1,454
    Windows 7 ultimate x64
       #10
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:11.
Find Us