Xigncode3 and AMD cpu Temps
Jan 19, 2024, 00:19 (UTC)
6214
206
716
255
Last Edit :
Jan 20, 2024, 14:44 (UTC)
# 111
On: Jan 20, 2024, 14:38 (UTC), Written by Toriia
Actually no, because the recommended voltages were patched on other MOBO producers before they were released, which is why you only hear about ASUS boards. But if I remember correctly Gigabyte was also having this issue on pre-patched boards they released. Several 3rd party hardware failure researchers confirmed this and that it was a software patch for a hardware failure. The chips themselves should be able to handle the 1.35v max setting they had it originally set to, but can't.
The 1.35v max setting is what they patched EXPO too. It was running 1.4 to 1.5v
My current expo is 1.35v and then downclocked by me to 1.25v
As a test I lowered my voltage to 1.15v and pbo -25 and then put my throttle limit at 85c - immediate blue screen on BDO loading screen but the BSOD error is an SSD one lol
Last Edit :
Jan 20, 2024, 14:56 (UTC)
# 112
On: Jan 20, 2024, 14:34 (UTC), Written by Toriia
Your argument is "BDO should swap back to EAC because only one brand's flawed hardware is failing". By your same logic, why should PA have to change AC just to fix a problem only X3D consumers are having? Don't get me wrong, I don't think BDO should be burning up CPUs, I just think people are placing the blame on something that isn't to blame. Again, if X3D processors are the ONLY subset that are failing, then it's a hardware issue. Something inside of that processor line is overprocessing what every other brand/line of processor is not. Xigncode is just showing the flaw exists, it's not the cause.
This is a really poor argument. If I introduce a bug at my company to our website that only affects Safari users, I don't put the blame on them for using Safarai. The blame is on me for not implementing it in a way that's supported across all of our browsers. Your argument in this entire thread is to white knight for PA (or even Intel) and makes next to no sense at all.
This thread was to bring awareness to the fact its happening and see how many people who use this forum are experiencing it. If you can't contribute anything to the conversation other than victim blaming, then move onto another thread.
Last Edit :
Jan 20, 2024, 15:13 (UTC)
# 113
Nobody is saying swap back to EAC, just test your stuff before you release it. Also not sure where you're getting your info from, but you're wrong. X3d chips were already released and used on variety of boards, before the vsoc became an issue and started frying them. And this happened on Asus because the chips were rated for 1.35v, while Asus was pushing well over 1.4v because that's the lazy approach to have more RAM sticks compatible at high speeds instead of testing for it. After that it was patched to a 1.3v limit for everyone.
Either way that's not the discussion here, plenty of people are saying 17th maint with Xigncode3 no issues, 18th maint with new update, issues start. What is so damn hard to understand.
Last Edit :
Jan 20, 2024, 15:14 (UTC)
# 114
On: Jan 20, 2024, 14:21 (UTC), Written by Toriia
No the thread is about people with X3D processors having an issue with the new AC. When in reality it's the processors themselves that are the problem. When you have only one category of hardware that is failing, it is not the software's fault. That is what I am saying. Other series of AMD CPUs don't have this problem either, so it's not the software. Generalizing and saying "oh it's the new anti-cheat because my X3D (the only series of processor on the market that is having this issue) is overheating" is overlooking the actual problem of the processor not being able to recognize a power draw issue and correct it. A CPU can (as mentioned by someone else) throttle itself, but that's just the clock speed, not the current draw. You CAN have a processor at half its clock speed but still drawing the same current, and it should be able to see that and lower the current coming in by communicating that to the BIOS. I already pointed out that the BIOS update that "patched" X3Ds exploding only monitors BIOS triggered over-voltage, not software triggered over-voltage/current. So it STILL is a problem with the X3D processor line itself, not the software.
that parroted stuff about some past x3d issue that occured during boot, has nothing to do with BDO behaving like a stress test suddenly after patch.
a stress test software is also fine by itself, no fault. but i don't have it running for hours, for no reason. does that make at least sense to you?
15
180
Lv Private
Spartakatz
Last Edit :
Jan 20, 2024, 15:38 (UTC)
# 115
On: Jan 20, 2024, 15:14 (UTC), Written by Spartakatz
that parroted stuff about some past x3d issue that occured during boot, has nothing to do with BDO behaving like a stress test suddenly after patch.
a stress test software is also fine by itself, no fault. but i don't have it running for hours, for no reason. does that make at least sense to you?
And i did a 100% cpu utilization stress test and it got lower temps than bdo is getting using less utlization of the cpu..
Last Edit :
Jan 20, 2024, 15:19 (UTC)
# 116
On: Jan 19, 2024, 09:25 (UTC), Written by Sideways
This is absolutely insane. Under no circumstances should a game developer be instructing users to mass disable all Windows services and startup programs, many of which are necessary for system health and security even including ones not signed by Microsoft. It is intolerable that a customer should have to open their system to potential hardware damage, data loss, and security risk in order to compensate for a notoriously buggy, unsafe, privacy-violating "anti-cheat" program that is also well-known to do nothing to stop cheaters.
XIGNCODE should be removed immediately, this is utterly unacceptable behavior for a company operating with a presence in the United States and Europe.
Last Edit :
Jan 20, 2024, 15:38 (UTC)
# 117
On: Jan 20, 2024, 15:19 (UTC), Written by Stormed
This is absolutely insane. Under no circumstances should a game developer be instructing users to mass disable all Windows services and startup programs, many of which are necessary for system health and security even including ones not signed by Microsoft. It is intolerable that a customer should have to open their system to potential hardware damage, data loss, and security risk in order to compensate for a notoriously buggy, unsafe, privacy-violating "anti-cheat" program that is also well-known to do nothing to stop cheaters.
XIGNCODE should be removed immediately, this is utterly unacceptable behavior for a company operating with a presence in the United States and Europe.
Yea i didn't trust myself doing that so i posted mine to the forum for someone maybe more knowledgeable to do so as i don't have the time..
Last Edit :
Jan 20, 2024, 15:53 (UTC)
# 118
I don't think performing a clean minimal boot is a bad thing to ask in terms of general troubleshooting in most situations but precisely WHAT would it achieve?
Oh, look, the problem goes away when I critically nerf my computer, which by the way, worked perfectly fine prior to xigncode. Now what? We enable one of the hundreds of services that window uses one at a time until we identify the culprit?
And what if it turns out it's one of the more critical services such as DCOM Server Process Launcher or Local Session Manager etc?
And, possibly even worse, what if it's a specific non-Microsoft service such as LGHub Manager or Asus ROG Service? You can't ask people to disable key peripheral software for hardware they've spent hundreds of pounds on.
xigncode is the common denominator and, from reading the thread, most issues happened after the mini-patch. The onus is on xigncode to provide a fix.
6
12
Lv 61
Baeyonetta
Last Edit :
Jan 20, 2024, 16:41 (UTC)
# 119
On: Jan 20, 2024, 13:55 (UTC), Written by Toriia
*uses Intel CPU and has no problems*
Boy it must suck to FOMO out on AMD's X3D series processors that are capable of burning up because of faulty hardware temperature protections. Let's blame it on xigncode and not on the manufacturer's admitted defects.
It is important to note that this is ONLY affecting AMD X3D processors and not their equally powerful but slightly more power hungry X series processors. Don't blame the anti-cheat. It's not what's killing your CPU. Your CPU is killing itself because it can't recognize there's a problem like every single other processor on the market can.
Wow, did Lisa Su personally hurt you? You sound salty xD
On topic: I have 5800x3D and no issue overall. During launch of the game max temp is 64°C at 24°C ambient. When playing stays at 55° with spikes to 60°. Running Windows 10, 6900XT and 32GB RAM (at 3600MHz). The only issue I had after maintenance: for some reason the volsnap.sys started on itself, even tho I have the recovery disabled, but I assume it's not linked with BDO/Xingcode and just coincidence.
To sum up: not, it's not all X3D CPUs. Maybe it's driver overhead, or drivers itself, or maybe in certain scenarios (W11 again?) the Xingcode is going fubar? The bottom line is: there's a issue, and some people are suffering, so PA should take a look.
Last Edit :
Jan 20, 2024, 16:46 (UTC)
# 120
AMD Radeon RX 7900 XTX and AMD 7800 x3D, i've noticed after this update that my fans are huffing and puffing. Also im noticing random freezing of my mouse cursor. And when i startup BDO my PC gets louder than usual.
3
6
Lv 66
The_Musassin
Reply