• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

6700k BSOD 0x00000124

Associate
Joined
22 Dec 2012
Posts
7
Hello everyone. I have a 6700k. Has worked beautifully for the last 14 months. Recently started getting BSOD uncorrectable error 0x00000124. The only way to avoid this BSOD is to dramatically reduce multiplier in my bios top around x34 in my bios.



HWINFO shows CPU Cache L0 errors.



Event viewer is showing "Error The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe306c0000028, 0x00000000f61fb800, 0x0000000000040150). "

Details on this Bugcheck are as follows,



System


- Provider
[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck


- EventID 1001


[ Qualifiers] 16384
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated


[ SystemTime] 2018-03-04T16:48:57.788986000Z
EventRecordID 31423
Correlation
-
Execution


[ ProcessID] 0
[ ThreadID] 0
Channel System
Computer DESKTOP-9BNV6TK
Security
-
EventData


param1 0x00000124 (0x0000000000000000, 0xffffe306c0000028, 0x00000000f61fb800, 0x0000000000040150)
param2 C:\WINDOWS\Minidump\030418-36203-01.dmp
param3 ea6c7982-6669-44bf-b71c-968aa9612ee9




I also get a warning,



"A corrected hardware error has occurred.





Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Cache Hierarchy Error

Processor APIC ID: 2





The details view of this entry contains further information."



- System


- Provider
[ Name] Microsoft-Windows-WHEA-Logger
[ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}


EventID 19
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated


[ SystemTime] 2018-03-04T16:50:25.514976000Z
EventRecordID 31434
- Correlation


[ ActivityID] {B58C64EB-C168-463B-8561-4FE8EE7B8275}
- Execution


[ ProcessID] 3564
[ ThreadID] 4464
Channel System
Computer DESKTOP-9BNV6TK
- Security


[ UserID] S-1-5-19
- EventData


ErrorSource 1
ApicId 2
MCABank 0
MciStat 0xd40d514000040150
MciAddr 0x1f80220ce79b0
MciMisc 0x0
ErrorType 9
TransactionType 0
Participation 256
RequestType 5
MemorIO 256
MemHierarchyLvl 0
Timeout 256
OperationType 256
Channel 256
Length 928
RawData 435045521002FFFFFFFF03000200000002000000A003000018321000040312140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F8904D7B039BD8B3D30100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000098020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000200000000000000000000000000000000000000000000007F010000000000000002010300000000E30605000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000200000000000000E306050000081002BFFBFA7FFFFBEBBF0000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00142000000000B079CE2002F801000000000000000000000000000000000000000000000000000100000001000000BDB81AE4D8B3D3010200000000000000000000000000000000000000000000005001040040510DD4B079CE2002F8010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000




Any help on solving this problem would be HUGELY appreciated.

Martin
 
Any overclock? What voltages? Rest of the computer specs?
Thanks for the reply.

I have run an overclock of 4.6 ghz at 1.29 volts for the last 8 months. Now cannot even run default settings without BSOD. Only way to use computer is to set multiplier to x34 in bios. With Multiplier at x34, Vcore Volts is max 1.264, still getting CPU Cache L0 errors in hwinfo, but no BSOD

Mobo - Asus ROG Z170 Maximus VIII Hero Motherboard
CPU - Intel i7 6700k
Ram - Corsair Vengeance LPX 16GB (2x8GB) 3200MHz DDR4 Memory
GPU - GTX 1080 Hybrid
SSD - 525GB Crucial MX300, M.2 SSD, SATA III - 6Gb/s, 3D NAND technology, Read 530MB/s, Write 510MB/s, 92K/83K IOPS
HDD - 500GB Toshiba DT01ACA050, 3.5" HDD, SATA III - 6Gb/s, 7200rpm, 32MB Cache
PSU - 750W Corsair Builder Series CX750M 80PLUS Bronze Modular Power Supply

Cooling is no issue. CPU and GPU both hybrid and never exceed 45 - 50 degrees C.

Thanks again.
 
Usually 124 BSOD is you don't have enough VTT/System Agent voltage - sometime not enough vcore but generally that is a brute force way to fix the problem.

It might also be the memory controller isn't upto the RAM or RAM settings you are using - sometimes this doesn't manifest at first until you start making more intensive use of the machine when more programs and updates, etc. are installed.
Does this sound like it can only be CPU dying? The Ram settings are all default in bios atm and still getting BSOD
 
Try setting the RAM manually to 2133MHz with the appropriate timings - 13-15-15-28 IIRC and work from there - if you haven't done it is worth running memtest86 as well to make sure RAM is stable.
I dont want to mess to much with memory as i dont know a lot about timings but I will run memtest and update you. Thank you
 
Try setting the RAM manually to 2133MHz with the appropriate timings - 13-15-15-28 IIRC and work from there - if you haven't done it is worth running memtest86 as well to make sure RAM is stable.

Memtest passed. Ijust had another BSOD. Event viewer showed;

- System


- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



EventID 41


Version 6


Level 1


Task 63


Opcode 0


Keywords 0x8000400000000002


- TimeCreated

[ SystemTime] 2018-03-05T18:15:56.306780600Z



EventRecordID 32049


Correlation


- Execution

[ ProcessID] 4
[ ThreadID] 8



Channel System


Computer DESKTOP-9BNV6TK


- Security

[ UserID] S-1-5-18



- EventData

BugcheckCode 292
BugcheckParameter1 0x0
BugcheckParameter2 0xffff9a0b09d85028
BugcheckParameter3 0xf61d7ac0
BugcheckParameter4 0x40150
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true
CheckpointStatus 0
 
updated any drivers/bios recently?
as i mentioned earlier, imo, it smells like the cpu giving up - assuming that you definitely had no problems with it for the last 14 months and haven't updated any core software

I have updated bios in order to repair this issue but did not work. nothing else changed with regards to CPU. I am also leaning towards broken CPU purely because reducing multiplier stops bsod. #
Definatly been no issues since buying it until now.
 
Back
Top Bottom