BSOD Screen 0x00000124 Help ASAP Please!

Page 2 of 2 FirstFirst 12

  1. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #11

    Ferni36 said:
    yowanvista said:
    Ferni36 said:

    I have , but it wont let me zip them... ;\
    Use 7-zip
    7-Zip

    Says acces denied to all of them
    Unless there is a problem with ownership of files in your computer this method should work: https://www.sevenforums.com/tutorials...en-forums.html
      My Computer


  2. Posts : 13
    Windows 7
    Thread Starter
       #12

    yowanvista said:
    Ferni36 said:
    yowanvista said:

    Use 7-zip
    7-Zip

    Says acces denied to all of them
    Unless there is a problem with ownership of files in your computer this method should work: https://www.sevenforums.com/tutorials...en-forums.html
    For some reason it says i have no Permission to zip the files... do you need all the DUMP files?
      My Computer


  3. Posts : 13
    Windows 7
    Thread Starter
       #13

    Ferni36 said:
    yowanvista said:
    Ferni36 said:


    Says acces denied to all of them
    Unless there is a problem with ownership of files in your computer this method should work: https://www.sevenforums.com/tutorials...en-forums.html
    For some reason it says i have no Permission to zip the files... do you need all the DUMP files?

    Ok ive done it , Heres the DUMP Files please tell me whats wrong thanks...
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #14

    Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
    RAM - Test with Memtest86+
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800838b028, b620a000, 135}
    
    Probably caused by : hardware
    
    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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, 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:  Crysis2.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
    fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
    fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 13
    Windows 7
    Thread Starter
       #15

    yowanvista said:
    Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
    RAM - Test with Memtest86+
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800838b028, b620a000, 135}
    
    Probably caused by : hardware
    
    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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, 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:  Crysis2.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
    fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
    fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------

    Is it just the RAM? because that would be an easy fix ill get the guy who sent me the PC to get me some new ram. Thanks for answering btw
      My Computer


  6. Posts : 13
    Windows 7
    Thread Starter
       #16

    [QUOTE=Ferni36;1325208]
    yowanvista said:
    Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
    RAM - Test with Memtest86+
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800838b028, b620a000, 135}
    
    Probably caused by : hardware
    
    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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, 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:  Crysis2.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
    fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
    fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------

    Also , The CPU was overclocked.... would that be the problem?
      My Computer


  7. Posts : 2,528
    Windows 10 Pro x64
       #17

    That's always the best place to start. This particular bugcheck is blaming one of the locations in the CPU's L1 cache specifically, so setting it back to stock (and making sure it's staying cooled properly) are good starts.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:54.
Find Us