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.

MS Outlook 2003 Reboot

Discussion in 'Windows XP' started by TecMan, 2006/02/22.

  1. 2006/02/22
    TecMan

    TecMan Inactive Thread Starter

    Joined:
    2006/02/22
    Messages:
    3
    Likes Received:
    0
    Hi Friends:

    Here is my computer's configuration (Device Manager)
    - Intel Desktop Board PBZLKPRES (BIOS: BZ87510A.86A.0106.P27)
    - Processor Pentium 4 3.0 Ghz
    - RAM: 2-512 modules (Kingston KVR400X64C3A_512MB PC3200 CL3 184-Pin DIMM)
    - Video Card (RADEON 9800) (with last driver)
    - Sound Blaster Audigy 2 Platinum (with last driver)
    - Two WD Serial ATA Hard Drivers (C:WD2500JD & D:WD2000JD)
    - Sony CD-RW (CRX220E1) & Plextor DVD (PX-716A)
    - OS: WinXP-SP2

    ok...When I try to click Send/Receive command in MS-Outlook 2003...my computer reboot with blackscreen with the following:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x00380002, 0x00000002, 0x00000001, 0x806ffa2a). A dump was saved in: C:\WINDOWS\Minidump\Mini022206-02.dmp.

    Microsoft Online Crash Analysis: Error caused by a device driver

    Considering that my MB & RAM are newest...I suspect that I have a Chipset Configuration Problem

    Here are the default settings:

    BIOS Version: BZ97510A.86A.0106.P27

    BIOS SETUP UTILITY/ADVANCED/Chipset Configuration

    PCI Latency Timer: 32

    - Burn-In Mode
    - Do you wish to continue: No
    - Host and I/O Burn-In Mode: Default
    - AGP/PCI Burn-In Mode: Default

    - Memory
    - SDRAM Timing Control: Auto
    - CPC Override: Auto

    What do you think?...What do you recommend me?

    Thanks

    TecMan
     
  2. 2006/02/22
    TecMan

    TecMan Inactive Thread Starter

    Joined:
    2006/02/22
    Messages:
    3
    Likes Received:
    0
    Here is Bugcheck Analysis

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini022206-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    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:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Wed Feb 22 10:13:38.234 2006 (GMT-6)
    System Uptime: 0 days 1:32:30.928
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    .......................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    Unable to load image AL_ADSFilter.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for AL_ADSFilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for AL_ADSFilter.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {380002, 2, 1, 806ffa2a}

    ***** 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 ***
    *** ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for ctac32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctac32k.sys
    Probably caused by : AL_ADSFilter.sys ( AL_ADSFilter+2699 )

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

  3. to hide this advert.

  4. 2006/02/22
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Arie,
    #3
  5. 2006/02/22
    TecMan

    TecMan Inactive Thread Starter

    Joined:
    2006/02/22
    Messages:
    3
    Likes Received:
    0
    Dump Data Log

    Here is Dump Data Log

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini022206-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    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:
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
    Debug session time: Wed Feb 22 10:13:38.234 2006 (GMT-6)
    System Uptime: 0 days 1:32:30.928
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    .................................................. .................................................. .................................................. .
    Loading User Symbols
    Loading unloaded module list
    .............
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    Unable to load image AL_ADSFilter.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for AL_ADSFilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for AL_ADSFilter.sys
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {380002, 2, 1, 806ffa2a}

    ***** 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 ***
    *** ***
    ************************************************** ***********************
    *** WARNING: Unable to verify timestamp for ctac32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctac32k.sys
    Probably caused by : AL_ADSFilter.sys ( AL_ADSFilter+2699 )

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

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.