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 : 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
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