Random BSOD 0x00000124

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #11

    It really was ALL fine before the format, also I have stress tested my CPU for about 90 minutes in Prime95 and also did some gaming for about 2-3 hours straight. There was NO crashes. Maybe I could format again? Also, I did something with mi hard drives yesterday. It was suppost to speed things up, dont know if it worked but this is what i did.

      My Computer


  2. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #12

    Reinstall again if you like but chances are there is damage to your hardware, or your overclocking is causing the system to be come unstable all the re-installs in the world wont fix that.
      My Computer


  3. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #13

    Dsprague said:
    Reinstall again if you like but chances are there is damage to your hardware, or your overclocking is causing the system to be come unstable all the re-installs in the world wont fix that.
    You know, Im just really suprised that it happened right after the last format
      My Computer


  4. Posts : 4,161
    Windows 7 Pro-x64
       #14

    The dump indicates a catastrophic failure but it is so bad that memory was too corrupt to complete the data collection for the dump. This could be caused by a CPU failure, chipset failure or corrupt memory modules.

    I agree with Dsprague that you should revert to standard timings until your system is stable. There's a possibility that your disk drive could have corrupt files also due to the nature of corrupt memory. To run tests on your hardware, you'll need a stable system.

    The following is for information only.

    Code:
     
    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: fffffa8008804028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff800`00ba8a98 fffff800`033fca3b : 00000000`00000124 00000000`00000000 fffffa80`08804028 00000000`be200000 : 0xfffff800`02e79c00
    fffff800`00ba8aa0 00000000`00000124 : 00000000`00000000 fffffa80`08804028 00000000`be200000 00000000`0005110a : 0xfffff800`033fca3b
    fffff800`00ba8aa8 00000000`00000000 : fffffa80`08804028 00000000`be200000 00000000`0005110a fffffa80`088eebd0 : 0x124
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    BUCKET_ID:  CORRUPT_MODULELIST
    Followup: MachineOwner
    ---------
    0: kd> !errrec fffffa8008804028
    ===============================================================================
    Common Platform Error Record @ fffffa8008804028
    -------------------------------------------------------------------------------
    Signature     : *** INVALID ***
    Revision      : 0.0
    Record Id     : 0000000000000000
    Severity      : Recoverable (0)
    Length        : 0
    Creator       : {00000100-000f-0000-3600-000000000000}
    Notify Type   : {00000100-000f-0000-3600-000000000000}
    Flags         : 0x00000000
    0: kd> lmnt
    start             end                 module name
    00000000`067b8040 00000000`0cf700c8   Unknown_Module_00000000_067b8040 Unknown_Module_00000000`067b8040 unavailable (00000000)
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Unloaded modules:
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
      My Computer


  5. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #15

    carwiz said:
    The dump indicates a catastrophic failure but it is so bad that memory was too corrupt to complete the data collection for the dump. This could be caused by a CPU failure, chipset failure or corrupt memory modules.

    I agree with Dsprague that you should revert to standard timings until your system is stable. There's a possibility that your disk drive could have corrupt files also due to the nature of corrupt memory. To run tests on your hardware, you'll need a stable system.

    The following is for information only.

    Code:
     
    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: fffffa8008804028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff800`00ba8a98 fffff800`033fca3b : 00000000`00000124 00000000`00000000 fffffa80`08804028 00000000`be200000 : 0xfffff800`02e79c00
    fffff800`00ba8aa0 00000000`00000124 : 00000000`00000000 fffffa80`08804028 00000000`be200000 00000000`0005110a : 0xfffff800`033fca3b
    fffff800`00ba8aa8 00000000`00000000 : fffffa80`08804028 00000000`be200000 00000000`0005110a fffffa80`088eebd0 : 0x124
    
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME:  Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    BUCKET_ID:  CORRUPT_MODULELIST
    Followup: MachineOwner
    ---------
    0: kd> !errrec fffffa8008804028
    ===============================================================================
    Common Platform Error Record @ fffffa8008804028
    -------------------------------------------------------------------------------
    Signature     : *** INVALID ***
    Revision      : 0.0
    Record Id     : 0000000000000000
    Severity      : Recoverable (0)
    Length        : 0
    Creator       : {00000100-000f-0000-3600-000000000000}
    Notify Type   : {00000100-000f-0000-3600-000000000000}
    Flags         : 0x00000000
    0: kd> lmnt
    start             end                 module name
    00000000`067b8040 00000000`0cf700c8   Unknown_Module_00000000_067b8040 Unknown_Module_00000000`067b8040 unavailable (00000000)
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Unloaded modules:
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    Missing image name, possible paged-out or corrupt data.
    000007fe`ea739e88 000007ff`00000000   Unknown_Module_000007fe`ea739e88
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  158C6178
    Missing image name, possible paged-out or corrupt data.
    Thanks, I'll try it now. Also, something weird happened to my GPU right now, it seemed that It crashed however in game only. I was playing Battlefield and all the colours got "funky" If oyu know what i mean. Bright green, red, blue, white all kinds of colours. The textures were there and I could play with stable 60-80fps however the colours were quiet badly messed up.

    @Edit

    Ok, turned everything right down In BIOS. The only thing turned on is "Performance Mode". CPU is jumping between 3.5GHz to 3.7GHz on desktop.
      My Computer


  6. Posts : 4,161
    Windows 7 Pro-x64
       #16

    First run SFC /scannow from an elevated command prompt so we know all the system files and Registry are intact. If you get any errors noted on the console, run it up to two more times then report back any messages.

    Run Memtest86+ and follow the recommend procedure (Part 3) for individual modules if you get any errors.

    If you pass those test, run a Check Disk on all disk drives to verify file structures.
      My Computer


  7. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #17

    carwiz said:
    First run SFC /scannow from an elevated command prompt so we know all the system files and Registry are intact. If you get any errors noted on the console, run it up to two more times then report back any messages.

    Run Memtest86+ and follow the recommend procedure (Part 3) for individual modules if you get any errors.

    If you pass those test, run a Check Disk on all disk drives to verify file structures.
    Ok, No errors for /scannow and the disk check. I tried memtest which didnt workout as it should, although USB was set to boot first. Anyway, Im pretty sure its not a RAM problem. It seems that CPU overlocking might have coursed that, and Afterburner just added on to it. I could find a tutorial on a stable 4.5 GHz overclock, as my 4.6 was more or less from memory, Vcore might have been a bit unstable - As I said however, got no errors from Prime95.

    Anyway, I would like to run the memtest sometime. Just dont know how to, I installed it on a memory stick and set the Boot menu in Bios to read from the USB first. Tried that three times with different settings and it didnt really work out.

    Im not gonna overclock anything for the next few days and see what happens. If its a GPU fault, Im planning to buy a new one after summer holidays anyway.
      My Computer


  8. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #18

    @BUMP

    Also installed some drivers for motherboard.
      My Computer


  9. Posts : 4,161
    Windows 7 Pro-x64
       #19

    How did the Memtest go? Are you still getting a BSOD?
      My Computer


  10. Posts : 17
    Windows 7 Pro x64
    Thread Starter
       #20

    carwiz said:
    How did the Memtest go? Are you still getting a BSOD?
    Dont even know how to run it tbh. It extracted and installed onto my Mem Stick, USB is set to first on BIOS and still no sign of anything. All the other test came out just fine.

    Just Did an intel burn test "20 times", on 4.7 GHz and im 100% sure that it is not a CPU problem. Temperature did not go over 75 degrees.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  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 10:26.
Find Us