Getting a Blue Screen of Death Occasionally


  1. Posts : 1
    Windows 7 Ultimate 32bit
       #1

    Getting a Blue Screen of Death Occasionally


    During the last couple of months my computer has been crashing occasionally. Today I decided to create a minidump to see what is going on. I would really appreciate it if you guys can help me out in how to fix this problem. Thank you.




    Microsoft ® Windows Debugger Version 6.12.0002.633 X86
    Copyright © Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\071013-40997-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.22318.x86fre.win7sp1_ldr.130505-1535
    Machine Name:
    Kernel base = 0x82c39000 PsLoadedModuleList = 0x82d79230
    Debug session time: Wed Jul 10 22:47:16.772 2013 (UTC - 4:00)
    System Uptime: 0 days 4:04:58.472
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................................
    Loading User Symbols
    Loading unloaded module list
    .......................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {4, 2, 0, 8aced055}

    Unable to load image UrlFilter.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for UrlFilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for UrlFilter.sys
    Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+e )

    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: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8aced055, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82d9882c
    Unable to read MiSystemVaType memory at 82d78d80
    00000004

    CURRENT_IRQL: 2

    FAULTING_IP:
    NETIO!CalloutStreamDataInit+e
    8aced055 8b5004 mov edx,dword ptr [eax+4]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: IMF.exe

    LAST_CONTROL_TRANSFER: from 8aced522 to 8aced055

    STACK_TEXT:
    a01e3710 8aced522 857b92a0 85e15144 a01e3730 NETIO!CalloutStreamDataInit+0xe
    a01e3758 8aced8d4 a01e37f4 85e150c0 85e15128 NETIO!StreamInvokeCalloutAndNormalizeAction+0x2f
    a01e3788 8aced9ef a01e37f4 85e150c0 85e15128 NETIO!StreamCalloutProcessData+0x31
    a01e37c8 8acede55 a01e37f4 85e150c0 85e15128 NETIO!StreamCalloutProcessingLoop+0x55
    a01e3834 8acdbf5c 00000014 8d643ee0 00000000 NETIO!StreamProcessCallout+0x128
    a01e3898 8acc6b3e 00000014 86e8e9e0 85d727c8 NETIO!ProcessCallout+0x120
    a01e390c 8acc521f 00000014 86e8e9e0 85d727c8 NETIO!ArbitrateAndEnforce+0xae
    a01e3a1c 8acecadd 00000014 86e8e9e0 85d727c8 NETIO!KfdClassify+0x1c7
    a01e3aa8 8acee33d 000b67ad 00000014 86e8e9e0 NETIO!StreamInternalClassify+0x84
    a01e3b04 8ace9c87 00000014 85d726f0 85b9bb30 NETIO!StreamInject+0x13f
    a01e3b48 8ae7dc40 00002cae 00000000 0000015f NETIO!FwppStreamInject+0xde
    a01e3b80 a3dc0a8e 87d17dc8 00000000 00000000 fwpkclnt!FwpsStreamInjectAsync0+0x93
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a01e3bd4 a3dc0b68 00000d7c 00002cae 00000000 UrlFilter+0x1a8e
    a01e3bfc 82c68045 870e4618 86d86f68 86d86f68 UrlFilter+0x1b68
    a01e3c14 82e3d8ec 8709c950 86d86f68 86d86fd8 nt!IofCallDriver+0x63
    a01e3c34 82e3fccf 870e4618 8709c950 00000000 nt!IopSynchronousServiceTail+0x1f8
    a01e3cd0 82e46ca1 870e4618 86d86f68 00000000 nt!IopXxxControlFile+0x6aa
    a01e3d04 82c6e846 00000680 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    a01e3d04 77307094 00000680 00000000 00000000 nt!KiSystemServicePostCall
    0dc4eb90 00000000 00000000 00000000 00000000 0x77307094


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NETIO!CalloutStreamDataInit+e
    8aced055 8b5004 mov edx,dword ptr [eax+4]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: NETIO!CalloutStreamDataInit+e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: NETIO

    IMAGE_NAME: NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 5189bf39

    FAILURE_BUCKET_ID: 0xD1_NETIO!CalloutStreamDataInit+e

    BUCKET_ID: 0xD1_NETIO!CalloutStreamDataInit+e

    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    To receive best possible help,
    Please follow:
    Blue Screen of Death (BSOD) Posting Instructions
      My Computer


 

  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 15:09.
Find Us