Windows 10 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124

N

Natza09

New Member
Joined
Sep 22, 2019
Messages
5
HI All,

I have recently built a new pc and am having nothing but issues with random freezing and crashing.

The hardware is:
Intel Core i7 9700K Processor (Not Overclocked)
ASUS ROG Maximus XI Hero Motherboard
NZXT Kraken X62 280mm AIO Liquid CPU Cooler
ADATA XPG SX8200 Pro M.2 NVMe SSD 1TB
Corsair AX850 Titanium Modular 850 Watt Power Supply
Corsair Vengeance RGB Pro CMW16GX4M2Z3600C18 16GB (2x8GB) DDR4 (XMP Not enabled)
EVGA GeForce GTX 1080 Founders Edition 8GB (This isnt new as its part of my old rig) (Not Overclocked)

I have done 2x fresh windows 10 pro installs and the problem still exsists.

The Asus Bios has been updated to the most current.

When i check the Reliability Monitor the error is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb507f3649028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\WINDOWS\Minidump\092219-8000-01.dmp. Report Id: f01fdacb-c9dc-47b4-a8a3-e73a19172c4b.

It is the same everytime it crashes, Also the crashes are random and can happen every day to every 4 or 5 days.

I have been doing a fair bit of digging around the net to try and resolve the issue however i cant seem to find a solution.

I would really appricate any help with this crashing problem.

Attached is the W7F Diagnostic Tool Zip.

Regards, Natz.
 

Attachments

Solution
S
  1. Go to (F2) BIOS and select Advanced Chipset Features. Disable the C1E Enhanced Halt State.
  2. Use a registry cleaner to clean the registry.
  3. Get the latest Microsoft hot fixes and updates.
  4. Verify all drivers and firmware are up to date.
  5. If over clocking is set, remove any of those settings.
  6. Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
Sort by date Sort by votes
You're getting a stop 0x124 pointing at the cpu being at fault. Can you update your bios to the latest.
 
Upvote 0 Downvote
@nmusk Thanks for your help.

I must admit i only flashed the BIOS a few weeks ago when i got the mobo so I ruled that out as an issue.

The Bios has just been updated to the latest 1302 from 1105, It will be a wait and see game now.

Thanks again, I report back in a week (sooner if it crashes) with an update.
 
Upvote 0 Downvote
Ok I crashed again while the pc was idle, The error is a bit different this time.

Error code:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000000, 0xfffff802311e4b30, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\092319-7343-01.dmp. Report Id: b96b05d9-226d-4496-a817-183af1887464.

New w7f file attached.
 

Attachments

Upvote 0 Downvote
I would also open an admin command prompt and do a sfc /scannow and then a dism /online /cleanup-image /restorehealth These commands will scan and attempt to fix any system corruption.
 
Upvote 0 Downvote
I have done another fresh install using the win10 upgrade tool advised by the Microsoft team.
I will see if that helps, I will also check for my Intel drivers and i will run the commands you mentioned above and report back in a few days.
Thanks for your help @nmsuk, I really appricate it as this issue has been doing my head in.
 
Upvote 0 Downvote
Ok so I just had another crash.

I used the intel tool (before the crash) which advised me that all drivers are up to date.

I have now just run the commands listed above (after the crash) and received this information:

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

The dism tool came back with;

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

I will let it run some more and see if the repaired corrupted files have fixed anything.

New W7F grabbed aswell.

Thanks.
 

Attachments

Upvote 0 Downvote
  1. Go to (F2) BIOS and select Advanced Chipset Features. Disable the C1E Enhanced Halt State.
  2. Use a registry cleaner to clean the registry.
  3. Get the latest Microsoft hot fixes and updates.
  4. Verify all drivers and firmware are up to date.
  5. If over clocking is set, remove any of those settings.
  6. Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.
 
Upvote 0 Downvote
Solution
I have been having similar issues with crashing and getting the same error. Where you able to resolve this issue? Of note, our PC's share the same CPU so I'd wonder if it's an issue with the 9700k.
 
Upvote 0 Downvote
I think backgroundTaskHost might be the issue if it's during gaming. I'm going to try disabling it. I already checked my CPU and it seems to be fine. I applied new thermal paste, and put a 3000rpm fan on the Noctua heat sink to replace the old fan. Between Destiny 2 and whatever the issue is, it just gets too hot.
 
Upvote 0 Downvote
I have this issue too, recently the cpu has been getting alot hotter. I don't believe summer is the reason why as last summer it didn't happen. did you find a solution to this?
 
Upvote 0 Downvote
new said:
I have this issue too, recently the cpu has been getting alot hotter. I don't believe summer is the reason why as last summer it didn't happen. did you find a solution to this?
Click to expand...
Dust build up?

Remove daust from vents and heatsinks.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 10 The bugcheck was: 0x00000124
Replies
1
Views
4K
kemical
G
  • Solved
Windows 10 BSOD - win10pro64 - The computer has rebooted from a bugcheck.
Replies
8
Views
4K
kemical
  • Solved
Windows 8 The computer has rebooted from a bugcheck.
Replies
4
Views
2K
Wallengard
S
  • Question Question
Windows 7 Frequent BSOD reboot : event log "......bugcheck was: 0x00000076 (0x0000000000000000, 0xfffffa8004b
Replies
1
Views
2K
ChatGPT