locked
Blue Screen Error - Win 7 - dmp file RRS feed

  • Question

  • Hello everybody,

    I've got a brand new Dell Inspiron 14 and despite not having installed that many software onto it yet, I am getting the Blue Screen Error, which causes the machine to turn itself off. I've done a little research about it but wasn't able to identify the problem.

    If anyone could help me out I'd be really thankful!!

    here is the skydrive link for the crash dump file:

    https://skydrive.live.com/redir.aspx?cid=a2fcd3daba60a9e7&resid=A2FCD3DABA60A9E7!309&parid=A2FCD3DABA60A9E7!239

    Thank you in advance

    Thursday, February 2, 2012 4:51 AM

Answers

  • hey thank you for the reply.

    Ive uninstalled the newest version of Bittorrent and installed an older version, so far it is working properly!

    Before that, though, Ive had downloaded and installed all the latest versions of my machine's drivers and the problems didnt stop.

     

    any ideas on why would Bittorrent cause such issue? or is it not related to Bittorrent at all?

     

    thanks once again


    blue screen crash
    • Marked as answer by Arthur Xie Tuesday, February 21, 2012 6:05 AM
    Friday, February 3, 2012 5:50 PM

All replies


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


    Loading Dump File [C:\Users\v-miya\Desktop\020112-48157-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*c:\Symbols*http://msdl.microsoft.com/download/symbols

    Executable search path is:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e64670
    Debug session time: Thu Feb  2 11:27:48.974 2012 (GMT+8)
    System Uptime: 0 days 0:37:37.239
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    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, fffff88001611b2d}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )

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

    2: 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: fffff88001611b2d, address which referenced memory

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    Unable to open image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4E02AAA35e9000\ntoskrnl.exe
    The system cannot find the file specified.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: NETIO

    FAULTING_MODULE: fffff80002c1f000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    0000000000000028

    CURRENT_IRQL:  0

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

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    LAST_CONTROL_TRANSFER:  from fffff80002c9b1e9 to fffff80002c9bc40

    STACK_TEXT: 
    fffff880`075fa3d8 fffff800`02c9b1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt+0x7cc40
    fffff880`075fa3e0 00000000`0000000a : 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`01611b2d : nt+0x7c1e9
    fffff880`075fa3e8 00000000`00000028 : 00000000`00000002 00000000`00000000 fffff880`01611b2d fffffa80`08fa3700 : 0xa
    fffff880`075fa3f0 00000000`00000002 : 00000000`00000000 fffff880`01611b2d fffffa80`08fa3700 00000000`00000000 : 0x28
    fffff880`075fa3f8 00000000`00000000 : fffff880`01611b2d fffffa80`08fa3700 00000000`00000000 00000000`00000000 : 0x2


    STACK_COMMAND:  .bugcheck ; kb

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

    SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  NETIO.SYS

    BUCKET_ID:  WRONG_SYMBOLS

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

    Issue may be caused by antivirus or the network adapter driver. The issue can also becaused by memory issues.

     


    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. ”
    Friday, February 3, 2012 11:47 AM
  • hey thank you for the reply.

    Ive uninstalled the newest version of Bittorrent and installed an older version, so far it is working properly!

    Before that, though, Ive had downloaded and installed all the latest versions of my machine's drivers and the problems didnt stop.

     

    any ideas on why would Bittorrent cause such issue? or is it not related to Bittorrent at all?

     

    thanks once again


    blue screen crash
    • Marked as answer by Arthur Xie Tuesday, February 21, 2012 6:05 AM
    Friday, February 3, 2012 5:50 PM
  •  
    Arthur had his symbols slightly wrong, the dump was 0xd1 referencing
    netio.sys,
     
     
    In this case we want to look at network related drivers (ex.
    AV/firewall, WLAN/LAN/WAN/VPN, etc...). In this case I found that you
    are running both AVG and McAfee. Running 2 or more AV applications
    simultaneously can cause these sorts of issues, so I would recommend
    choosing 1 and removing the other(s)...
     
    2: 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: fffff88001611b2d, address which referenced memory
     
    Debugging Details:
    ------------------
     READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ece100
     0000000000000028
     
    CURRENT_IRQL:  2
     
    FAULTING_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`01611b2d 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:  fffff880075fa520 -- (.trap 0xfffff880075fa520)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880075fa740 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001611b2d rsp=fffff880075fa6b0 rbp=fffff880075fa7e0
     r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
    r11=fffffa8005ecfcd0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    NETIO!RtlCopyBufferToMdl+0x1d:
    fffff880`01611b2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:25a0:00000000`00000028=????????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from fffff80002c9b1e9 to fffff80002c9bc40
     
    STACK_TEXT:
    fffff880`075fa3d8 fffff800`02c9b1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`075fa3e0 fffff800`02c99e60 : 00000000`00000001 fffff880`075fa670 fffffa80`057a9870 00000000`00000044 : nt!KiBugCheckDispatch+0x69
    fffff880`075fa520 fffff880`01611b2d : 00000000`00000032 fffff880`018edfec 00000000`0000000b fffffa80`061af468 : nt!KiPageFault+0x260
    fffff880`075fa6b0 fffff880`01975bac : 00000000`00000000 fffff880`01944906 00000000`00000001 fffff880`066a38f8 : NETIO!RtlCopyBufferToMdl+0x1d
    fffff880`075fa710 fffff880`01941ef3 : fffffa80`05ecfcd0 00000000`00000001 fffffa80`0c123230 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d5cf
    fffff880`075fa780 fffff880`01934d54 : fffff880`075fac38 fffffa80`00000029 fffffa80`0c123230 fffff880`016f9750 : tcpip!TcpTcbCarefulDatagram+0x543
    fffff880`075fa930 fffff880`0193367a : fffffa80`07c31c20 fffff880`0192bb34 fffffa80`07c0ab50 00000000`00000000 : tcpip!TcpTcbReceive+0x694
    fffff880`075faae0 fffff880`019352ab : fffff880`04b530fa fffffa80`07d66000 00000000`00000000 fffff880`075fae00 : tcpip!TcpMatchReceive+0x1fa
    fffff880`075fac30 fffff880`0192c1c7 : fffffa80`07c31c20 fffffa80`07c475ed fffffa80`00009283 00000000`00009283 : tcpip!TcpPreValidatedReceive+0x36b
    fffff880`075fad00 fffff880`0192bd3a : 00000000`00000000 fffff880`01a46800 fffff880`075faec0 fffffa80`0aa99010 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`075fadc0 fffff880`0192b339 : 00000000`00000000 fffffa80`0aa97010 fffffa80`0b75b010 fffff880`075faeb0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`075fae60 fffff880`019290af : 00000000`00000000 00000000`0865a000 fffff880`01a46800 fffff880`01a46800 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`075faf40 fffff880`019286a2 : fffffa80`08527240 00000000`00000000 fffffa80`0865a000 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`075fb140 fffff880`019a734a : 00000000`00000000 fffffa80`0bdab6c0 fffffa80`0865a010 00000000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`075fb220 fffff800`02ca8618 : fffffa80`0bd15ca0 fffff880`0161d6fa fffffa80`09464b60 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x55122
    fffff880`075fb270 fffff880`01928202 : fffff880`01927a60 fffffa80`0bc4a190 fffff880`01a4b900 fffff880`0192d401 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`075fb350 fffff880`017b60eb : fffffa80`0866f8d0 00000000`00000000 fffffa80`0858b1a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`075fb3c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`01611b2d 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
    ---------
     

    -- Mike Burr
    Interesting Reading on Technology and Finance
    Sunday, February 5, 2012 8:33 AM
  • *******************************************************************************
    *                                                                             *
    *                        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: fffff88001611b2d, address which referenced memory
    Debugging Details:
    ------------------
    READ_ADDRESS:  0000000000000028 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`01611b2d 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:  fffff880075fa520 -- (.trap 0xfffff880075fa520)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff880075fa740 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001611b2d rsp=fffff880075fa6b0 rbp=fffff880075fa7e0
     r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
    r11=fffffa8005ecfcd0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    NETIO!RtlCopyBufferToMdl+0x1d:
    fffff880`01611b2d 448b5228        mov     r10d,dword ptr [rdx+28h] ds:25a0:00000000`00000028=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002c9b1e9 to fffff80002c9bc40
    STACK_TEXT:  
    fffff880`075fa3d8 fffff800`02c9b1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`075fa3e0 fffff800`02c99e60 : 00000000`00000001 fffff880`075fa670 fffffa80`057a9870 00000000`00000044 : nt!KiBugCheckDispatch+0x69
    fffff880`075fa520 fffff880`01611b2d : 00000000`00000032 fffff880`018edfec 00000000`0000000b fffffa80`061af468 : nt!KiPageFault+0x260
    fffff880`075fa6b0 fffff880`01975bac : 00000000`00000000 fffff880`01944906 00000000`00000001 fffff880`066a38f8 : NETIO!RtlCopyBufferToMdl+0x1d
    fffff880`075fa710 fffff880`01941ef3 : fffffa80`05ecfcd0 00000000`00000001 fffffa80`0c123230 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x1d5cf
    fffff880`075fa780 fffff880`01934d54 : fffff880`075fac38 fffffa80`00000029 fffffa80`0c123230 fffff880`016f9750 : tcpip!TcpTcbCarefulDatagram+0x543
    fffff880`075fa930 fffff880`0193367a : fffffa80`07c31c20 fffff880`0192bb34 fffffa80`07c0ab50 00000000`00000000 : tcpip!TcpTcbReceive+0x694
    fffff880`075faae0 fffff880`019352ab : fffff880`04b530fa fffffa80`07d66000 00000000`00000000 fffff880`075fae00 : tcpip!TcpMatchReceive+0x1fa
    fffff880`075fac30 fffff880`0192c1c7 : fffffa80`07c31c20 fffffa80`07c475ed fffffa80`00009283 00000000`00009283 : tcpip!TcpPreValidatedReceive+0x36b
    fffff880`075fad00 fffff880`0192bd3a : 00000000`00000000 fffff880`01a46800 fffff880`075faec0 fffffa80`0aa99010 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`075fadc0 fffff880`0192b339 : 00000000`00000000 fffffa80`0aa97010 fffffa80`0b75b010 fffff880`075faeb0 : tcpip!IppProcessDeliverList+0x5a
    fffff880`075fae60 fffff880`019290af : 00000000`00000000 00000000`0865a000 fffff880`01a46800 fffff880`01a46800 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`075faf40 fffff880`019286a2 : fffffa80`08527240 00000000`00000000 fffffa80`0865a000 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`075fb140 fffff880`019a734a : 00000000`00000000 fffffa80`0bdab6c0 fffffa80`0865a010 00000000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`075fb220 fffff800`02ca8618 : fffffa80`0bd15ca0 fffff880`0161d6fa fffffa80`09464b60 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x55122
    fffff880`075fb270 fffff880`01928202 : fffff880`01927a60 fffffa80`0bc4a190 fffff880`01a4b900 fffff880`0192d401 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`075fb350 fffff880`017b60eb : fffffa80`0866f8d0 00000000`00000000 fffffa80`0858b1a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`075fb3c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`01611b2d 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
    ---------------------------------------------------------------------------------------
    Please start by that:
    • Update your NIC cards drivers
    • Disable all security softwares (You can try uninstalling them and installing MSE for just checking)

    If this does not help, proceed like that:

  • Update all possible drivers you have
  • Uninstall all unused programs
  • Run msconfig and disable all startup items / services except Microsoft ones
  • Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support

    You can also contact Microsoft CSS for assistance.



    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 Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

Sunday, February 5, 2012 12:14 PM