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.

Windows Vista Dump data [NTFS_FILE_SYSTEM (24)]

Discussion in 'Legacy Windows' started by thenut68, 2009/03/14.

  1. 2009/03/14
    thenut68

    thenut68 Inactive Thread Starter

    Joined:
    2009/03/14
    Messages:
    2
    Likes Received:
    0
    hello I was hoping somebody could make sense of
    this debugging data It looks like Greek to me
    thanks


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


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

    Symbol search path is: SRV*c:\websymbols*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.18145.x86fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0x8244a000 PsLoadedModuleList = 0x82561c70
    Debug session time: Thu Mar 12 07:20:48.327 2009 (GMT-5)
    System Uptime: 0 days 0:00:20.155
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1904aa, 8c34f6d4, 8c34f3d0, 8b891d4a}

    Probably caused by : Ntfs.sys ( Ntfs!NtfsAddRecentlyDeallocated+a9 )

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

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

    NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
    Arguments:
    Arg1: 001904aa
    Arg2: 8c34f6d4
    Arg3: 8c34f3d0
    Arg4: 8b891d4a

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


    EXCEPTION_RECORD: 8c34f6d4 -- (.exr 0xffffffff8c34f6d4)
    ExceptionAddress: 8b891d4a (Ntfs!NtfsAddRecentlyDeallocated+0x000000a9)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 00000020
    Attempt to read from address 00000020

    CONTEXT: 8c34f3d0 -- (.cxr 0xffffffff8c34f3d0)
    eax=882e5730 ebx=00000000 ecx=00000000 edx=00000000 esi=8c34fa3c edi=882e5418
    eip=8b891d4a esp=8c34f79c ebp=8c34f7d8 iopl=0 nv up ei pl nz na po cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
    Ntfs!NtfsAddRecentlyDeallocated+0xa9:
    8b891d4a 8b4320 mov eax,dword ptr [ebx+20h] ds:0023:00000020=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    EXCEPTION_PARAMETER1: 00000000

    EXCEPTION_PARAMETER2: 00000020

    READ_ADDRESS: GetPointerFromAddress: unable to read from 82581868
    Unable to read MiSystemVaType memory at 82561420
    00000020

    FOLLOWUP_IP:
    Ntfs!NtfsAddRecentlyDeallocated+a9
    8b891d4a 8b4320 mov eax,dword ptr [ebx+20h]

    FAULTING_IP:
    Ntfs!NtfsAddRecentlyDeallocated+a9
    8b891d4a 8b4320 mov eax,dword ptr [ebx+20h]

    BUGCHECK_STR: 0x24

    DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER: from 8b851ade to 8b891d4a

    STACK_TEXT:
    8c34f7d8 8b851ade 00000000 06be8000 00000000 Ntfs!NtfsAddRecentlyDeallocated+0xa9
    8c34fa70 8b853eb8 875530b0 882e5498 00000000 Ntfs!NtfsScanEntireBitmap+0x16a
    8c34fab4 8b8534c1 875530b0 882e5498 07b087db Ntfs!NtfsInitializeClusterAllocation+0x4d
    8c34fca0 8b8a0963 875530b0 8765d510 8c34fcc0 Ntfs!NtfsMountVolume+0x1779
    8c34fcc4 8b81303e 875530b0 8765d510 07b0863f Ntfs!NtfsCommonFileSystemControl+0x80
    8c34fd44 82482445 00000000 00000000 84f73d78 Ntfs!NtfsFspDispatch+0x264
    8c34fd7c 8261fb18 875530b0 5d337253 00000000 nt!ExpWorkerThread+0xfd
    8c34fdc0 82478a2e 82482348 00000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: Ntfs!NtfsAddRecentlyDeallocated+a9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Ntfs

    IMAGE_NAME: Ntfs.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47918a96

    STACK_COMMAND: .cxr 0xffffffff8c34f3d0 ; kb

    FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsAddRecentlyDeallocated+a9

    BUCKET_ID: 0x24_Ntfs!NtfsAddRecentlyDeallocated+a9

    Followup: MachineOwner
    ---------
     
  2. 2009/03/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Welcome to WindowsBBS :)

    Yes, geek to most of us too, so the usual rider .....
    However there is sufficient info there that is possibly allied to either a drive problem or memory problem - I suggest you check out both.

    Check the drive with the drive manufacturer's disk diagnostic software ......

    Disk Diagnostic Software ....

    ExcelStore

    Hitachi/IBM

    Samsung

    Seagate, Maxtor, Quantum

    Western Digital

    Alternatively run chkdsk /r - a data backup is good insurance before doing this.

    Check out the memory, noting first ....
    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.
     

  3. to hide this advert.

  4. 2009/03/14
    thenut68

    thenut68 Inactive Thread Starter

    Joined:
    2009/03/14
    Messages:
    2
    Likes Received:
    0
    wd data life guard

    i ran the data life guard and it said there were errors on the disk

    then the repair failed due to errors

    it said i should contact wd support
     
  5. 2009/03/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    I would contact WD, but before you do so you you should back up all your data to an external source - USB hard drive, DVD/CD and check that you have all the installation media for your software, including the OS.
     

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.