BSoD and messed up system -- dies almost daily

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by JenWest, Oct 6, 2011.

  1. JenWest

    JenWest New Member

    Joined:
    Oct 6, 2011
    Messages:
    2
    Likes Received:
    0
    Hi,

    I have an Acer laptop with serious issues. The original hard drive was replaced while under warranty in Thailand (at supposed "authorized" Acer service center). The way they set it up is bizarre and admin rights are questionable.

    BSoD happens regularly, tho so quickly that there is no notice, just a complete shutdown then dump file. It can happen any time - no discernible pattern, although if more than one program is running it is more likely.

    I tried to run WinDbg but got the message below.

    I am attaching the dmp files for about the past month only.

    I regularly run CCleaner and Smart Defrag and have checked the entire mess with Malwarebytes, spybot S&D, Ad Aware (none of which find anything malicious). Also running Zone Alarm.

    Any help or advice very welcome!
    J



    [​IMG]



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


    Loading Dump File [C:\Windows\Minidump\060811-23197-01.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x82e16000 PsLoadedModuleList = 0x82f5e810
    Debug session time: Wed Jun 8 20:55:32.356 2011 (UTC + 7:00)
    System Uptime: 0 days 11:43:01.384
    *********************************************************************
    * 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 68, b6b07bd4, 0}

    ***** 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 halmacpi.dll
    *** ERROR: Module load completed but symbols could not be loaded for halmacpi.dll
    *************************************************************************
    *** ***
    *** ***
    *** 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 : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

    Attached Files:

  2. yowanvista

    yowanvista Well-Known Member

    Joined:
    Apr 10, 2011
    Messages:
    82
    Likes Received:
    0
    Its a hardware error caused by defective components/outdated BIOS
    Stop any overclocking

    Run Prime 95 again to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 00000000, Machine Check Exception
    Arg2: 867ca8fc, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    8d71bcc4 832d2fc5 867ca8e0 8336bc28 8336bc20 nt!WheapCreateTriageDumpFromPreviousSession+0x32
    8d71bce4 832d3def 8336bc20 867ca8e0 8336bc50 nt!WheapProcessWorkQueueItem+0x56
    8d71bd00 83271f2b 8336bc20 00000000 857e5d48 nt!WheapWorkQueueWorkerRoutine+0x1f
    8d71bd50 8341266d 00000001 aa5e63cf 00000000 nt!ExpWorkerThread+0x10d
    8d71bd90 832c40d9 83271e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV
    
    Followup: MachineOwner
    ---------
    
    
     

Share This Page

Loading...