Hello, Is anyone else having troubles with the intel i9 CPU on a GIGAbyte motherboard. TBC kicks me out when I want to produce a cut/fill map. I allready had to change one CPU on the computer wich I use to calculate my pointclouds (3D Survey) I have it replaced by an older version with update wich works fine. 13900KF updated BIOS version FG updated
article on the site of GIGABYTE:
1 Like
Hello Sofie,
What type of error are you getting? It could be related to the Intel 13th/14th generation stability issues going on right now. I had a 14th gen that I built earlier this year that I had to return due to this issue. Here is a link to a intel community article if you are interested. July 2024 Update on Instability Reports on Intel Core 13th and 14th Gen Desktop Processors - Intel Community
From what I understand they are working on an updated microcode patch to try and address the issue.
2 Likes
Hi Sofie,
Does TBC crash and disappear? Have you checked the Windows event log for more details? If I am not mistaken, the cut-fill process in TBC can be GPU-intensive. If you are using an external GPU (as opposed to integrated) and on Windows 11, you need to enable Game mode and add TBC for Windows to utilize the GPU driver correctly. An issue like you’re experiencing can be a rabbit hole, and more information about the issue can help the community pin down the problem.
1 Like
Sofie
I will leave this to Shane - he is our resident Hardware guru - but I cannot say we have a lot of breadth of experience on supporting hardware related issues at RPS - this would be a question for Trimble more than us - not wanting to “pass the buck” here, but there is little info or help provided to us on this at all. I have not heard anything ether way on that Motherboard personally, however Shane builds a lot of computers and is more familiar with issues surrounding hardware.
Apologies that I cannot be more help personally
Alan
TBC crashes and close down when processing a cut/fill command where the original ground is a surface from a pointcloud. It is a Intel i9 14900KF BIOS version FH on my other machine, the one I use for pointcloud processing I have an updated FG and it works for the pointclouds(software = 3D Survey) since the update. The FH version has no update yet. I try to install TBC on the other machine
From what I understand the instability issue isn’t affecting all of the processors but it is a substantial amount of them. Running a stress test on the machine might help diagnose the issue but I would exercise extreme caution on this as you could do permanent damage to the processor if temperatures get outside of safe ranges and that seems to be what the microcode issue is related to. Your best bet would be to reach out to Gigabyte or Trimble to see if they have more information. I run Gigabyte motherboards in my desktops and have always had good luck with them. My gut tells me that it might be related to the microcode issue on Intel’s side but without having my hands on the system its hard to say for certain. If the CPU is in return window it may be best to return it and get a CPU outside of the affected sku’s.
Here are some other links that may be useful: https://www.reddit.com/r/intel/comments/1egthzw/megathread_for_intel_core_13th_14th_gen_cpu/?rdt=40550
2 Likes
Hello, I’ve got my Intel processor and Gygabite motherboard replaced by an AMD Ryzen 9 processor on a suitable Gygabite motherboard. Now I have this issue when I startup TBC 2024
What can I do ?
1 Like
In TBC 5.00 a component was added which makes use of Intel’s internal threading API. This API is not supported on certain AMD Ryzen processors. The effect is that when you start the program, a text box is created that displays an error message similar to the following: “KMP_AFFINITY: affinity not supported, using “disabled””. If you close the text box, TBC will crash.
I believe that you may be able to set an environment variable that will disable this, but without a computer I cannot verify it. Try setting KMP_AFFINITY=disabled and let us know if this corrects the problem.
Go to control panel>system>advanced systems settings>environment variables>
Create a new system variable
Name = KMP_AFFINITY
Variable value = disabled
Start TBC and see if the problem still persists.
1 Like
This works for me.
Thanks a lot.