Solved BSOD 0x00000124 random times

[eracet]

I have had a lot of issues lately with BSOD crashes.

This is currently happening 4-5 times a day.

I was gone out of town for a few days and when I came back it had a crash error of hardware.
Restarted PC and a few hours later it crashed the same again.

I have had it happen before when I had memory managment crashes but this was never resolved with same setup.

Here is what have tried to fix or troubleshoot the issue.
Turned off any overclocking of processor or ram.
Checked all cards to make sure they are seated correctly.
Ran virus scans on software.
Removed Dimms out one at a time until crashing happened.
Cleared any dust that may of clogged fans..(minor dust only I clean regularly)

The last crash it seemed to be something with my motherboard , since it seemed to reset when I restarted. (restarted power and hesitated then had to restart again).

Any help with any thing I may of missed would be great.

Attached Hardware/software copy

 

[axe0]

Hi eracet,

Please remove items from the startup
How to remove items from startup - Windows 7 Help Forums
These programs could interfere with the boot process giving you trouble.

Please check {windows partition}\windows\minidump and check if there are any (recent) dump files saved.
The zip is empty of dump files.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

 

[eracet]

The boot process works ok. Seems to be at random.
Was better when I had one SDRAM removed, thinking I may have multiple SD that are bad.
Currently running half the ram 2 removed to see if it happens again. Going to do a memtest before bed and let it run all night and work day. See if any issues come back . Will put all ram in for test.

I did not see any windows minidump at all. and looks to be configured correctly. Not sure why it isnt creating a file. Looked at my other partitions and they have older ones, from previous windows but nothing current.

 

[eracet]

Surprisingly all RAM was ok after 19+ hours of running memtest86.
So now on to the next thing...

I doublechecked that small memory dump should record.. hopefully it does this time if it crashes again. So at least we can have a log to look at.

Disabled most of the background processes. Steam/ Aida / others/ to see if it still happens.

If it does happen again I will post minidump file .

 

[eracet]

Well disabled carbonite and killed most of the processes.

But did recieve another BS.
This time it was a different description.


A clock interrupt was not received on a secondary processor within the allocated time interval.

Good news is it created a dmp file.
Attached is the file.

 

[axe0]

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

 

[eracet]

Diagnostics Test

 HDD TEST

:ar: Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

:ar: Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

I run Hard Disk Sentinel and that shows most problems with HDD.
I have 6 HDDs, and 9 partitions. Some that run programs and some that just run windows. A few just for data (pictures, video)

I also have a new minidump that happened just after last reboot, same hardware error but logged now.

 

[eracet]

Did a CHKDSK an all came back fine. had seagate tools and that had the same results.
Hard Disk Sentinal shows no problems as well , at least on main drive. One drive has 3 bad sectors other then that rest are ok.

 

[axe0]

An internal error has occurred.

0: kd> !errrec fffffa8010e42028
===============================================================================
Common Platform Error Record @ fffffa8010e42028
-------------------------------------------------------------------------------
Record Id     : 01d0fd58b6a144e4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/2/2015 22:42:58 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010e420a8
Section       @ fffffa8010e42180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010e420f0
Section       @ fffffa8010e42240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8010e42240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010e42138
Section       @ fffffa8010e422c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR="Red"]Error         : Internal timer (Proc 0 Bank 3)[/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x0000388006355b76
  Misc.       : 0x000000000003ffff

As I understood from some users, either this error or another similar error was being caused a lot by the PSU.
Please check your PSU for connection and the voltages.
Please check your BIOS for the 3.3v, 5v and 12v values.

Please note the temperatures of your CPU when idle and under load.

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

[axe0]

Did a CHKDSK an all came back fine. had seagate tools and that had the same results.
Hard Disk Sentinal shows no problems as well , at least on main drive. One drive has 3 bad sectors other then that rest are ok.

Please disconnect this hard drive while troubleshooting.

 

[eracet]

I checked connections and all seemed solid. But one thing made me wonder is if the UPS could be having issues. Less than a year old. So I took the UPS off of the tower supply for now.
Changed some settings in the bios after my last crash, voltage etc .. just troubleshooting.. obvious it didn't work since it crashed again this morning.
According to my logs CPU was running at 8.5% when it crashed.
At idle PSU temps run a consistent 100-120F tops.
Will attach some Aida64 info. Also another DMP file.

 

[eracet]

Here is another few reports.

 

[axe0]

Please revert the overclocking back to stock as it could cause the 0x124 you get.

CPU Clock   4430.1 MHz  (original: 3400 MHz, overclock: 30%)

The last crash has the same cause btw.

0: kd> !errrec fffffa8010eb2028
===============================================================================
Common Platform Error Record @ fffffa8010eb2028
-------------------------------------------------------------------------------
Record Id     : 01d0fd92c7736f25
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/3/2015 13:04:20 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010eb20a8
Section       @ fffffa8010eb2180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010eb20f0
Section       @ fffffa8010eb2240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8010eb2240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8010eb2138
Section       @ fffffa8010eb22c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR="Red"]Error         : Internal timer (Proc 0 Bank 3)[/COLOR]
  Status      : 0xbe00000000800400
  Address     : 0x00003960007900d4
  Misc.       : 0x000000000003ffff

 

[eracet]

Seen it was saying that, last bios settings I did it either goes 1648 or 4430.
Usually when I ran games or programs before it jumped to 4400. The last time I was going through bios I let it autoset.
I do see the FSB is a constant overclock or 3%.

Its not crashing now , if it goes BS again I will set all to default stock.

Hoping that the UPS did the trick, but who knows.

 

[eracet]

Over the past 2 days I have ran the PC without using the UPS that I got in June. (at least the battery backup part)
And everything worked great and as normal.

This morning I tested the battery + surge part on the PC and it crashed with a memory managment error within an hour.

Did a screen record during this time with the UPS software to see if it jumps in output volts.

Had to do a repair on the video due to crash during recording.
But I am 94.3 Percent sure that the battery backup is the cause.

I will wait until the end of this week to consider it solved.
Thank you for helping me troubleshoot. This is what lead me to working on power issues instead of software issues.

 

[axe0]

You're welcome
Let me know how it goes meanwhile.

 

[eracet]

To my surprise I had 2 BS crashes within 24 hours.
Memory management. on both occasions.
After these crashes happened motherboard had some strange restart.

BS Crash
Hold power to reset.
Started power then a pause.
no visual or HDD activity and code 9a on motherboard.
Another hard reset and worked fine.

After the first log I turned down overclocking a lot. and checked some other settings.

After second BSOD I changed ram timing to auto instead of what was default.

Attached are that last 2 BSOD

 

[axe0]

After the first log I turned down overclocking a lot. and checked some other settings.

You stated in your first post that you reverted back to stock, did you started to overclock again?
Please make sure nothing is overclocked while troubleshooting.

The first is the 0x101(CLOCK_WATCHDOG_TIMEOUT) which has a great chance to be related with overclocking.

If you are getting any BSOD, please use the tool again and upload the zip file.

 

[eracet]

After the first log I turned down overclocking a lot. and checked some other settings.

You stated in your first post that you reverted back to stock, did you started to overclock again?
Please make sure nothing is overclocked while troubleshooting.

The first is the 0x101(CLOCK_WATCHDOG_TIMEOUT) which has a great chance to be related with overclocking.

If you are getting any BSOD, please use the tool again and upload the zip file.

Not sure had some turbo mode set. I did the UPS check plugin adjustment. I did make changes (many changes in bios) to help resolve some issues before I did that.

Overall.... I changed stuff in the bios 3 times, may of did the wrong one before the UPS surge plugin thing.
This bios really.. wants to you to overclock. so may of reverted before I resaved. some of the settings didn't adjust correctly. Like typing clock speed then going to another page and it goes back to what it was before.

I do have a speed monitor on my keyboard so can keep an eye on it reguardless of what is going on.

I think I got it turned down some now. Going to do some research on the MB and see what I can find out about some of the settings.

 

[eracet]

Since the last post I have not had any BS crashes. Clock speed was reduced.

This Thursday night I am going to try the power UPS again , and if it crashes with the PS issue going to submit warranty on the UPS.

Also recieved my Windows 10 upgrade , have not did it yet, going to probably do it on Friday so I have a chance to monitor it while I have a day off.