*Official Benchmark Thread* - Post it here or it didn't happen :D

[Papusan]

 

2 hours ago, electrosoft said:

 

Intel can push the new MC, but it still comes down to MB makers responsibly enforcing it while also allowing advanced users to disable it if they see fit. I am sure we will see a few more BIOS updates fleshing it out

 

Intel haven't many other choices. The sales in Korea has sinked as a stone in the ocean and more of this news you see below will increase the damage further. And all the new bugged beta bios from the mb manufacturers don't help on the situation.

 

Raptor Lake instability hits streamer Asmongold — Black Myth: Wukong shader compilation fails on stream

 

https://www.tomshardware.com/pc-components/cpus/raptor-lake-instability-hits-streamer-asmongold-black-myth-wukong-shader-compilation-fails-on-stream

[D2ultima]

1 hour ago, Papusan said:

 

See below. File contain innstaller and uninstaller from our old good friend @Prema But no need for latest Intel ME Firmware Update v16.1.32.2418. Also latest MEI driver if this is something you want for the ME firmware.

 

 

I saw the updater when he posted it on the eluk discord but I didn't realize it worked for all systems. No harm using it, I suppose.

[electrosoft]

Apparently the new Final Fantasy XVI Demo on Steam released on the 19th also is giving some users fits with its shader compiles. I just ran it on my main desktop (7950X3D/4090) and no problems at all. I'll try it on my 14900KS/7900XTX setup later to see how it stacks up against the Wukong fun times.

 

https://store.steampowered.com/app/2738000/FINAL_FANTASY_XVI_DEMO/

[Mr. Fox]

2 hours ago, Papusan said:

So even with the MC 0x129 with the new Asus XOC beta bios you got back the SA bug.... Hmmmm. 

 

Your reply. I tested the ASUS XOC BIOS that @safedisk posted (v9933) and the SA bug returned to that CPU even with 0x129 MC.

 

What a disgusting soap opera this has become with the different motherboard manufacturers. 1.6V when loading up the OS with the new so called fixed bios (MC 0x129). Could be a detective board but who knows.

It may be  another setting and not the SA bug. I went back to 1503 and applied my old profile and it was freezing in AIDA64 the same as 9933. Not sure why, so I applied XMP and manually set VCCSA to 1.350V and no freezing. So, something did change. I switched to XMP I (instead of XMP Tweaked) and applied my settings and now no more freezing. So, I may go back and test 9933 again with different settings to see for sure. It's weird that it was working fine and then suddenly XMP Tweaked would cause it to start freezing.

1 hour ago, D2ultima said:

You all getting so many problems with the new BIOSes I'm just not even wanting to update mine. I don't know what BIOS I'm on but I haven't updated it since I got the system and the CPU does about 1.1 to 1.2v under load and I've never seen it higher than 1.24v at all, so I suppose I'll count my luck.

 

If I could update the microcode alone without touching anything else I could probably consider it but I doubt that's how this works for a lower end ASUS board

The only reason I even considered updating the BIOS at all was to see if it fixed the SA bug on this one CPU. Otherwise, no need for BIOS updates. Waste of time and often brings less desirable performance, especially if "security" mitigations are part of the cancer payload. I was pleasantly surprised that it fixed that. Applying the microcode in Windows does NOT fix the SA bug. (I tried the Windows MC Prema shared and it did not correct the issue.) We  are also only assuming it was the microcode update. Logical assumption, but it could be something else. I say logical because the SA bug was motherboard agnostic. Was the same on my MSI board as the ASUS and the BIOS update corrected it.

1 hour ago, electrosoft said:

Intel can push the new MC, but it still comes down to MB makers responsibly enforcing it while also allowing advanced users to disable it if they see fit. I am sure we will see a few more BIOS updates fleshing it out.

 

As for the SA Bug, when all is said and done, I am still setting my SA back to 1.18 for 8200 because it works and no need to feed more voltage than required. Of course for benching and testing, I let it run free. 🙂

If I had left this CPU in the MSI Z790I Edge ITX board it would have continued to be perfectly fine with the SA bug for the same reason you mention. Air cooled in a small chassis and poor circulation, 8200 is the edge of stability due to temperatures anyhow. Having low VCCSA because you can and because you want to is good. It's only an issue if you wanted to push it further and can't because of a flaw preventing it. Inconsequential  otherwise. But, nobody like knowing there is a fly in the ointment.

 

So, it is working without issue again. Will play with tightening up the timings again now that I am using the XMP I instead of XMP Tweaked option. Interesting change that makes no sense. The Intel ME was not updated, so I cannot blame it on that.

[D2ultima]

6 minutes ago, Mr. Fox said:

The only reason I even considered updating the BIOS at all was to see if it fixed the SA bug on this one CPU. Otherwise, no need for BIOS updates. Waste of time and often brings less desirable performance, especially if "security" mitigations are part of the cancer payload. I was pleasantly surprised that it fixed that. Applying the microcode in Windows does NOT fix the SA bug. (I tried the Windows MC Prema shared and it did not correct the issue.) We  are also only assuming it was the microcode update. Logical assumption, but it could be something else. I say logical because the SA bug was motherboard agnostic. Was the same on my MSI board as the ASUS and the BIOS update corrected it.

 

Speaking of BIOS not needing updates, my BIOS is old as hell 

 

I got curious and went and checked after I mentioned it haha

 

What was the SA bug?

[tps3443]

I have a SP103 14900KS that I will be delidding and running on direct die. Will be testing the IMC as well. I want to see what something like this does at 5.8Ghz all core on direct die.

[Mr. Fox]

26 minutes ago, D2ultima said:

I got curious and went and checked after I mentioned it haha

 

What was the SA bug?

Yeah, older BIOS is almost always better than newer. There was an exception as DDR5 technology was needing work, but we are way past that now.

 

SA Bug: If your CPU has it, if you set System Agent voltage (VCCSA) above a certain value, usually a very low value, the system will start freezing. It would lock up in the BIOS or in Windows. This one 14900KF has it and if I left it set on Auto it would go too high and freeze with the CPU under load. I had to manually set it at 1.190V, which was fine up to 8200 CL38, but any higher memory clock than that was not stable because it needed more system agent voltage. I set 1.250V for 8400 CL38 and tight timings. That "no workey" with the SA bug.

 

If you don't want to overclock the memory that high it is not a big deal, but it might lead one to believe something else is wrong if the freezing happens with the BIOS left on Auto and you don't know you have to manually decrease it from default. Using as little as you need is always good as long as you are not limited by the bug.

18 minutes ago, tps3443 said:

I have a SP103 14900KS that I will be delidding and running on direct die. Will be testing the IMC as well. I want to see what something like this does at 5.8Ghz all core on direct die.

Welcome back to bare die paradise. I thought you had lost your marbles there for a bit. I hate having an IHS on my CPUs. It sucks, LOL.

[tps3443]

56 minutes ago, Mr. Fox said:

It may be  another setting and not the SA bug. I went back to 1503 and applied my old profile and it was freezing in AIDA64 the same as 9933. Not sure why, so I applied XMP and manually set VCCSA to 1.350V and no freezing. So, something did change. I switched to XMP I (instead of XMP Tweaked) and applied my settings and now no more freezing. So, I may go back and test 9933 again with different settings to see for sure. It's weird that it was working fine and then suddenly XMP Tweaked would cause it to start freezing.

The only reason I even considered updating the BIOS at all was to see if it fixed the SA bug on this one CPU. Otherwise, no need for BIOS updates. Waste of time and often brings less desirable performance, especially if "security" mitigations are part of the cancer payload. I was pleasantly surprised that it fixed that. Applying the microcode in Windows does NOT fix the SA bug. (I tried the Windows MC Prema shared and it did not correct the issue.) We  are also only assuming it was the microcode update. Logical assumption, but it could be something else. I say logical because the SA bug was motherboard agnostic. Was the same on my MSI board as the ASUS and the BIOS update corrected it.

If I had left this CPU in the MSI Z790I Edge ITX board it would have continued to be perfectly fine with the SA bug for the same reason you mention. Air cooled in a small chassis and poor circulation, 8200 is the edge of stability due to temperatures anyhow. Having low VCCSA because you can and because you want to is good. It's only an issue if you wanted to push it further and can't because of a flaw preventing it. Inconsequential  otherwise. But, nobody like knowing there is a fly in the ointment.

 

So, it is working without issue again. Will play with tightening up the timings again now that I am using the XMP I instead of XMP Tweaked option. Interesting change that makes no sense. The Intel ME was not updated, so I cannot blame it on that.

You ever have any retrain stability problems? I did with my r-batch with 8400/8533. I could get it absolutely stable 100%, try a different bios, switch back to old bios, load exact setting and profile to a T. And it would not be stable anymore. So I’d have to “Re-gain stability again” It’s always what Buildzoid talks about with these Intel memory controllers.

 

27 minutes ago, Mr. Fox said:

Welcome back to bare die paradise. I thought you had lost your marbles there for a bit. I hate having an IHS on my CPUs. It sucks, LOL.

Oh I am just testing the sp103 chip, it’s not mine though. I am not delidding my SP108. No need to go direct die honestly. Very happy with my 5.9/4.8/5.0 8600c36 profile. It runs amazing.

[Papusan]

39 minutes ago, Mr. Fox said:

The only reason I even considered updating the BIOS at all was to see if it fixed the SA bug on this one CPU. Otherwise, no need for BIOS updates. Waste of time and often brings less desirable performance, especially if "security" mitigations are part of the cancer payload.

 

Yup. And this apply also for the OS. 

An update made to fix a vulnerability broke dual-boot Windows-Linux PCs

neowin.com · 7 hours ago

A Windows Patch Tuesday update that was supposed to fix a vulnerability has caused a number of dual-boot Windows-Linus PCs to no longer boot up in Linux. Microsoft has yet to fix this problem.

[Mr. Fox]

25 minutes ago, tps3443 said:

You ever have any retrain stability problems? I did with my r-batch with 8400/8533. I could get it absolutely stable 100%, try a different bios, switch back to old bios, load exact setting and profile to a T. And it would not be stable anymore. So I’d have to “Re-gain stability again” It’s always what Buildzoid talks about with these Intel memory controllers.

That is EXACTLY what happened when I went from 1503 to the 9933 XOC BIOS that Safedisk provided last week. I did not try to use an old CMO file. I saved the text and set everything manually. It seemed stable at first but then started locking up in AIDA64 and TM5. I went back to 1503 and applied the stable profile and it was no longer stable like it was before 9933.

 

I still have to do more messing with it to confirm, but I think the XMP Tweaked menu option is causing it now. It did not cause it before, which is weird.

 

ASUS does some nice things with their BIOS, but they do some stupid things as well. When you flash firmware there are certain regions that are protected and never go back to what they were before when you flash the older firmware. That is why I generally think it is best to avoid firmware updates unless I am expecting something I need to happen. MSI and EVGA BIOS updates erase and re-write everything, in all regions. That is how it should be and ASUS needs to get a clue on this. If you pay close attention during an ASUS BIOS update and read the text at the bottom of the screen, sometimes it skips over certain regions and it never flashes some of them.

 

They also need to stop insisting on Intel ME updates and bundling it with the BIOS. Intel ME updates are totally unnecessary. No Intel system requires the Intel ME to fully function. They need to provide the option to disable it. It serves no useful purpose for consumers and having it creates extra security risks that some people get wigged out about. No ME means no vulnerabilities associated with ME.

 

Edit: I think I am going to try the BIOS Flashback recovery and then retest my saved profile with XMP Tweaked. BIOS flashback forces flashing of regions and allows some BIOS mods to be flashed that are blocked through a normal flash update.

 

Edited August 21 by Mr. Fox
going to test BIOS flashback

[Mr. Fox]

  

30 minutes ago, Papusan said:

 

Yup. And this apply also for the OS. 

An update made to fix a vulnerability broke dual-boot Windows-Linux PCs

neowin.com · 7 hours ago

A Windows Patch Tuesday update that was supposed to fix a vulnerability has caused a number of dual-boot Windows-Linus PCs to no longer boot up in Linux. Microsoft has yet to fix this problem.

They'll deny it, but I would not be surprised if it was a deliberate act of sabotage rather than a mistake. They are losing market share to older versions of Windows and Linux due to their filthy new cancer OS and what better way to block it than preventing users from booting into Linux when they don't want to deal with Micro$haft's garbage. They are not an honorable company and their lack of integrity is evident to anyone paying attention.

[tps3443]

34 minutes ago, Mr. Fox said:

That is EXACTLY what happened when I went from 1503 to the 9933 XOC BIOS that Safedisk provided last week. I did not try to use an old CMO file. I saved the text and set everything manually. It seemed stable at first but then started locking up in AIDA64 and TM5. I went back to 1503 and applied the stable profile and it was no longer stable like it was before 9933.

 

I still have to do more messing with it to confirm, but I think the XMP Tweaked menu option is causing it now. It did not cause it before, which is weird.

 

ASUS does some nice things with their BIOS, but they do some stupid things as well. When you flash firmware there are certain regions that are protected and never go back to what they were before when you flash the older firmware. That is why I generally think it is best to avoid firmware updates unless I am expecting something I need to happen. MSI and EVGA BIOS updates erase and re-write everything, in all regions. That is how it should be and ASUS needs to get a clue on this. If you pay close attention during an ASUS BIOS update and read the text at the bottom of the screen, sometimes it skips over certain regions and it never flashes some of them.

 

They also need to stop insisting on Intel ME updates and bundling it with the BIOS. Intel ME updates are totally unnecessary. No Intel system requires the Intel ME to fully function. They need to provide the option to disable it. It serves no useful purpose for consumers and having it creates extra security risks that some people get wigged out about. No ME means no vulnerabilities associated with ME.

 

Edit: I think I am going to try the BIOS Flashback recovery and then retest my saved profile with XMP Tweaked. BIOS flashback forces flashing of regions and allows some BIOS mods to be flashed that are blocked through a normal flash update.

 

 

You do not want to use CMO files from other bios. You will have to make a new profile from scratch on the new bios always for best results. Sucks but, that’s just how it is.
 

The reason why this instability happens plain and simple is because you are too close to the IMC limits, any little thing that isn’t exact as before, will throw it for a loop. So when you go back to those settings one little thing prevents it from being stable. That is why the term. “Re-train stable” is used with these latest Intel chips. “Re-Train stable” is when you can stabilize a profile, save the profile, reset your bios, re-load that profile on that exact bios, and it will be 100% stable no questions asked. 
 

Now, you are going to have to make a new profile with all new bios for best results. Thats what I do. It’s a hassle. But it just saves time in the long run. Because you are working up a stable profile for that bios. But, here’s the thing, not being re-train stable can occur at any time. What you need to do is this:

 

(1) Pick your favorite bios ME etc 

(2) Build up a stable profile that can pass 1usmus 3 cycles.

(3) Save the profile 

(4) Turn off the PC, flip PSU switch off for 1 months minute.

(5) Power on PC, go and see if it can pass 1usmus 3 cycle again. 
 

The process from flipping PSU switch back on forces a re-train on the next power up, and if it’s not stable on the next stability test, it is due to being very close to IMC limits. If anything hangs over the edge, it’s immediately not stable. 

[Papusan]

This sum up today's new modern tech. Create disasters to be able to maximice profits. We need bigger chips and with same sorts of cores. And more cores if needed for more performance. Not this modern hybrid or glued togeter tiles mess.

 

 

 

@Prema Here's is the latest Intel ME Firmware Update v16.1.32.2473. Can you see what this brings? Probably new security fixes as usual. Or a re-brand. Thanks

[Mr. Fox]

2 hours ago, tps3443 said:

You do not want to use CMO files from other bios. You will have to make a new profile from scratch on the new bios always for best results. Sucks but, that’s just how it is.

I do not do use CMO files across BIOS versions. That is why I save a text file for the profiles I use. Then I can recreate them manually for a newer or older BIOS version.

2 hours ago, Mr. Fox said:

Edit: I think I am going to try the BIOS Flashback recovery and then retest my saved profile with XMP Tweaked. BIOS flashback forces flashing of regions and allows some BIOS mods to be flashed that are blocked through a normal flash update.

That fixed it. Something from 9933 did not revert back to what it was with 1503 using the in-BIOS flash tool. If you run into weirdness after an in-BIOS update, or going back to a better older version, run BIOS flashback from USB using the button on the rear I/O. Now I can use XMP Tweaked again and no lockups and confirmed no SA bug. It flashed everything doing it that way instead of keeping crap in some regions with a newer timestamp. It takes over twice as long to flash that way, but it does a better job.

 

Back to normal... all settings that worked before still work after BIOS flashback. No SA bug with MC 0x129.

It did nothing to help my 81°F (27°C) ambient  temperatures in my office. 🤣 Water in my loop is 28°C. 😡

1 hour ago, Papusan said:

Intel ME Firmware Update v16.1.32.2473

[electrosoft]

3 hours ago, tps3443 said:

I have a SP103 14900KS that I will be delidding and running on direct die. Will be testing the IMC as well. I want to see what something like this does at 5.8Ghz all core on direct die.

 

Considering you said your SP99 vs SP108 was fairly close with chiller love (temps rule everything), I am sure you will get amazing results from it too. I'm always curious about the IMC.

 

 

[electrosoft]

5 hours ago, Papusan said:

This sum up today's new modern tech. Create disasters to be able to maximice profits. We need bigger chips and with same sorts of cores. And more cores if needed for more performance. Not this modern hybrid or glued togeter tiles mess.

 

 

 

@Prema Here's is the latest Intel ME Firmware Update v16.1.32.2473. Can you see what this brings? Probably new security fixes as usual. Or a re-brand. Thanks

 

Hmmmm, I think I remember someone basically saying the same thing. Lemme see if I can find it...ah yes....here it is....

 

On 8/18/2024 at 2:54 PM, electrosoft said:

 

The real problem was when Intel and AMD started to deviate from a monolithic type design and started offering these hybrid designs both in core differentials (P vs E) and core functionality (X3D vs non-X3D) so OSes could no longer just work with a generic scheduler. We're expecting M$ and AMD/Intel to work hand in hand to properly have their CPUs know what and how to prioritize tasks.

 

It has gotten somewhat better since Alderlake and 7950X3D/7900X3D introduction but it will always be a work in progress.....

 

 

 

🤣

[tps3443]

2 hours ago, electrosoft said:

 

Considering you said your SP99 vs SP108 was fairly close with chiller love (temps rule everything), I am sure you will get amazing results from it too. I'm always curious about the IMC.

 

 

This SP103 is toast! I feel bad for the guy who bought it. I went straight to direct die, didn’t even test it before hand. But the chip needs like 1.225v just to run 5.6P at 48c package temp. Someone smoked the chip. 5.7/5.8/5.9 are all completely unstable. Launching anything other than a browser will BSOD. Turning off or reducing the E-Cores helps a lot. So, all I could get “Kinda useable” was 5.6P/4.3E/4.5R on direct die+ chilled water. 😂 Wonder if that’s why it was only $400 bucks for a 14900KS. 🤔 Anyways, I tried everything I could with the CPU. It just can't run at all without failing it seems. 

The chip refuses to launch R23 under any circumstances. Any light games are closing to desktop. This chip is defective, or it was cooked with so much voltage that it is so degraded it can barely run anymore at all. Since it needed about 1.225V for 5.6P and still would fail to run R24 consistently this makes me think it has been degraded or abused. But, I do not really know. I have never dealt with a CPU like this. I spent a lot of time with it. Not sure what it may be. 🤷‍♂️

[Mr. Fox]

9 hours ago, electrosoft said:

 

Hmmmm, I think I remember someone basically saying the same thing. Lemme see if I can find it...ah yes....here it is....

 

 

🤣

Nobody here disagreed with you that I know of. You are correct. I don't think it will ever work well. It will always have flaws because the entire concept is flawed and was invented by goofballs.

 

AMD started the abomination with their cobbled together mini CPUs and Infinity Fabric crap. People bought it and were excited about the mess, so Intel jumped on the bandwagon with their smartphone core crap. Now we all have to deal with messy doo-doo on both sides of the fence. The moral to the story is this: If it is what the sheeple want and believe in, there is at least a 50% chance that it is trash. It doesn't matter which school they attend, newer is always better newer. Computer technology is circling the drain, regressing rather than progressing. And, the demons that want to drag us into their pit don't care whether we are wearing red or blue pants. Seems to mirror other facets of life beyond technology to a great degree. The world we live in is pretty screwed up.

8 hours ago, tps3443 said:

This SP103 is toast! I feel bad for the guy who bought it. I went straight to direct die, didn’t even test it before hand. But the chip needs like 1.225v just to run 5.6P at 48c package temp. Someone smoked the chip. 5.7/5.8/5.9 are all completely unstable. Launching anything other than a browser will BSOD. Turning off or reducing the E-Cores helps a lot. So, all I could get “Kinda useable” was 5.6P/4.3E/4.5R on direct die+ chilled water. 😂 Wonder if that’s why it was only $400 bucks for a 14900KS. 🤔 Anyways, I tried everything I could with the CPU. It just can't run at all without failing it seems. 

The chip refuses to launch R23 under any circumstances. Any light games are closing to desktop. This chip is defective, or it was cooked with so much voltage that it is so degraded it can barely run anymore at all. Since it needed about 1.225V for 5.6P and still would fail to run R24 consistently this makes me think it has been degraded or abused. But, I do not really know. I have never dealt with a CPU like this. I spent a lot of time with it. Not sure what it may be. 🤷‍♂️

Are the SP ratings deceptively good and not matching nasty details the VF curve, or is all of the information, including what it shows on the VF curve and SP ratings, not the reality of how it behaves? That is pretty sad, but it may have been that way new. The 14900K/KF CPUs I returned to Amazon, NewEgg and the 14900KS returned to Central Computer were the absolute worst silicon samples I have ever had in my possession before. Bad enough there was no way I would try to use them or sell them to someone else at a loss, so I insisted on refunds and got my money back. The KS needed like 1.550V to run Cinebench on BIOS defaults and stock turbo with no ASUS enhancements. I think I remember seeing posts by the guy selling it that he was struggling to get it to behave acceptable. I might have him mistaken for someone else and can't swear to it, but that's why I did not reply to your post if it was the same CPU that you were commenting about how good the predictions looked.

 

This is why I have stocked up on 13th and 14th Gen CPUs of good bin quality. AMD brought nothing worth buying and I expect Intel will have nothing worth buying in their next gen. All the focus is on wrong things. Quality, integrity and customer experience are no longer main points of focus. The focus is developing AI to further the tech syndicate's theft of information and crimes against humanity, a resource for governments to rule by manipulation and fiat, with funding sourced by selling grossly overpriced broken crap to silly people that are addicted to electronics feces and believe everything they see, read and hear on TV and social media.

[electrosoft]

3 hours ago, tps3443 said:

This SP103 is toast! I feel bad for the guy who bought it. I went straight to direct die, didn’t even test it before hand. But the chip needs like 1.225v just to run 5.6P at 48c package temp. Someone smoked the chip. 5.7/5.8/5.9 are all completely unstable. Launching anything other than a browser will BSOD. Turning off or reducing the E-Cores helps a lot. So, all I could get “Kinda useable” was 5.6P/4.3E/4.5R on direct die+ chilled water. 😂 Wonder if that’s why it was only $400 bucks for a 14900KS. 🤔 Anyways, I tried everything I could with the CPU. It just can't run at all without failing it seems. 

The chip refuses to launch R23 under any circumstances. Any light games are closing to desktop. This chip is defective, or it was cooked with so much voltage that it is so degraded it can barely run anymore at all. Since it needed about 1.225V for 5.6P and still would fail to run R24 consistently this makes me think it has been degraded or abused. But, I do not really know. I have never dealt with a CPU like this. I spent a lot of time with it. Not sure what it may be. 🤷‍♂️

 

There have been plenty out of the box new 14th gen CPUs that were failing on auto settings because they were garbage, but this one seems like uber trash. It could be a dud , abused/degraded or a bit of both.

 

That is stupidly high load voltage for 48c at 5.6.

 

How does it work on pure auto? Incrementing + offset to see if you can find a level of stability since it is DD/water chilled to take heat out of the equation.

 

 

[Prema]

MS can also push microcodes via Windows update as they did with the Spectre versions.

 

It's working similar to what we did with the manual update that I posted before, except for it being WHQL driver backed.

 

So, I've been testing v123, v124, v125 & v129 microcodes on my HM77 mobile platform with 13900HX and the latter three require additional 0.025v Memory Controller Voltage at 6400Mhz XMP to be TM5 stable while v123 runs them at BIOS defaults.

 

🧐

 

 

 

[Meaker]

https://www.3dmark.com/sn/1192179

 

Slightly better score as I've dialled in the GPU volt/freq curve.

[Mr. Fox]

3 hours ago, Prema said:

MS can also push microcodes via Windows update as they did with the Spectre versions.

 

It's working similar to what we did with the manual update that I posted before, except for it being WHQL driver backed.

 

So, I've been testing v123, v125 & v129 microcodes on my HM77 mobile platform with 13900HX and the latter two require additional 0.025v Memory Controller Voltage at 6400Mhz XMP to be TM5 stable while v123 runs them at BIOS defaults.

 

🧐

Happy Thursday, Brother @Prema. It has been nice seeing you here.

 

I noticed the same. I had manually set it in the BIOS for less than default (Auto) and had to set it back to Auto to make the 8400 memory clock stable.

 

You know me. I'm not going to let the Redmond Reprobates make decisions for me. I, and I alone, will decide what runs on my PC. Much better that way. EULA be damned. Posted this in another thread yesterday...

---

A "secure" system (actually a myth) that doesn't do what you want it to do is worthless. Function and performance always trump security as far as I am concerned. All the patches and security fixes in the world won't fix the DIMM-wit using the keyboard. (Yeah, you saw what I did there, LOL.)

 

The biggest security risk with any computer is a stupid user.

 

Simple fix... for unwanted updates, not for stupid users or stupid employees working on the Windoze Support Team (can't fix stupid)... just tweak the registry and hit "Advanced options" on the Windoze Updates page in settings and delay them for 10 years. Hint: You'll need to scroll a LOOOONG way down to reach the 10 year mark.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]
"ActiveHoursEnd"=dword:00000011
"ActiveHoursStart"=dword:00000008
"AllowAutoWindowsUpdateDownloadOverMeteredNetwork"=dword:00000000
"ExcludeWUDriversInQualityUpdate"=dword:00000001
"FlightCommitted"=dword:00000000
"IsExpedited"=dword:00000000
"LastToastAction"=dword:00000000
"UxOption"=dword:00000004
"InsiderProgramEnabled"=dword:00000000
"SvDismissedState"=dword:00000001
"SmartActiveHoursSuggestionState"=dword:00000001
"SmartActiveHoursTimestamp"=hex(b):b9,80,63,7c,b6,73,da,01
"HideMCTLink"=dword:00000001
"RestartNotificationsAllowed2"=dword:00000000
"SmartActiveHoursStart"=dword:00000007
"SmartActiveHoursEnd"=dword:00000010
"FlightSettingsMaxPauseDays"=dword:00000e42

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\ModelState]
"SignalRegistered"="::2F1AAFCACF"

 

No need to worry about stupid crap like this (below) ruining your day when you're calling all of the shots and keeping the numbskulls at Micro$lop out of your business.

15 hours ago, Papusan said:

 

Yup. And this apply also for the OS. 

An update made to fix a vulnerability broke dual-boot Windows-Linux PCs

neowin.com · 7 hours ago

A Windows Patch Tuesday update that was supposed to fix a vulnerability has caused a number of dual-boot Windows-Linus PCs to no longer boot up in Linux. Microsoft has yet to fix this problem.

[tps3443]

5 hours ago, electrosoft said:

 

There have been plenty out of the box new 14th gen CPUs that were failing on auto settings because they were garbage, but this one seems like uber trash. It could be a dud , abused/degraded or a bit of both.

 

That is stupidly high load voltage for 48c at 5.6.

 

How does it work on pure auto? Incrementing + offset to see if you can find a level of stability since it is DD/water chilled to take heat out of the equation.

 

 

I couldn’t even bare it. The chip was just completely unstable on auto/default everything and DDR5 5600. I ran it for like 3 hours last night trying to see if I could get it working properly. And I couldn’t do anything but crash and run in circles. It acted like a 1000% defective CPU to me.
 

(1) Opening R23 was impossible. 

(2) Extracting new R23 file would freeze during extraction.

(3) opening any game would close to desktop after just a second, even games like BeamNG that are easy to run without shader compiling. 
(4) The only thing I could run was CPU-Z bench/Stress, which case the temps were really really good. 
(5) Opening a browser would lose internet connection and say, you‘re not connected to the internet.
 

Using 5.9/4.5/4.5 with DDR5 5600c46 complete auto settings was next to impossible. I increased SA voltage which actually helped stability a little bit. R24 load would shoot load voltage up, and crash before it even started. 
 

It would only run properly if the chip was de-tuned to 5.6P/4.3E. Then it was useable as a chip. I did test memory stability at which passed fine as well. I pulled the chip and put mine back in. 
 

Here are a few pictures of the CPU. 
 

 

 

[Talon]

17 hours ago, Papusan said:

 

 

Intel haven't many other choices. The sales in Korea has sinked as a stone in the ocean and more of this news you see below will increase the damage further. And all the new bugged beta bios from the mb manufacturers don't help on the situation.

 

Raptor Lake instability hits streamer Asmongold — Black Myth: Wukong shader compilation fails on stream

 

https://www.tomshardware.com/pc-components/cpus/raptor-lake-instability-hits-streamer-asmongold-black-myth-wukong-shader-compilation-fails-on-stream

 

He hasn't updated his microcode. The comments on Steam show that after users updated their BIOS, the crashing stops and they can compile. Unfortunately so many don't know how or won't update their BIOS. 

 

 

 

[tps3443]

9 minutes ago, Talon said:

 

He hasn't updated his microcode. The comments on Steam show that after users updated their BIOS, the crashing stops and they can compile. Unfortunately so many don't know how or won't update their BIOS. 

 

 

 

Watching these videos baffles me. I keep hearing him talk about "this CPU is only 3% faster in gaming" "theirs was 5% faster in gaming, but its not all that much fast" Where is this performance coming from? I am GPU bottlenecked like the rest of us. 🤣