Random BSOD 0x00000124

[MAGNEZ]

Hi there guys, since I have formatted my PC im getting random BSODs with the same exact error every time.
They occour pretty randomly, sometimes when Im writing a Word document, chatting with my friends, gaming or just browsing the internet. I do not know what is the main reason. My CPU is overclocked to 4.6GHz, however this has not been a problem AT ALL before the disk format. Right now Im running prime95 for the last hour with temperature not exceeding 73 degrees on 100% usage + no laggs nor crashes.

My main concern is MSI Afterburner. I overclock pretty much everything that is overclockable (Is that w word? D Afterburner has updated recently and so I try to get the settings same as before, however iits constructed a bit different so Im not sure If im doing it right. The "fun" part is that I dont remember whether my GPU was overclocked during the crashes or not. I had a Crash about 90 minutes ago, during which my GPU WAS overclocked. Its the only one I remember.

The error im getting is 0x00000124

Thanks.

 

[Dsprague]

please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[MAGNEZ]

please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Thanks for that, havent seen it. Done.

 

[Dsprague]

OK So I looked through your files, and it seems that your PC is crashing HARD from some hardware level error, It stumped me at first because I could literally get no information from your crash dumps now there is not muc hthat can be done for these types of errors, other than try and figure out what piece of hard ware is failing (again not any clues here from the dump files)

Have a look at this thread and see if it is any help: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[MAGNEZ]

Yes, its crashing alot. Im not using afterburner for the next few days and see whats gonna happen. During this time I'll look for any "faulty" hardware and update if possible. I might have not installed some stuff after the format. We'll see what I can do

Thanks anyway.

 

[Dsprague]

Your very welcome Sorry we couldn't provide more information.

 

[MAGNEZ]

Havent used Afterburner since and no crashes. Can the software suddenly become uncompatible?
Im using nearly the same settings.

 

[Dsprague]

Not that I know of but it is always possible that the install was corrupted for what ever reason.

 

[MAGNEZ]

Ok, I left my computer downloading over night and nothing happened. However, I left it again about two hours ago and during that time I had another crash. Although I did not use afterburner. The error Is still the same and I really have no idea what to do now.

Im also adding that diagnostics.

 

[Dsprague]

So it is still the same error, and there is still very very little information in the dump files, I think the best thing at this point is to stop any and all over clocking atleast untill such a time that there is evidence that this issue is not being caused by over clocking. some information about over clcoking:

What are the risk of overclocking?
In most situations, Overclocking will void the warranty of your equipment.
The lifespan of the CPU and other devices will be shortened.
You could potentially destroy your CPU, memory, motherboard, and other expensive items.
Room temperature is likely to increase.
Your system could become unstable.

Taken from this article: Overclocking FAQ (Frequently Asked Questions) - How to Overclock! - Overclockers Club

And thanks to another of our BSOD analysts XBluerobot

 

[MAGNEZ]

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.

 

[Dsprague]

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.

 

[MAGNEZ]

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

 

[carwiz]

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.

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.

 

[MAGNEZ]

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.

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.

 

[carwiz]

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.

 

[MAGNEZ]

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.

 

[MAGNEZ]

@BUMP

Also installed some drivers for motherboard.

 

[carwiz]

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

 

[MAGNEZ]

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.