none
BSOD when running Bittorrent after Windows 7 Service Pack 1 Install

    Question

  • I've run bittorrent regularly on this system.  Around March 26 I installed SP1 and ever since then I get a BSOD shortly after starting bittorrent.  I don't use it that often so I haven't tried to deal with it until now.  So far I've run sfc /scannow, windows memory test, memtest86 for several passes and checked my hard drive for errors - all with no errors or problems.

    I've opened the .dmp files with windows debugger (see below) and see that it is netio.sys.  I've updated all the drivers (driveragent was a big help in identifying them).  Mainly, I've updated both the motherboard chipset drivers and Realtek NIC driver to the latest and greatest - still get BSOD.  Keep in mind that everything was fine before installing Service Pack 1 so I think it introduced something.

     


    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [D:\041611-59342-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`03a67000 PsLoadedModuleList = 0xfffff800`03cace90
    Debug session time: Sat Apr 16 21:02:15.426 2011 (UTC - 4:00)
    System Uptime: 0 days 1:01:06.361
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {28, 2, 0, fffff880015b0b2d}

    Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880015b0b2d, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d180e8
     0000000000000028

    CURRENT_IRQL:  2

    FAULTING_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`015b0b2d 448b5228        mov     r10d,dword ptr [rdx+28h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff880085de7f0 -- (.trap 0xfffff880085de7f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880085dea10 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880015b0b2d rsp=fffff880085de980 rbp=fffff880085deab0
     r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
    r11=fffffa800cf86d90 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    NETIO!RtlCopyBufferToMdl+0x1d:
    fffff880`015b0b2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:744e:00000000`00000028=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80003ae6be9 to fffff80003ae7640

    STACK_TEXT: 
    fffff880`085de6a8 fffff800`03ae6be9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`085de6b0 fffff800`03ae5860 : 00000000`00000000 00000000`00000000 000067ee`eaf48ef4 00000000`00000044 : nt!KiBugCheckDispatch+0x69
    fffff880`085de7f0 fffff880`015b0b2d : 00000000`00000000 00000000`00000000 fffff880`085dea10 00000000`00000008 : nt!KiPageFault+0x260
    fffff880`085de980 fffff880`016d25ec : fffff880`085de960 fffff880`016a1376 00000000`00000001 fffffa80`0b36e180 : NETIO!RtlCopyBufferToMdl+0x1d
    fffff880`085de9e0 fffff880`0169e963 : fffffa80`0cf86d90 00000000`00000001 fffffa80`11b9c2e0 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d6ef
    fffff880`085dea50 fffff880`0168cd54 : fffffa80`0d114a70 00000000`000022f7 fffff880`085def48 fffffa80`0b052000 : tcpip!TcpTcbCarefulDatagram+0x543
    fffff880`085dec00 fffff880`0168b5ea : fffffa80`0af45e80 fffff880`01683a00 fffffa80`0af01cb8 00000000`00000000 : tcpip!TcpTcbReceive+0x724
    fffff880`085dedf0 fffff880`0168d2ab : fffff880`08247cd2 fffffa80`0b052000 00000000`00000000 fffff880`085df100 : tcpip!TcpMatchReceive+0x1fa
    fffff880`085def40 fffff880`01684137 : fffffa80`0af45e80 fffffa80`0af422f7 fffffa80`000052da 00000000`000052da : tcpip!TcpPreValidatedReceive+0x36b
    fffff880`085df010 fffff880`01683caa : 00000000`00000000 fffff880`01793800 fffff880`085df1d0 fffff880`012a5d80 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`085df0d0 fffff880`016832a9 : 00000000`00000000 00000000`00000000 fffff880`00000000 fffff880`085df1c0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`085df170 fffff880`01680fff : 00000000`00000000 00000000`0c70a000 fffff880`01793800 fffff880`01793800 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`085df250 fffff880`016805f2 : fffffa80`0c70e280 00000000`00000000 fffffa80`0c70a000 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`085df450 fffff880`016f475a : fffffa80`0ae4d6a8 fffff880`00df283a fffffa80`0c70a010 fffffa80`0a02ed04 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`085df530 fffff800`03af4078 : 00000000`001e8480 fffffa80`0a02ed80 fffffa80`0d1c8b60 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x56e52
    fffff880`085df580 fffff880`01680152 : fffff880`0167f9b0 00000000`00000000 00000000`00000000 fffff880`085df601 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`085df660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`015b0b2d 448b5228        mov     r10d,dword ptr [rdx+28h]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: NETIO

    IMAGE_NAME:  NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

    BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

    Followup: MachineOwner
    ---------

     

    Sunday, April 17, 2011 1:14 AM

Answers

  • Disable all security softwares, update all possible drivers / firmwares, uninstall all unwanted applications and check BSODs disappear. Also, use memtest86+ to check that all is okay with your RAM.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011

    Microsoft Certified Professional

    Microsoft Certified Systems Administrator: Security

    Microsoft Certified Systems Engineer: Security

    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows 7, Configuring

    Microsoft Certified IT Professional: Enterprise Administrator

     


    • Marked as answer by Herschel Friday, June 3, 2011 12:51 AM
    Thursday, June 2, 2011 8:05 PM

All replies

  • Here are all the BSOD memory dumps - they're all for the same reason.  It's the first time I've seen BSOD in a while.

     

    http://cid-5dcd500dbf239889.office.live.com/self.aspx/.Public/debug%20files.zip

     

     

    Sunday, April 17, 2011 1:17 AM
  • I have checked all the dump files. The reason
    caused BOSD is NETIO.SYS.

    NETIO.sys indicates an issue with the network
    drivers. Please update your network driver, wireless driver, also update your
    BIOS to the latest version.


    Seven




    • Proposed as answer by kubilayelmas Thursday, April 21, 2011 2:49 PM
    • Marked as answer by Leo HuangModerator Monday, April 25, 2011 7:05 AM
    • Unmarked as answer by Herschel Tuesday, April 26, 2011 2:19 AM
    • Unproposed as answer by Herschel Tuesday, April 26, 2011 2:19 AM
    Monday, April 18, 2011 9:04 AM
  • Hi,

     

    Did your issue solved? Please feel free to give me any update.

     

    Thanks.

     

    Regards, 

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, April 21, 2011 9:48 AM
    Moderator
  • Hi,

     

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, April 25, 2011 7:05 AM
    Moderator
  • Sevin,

    As I mention in my original post, I've updated all drivers, especially the network (NIC) driver, to the latest version.  That's not a problem, unless a driver was included in SP1 which is about when this was introduced.

    Thanks for the idea - but I already tried updated everything after reading posts about other issues with netio.sys.  The system hasn't crashed in the weeks since my original posting.  I just started Bittorrent and within 10 minutes I got BSOD again.  It seems to have something to do with heavy load placed on the network adapter.

    Tuesday, April 26, 2011 2:22 AM
  • Leo,

    Unfortunately the problem isn't solved.  The proposed solution to just update the drivers was done before I posted the original question. 

    Hopefully someone will have more ideas of how to determine the exact problem netio.sys is having.  This started right after I installed SP1.  The configuration worked fine for many months before the installation of SP1 so I can helped but think it's something associated with SP1 or perhaps other updates I did at that time.  I did have an issue installed SP1 and had to go through the troubleshooting steps provided by MSFT for issues installing SP1.  I don't recall exactly the procedure I followed but it seemed to be comon enough for MSFT to post an article for it.

    Thanks

    Herschel

    Tuesday, April 26, 2011 2:27 AM
  • Hi,

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Thank you for your understanding.

     

     

    Regards,

    Leo   Huang

     

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, April 26, 2011 6:29 AM
    Moderator
  • DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880017b1b2d, address which referenced memory
    Debugging Details:
    ------------------
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fa0e8
     0000000000000028 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`017b1b2d 448b5228        mov     r10d,dword ptr [rdx+28h]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff880033a07f0 -- (.trap 0xfffff880033a07f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880033a0a10 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880017b1b2d rsp=fffff880033a0980 rbp=fffff880033a0ab0
     r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
    r11=fffffa8016d1db10 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    NETIO!RtlCopyBufferToMdl+0x1d:
    fffff880`017b1b2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:0010:00000000`00000028=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800036c8be9 to fffff800036c9640
    STACK_TEXT:  
    fffff880`033a06a8 fffff800`036c8be9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`033a06b0 fffff800`036c7860 : fffffa80`0ae66af0 fffff880`0186bdd2 fffffa80`0b29c5d0 00000000`00000044 : nt!KiBugCheckDispatch+0x69
    fffff880`033a07f0 fffff880`017b1b2d : ffff0000`02acf95a 00000000`00000001 00000000`00000000 fffff880`017bdb14 : nt!KiPageFault+0x260
    fffff880`033a0980 fffff880`018af5ec : fffff880`033a0960 fffff880`0187e376 00000000`00000001 fffffa80`1778d010 : NETIO!RtlCopyBufferToMdl+0x1d
    fffff880`033a09e0 fffff880`0187b963 : fffffa80`16d1db10 00000000`00000001 fffffa80`128773d0 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d6ef
    fffff880`033a0a50 fffff880`01869d54 : fffffa80`12b15980 00000000`00004edc fffff880`033a0f48 fffffa80`0b05f000 : tcpip!TcpTcbCarefulDatagram+0x543
    fffff880`033a0c00 fffff880`018685ea : fffffa80`0af2a960 fffff880`01860a00 fffffa80`0af01718 00000000`00000000 : tcpip!TcpTcbReceive+0x724
    fffff880`033a0df0 fffff880`0186a2ab : fffff880`08932052 fffffa80`0b05f000 00000000`00000000 fffff880`033a1100 : tcpip!TcpMatchReceive+0x1fa
    fffff880`033a0f40 fffff880`01861137 : fffffa80`0af2a960 fffffa80`0af24edc fffffa80`000052da 00000000`000052da : tcpip!TcpPreValidatedReceive+0x36b
    fffff880`033a1010 fffff880`01860caa : 00000000`00000000 fffff880`01970800 fffff880`033a11d0 fffffa80`17869590 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`033a10d0 fffff880`018602a9 : 00000000`00000000 fffffa80`0cf95000 00000000`00000000 fffff880`033a11c0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`033a1170 fffff880`0185dfff : 00000000`00000000 00000000`0c4ebb00 fffff880`01970800 fffff880`01970800 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`033a1250 fffff880`0185d5f2 : fffffa80`0c522970 00000000`00000000 fffffa80`0c4ebb00 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`033a1450 fffff880`018d175a : 00000000`00000001 00000000`00000014 fffffa80`0c4ebba0 fffff880`0110bf4f : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`033a1530 fffff800`036d6078 : fffffa80`0af2d858 00000000`00000000 fffffa80`0a0771a0 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x56e52
    fffff880`033a1580 fffff880`0185d152 : fffff880`0185c9b0 fffffa80`0ae6a2f0 00000000`00000000 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`033a1660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`017b1b2d 448b5228        mov     r10d,dword ptr [rdx+28h]
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NETIO
    IMAGE_NAME:  NETIO.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381
    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d
    BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d
    Followup: MachineOwner
    ---------
    ____________________________________________________________________
    Bug Check Code 0xD1: The DRIVER_IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x000000D1. This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    As your Windows is SP1 there should be no new hotfix for the problem. What I recommand is that you contact your manufacturer Technical Support as this seems to be a problem with drivers.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    • Marked as answer by Leo HuangModerator Monday, May 2, 2011 1:19 AM
    • Unmarked as answer by Herschel Thursday, June 2, 2011 7:57 PM
    Tuesday, April 26, 2011 6:48 AM
  • Hi Herschel,

     

    Did your issue solved by the suggestion of Mr X? Please feel free to give me any update.

     

    Thanks.

     

    Regards, 

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, April 28, 2011 5:19 AM
    Moderator
  • Hi,

     

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, May 2, 2011 1:19 AM
    Moderator
  • No, the problem is still not fixed.  I've been in contact with Realtek support.  They had me update the driver and send dumps.  They say the problem is with netio.sys. 

     

    The problem is with the large number of open connections associated with bittorrent.  If I throttle the maximum number of connections in the bittorrent client down to 10 I seem to have no problem.  If I have it at 50 I have a problem.  Prior to SP1 I'd typically have it at 600 or so.  It seems that the driver is associated with the 3/21/2011 Realtek NIC driver that came as part of SP1.  I'm trying to figure out a way to install an older driver but deleting the driver and driver files from control panel still leaves me with the 3/21/2011 driver (I think because it comes with SP1).

    Wednesday, June 1, 2011 7:31 PM
  • Note that even at 10 connections I got BSOD after about nine hours.

    I downgraded to an older version of the NIC driver provided by Realtek and still get the BSOD.

    I've opened a case with Microsoft Support to further investigate the issue.

    Thursday, June 2, 2011 7:59 PM
  • Disable all security softwares, update all possible drivers / firmwares, uninstall all unwanted applications and check BSODs disappear. Also, use memtest86+ to check that all is okay with your RAM.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011

    Microsoft Certified Professional

    Microsoft Certified Systems Administrator: Security

    Microsoft Certified Systems Engineer: Security

    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows 7, Configuring

    Microsoft Certified IT Professional: Enterprise Administrator

     


    • Marked as answer by Herschel Friday, June 3, 2011 12:51 AM
    Thursday, June 2, 2011 8:05 PM
  • Here we are, almost a year later, and the problem is still unsolved. I bought a new G570 laptop from Lenovo with Windows Vista. Utorrent was working fine until Windows automatically updated itself (who knows what files it "updated") ... since then, every time I open utorrent I get a blue screen about 5-10 minutes later... very disappointed!!! I've been using Windows since I can remember and never had a problem until now. 
    Sunday, April 22, 2012 7:52 PM
  • I finally solved the same bluescreens in my system.

    For me the solution was to disable ipv6 through the registry. (disabling in Realtek driver was not enough)

    It seems there is some calling on an ipv6 function which causes these bluescreens.

    Of course only use this solution if you don't use or need ipv6...

    Edit:

    Fuggedabout it, bluescreen again just a few minutes after posting this :-(

    • Edited by jist Sunday, October 13, 2013 1:16 PM
    Sunday, October 13, 2013 12:53 PM