locked
Brand new laptop having bsod problems RRS feed

  • Question

  • I have a brand new acer aspire 5253 laptop and i keeps having bsod problems it doesnt happen often but it is very annoying i have the dump files and i downloaded windows debugger and i looked at the dump files and all it says was probably caused by: hardware then near the bottom and it says lmvm hardware here is the link to the dump file download  https://cid-38f260a2c142e70a.office.live.com/browse.aspx/.Documents?uc=2
    Saturday, April 2, 2011 11:48 PM

Answers

  • Hello,

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 124, {0, fffffa8003419038, b6000000, 10015}

     

    Probably caused by : hardware

     

    Followup: MachineOwner

    ---------

     

    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        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: 0000000000000000, Machine Check Exception

    Arg2: fffffa8003419038, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 0000000000010015, Low order 32-bits of the MCi_STATUS value.

     

    Debugging Details:

    ------------------

     

     

    OVERLAPPED_MODULE: Address regions for 'EX64' and 'ENG64.SYS' overlap

     

    BUGCHECK_STR:  0x124_AuthenticAMD

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    PROCESS_NAME:  java.exe

     

    CURRENT_IRQL:  f

     

    STACK_TEXT:  

    fffff800`0406aac8 fffff800`02a31903 : 00000000`00000124 00000000`00000000 fffffa80`03419038 00000000`b6000000 : nt!KeBugCheckEx

    fffff800`0406aad0 fffff800`02bee5a3 : 00000000`00000001 fffffa80`031857d0 00000000`00000000 fffffa80`03185820 : hal!HalBugCheckSystem+0x1e3

    fffff800`0406ab10 fffff800`02a315c8 : 00000000`00000728 fffffa80`031857d0 fffff800`0406ae70 00000000`ffffff00 : nt!WheaReportHwError+0x263

    fffff800`0406ab70 fffff800`02a30f1a : fffffa80`031857d0 fffff800`0406ae70 fffffa80`031857d0 00000000`00000000 : hal!HalpMcaReportError+0x4c

    fffff800`0406acc0 fffff800`02a24e8f : 00000000`0000013b 00000000`00000001 fffff800`0406aef0 00000000`00000000 : hal!HalpMceHandler+0x9e

    fffff800`0406ad00 fffff800`02ad6fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47

    fffff800`0406ad30 fffff800`02ad6e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c

    fffff800`0406ae70 00000000`02590485 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153

    00000000`05c4f120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2590485

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: hardware

     

    IMAGE_NAME:  hardware

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB

     

    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB

     

    Followup: MachineOwner

    ||||||||||||||||||||||||||||||||||||||||||

    The BSOD was caused by your AMD processor. Please check that it is not to hot. Also, contact your manifacturer Technical Support.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    • Marked as answer by rockstar1996 Sunday, April 3, 2011 5:13 PM
    Sunday, April 3, 2011 6:43 AM

All replies

  • Hello, make sure that your share is set to public access. 

    I am unable to use the link.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Saturday, April 2, 2011 11:58 PM
  • okay here is the link again sorry i thought it was set right it should work now http://cid-38f260a2c142e70a.office.live.com/browse.aspx/.Documents?permissionsChanged=1&1
    Sunday, April 3, 2011 5:56 AM
  • Hello,

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 124, {0, fffffa8003419038, b6000000, 10015}

     

    Probably caused by : hardware

     

    Followup: MachineOwner

    ---------

     

    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        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: 0000000000000000, Machine Check Exception

    Arg2: fffffa8003419038, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 0000000000010015, Low order 32-bits of the MCi_STATUS value.

     

    Debugging Details:

    ------------------

     

     

    OVERLAPPED_MODULE: Address regions for 'EX64' and 'ENG64.SYS' overlap

     

    BUGCHECK_STR:  0x124_AuthenticAMD

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    PROCESS_NAME:  java.exe

     

    CURRENT_IRQL:  f

     

    STACK_TEXT:  

    fffff800`0406aac8 fffff800`02a31903 : 00000000`00000124 00000000`00000000 fffffa80`03419038 00000000`b6000000 : nt!KeBugCheckEx

    fffff800`0406aad0 fffff800`02bee5a3 : 00000000`00000001 fffffa80`031857d0 00000000`00000000 fffffa80`03185820 : hal!HalBugCheckSystem+0x1e3

    fffff800`0406ab10 fffff800`02a315c8 : 00000000`00000728 fffffa80`031857d0 fffff800`0406ae70 00000000`ffffff00 : nt!WheaReportHwError+0x263

    fffff800`0406ab70 fffff800`02a30f1a : fffffa80`031857d0 fffff800`0406ae70 fffffa80`031857d0 00000000`00000000 : hal!HalpMcaReportError+0x4c

    fffff800`0406acc0 fffff800`02a24e8f : 00000000`0000013b 00000000`00000001 fffff800`0406aef0 00000000`00000000 : hal!HalpMceHandler+0x9e

    fffff800`0406ad00 fffff800`02ad6fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47

    fffff800`0406ad30 fffff800`02ad6e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c

    fffff800`0406ae70 00000000`02590485 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153

    00000000`05c4f120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2590485

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: hardware

     

    IMAGE_NAME:  hardware

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB

     

    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB

     

    Followup: MachineOwner

    ||||||||||||||||||||||||||||||||||||||||||

    The BSOD was caused by your AMD processor. Please check that it is not to hot. Also, contact your manifacturer Technical Support.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    • Marked as answer by rockstar1996 Sunday, April 3, 2011 5:13 PM
    Sunday, April 3, 2011 6:43 AM
  • Thanks you very much i got the same thing when i did the analysis but i was not sure if i did it right and i was not sure what it was but thank you for finding out what the actual problem was.
    Sunday, April 3, 2011 5:12 PM