locked
How to solve the BlueScreen problem? RRS feed

  • Question

  • Hello there, thanks for reading this.
    I recently cannot configure the TCP/IP settings, because I got a bluescreen error as long as click the "OK" after filling the IP address, default gateway and DNS server. I've saved the error code, however, they were not always the same, for instance, once it was 0xD1(driver_irql_not_less_or_equal), another was BAD_POOL_HEADER,...
    So could anyone help me with this problem? The OS is Windows Vista Ultimate with SP1 (6001). (By the way, my another system of Widows 7 RC also got this!)
    Any help is appreciated!
    Here is one of the dump information(analyzed by windbg):

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

    Symbol search path is: SRV*C:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
    Machine Name:
    Kernel base = 0x82804000 PsLoadedModuleList = 0x8291bc70
    Debug session time: Thu Jul 30 09:21:37.378 2009 (GMT+8)
    System Uptime: 0 days 0:07:07.146
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {927f0000, 0, 828b9693, 0}

    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    Probably caused by : tcpipreg.sys ( tcpipreg!TcpipRegCheckUpdateRegistryValue+2d4 )

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

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: 927f0000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 828b9693, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000000, (reserved)

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 8293b868
    Unable to read MiSystemVaType memory at 8291b420
     927f0000

    FAULTING_IP:
    nt!memcpy+33
    828b9693 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  explorer.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  b70a88a0 -- (.trap 0xffffffffb70a88a0)
    ErrCode = 00000000
    eax=927d7246 ebx=927d7238 ecx=3fff9c91 edx=00000002 esi=927f0000 edi=8957eaa8
    eip=828b9693 esp=b70a8914 ebp=b70a891c iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!memcpy+0x33:
    828b9693 f3a5            rep movs dword ptr es:[edi],dword ptr [esi]
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 8285eb54 to 828a90f5

    STACK_TEXT: 
    b70a8888 8285eb54 00000000 927f0000 00000000 nt!MmAccessFault+0x10a
    b70a8888 828b9693 00000000 927f0000 00000000 nt!KiTrap0E+0xdc
    b70a891c 9cbd295a 89565cf0 927d7248 fffffffe nt!memcpy+0x33
    b70a894c 9cbd2e27 9de7e9d8 800012a4 9cbd5560 tcpipreg!TcpipRegCheckUpdateRegistryValue+0x2d4
    b70a8994 84d56ec1 8c131f9c 00000001 8c131fb0 tcpipreg!TcpipRegUpdateRegistryValue+0x15d
    b70a8a00 84d56d7a 8c131f9c 00000001 8c131fb0 NETIO!NsipWritePersistentData+0x443
    b70a8a5c 8e9f1551 00000001 b319ef64 00000000 NETIO!NsiSetAllParametersEx+0x164
    b70a8aa8 8e9f1eb8 00000000 8c131fc0 8c131fe8 nsiproxy!NsippSetAllParameters+0x1b1
    b70a8acc 8e9f1f91 b319ef01 00000000 927f6220 nsiproxy!NsippDispatchDeviceControl+0x88
    b70a8ae4 82ae66be 8d4ca868 b319ef48 b319ef48 nsiproxy!NsippDispatch+0x33
    b70a8b08 828bff8a b319efdc 00000014 8d4ca868 nt!IovCallDriver+0x23f
    b70a8b1c 8e43efc7 00000000 00000014 076ae6d4 nt!IofCallDriver+0x1b
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b70a8bc8 8e43f586 8d5be520 b319ef48 b319efdc kl1+0x3afc7
    b70a8c0c 82ae66be 8d5be468 00000028 acf325f0 kl1+0x3b586
    b70a8c30 828bff8a b319efdc b319ef48 8d5be468 nt!IovCallDriver+0x23f
    b70a8c44 82a505e5 acf325f0 b319ef48 b319efdc nt!IofCallDriver+0x1b
    b70a8c64 82a50d8a 8d5be468 acf325f0 076ae600 nt!IopSynchronousServiceTail+0x1d9
    b70a8d00 82a3aa5d 8d5be468 b319ef48 00000000 nt!IopXxxControlFile+0x6b7
    b70a8d34 8285ba1a 000007cc 00000e00 00000000 nt!NtDeviceIoControlFile+0x2a
    b70a8d34 77069a94 000007cc 00000e00 00000000 nt!KiFastCallEntry+0x12a
    076ae610 00000000 00000000 00000000 00000000 0x77069a94


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    tcpipreg!TcpipRegCheckUpdateRegistryValue+2d4
    9cbd295a 8b430c          mov     eax,dword ptr [ebx+0Ch]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  tcpipreg!TcpipRegCheckUpdateRegistryValue+2d4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: tcpipreg

    IMAGE_NAME:  tcpipreg.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  479190f7

    FAILURE_BUCKET_ID:  0x50_VRF_tcpipreg!TcpipRegCheckUpdateRegistryValue+2d4

    BUCKET_ID:  0x50_VRF_tcpipreg!TcpipRegCheckUpdateRegistryValue+2d4

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

    Thursday, July 30, 2009 5:10 AM

Answers

  • Hi, to troubleshoot BSOD crash issues, we need to debug the crashed system dump (including the minidump in the post). Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. 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


    Sean Zhu - MSFT
    • Marked as answer by ZQq_Eric Monday, August 3, 2009 7:42 AM
    Friday, July 31, 2009 6:57 AM
    Moderator