0x00000124 BSOD (system hang) after opening MSI Afterburner

Spykeeboy · Apr 10, 2015

Hello everyone,

I am relatively new here but would very much appreciate any and all advice. I have built a computer 3 days ago, installed Windows 7 64bit Home Premium and had my first BSOD immediately after opening MSI Afterburner. The system hung and I didn't see a blue screen, but a minidump got saved and I had to hard-reset. I know it's not a temperature problem as my CPU and GPU are 53C and 74C under load respectively which is not bad and certainly not overheating.

I have used MSI Afterburner for the past 3 days with no problems, I do NOT overclock at all and just use the program to monitor my GPU and CPU temperatures during gaming. The crash happened today only and the code was 0x00000124 with no bug check string Also, after the crash MSI Afterburner started and worked just fine.

The system specs are:

Gigabyte Z87-HD3 motherboard
i5-4670K processor (not overclocked at all) with CoolerMaster EVO 412PWM cooler
MSI R9 290 Gaming Edition 4GB GPU (factory overclock)
Corsair Vengeance 1600MHz 8GB (2x4GB) RAM
Seasonic x-750 750W PSU
Samsung 840 EVO 120GB SSD (for system only)
WD Red 1TB HDD (storage only)

I have uploaded a .zip file containing the minidump and event logs if anyone could please take a look. I would very very much appreciate all advice regarding this problem - is it a fluke? Could it be a fluke or is it definitely a hardware issue? Should I use a different program to MSI Afterburner and RivaTuner server to monitor temperatures?

It took me a lot of time and resources to build this PC and to see problems so soon with hardly anything installed on the PC is concerning

If you need any other information from me please let me know.

LINK to minidumps and eventlogs:
https://drive.google.com/file/d/0B_cjEpj35HqPUVFQMy12cEF4MUk/view?usp=sharing

johnbl · Apr 10, 2015

the power to the CPU dropped too low and your machine rebooted. The power supply was suppose to prevent the start up of the CPU until the power was stable but it did not. The CPU attempted to restart with unstable power and got an internal timer error on processor 0 cache memory bank 3 this error is a fatal error and the CPU called a bugcheck 0x124 to shutdown the system 1.7 seconds after the system rebooted.

because the CPU was in "panic" mode it only has a partial memory dump. I can not see the BIOS info or CPU speed that the system was running at and the driver list is only a partial list but I would expect the overclocking driver was overclocking.

you might want to find out why your PSU/motherboard allowed the system to start up while the power levels were in flux. Most likely because the PSU did not provide a proper power_ok signal to the motherboard.
(common for cheaper power supplies to fake this signal, people never figure it out and blame the motherboard and the supplier saves 50 cents on each unit) Note: generally Seasonic power supplies don't have this problem but I have not purchased one in a year or so. (so I don't know anymore)

for this reason: check your BIOS version and the date your CPU was release and make sure your BIOS supports the CPU. If the BIOS supplies the wrong voltage (too much) for the CPU you can get this same error when you are not overclocking. Common if you use a newer low voltage CPU but have a old BIOS version that does not correct the voltage vs clock frequency tables and runs the CPU at too high of a voltage.

Spykeeboy · Apr 10, 2015

johnbl :

the power to the CPU dropped too low and your machine rebooted. The power supply was suppose to prevent the start up of the CPU until the power was stable but it did not. The CPU attempted to restart with unstable power and got an internal timer error on processor 0 cache memory bank 3 this error is a fatal error and the CPU called a bugcheck 0x124 to shutdown the system 1.7 seconds after the system rebooted.

because the CPU was in "panic" mode it only has a partial memory dump. I can not see the BIOS info or CPU speed that the system was running at and the driver list is only a partial list but I would expect the overclocking driver was overclocking.

you might want to find out why your PSU/motherboard allowed the system to start up while the power levels were in flux. Most likely because the PSU did not provide a proper power_ok signal to the motherboard.
(common for cheaper power supplies to fake this signal, people never figure it out and blame the motherboard and the supplier saves 50 cents on each unit) Note: generally Seasonic power supplies don't have this problem but I have not purchased one in a year or so. (so I don't know anymore)

for this reason: check your BIOS version and the date your CPU was release and make sure your BIOS supports the CPU. If the BIOS supplies the wrong voltage (too much) for the CPU you can get this same error when you are not overclocking. Common if you use a newer low voltage CPU but have a old BIOS version that does not correct the voltage vs clock frequency tables and runs the CPU at too high of a voltage.

Thank you so very much for the advice. I have checked the BIOS version and it is indeed outdated by at least 2 releases. I will update it and maybe set the CPU voltages manually to what they should be (not sure if this is a good idea however). Also I have never flashed the BIOS before so may need to find a good tutorial.

Thanks again!

Search

0x00000124 BSOD (system hang) after opening MSI Afterburner

Spykeeboy

Reputable

johnbl

johnbl

Polypheme

Spykeeboy

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page