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.

DUMP DATA: Win XP crashes suddenly

Discussion in 'Windows XP' started by pj94z, 2007/12/27.

  1. 2007/12/27
    pj94z

    pj94z Inactive Thread Starter

    Joined:
    2007/12/27
    Messages:
    3
    Likes Received:
    0
    I was having some issues with applications crashing, so I re-installed windows xp - I did a clean install....wiping out and formatting the HDD.

    After that, I was running a database import and had several programs open...when my PC just rebooted...no blue screen...just a reboot.

    I have a feeling that re-installing the OS did not fix my previous issues and feel something else maybe wrong.


    Below is the Dump Data from the USER.DMP file...Any help appreciated!!



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


    Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    Windows XP Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: SingleUserTS
    Debug session time: Thu Dec 27 02:57:24.000 2007 (GMT-5)
    System Uptime: not available
    Process Uptime: 0 days 0:00:01.000
    ............
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (6b0.6bc): Access violation - code c0000005 (first/second chance not available)
    eax=00000000 ebx=001445c8 ecx=7c80996d edx=00040001 esi=00000001 edi=00000000
    eip=0012e7b0 esp=0095ffb8 ebp=001445d0 iopl=0 nv up ei pl zr na pe nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
    0012e7b0 0000 add byte ptr [eax],al ds:0023:00000000=??
    WARNING: Non-directory path: 'C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp'
     
  2. 2007/12/27
    dale456654

    dale456654 Inactive

    Joined:
    2007/04/02
    Messages:
    130
    Likes Received:
    2
    Configure your computer so that it does not automatically restart and shows a blue screen.

    Right-click on the Computer icon and choose Properties.The Advanced tab should already be selected, so you'll want to click the Settings button under "Startup and Recovery ".
    Here we go… just uncheck the option for Automatically restart under the System failure section.

    Next time you get a BSOD you'll be able to see what the problem is.
     

  3. to hide this advert.

  4. 2007/12/27
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    Hi, pj94z. Welcome to Windows BBS! :)

    In addition to dale456654's suggestion, please carefully follow the instructions in this link to produce potentially more helpful dump log data.

    I suspect that will also take care of the "Symbol search path is: *** Invalid ***" and empty "Executable search path is:" issues.


    There are only a couple people (who visit Windows BBS occasionally) who have the expertise necessary to decipher the dump log output and offer their suggestions. The rest of us offer suggestions based on observation only.

    Perhaps this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4) will help you identify the culprit after you produce a DebugWiz-generated dump log.

    Note: The crash you described in the thread title and your initial problem description appears to be a system crash (not a program crash). Therefore the .DMP file you're looking to analyze is probably C:\MEMORY.DMP or (for Mini-dumps) C:\WINDOWS\Minidump\Minixxxxxx-yy.dmp (The x's will be the date and the y's will be the crash count for the day.)
     
    Last edited: 2007/12/27
  5. 2007/12/27
    pj94z

    pj94z Inactive Thread Starter

    Joined:
    2007/12/27
    Messages:
    3
    Likes Received:
    0
    memorty test

    Hey guys - I downloaded memtest86+ and am currently running the memtest on the PC with the issue.

    The PC is AMD 64 with Dual Channell DDR2 - it has 4 memory sticks. It came with 2, and I installed 2 myself about 4 months ago (worked fine until now!).


    Anyway, here is a screen shot of what the memtest screen looks like right now... as you can see... the test has been running for over 1 hour and 30 mins.

    Does anyone know what the RED line errors indicate? Does this mean I have a bad memory stick? How can I figure out which stick to replace, if that's the case?

    Thanks !!


    http://www.pjdarji.com/pc/mem1.jpg
     
  6. 2007/12/27
    mailman Lifetime Subscription

    mailman Geek Member

    Joined:
    2004/01/17
    Messages:
    1,901
    Likes Received:
    11
    1. Remove some of the memory modules from the computer (while the computer is off, of course).
      • For example, if two RAM modules are installed in your computer, remove one of the RAM modules.
    2. Start your computer and see if the problem goes away.
    3. If you continue to have unexpected reboots/BSODs, then replace that RAM module with another module, or install the module in a different memory slot.
    4. Start your computer and see if the problem goes away.
    Continue this process to see if you can pinpoint the cause of your problem to a specific RAM module or slot.

    ==========

    • Microsoft KB134503:

    EDIT: BTW, when using multiple memory sticks, having matched pairs of sticks is reportedly important with some computer configurations. In your case, it might be important that all 4 sticks match.
     
    Last edited: 2007/12/27
  7. 2007/12/29
    pj94z

    pj94z Inactive Thread Starter

    Joined:
    2007/12/27
    Messages:
    3
    Likes Received:
    0
    Fixed !

    Well, after the memtest finished....I thought about my problem some more:

    My PC only crashed when using certain applications - app A or B.

    One of these apps has a database associated with it which I had recently backed up and tried to restore (sql).

    Well - I remembered there were some errors during the database restore...and felt maybe the crashes were due to the database issues.

    Well - turns out, I was right. I re-installed apps A and B. Re-installed DB server and used a different backup - and got no errors.

    Ever since then, My PC is running very smooth...no errors and no crashes.

    So - althouht memtest detected an error -- it seems it's probably too small to really make much of a difference.
    In reality, the errors were caused by the corrupted Database.

    Thanks
     
  8. 2007/12/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Glad to hear that you found the problem, but, please note ....
    Hence Mailman's suggestion re. relocating/removing sticks.
     

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.