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 need help!

Discussion in 'Windows XP' started by dhuynh, 2008/01/09.

  1. 2008/01/09
    dhuynh

    dhuynh Inactive Thread Starter

    Joined:
    2008/01/09
    Messages:
    21
    Likes Received:
    0
    Loading Dump File [C:\Documents and Settings\dhuynh\Desktop\bluescreenDUMPfile\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
     
  2. 2008/01/09
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    dhuynh - Welcome to the Board :)

    Very difficult to offer any help without details of your problems on the computer and a full dump data log.
     

  3. to hide this advert.

  4. 2008/01/09
    dhuynh

    dhuynh Inactive Thread Starter

    Joined:
    2008/01/09
    Messages:
    21
    Likes Received:
    0
    I am unable to run the darn thing cause it is saying i dont have the right symbol




    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_qfe.070227-2300
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
    Debug session time: Tue Jan 8 22:46:54.084 2008 (GMT-6)
    System Uptime: 0 days 1:56:32.947
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Loading Kernel Symbols
    .............................................................................................................................................................
    Loading User Symbols

    Loading unloaded module list
    ..................
    *** ERROR: Module load completed but symbols could not be loaded for ar5211.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {b9c98c68, 2, 0, b9c46c40}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for VSApiNt.sys -
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************




    Probably caused by : ar5211.sys ( ar5211+15c40 )

    Followup: MachineOwner
    ---------
     
  5. 2008/01/09
    dhuynh

    dhuynh Inactive Thread Starter

    Joined:
    2008/01/09
    Messages:
    21
    Likes Received:
    0
    also thanks for the welcoming
     
  6. 2008/01/09
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,680
    Likes Received:
    104
  7. 2008/01/09
    dhuynh

    dhuynh Inactive Thread Starter

    Joined:
    2008/01/09
    Messages:
    21
    Likes Received:
    0
    that link you sent me is where i started... please help with the


    Probably caused by : ar5211.sys ( ar5211+15c40 )

    i also understand i am not using atheros driver, i am using intel... can i delete that file? would that solve it?
     
  8. 2008/01/09
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    See this thread ....

    http://www.windowsbbs.com/showthread.php?t=46819

    ar5211.sys is the wireless driver for Atheros cards - nothing to do with Intel :)

    Without the benefit of a full dump log - did you debug while connected to the internet as noted in the URL Admin posted? - my best suggestion is to re-install the wireless card - try disabling it first - if rhe BSOD's cease you know the culprit.

    You have not posted the condition under which the BSOD occurs.
     

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.