Hello everyone !
So I work on Unreal Engine and so must build the engine every now and then. The same task work flawlessly on my other (much older) computers.
But lastly I cound not build the engine anymore on my main Workstation as Visual Studio constantly crash with a lot of compiler internal Errors :
This continue until complete build failure or system freez and the occasional BSOD.
On the Windows Event Viewer, each VS reported errors are preceded by a Warning of corrected Hardware Failure :
I Tried reinstalling the source code multiple time, on different SSDs, reinstalling different version of Visual Studio multiple time, I formatted my computed and reinstalled it.
I modified my Windows power plan to not allow the CPU to go above 95% power usage.
I ran a CHKdsk disk check, a MemTest86, both without error.
The strange thing is than I fail to put my CPU at fault with other stress test, but the VS build procedure always make it go haywire. A shame considering than I bought it specifically for that task in January 2023.
My Workstation :
Also I saw (very few) other peoples having kind of similar problem a few mouths back, on of them at least was also using the Asus MB + i9 CPU Setup.
Considering the Hardware error is always reported on "Processor APIC ID: 32" I am heavily tempted to think than the issue come from my CPU and than said core is cooked. But I don't know if what data I have collected so far is proof enough.
Thank you for having read me and I hope you may have insight as to what I should do next.
Not being able to work for now 3 days straight as I just released a product I cannot support is becoming increasingly unfun.
RedYggdrasil
So I work on Unreal Engine and so must build the engine every now and then. The same task work flawlessly on my other (much older) computers.
But lastly I cound not build the engine anymore on my main Workstation as Visual Studio constantly crash with a lot of compiler internal Errors :
Code:
1>C:\UE_B\UnrealEngine\Engine\Source\Runtime\Core\Public\Containers\Map.h(921): fatal error C1001: Internal compiler error.
1>(compiler file 'D:\a\_work\1\s\src\vctools\Compiler\Utc\src\p2\main.c', line 225)
1> To work around this problem, try simplifying or changing the program near the locations listed above.
1>If possible please provide a repro here: https://developercommunity.visualstudio.com
1>Please choose the Technical Support command on the Visual C++
1> Help menu, or open the Technical Support help file for more informationThis continue until complete build failure or system freez and the occasional BSOD.
On the Windows Event Viewer, each VS reported errors are preceded by a Warning of corrected Hardware Failure :
Code:
A corrected hardware error has occurred.
Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 32
The details view of this entry contains further information.I Tried reinstalling the source code multiple time, on different SSDs, reinstalling different version of Visual Studio multiple time, I formatted my computed and reinstalled it.
I modified my Windows power plan to not allow the CPU to go above 95% power usage.
I ran a CHKdsk disk check, a MemTest86, both without error.
The strange thing is than I fail to put my CPU at fault with other stress test, but the VS build procedure always make it go haywire. A shame considering than I bought it specifically for that task in January 2023.
My Workstation :
Code:
OS : Windows 11 Pro
Motherboard : ROG STRIX Z790-E GAMING WIFI (BIOS Updated yesterday as part of the troubleshooting process, no change)
CPU : Intel i9-13900K
RAM : G.Skill Ripjaws F5-6000J3040G32GX2-RS5K 64 Go 2 x 32 Go DDR5 6000 MHz
SSD : XPG GAMMIX S70 BLADE 2To x2 (tested on both)
HDD : FireCuda 8TB (not used)
GPU : NVIDIA GeForce RTX 3090Also I saw (very few) other peoples having kind of similar problem a few mouths back, on of them at least was also using the Asus MB + i9 CPU Setup.
Considering the Hardware error is always reported on "Processor APIC ID: 32" I am heavily tempted to think than the issue come from my CPU and than said core is cooked. But I don't know if what data I have collected so far is proof enough.
Thank you for having read me and I hope you may have insight as to what I should do next.
Not being able to work for now 3 days straight as I just released a product I cannot support is becoming increasingly unfun.
RedYggdrasil
