I kinda doubt you will get an answer from another Aurora-R13 owner (on this issue), but it's good to live in hope.
But let me ask you ... when they swapped the motherboards ... can you definitively list the parts that were transferred over? My idea is that if it's not the motherboard, it might be one of the components that were transferred.
Thank you for the suggestion. The WHEA-Logger Event ID 17 errors specifically identify Intel PCIe Root Complex device 8086:7ABC on PCIe Root Port 5 which is integrated into the Z690 chipset on the motherboard itself. The Killer E3100G NIC connected to that root port is soldered directly onto the motherboard and cannot be transferred between boards. Intel's own published Specification Update Document 682436 confirms errata ADL013 and ADL014 as NO FIX silicon level defects present in every i9-12900F processor meaning the defect exists at the platform level regardless of which motherboard is installed and components added to it.
0. The components transferred between motherboards were the i9-12900F processor, 128GB DDR5 RAM, RTX 3080 GPU, and NVMe SSD. The Killer E3100G NIC is soldered directly onto the motherboard and was replaced with each motherboard swap.
1. Currently running BIOS version 1.26.0.
2. Intel ME Interface driver version is 2433.6.3.0 dated August 15 2024. Dell does not publicly document which specific ME version is bundled with each R13 BIOS release so I am unable to confirm whether this is the exact matching version for 1.26.0.
The crash pattern began at approximately once per month and has escalated dramatically to multiple times daily over the course of months. A BIOS or Intel ME firmware issue would not exhibit this kind of progressive escalation pattern. This is consistent with hardware degradation, not a firmware configuration issue.
A BIOS or Intel ME firmware issue would not exhibit this kind of progressive escalation pattern. This is consistent with hardware degradation, not a firmware configuration issue.
Maybe your first post in this thread was just venting. I thought you were reaching out to the community for help.
I read your reluctance.
I certainly have better things to do. Would you rather I stop trying to help you, and you can just wait for the other Aurora-R13 owners (with this same problem) to start posting so yall can compare notes?
According to Intel's Specification Update Document 682436 Summary Table of Changes, ADL013 and ADL014 are listed as No Fix under the S processor line — which covers all 12th Gen Alder Lake desktop processors including both the i9-12900F and the i9-12900K. Both SKUs share the same silicon and are equally affected by these errata with no fix available across all steppings.
Motherboard: MSI PRO Z690-A WIFI DDR5 (MS-7D25) Memory: 32GB CORSAIR VENGEANCE DDR5 5200MHz (2x16GB DIMMs running Dual Channel) Monitor: LG 32in 4K UltraGear Nvidia-GSync IPS 144-Hz Gaming-Monitor Window-11 Pro (VBS is Disabled for Max-Gaming Performance)
It is pushed hard (one example is bi-weekly multi-hour WoW Guild Raiding Sessions). It is now and has always been rock hard stable. I just checked and it's Reliability History Report score is still 10.
In 4-years, I've never seen a STOP-screen or BSoD. AFAIK, no WHEA errors (but I'll be glad to look for them if you tell me where you found yours).
So, if your theory is that your problems are linked to some inherent defect in ALL Intel i9-12900 model processors, I have a real-life example that goes against that theory.
2a. Intel ME Interface driver version is 2433.6.3.0 dated August 15 2024.
2b. Dell does not publicly document which specific ME version is bundled with each R13 BIOS release
3. A BIOS or Intel ME firmware issue would not exhibit this kind of progressive escalation pattern. This is consistent with hardware degradation, not a firmware configuration issue.
0. Good list.
My idea is that since the motherboard has been replaced 2-3 times and the issue still exists, maybe the problem is with one of the components that gets swapped across.
1. A little outdated, but not too badly (about 4 revisions behind).
Among other things, they address CVE's and even hard-defects (like 0x12B) with updated MicroCode.
2a. Acknowledged.
2b. Yes they do (in a round-about way). When-and-if the time comes, I can show you how.
3. I don't have any information about such things.
My experience has shown me that any deficiency with the computer tends to eventually affect its operation as a whole (weakest-link and all that).
I do seem to remember that WHEA errors are often related to ram memory and that sub-system.
I have been experiencing persistent WHEA-Logger Event ID 17 errors
On the computer with the Intel i9-12900K ...
Event Viewer / Windows Logs / System /
- I click on Source field at top to alphabetize
I have no WHEA entries or errors shown (like between Volsnap and Windows-Firewall)
Additionally, if I Filter by WHEA-Logger nothing appears.
This is still the original Windows-11 Pro install on this computer, so AFAIK ... these logs should go back like 4 years and seem to indicate it HAS NEVER had a WHEA error.
Hello, you can try this fix, set power option to high performance or ultimate performance, and turn OFF the PCI Express Bus, Link State Power Management.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 00:50
I kinda doubt you will get an answer from another Aurora-R13 owner (on this issue), but it's good to live in hope.
But let me ask you ... when they swapped the motherboards ... can you definitively list the parts that were transferred over? My idea is that if it's not the motherboard, it might be one of the components that were transferred.
Dpiperjr
2 Intern
•
5 Posts
0
March 28th, 2026 00:59
@Tesla1856
Thank you for the suggestion. The WHEA-Logger Event ID 17 errors specifically identify Intel PCIe Root Complex device 8086:7ABC on PCIe Root Port 5 which is integrated into the Z690 chipset on the motherboard itself. The Killer E3100G NIC connected to that root port is soldered directly onto the motherboard and cannot be transferred between boards. Intel's own published Specification Update Document 682436 confirms errata ADL013 and ADL014 as NO FIX silicon level defects present in every i9-12900F processor meaning the defect exists at the platform level regardless of which motherboard is installed and components added to it.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 01:24
More good info, thanks.
But can you answer my original question?
0. Can you definitively list the parts that were transferred over? If so, please list them.
1. Also, what BIOS-Firmware version are you running on this motherboard?
2. Finally, is your Intel-ME version the proper matching-one for this Firmware BIOS?
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 01:33
Are you sure it's a i9-12900F ... and not a i9-12900K ?
This theory you have ...
Do you think it affects all i9-12900 models (including the i9-12900K) or by your research, does it only apply to the i9-12900F?
Dpiperjr
2 Intern
•
5 Posts
0
March 28th, 2026 01:41
0. The components transferred between motherboards were the i9-12900F processor, 128GB DDR5 RAM, RTX 3080 GPU, and NVMe SSD. The Killer E3100G NIC is soldered directly onto the motherboard and was replaced with each motherboard swap.
1. Currently running BIOS version 1.26.0.
2. Intel ME Interface driver version is 2433.6.3.0 dated August 15 2024. Dell does not publicly document which specific ME version is bundled with each R13 BIOS release so I am unable to confirm whether this is the exact matching version for 1.26.0.
The crash pattern began at approximately once per month and has escalated dramatically to multiple times daily over the course of months. A BIOS or Intel ME firmware issue would not exhibit this kind of progressive escalation pattern. This is consistent with hardware degradation, not a firmware configuration issue.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 01:56
@Dpiperjr ,
Maybe your first post in this thread was just venting. I thought you were reaching out to the community for help.
I read your reluctance.
I certainly have better things to do. Would you rather I stop trying to help you, and you can just wait for the other Aurora-R13 owners (with this same problem) to start posting so yall can compare notes?
(edited)
Dpiperjr
2 Intern
•
5 Posts
0
March 28th, 2026 01:57
Yes confirmed i9-12900F.
According to Intel's Specification Update Document 682436 Summary Table of Changes, ADL013 and ADL014 are listed as No Fix under the S processor line — which covers all 12th Gen Alder Lake desktop processors including both the i9-12900F and the i9-12900K. Both SKUs share the same silicon and are equally affected by these errata with no fix available across all steppings.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 15:15
@Dpiperjr ,
1. Acknowledged
2. Acknowledged
So, we also own this computer:
Origin-PC Millennium (circa 2022)
CPU: Intel i9-12900K (12th Gen) with Liquid-Cooling
GPU: Nvidia RTX-3080 FE (10gb)
Motherboard: MSI PRO Z690-A WIFI DDR5 (MS-7D25)
Memory: 32GB CORSAIR VENGEANCE DDR5 5200MHz (2x16GB DIMMs running Dual Channel)
Monitor: LG 32in 4K UltraGear Nvidia-GSync IPS 144-Hz Gaming-Monitor
Window-11 Pro (VBS is Disabled for Max-Gaming Performance)
It is pushed hard (one example is bi-weekly multi-hour WoW Guild Raiding Sessions). It is now and has always been rock hard stable. I just checked and it's Reliability History Report score is still 10.
In 4-years, I've never seen a STOP-screen or BSoD. AFAIK, no WHEA errors (but I'll be glad to look for them if you tell me where you found yours).
So, if your theory is that your problems are linked to some inherent defect in ALL Intel i9-12900 model processors, I have a real-life example that goes against that theory.
EDITED
(edited)
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 19:02
@Dpiperjr ,
0. Good list.
My idea is that since the motherboard has been replaced 2-3 times and the issue still exists, maybe the problem is with one of the components that gets swapped across.
1. A little outdated, but not too badly (about 4 revisions behind).
Among other things, they address CVE's and even hard-defects (like 0x12B) with updated MicroCode.
2a. Acknowledged.
2b. Yes they do (in a round-about way). When-and-if the time comes, I can show you how.
3. I don't have any information about such things.
My experience has shown me that any deficiency with the computer tends to eventually affect its operation as a whole (weakest-link and all that).
I do seem to remember that WHEA errors are often related to ram memory and that sub-system.
(edited)
Tesla1856
8 Wizard
•
17.3K Posts
0
March 28th, 2026 23:00
On the computer with the Intel i9-12900K ...
Event Viewer / Windows Logs / System /
- I click on Source field at top to alphabetize
I have no WHEA entries or errors shown (like between Volsnap and Windows-Firewall)
Additionally, if I Filter by WHEA-Logger nothing appears.
This is still the original Windows-11 Pro install on this computer, so AFAIK ... these logs should go back like 4 years and seem to indicate it HAS NEVER had a WHEA error.
Chino de Oro
9 Legend
•
8.3K Posts
0
March 28th, 2026 23:57
Hello, you can try this fix, set power option to high performance or ultimate performance, and turn OFF the PCI Express Bus, Link State Power Management.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 29th, 2026 19:41
Going down the list:
Motherboard
CPU
Ram ... where did that 128gb of ram-memory come from?
Was it factory installed?
What is the make and model of those DIMMs?
What is the DIMM configuration for all those slots?