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.

Minidump 1-4

Discussion in 'Windows XP' started by rki, 2006/08/14.

  1. 2006/08/14
    rki

    rki Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    4
    Likes Received:
    0
    Hello all.
    I've read most thread pertaining to Minidump on the site. And, most of them are very helpful. Though I don't know whats wrong with my system but it frequently reboots itself on several occasions, like;

    - On a fresh Install of OS(not connected to the net)
    - Mostly when trying to surf on the internet(like when trying to open a new browser/tab)
    - On a 3days interval or so
    - On a regular basis now

    Moreover, I've ran Everest, Memtest86+ without any errors.
    Since, the forum dosen't support uploading attachments and I don't want to spam the forum with all my minidumps logs, so, I thought it's best it I'd upload them online.

    http://www.megaupload.com/?d=NOA60STD

    This contains all my minidumps.

    Thanks.
     
    rki,
    #1
  2. 2006/08/14
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Follow these instructions to post a Dump Data Log.

    You'll better post 2 or 3 dumps. Leave out the sections Unloaded modules: & start end module name from subsequent logs.
     
    Arie,
    #2


  3. to hide this advert.

  4. 2006/08/14
    rki

    rki Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    4
    Likes Received:
    0
    Minidump-1

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini081406-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 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 Aug 14 21:41:53.359 2006 (GMT+4)
    System Uptime: 0 days 0:32:26.958
    Loading Kernel Symbols
    .....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c000001d, bf827781, b91aa558, 0}

    Probably caused by : hardware ( win32k!vSolidFillRect1+f6 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c000001d, The exception code that was not handled
    Arg2: bf827781, The address that the exception occurred at
    Arg3: b91aa558, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

    FAULTING_IP:
    win32k!vSolidFillRect1+f6
    bf827781 8417 test byte ptr [edi],dl

    TRAP_FRAME: b91aa558 -- (.trap ffffffffb91aa558)
    ErrCode = 00000000
    eax=000002f5 ebx=00000068 ecx=ffffffff edx=000002fc esi=02000000 edi=020231cc
    eip=bf827781 esp=b91aa5cc ebp=b91aa5f0 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    win32k!vSolidFillRect1+0xf6:
    bf827781 8417 test byte ptr [edi],dl ds:0023:020231cc=00
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: firefox.exe

    MISALIGNED_IP:
    win32k!vSolidFillRect1+f6
    bf827781 8417 test byte ptr [edi],dl

    LAST_CONTROL_TRANSFER: from bf82760e to bf827781

    FAILED_INSTRUCTION_ADDRESS:
    win32k!vSolidFillRect1+f6
    bf827781 8417 test byte ptr [edi],dl

    STACK_TEXT:
    b91aa5f0 bf82760e b91aa864 000002fc 02000000 win32k!vSolidFillRect1+0xf6
    b91aa770 bf8271b2 bf8276d0 b91aa864 00000000 win32k!vDIBSolidBlt+0x19b
    b91aa7dc bf8052b7 e1518008 00000000 00000000 win32k!EngBitBlt+0xe1
    b91aa82c bf80871f e4127de4 b91aa880 b91aa864 win32k!GrePatBltLockedDC+0x1ea
    b91aa8c4 bf82cb8c b91aa8fc 0000f0f0 0012f61c win32k!GrePolyPatBltInternal+0x17c
    b91aa918 804df06b fe010ff7 00f00021 0012f61c win32k!NtGdiPolyPatBlt+0xb5
    b91aa918 7c90eb94 fe010ff7 00f00021 0012f61c nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012f5f8 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!vSolidFillRect1+f6
    bf827781 8417 test byte ptr [edi],dl

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    SYMBOL_NAME: win32k!vSolidFillRect1+f6

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID: IP_MISALIGNED

    BUCKET_ID: IP_MISALIGNED

    Followup: MachineOwner
    ---------
     
    rki,
    #3
  5. 2006/08/14
    rki

    rki Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    4
    Likes Received:
    0
    Minidump-2

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini081406-02.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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Mon Aug 14 23:44:54.475 2006 (GMT+4)
    System Uptime: 0 days 0:09:34.055
    Loading Kernel Symbols
    .....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 80570410, ba1bd9f0, 0}

    Probably caused by : memory_corruption

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 80570410, The address that the exception occurred at
    Arg3: ba1bd9f0, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    nt!IopParseDevice+61f
    80570410 8a441485 mov al,byte ptr [esp+edx-7Bh]

    TRAP_FRAME: ba1bd9f0 -- (.trap ffffffffba1bd9f0)
    ErrCode = 00000000
    eax=84eabe68 ebx=84ea5da8 ecx=804e86ed edx=84ec8008 esi=84ec8008 edi=84eb0188
    eip=80570410 esp=ba1bda64 ebp=ba1bdb3c iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    nt!IopParseDevice+0x61f:
    80570410 8a441485 mov al,byte ptr [esp+edx-7Bh] ss:0010:3f0859f1=??
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: update.exe

    LAST_CONTROL_TRANSFER: from 8056316c to 80570410

    STACK_TEXT:
    ba1bdb3c 8056316c 867dc900 00000000 84eabdd0 nt!IopParseDevice+0x61f
    ba1bdbc4 8056729a 00000000 ba1bdc04 00000040 nt!ObpLookupObjectName+0x56a
    ba1bdc18 80570b73 00000000 00000000 56384301 nt!ObOpenObjectByName+0xeb
    ba1bdc94 80570c42 0006b498 80100080 0006b438 nt!IopCreateFile+0x407
    ba1bdcf0 80570d78 0006b498 80100080 0006b438 nt!IoCreateFile+0x8e
    ba1bdd30 804de7ec 0006b498 80100080 0006b438 nt!NtCreateFile+0x30
    ba1bdd30 7c90eb94 0006b498 80100080 0006b438 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0006b490 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    80570410-8057041f 16 bytes - nt!IopParseDevice+61f
    [ 89 85 4c ff ff ff 8b 45:8a 44 14 85 46 20 c7 46 ]
    16 errors : !nt (80570410-8057041f)

    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
    ---------
     
    rki,
    #4
  6. 2006/08/14
    rki

    rki Inactive Thread Starter

    Joined:
    2006/08/14
    Messages:
    4
    Likes Received:
    0
    Minidump-3

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini081506-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Tue Aug 15 00:13:09.456 2006 (GMT+4)
    System Uptime: 0 days 0:21:24.041
    Loading Kernel Symbols
    .....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1902fe, f5c7292c, f5c72628, 8058d011}

    *** WARNING: Unable to verify timestamp for amon.sys
    *** ERROR: Module load completed but symbols could not be loaded for amon.sys
    Probably caused by : Ntfs.sys ( Ntfs!NtfsNotifyChangeDirectory+ee )

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

    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: 001902fe
    Arg2: f5c7292c
    Arg3: f5c72628
    Arg4: 8058d011

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


    EXCEPTION_RECORD: f5c7292c -- (.exr fffffffff5c7292c)
    ExceptionAddress: 8058d011 (nt!FsRtlNotifyFilterChangeDirectory+0x00000074)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000000
    Parameter[1]: 7ac22ae0
    Attempt to read from address 7ac22ae0

    CONTEXT: f5c72628 -- (.cxr fffffffff5c72628)
    eax=85f55e78 ebx=84fb0008 ecx=867c75d0 edx=f5c72ad8 esi=00000000 edi=84fb01bc
    eip=8058d011 esp=f5c729f4 ebp=f5c72a40 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!FsRtlNotifyFilterChangeDirectory+0x74:
    8058d011 ff7510 push dword ptr [ebp+10h] ss:0010:f5c72a50=e22ddae0
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: winlogon.exe

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

    READ_ADDRESS: 7ac22ae0

    BUGCHECK_STR: 0x24

    EXCEPTION_DOESNOT_MATCH_CODE: This indicates a hardware error.
    Instruction at 8058d011 does not read/write to 7ac22ae0

    LAST_CONTROL_TRANSFER: from f76c9d07 to 8058d011

    STACK_TEXT:
    f5c72a40 f76c9d07 867c75d0 8678f400 e22ddae0 nt!FsRtlNotifyFilterChangeDirectory+0x74
    f5c72ab0 f76c9c5b 85638ef0 84fb0008 8678f100 Ntfs!NtfsNotifyChangeDirectory+0xee
    f5c72ae4 f76c5359 85638ef0 e1485920 84fac018 Ntfs!NtfsCommonDirectoryControl+0x69
    f5c72c5c 804e37f7 8678f020 84fb0008 867cba58 Ntfs!NtfsFsdDirectoryControl+0xad
    f5c72c6c f7741459 f5c72cb4 804e37f7 86758478 nt!IopfCallDriver+0x31
    f5c72c74 804e37f7 86758478 84fb0008 ba2f8d14 sr!SrPassThrough+0x31
    f5c72c84 ba2b5208 84fac018 85f615c8 804e37f7 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f5c72cb4 8058cfac 860e0020 84fb0008 85f55e78 amon+0x4208
    f5c72d38 804de7ec 00000208 00000408 00000000 nt!NtNotifyChangeDirectoryFile+0x22f
    f5c72d38 7c90eb94 00000208 00000408 00000000 nt!KiFastCallEntry+0xf8
    00edff5c 00000000 00000000 00000000 00000000 0x7c90eb94


    FOLLOWUP_IP:
    Ntfs!NtfsNotifyChangeDirectory+ee
    f76c9d07 c745d003010000 mov dword ptr [ebp-30h],103h

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Ntfs

    IMAGE_NAME: Ntfs.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea

    SYMBOL_NAME: Ntfs!NtfsNotifyChangeDirectory+ee

    STACK_COMMAND: .cxr 0xfffffffff5c72628 ; kb

    FAILURE_BUCKET_ID: 0x24_CODE_ADDRESS_MISMATCH_Ntfs!NtfsNotifyChangeDirectory+ee

    BUCKET_ID: 0x24_CODE_ADDRESS_MISMATCH_Ntfs!NtfsNotifyChangeDirectory+ee

    Followup: MachineOwner
    ---------
     
    rki,
    #5
  7. 2006/08/14
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    To my untrained eyes looks like a memory error.

    Probably the best thing to do is to go to Microsoft Support Services, and select an option to "open" a support request.

    You can use the log file (debuglog.txt) generated to supply the needed information to start your support request.
     
    Arie,
    #6

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...