1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Restart XP

Discussion in 'Windows XP' started by hpbaxxter, 2008/11/17.

  1. 2008/11/17
    hpbaxxter

    hpbaxxter Inactive Thread Starter

    Joined:
    2008/11/17
    Messages:
    3
    Likes Received:
    0
    H i trouble with my XP and now i analysis with result. But i don't know what is it problem. Do you have hepl me with this?


    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Mon Nov 17 18:29:21.062 2008 (GMT+1)
    System Uptime: 0 days 0:11:29.671
    Loading Kernel Symbols
    .................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D4, {b9c1f938, ff, 1, 804e34dd}

    Unable to load image klif.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for klif.sys
    *** ERROR: Module load completed but symbols could not be loaded for klif.sys
    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

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

    SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (d4)
    A driver unloaded without cancelling lookaside lists, DPCs, worker threads, etc.
    The broken driver's name is displayed on the screen.
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    An attempt was made to access the driver at raised IRQL after it unloaded.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: b9c1f938, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 804e34dd, address which referenced memory

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


    WRITE_ADDRESS: b9c1f938

    CURRENT_IRQL: ff

    FAULTING_IP:
    nt!ExfInterlockedInsertTailList+d
    804e34dd 8910 mov dword ptr [eax],edx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0xD4

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 804e7586 to 804e34dd

    STACK_TEXT:
    f89898e4 804e7586 8055190c f8989948 81a64d58 nt!ExfInterlockedInsertTailList+0xd
    f89898f8 804ee00d 81a64d90 f89899e4 f89899dc nt!ExInitializeResourceLite+0x47
    f8989910 804f0ee0 81e752c8 81a09ce8 f8989948 nt!CcAllocateInitializeBcb+0x6e
    f898999c 8057a5a7 822a7c68 f89899dc 00004000 nt!CcPinFileData+0x194
    f8989a10 80584047 822a7c68 f8989a38 00004000 nt!CcPinMappedData+0xf4
    f8989a60 80583ff6 e1035b60 e30704e8 c4454f74 nt!CmpPinCmView+0x3d
    f8989a7c 8059d35d e1035b60 00099b88 e1035b60 nt!HvMarkCellDirty+0x6c
    f8989a9c 8059d3d2 e1035b60 002d3f70 e2b9bcb0 nt!CmpMarkKeyDirty+0xa2
    f8989ab4 8059d4f2 e1035b60 002d3f70 00000001 nt!CmpFreeKeyByCell+0x14
    f8989ae4 8059d76a e3a8dab0 f8989b7c f8989bf8 nt!CmDeleteKey+0x8c
    f8989b44 f594a3f9 80001d1c f594a3d2 80558cc0 nt!NtDeleteKey+0x138
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f8989b70 804df06b 80001d1c f8989c7c 804dd1fd klif+0xe3f9
    f8989b70 804dd1fd 80001d1c f8989c7c 804dd1fd nt!KiFastCallEntry+0xf8
    f8989bec 805c2aa4 80001d1c c0000365 00000000 nt!ZwDeleteKey+0x11
    f8989c7c 805ac6cd 0000206c 00000000 00000000 nt!IopDriverLoadingFailed+0x282
    f8989d4c 805a6ca8 0000206c 00000001 00000000 nt!IopLoadDriver+0x2c2
    f8989d74 804e47fe 0000206c 00000000 823c83c8 nt!IopLoadUnloadDriver+0x45
    f8989dac 8057dfed baa6dcdc 00000000 00000000 nt!ExpWorkerThread+0x100
    f8989ddc 804fa477 804e4729 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    804e3024-804e3027 4 bytes - nt!KiServiceTable+304
    [ 92 d8 64 80:12 9c 94 f5 ]
    804e3040-804e3043 4 bytes - nt!KiServiceTable+320 (+0x1c)
    [ 0f 86 57 80:b4 d0 94 f5 ]
    804e3050-804e3053 4 bytes - nt!KiServiceTable+330 (+0x10)
    [ b0 c3 64 80:74 9d 94 f5 ]
    804e3058-804e305f 8 bytes - nt!KiServiceTable+338 (+0x08)
    [ d5 f8 57 80 57 c4 64 80:68 e5 94 f5 10 9a 94 f5 ]
    804e3068-804e306b 4 bytes - nt!KiServiceTable+348 (+0x10)
    [ 7d 5d 58 80:cc c6 94 f5 ]
    804e3074-804e3077 4 bytes - nt!KiServiceTable+354 (+0x0c)
    [ 5b c8 62 80:c0 ac 94 f5 ]
    804e30d4-804e30d7 4 bytes - nt!KiServiceTable+3b4 (+0x60)
    [ 78 db 59 80:4a dd 94 f5 ]
    804e30e0-804e30e3 4 bytes - nt!KiServiceTable+3c0 (+0x0c)
    [ 10 51 5a 80:e0 e1 94 f5 ]
    804e30fc-804e30ff 4 bytes - nt!KiServiceTable+3dc (+0x1c)
    [ 27 55 57 80:48 a1 94 f5 ]
    804e3114-804e311f 12 bytes - nt!KiServiceTable+3f4 (+0x18)
    [ 31 e4 62 80 1b c6 5d 80:c4 e2 94 f5 f0 e3 94 f5 ]
    804e3124-804e3127 4 bytes - nt!KiServiceTable+404 (+0x10)
    [ 1e ae 58 80:92 aa 94 f5 ]
    804e3174-804e3177 4 bytes - nt!KiServiceTable+454 (+0x50)
    [ 23 c1 57 80:04 ab 94 f5 ]
    60 errors : !nt (804e3024-804e3177)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: LARGE

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

    BUCKET_ID: MEMORY_CORRUPTION_LARGE

    Followup: memory_corruption
    ---------

    kd> lmvm memory_corruption
    start end module name
    kd> lmvm memory_corruption
    start end module name
     
    hpbaxxter,
    #1
  2. 2008/11/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    hpbaxxter - Welcome to the Board :)

    Please be aware .....
    However your log references memory corruption and I suggest you test out your memory ....
    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2008/11/17
    markp62

    markp62 Geek Member Alumni

    Joined:
    2002/05/01
    Messages:
    4,012
    Likes Received:
    16
    markp62,
    #3
  5. 2008/11/24
    hpbaxxter

    hpbaxxter Inactive Thread Starter

    Joined:
    2008/11/17
    Messages:
    3
    Likes Received:
    0
    OK, I tesed memory with memtest. And the program freezen when run and test 3 invest bit 80808080 etc. Test1, test 2 is good but test 3 after cca 20 sec end because the memtest freezen.But i buy new memory but same problem may corrupt old or new RAM but i don's sure
     
    Last edited: 2008/11/24
    hpbaxxter,
    #4
  6. 2008/11/24
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    As I posted above - and will repeat .....
    If you replace the memory and the problem remains it is likely that there is a problem with the slots on the motherboard. New memory will not corrupt the ols - corruption is physical and applies to the modules in question.
     
    PeteC,
    #5
  7. 2008/11/24
    hpbaxxter

    hpbaxxter Inactive Thread Starter

    Joined:
    2008/11/17
    Messages:
    3
    Likes Received:
    0
    So you can tell me why is ok when i testing computer with spyware utily in safe mode. And computer not blue screen. But when i testing XP without safe mode it same. The XP fallen starup MWAV
     
    hpbaxxter,
    #6
  8. 2008/11/24
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I can only be guided by the dump data analysis you first posted which clearly stated memory corruption.

    If you are still blue screening post another dump data log from the latest blue screen.
     
    PeteC,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...