random bsod every day bugcheck - 0x124 - Windows 10 x64

Justuss

Justuss

Member
Joined
Mar 5, 2019
Posts
15
hello
001.png


well... thank you for the great forum i do really enjoy reading those tutorials and guide about the pc world
I'am having bad time with my desktop trying to fix the BSOD problem so , it occurs randomly no specific time or period the thing is i was using my computer normally as usual and suddenly blue screen .

so i tried to run some guides trying to isolate the issue but it seems nothing is working
i did run gpu stress test for 1 hour and cpu stress test for 2 hours and memtest with 8 passes also did the chkdsk /f /r ,did not show any error or bsod ,my last resort was installing clean windows and still same thing also I did reset my bios with no overclocking
also i did test the HDD using SeaTools and its all good long test and the ssd using the HD Tune it does show this in the health window as below

44644

last thing it does say weha_uncorrectable_error on the blue screen with bugcheck 0x124

i will try to run Driver Verifier later as it take long time

the requested files is attached

your help will be greatly appreciated

· OS - Windows 10, 8.1, 8, 7, Vista ? win 10 pro 64bit
· x86 (32-bit) or x64 (64-bit)?
· What was the originally installed OS on the system? win 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?full retail version
· Age of system (hardware) ? 4 years
· Age of OS installation - have you re-installed the OS? yes 1-2 month after re-installation

· CPU Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
· Video Card (1) Intel(R) HD Graphics 530 (2) NVIDIA GeForce GTX 970
· MotherBoard - ASUSTeK COMPUTER INC. Z170 PRO GAMING
· Power Supply - xfx ts850 watt
· System Manufacturer custom build
· Exact model number (if laptop, check label on the bottom)

· Laptop or Desktop? Desktop


Computer Type: PC/Desktop
System Manufacturer/Model Number: ASUSTeK COMPUTER INC.
OS: Microsoft Windows 10 Pro 64-bit 17763
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Motherboard: ASUSTeK COMPUTER INC. Z170 PRO GAMING
Memory: G-Skill 16.00 GB F4-3200C16-8GVKB
Graphics Card: (1) Intel(R) HD Graphics 530 (2) NVIDIA GeForce GTX 970
Sound Card: (1) NVIDIA High Definition Audio (2) NVIDIA Virtual Audio Device (3) Realtek High Definition Aud
Monitor(s) Displays: asus 23"
Screen Resolution: 1920 x 1080 x 32 bits (4294967296 colors) @ 60 Hz
Keyboard: hyper x fps alloy
Mouse: asus Cerberus
PSU: xfx ts850 watt
Case: xegmatic tower case
Cooling: seidon 120v plus cooler master
Hard Drives: (1) ssd KINGSTON SHSS37A240G (2) hdd WDC WD20EZRX-00D8PB0 (3) hdd ST1000DM003-1CH162
Internet Speed: 14 mbps
Browser: chrome/firfox
Antivirus: malwarebyte
 

Attachments

Hello Justuss,

Hardware errors like you are getting are amongst the hardest BSODs to diagnose. It could be SSD, motherboard or CPU. The CPU reports the error as being a Micro architecture error but with the result you got from the SSD test I would start there and try a new or good SSD if you have one you can use. Next item would be the CPU if you can try a replacement or test with another one.

3: kd> !errrec ffffad8fb7ad4028
===============================================================================
Common Platform Error Record @ ffffad8fb7ad4028
-------------------------------------------------------------------------------
Record Id : 01d4d2d84266ab2c
Severity : Fatal (1)
Length : 864
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/4/2019 23:03:02 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40a8
Section @ ffffad8fb7ad4180
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 : 0x00000000000506e3
Processor ID : 0x0000000000000003

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40f0
Section @ ffffad8fb7ad4240
Offset : 536
Length : 64
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000003
CPU Id : e3 06 05 00 00 08 10 03 - bf fb fa 7f 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

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad4138
Section @ ffffad8fb7ad4280
Offset : 600
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 3 Bank 0)
Status : 0xf20000c000010005
 
Hi. . .

We just migrated from vBulletin 4 to to the new XenForo 2.1 forum software and I like the way you used the spoilers with the titles. I was unaware of this feature with the spoiler titles. Thank you for showing me how to use them! :)

I don't exactly know the meaning of the HD Tune (B7) SATA Downshift Count failure and will need to ask a hardware expert about it. I sit on the software side of the fence.

I see that you listed the hardware as about 4 years old, but the Windows 10 OS is listed in one of the reports as having been reinstalled about 17 days ago -
Code: 
Original Install Date: 2019-02-16, 8:32:32 PM

Was there any particular reason for reinstalling Windows 10 so recently like BSODs or other system problems?

The bugcheck on all 4 dumps was 0x124 = WHEA = Windows Hardware Error Architecture, a/k/a "Machine Check Exception".

Machine-check exception - Wikipedia

0x124 BSODs are notoriously difficult to solve because the cause is simply "unknown hardware failure".

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

I see that you have an Intel CPU, so I'd like you to run this Intel CPU test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)

Otherwise, all I can really do here is to give you some hardware diagnostic programs to run - which I know that you've said that you have already run.
The problem may also be with other hardware parts such as the motherboard or PSU for which there are no valid software tests.

Both RAM and HDD diagnostic tests are DOS-based, so Windows does not load during boot-up. You will be booting from your system's DVD/CD drive, so you may need to change the "firing order" (the order in which the system determines which device to boot from first -- e.g., the HDD, USB, DVD/CD drive, etc... ).

All 4 BSODs have today's date on them - 5 March 2019. Did the BSODs just suddenly start today? Have you ever had a BSOD on the system before - whether with the current OS or a prior OS, if you recall?

Any recent hardware changes/upgrades?

We're looking for something, anything really.

This is the actual WHEA record from one of the dumps. All 4 say basically the same thing. Scroll down to the bottom -
Code: 
3: kd> !errrec ffffad8fb7ad4028
===============================================================================
Common Platform Error Record @ ffffad8fb7ad4028
-------------------------------------------------------------------------------
Record Id : 01d4d2d84266ab2c
Severity : Fatal (1)
Length : 864
Creator : Microsoft
Notify Type : [HI]Machine Check Exception[/HI]
Timestamp : 3/4/2019 23:03:02 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40a8
Section @ ffffad8fb7ad4180
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 : 0x00000000000506e3
Processor ID : 0x0000000000000003

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40f0
Section @ ffffad8fb7ad4240
Offset : 536
Length : 64
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000003
CPU Id : e3 06 05 00 00 08 10 03 - bf fb fa 7f 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

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad4138
Section @ ffffad8fb7ad4280
Offset : 600
Length : 264
Flags : 0x00000000
Severity : Fatal

[HI]Error : Unknown (Proc 3 Bank 0)[/HI]
Status : 0xf20000c000010005

As you can see at the end of that WHEA error record, the error is listed as "unknown" and mentions Processor 3; bank 0.

Here are all 4 dump error records (just that last "Error" record line) - windbg command !errrec memory_address_WHEA_record -
Code: 
Error : Unknown (Proc 2 Bank 0)
Error : Unknown (Proc 3 Bank 0)
Error : Unknown (Proc 3 Bank 0)
Error : Unknown (Proc 3 Bank 0)

This unknown error could be caused by just about anything from the motherboard itself to RAM, PSU, CPU, a wire, a cable, etc... - very difficult to ascertain the origin.

Please do run Driver Verifier, although I do not believe at this time that the BSODs are being caused by a rogue 3rd party driver.

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

You can use the system while running Driver Verifier (DV), but please note that if DV detects a violation, it will BSOD your system immediately and you'll lose any open files. So, if you are working, be sure to constantly save your work files.

DV must run in the background for a minimum of 24 hours. If a BSOD occurs, go to \windows\minidump, look at the filenames (dates) and get the most recent one; copy out to Documents or Desktop, zip it up and attach to your next post. You cannot zip files in the \windows directory.

Regards. . .

jcgriff2
 
Last edited:
jcgriff2 said:
I don't exactly know the meaning of the HD Tune (B7) SATA Downshift Count failure and will need to ask a hardware expert about it. I sit on the software side of the fence.
Click to expand...
An information parameter used by many disc manufacturers. Most commonly used by Western Digital and Samsung. It may be the result of aging disk and / or problems with electromechanical components. It does not indicate a failure directly. With an increasing parameter, it is recommended to create regular copies and monitor the disk.
Source:
https://www.elektroda.pl/rtvforum/topic1467175.html
 
philc43 said:
Hello Justuss,

Hardware errors like you are getting are amongst the hardest BSODs to diagnose. It could be SSD, motherboard or CPU. The CPU reports the error as being a Micro architecture error but with the result you got from the SSD test I would start there and try a new or good SSD if you have one you can use. Next item would be the CPU if you can try a replacement or test with another one.

3: kd> !errrec ffffad8fb7ad4028
===============================================================================
Common Platform Error Record @ ffffad8fb7ad4028
-------------------------------------------------------------------------------
Record Id : 01d4d2d84266ab2c
Severity : Fatal (1)
Length : 864
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 3/4/2019 23:03:02 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40a8
Section @ ffffad8fb7ad4180
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 : 0x00000000000506e3
Processor ID : 0x0000000000000003

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40f0
Section @ ffffad8fb7ad4240
Offset : 536
Length : 64
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000003
CPU Id : e3 06 05 00 00 08 10 03 - bf fb fa 7f 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

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad4138
Section @ ffffad8fb7ad4280
Offset : 600
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 3 Bank 0)
Status : 0xf20000c000010005
Click to expand...

thank you ,
yes indeed its hard as i tried a lot of things i will try to replace the ssd and keep monitoring .
 
jcgriff2 said:
Hi. . .

We just migrated from vBulletin 4 to to the new XenForo 2.1 forum software and I like the way you used the spoilers with the titles. I was unaware of this feature with the spoiler titles. Thank you for showing me how to use them! :)

I don't exactly know the meaning of the HD Tune (B7) SATA Downshift Count failure and will need to ask a hardware expert about it. I sit on the software side of the fence.

I see that you listed the hardware as about 4 years old, but the Windows 10 OS is listed in one of the reports as having been reinstalled about 17 days ago -
Code: 
Original Install Date: 2019-02-16, 8:32:32 PM

Was there any particular reason for reinstalling Windows 10 so recently like BSODs or other system problems?

The bugcheck on all 4 dumps was 0x124 = WHEA = Windows Hardware Error Architecture, a/k/a "Machine Check Exception".

Machine-check exception - Wikipedia

0x124 BSODs are notoriously difficult to solve because the cause is simply "unknown hardware failure".

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

I see that you have an Intel CPU, so I'd like you to run this Intel CPU test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)

Otherwise, all I can really do here is to give you some hardware diagnostic programs to run - which I know that you've said that you have already run.
The problem may also be with other hardware parts such as the motherboard or PSU for which there are no valid software tests.

Both RAM and HDD diagnostic tests are DOS-based, so Windows does not load during boot-up. You will be booting from your system's DVD/CD drive, so you may need to change the "firing order" (the order in which the system determines which device to boot from first -- e.g., the HDD, USB, DVD/CD drive, etc... ).

All 4 BSODs have today's date on them - 5 March 2019. Did the BSODs just suddenly start today? Have you ever had a BSOD on the system before - whether with the current OS or a prior OS, if you recall?

Any recent hardware changes/upgrades?

We're looking for something, anything really.

This is the actual WHE record from one of the dumps. All 4 say basically the same thing. Scroll down to the bottom -
Code: 
3: kd> !errrec ffffad8fb7ad4028
===============================================================================
Common Platform Error Record @ ffffad8fb7ad4028
-------------------------------------------------------------------------------
Record Id : 01d4d2d84266ab2c
Severity : Fatal (1)
Length : 864
Creator : Microsoft
Notify Type : [HI]Machine Check Exception[/HI]
Timestamp : 3/4/2019 23:03:02 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40a8
Section @ ffffad8fb7ad4180
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 : 0x00000000000506e3
Processor ID : 0x0000000000000003

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad40f0
Section @ ffffad8fb7ad4240
Offset : 536
Length : 64
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000003
CPU Id : e3 06 05 00 00 08 10 03 - bf fb fa 7f 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

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffad8fb7ad4138
Section @ ffffad8fb7ad4280
Offset : 600
Length : 264
Flags : 0x00000000
Severity : Fatal

[HI]Error : Unknown (Proc 3 Bank 0)[/HI]
Status : 0xf20000c000010005

As you can see at the end of that WHEA error record, the error is listed as "unknown" and mentions Processor 3; bank 0.

Here are all 4 dump error records (just that last "Error" record line) - windbg command !errrec memory_address_WHEA_record -
Code: 
Error : Unknown (Proc 2 Bank 0)
Error : Unknown (Proc 3 Bank 0)
Error : Unknown (Proc 3 Bank 0)
Error : Unknown (Proc 3 Bank 0)

This unknown error could be caused by just about anything from the motherboard itself to RAM, PSU, CPU, a wire, a cable, etc... - very difficult to ascertain the origin.

Please do run Driver Verifier, although I do not believe at this time that the BSODs are being caused by a rogue 3rd party driver.

Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

You can use the system while running Driver Verifier (DV), but please note that if DV detects a violation, it will BSOD your system immediately and you'll lose any open files. So, if you are working, be sure to constantly save your wotk files.

DV must run in the background for a minimum of 24 hours. If a BSOD occurs, go to \windows\minidump]/b], look at the filenames (dates) and get the most recent one; copy out to Documents or Desktop, zip it up and attach to your next post. You cannot zip files in the \windows directory.

Regards. . .

jcgriff2
Click to expand...

yeah its a nice feature :D

regarding the ssd i will try to get it replaced ASAP
yeah i did re-install the windows because of the bsod since that time im having it and trying to figure out the soluation

regarding the cpu stress i did the test today for 15 min and the ipdt test twice and the results was pass
yeah i tried to find any piece of software to test the motherboard but didnt find ,but for the psu i did monitor the voltages
from the bios all with the accepted tolerance

ooh yes alot its not the only day that i have bsod and yeah with this OS and the previouse one ,actually i did the re-install
to fix it xd

No changes/upgrades

I tried searching on google for those codes and came with nothing

so to summarize :-
  • need to do memtest+ for each stick
  • run the Driver Verifier 24 hrs
  • replacing my ssd

one more thing i need to know i did the HDD test NOT the DOS test is there a difference should i do it again on the DOS ?

thank you for the reply
 
Yes - do the DOS Disk test. The test done within Windows cannot access the entire HDD. It cannot hurt anything to do the test.

"need to do memtest+ for each stick" - yes and for each slot as well. I know that will take extra time, but it should be done that way.

How old is the SSD?

My pleasure on the reply, but I think the others pretty much covered everything first!

Be sure to do the Intel CPU test.
 
jcgriff2 said:
Yes - do the DOS Disk test. The test done within Windows cannot access the entire HDD. It cannot hurt anything to do the test.

"need to do memtest+ for each stick" - yes and for each slot as well. I know that will take extra time, but it should be done that way.

How old is the SSD?

My pleasure on the reply, but I think the others pretty much covered everything first!

Be sure to do the Intel CPU test.
Click to expand...

Ok
how many passes should be enough for the memtest+ ?

its 4 years approximately
 
Justuss said:
thank you ,
for mentioning the update daily i check for the update and i took your advice and updated the bios
hope that solve the problem .
Click to expand...

Do keep us posted on progress. If you get any new BSODs post a new set of logs. When making lots of changes it can be challenging to identify which one makes a difference, therefore I would suggest you allow the system to run for a while between each change to get some feel for whether it has made an improvement.

I advise 8 passes for Memtest+
 
Hello,

update :

while running Driver verifier my pc freeze and couldn't collect dumps or event logs

i get this message in the event logs "Dump file creation failed due to error during dump creation."

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 2

The details view of this entry contains further information.


any idea on this ?
 
Last edited:
The warning may be as a result of update to Windows/BIOS for Meltdown and Spectre mitigation.

Failure to create a dumpfile Meltdown and Spectre Mitigation possibly related to the drive issue.

What other tests/checks did you do? If so, any results/comments about them?

Can you upload another set of logs for the team to take a look at, please?
 
satrow said:
The warning may be as a result of update to Windows/BIOS for Meltdown and Spectre mitigation.

Failure to create a dumpfile Meltdown and Spectre Mitigation possibly related to the drive issue.

What other tests/checks did you do? If so, any results/comments about them?

Can you upload another set of logs for the team to take a look at, please?
Click to expand...


Oh I see

will i did the processor test for 20 min each test in prim95 with ipdt and furmark for 30 min all pass

regarding the driver verifier i did run it for 21 hrs all was good until the freeze so i stoped the verifier

and started using the pc for maybe 5 hrs then i got bsod 3 times - i have the dumps for it - after that i tried to run the verifier again and the same freeze happened in few hours

also i changed the sata cable and the socket on the motherboard .

couldn't run HDD test in Dos as i did manage to get the bootable usb for the software but the GUI didn't work only CLI so skipped the test as i did it on windows and dont know any command for that

regarding the memtest+ it does need a lot of time to do so i will keep it for last as i don't think its necessary after the memtest i have done unless if i found any error in the previous memtest to isolate which slot or which socket have made that error

anyway here is the new logs as requested and im going to get new ssd as the s.m.a.r.t info indicate there is error and aging drive so will come back after the replacement

thank you
 

Attachments

jcgriff2 said:
See if there is a BIOS update for your system. Current BIOS:
Code: 
BIOS Version/Date    American Megatrends Inc. 3805, 2018-05-16
SMBIOS Version    3.0

Run Intel CPU Test - CPU STRESS testing: Mersenne.org Prime95 and Intel Processor Diagnostic Tool (IPDT)

Regards. . .

jcgriff2
Click to expand...

ok here is the result in text file for the intel cpu test attached

44779

regarding the BIOS i did update it last time this the last version
Z170 PRO GAMING BIOS & FIRMWARE | Motherboards | ASUS USA

version 3805
 

Attachments

Well... you passed the Intel test, which is good, but does not help us in our quest to find the cowardly hidden faulty hardware component.

The link you gave me for the BIOS update says "Version 11.8.55.3510"

Yet your system reports like systeminfo and msinfo32 shows:
Code: 
BIOS Version/Date    American Megatrends Inc. 3805, 2018-05-16
SMBIOS Version    3.0

Also, the date from the link = 2018/08/27 where your BIOS date = 2018-05-16

They appear different to me.

Please boot into BIOS and check the information there. We certainly don't want to risk updating BIOS with the wrong BIOS update.

Regards. . .

jcgriff2
 
jcgriff2 said:
Well... you passed the Intel test, which is good, but does not help us in our quest to find the cowardly hidden faulty hardware component.

The link you gave me for the BIOS update says "Version 11.8.55.3510"

Yet your system reports like systeminfo and msinfo32 shows:
Code: 
BIOS Version/Date    American Megatrends Inc. 3805, 2018-05-16
SMBIOS Version    3.0

Also, the date from the link = 2018/08/27 where your BIOS date = 2018-05-16

They appear different to me.

Please boot into BIOS and check the information there. We certainly don't want to risk updating BIOS with the wrong BIOS update.

Regards. . .

jcgriff2
Click to expand...


hello ,

well the second version in the link is for the last bios version as the first one is for meltdown mitigation fix
so i did this : removed the chipset driver -> restart -> installed it again -> restart -> load the last version of the bios again --> last i did install the mitigation tool and used it

so far so good no bsod if anything happened i will update the topic

thank you
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top