Cinebench r23 ошибка

Hey Everyone! I’m really struggling to figure out what the issue is with my latest build. My reddit post goes into some more detail but I’ll keep it brief here.

I’m having games crash on me, specifically Warzone 2.0 and World of Warcraft. Both present error messages along the lines of «ACCESS_VOILATION» related to memory. Cinebench and Benchmark crash instantly.

My current system:
ASUS Z690-E ROG Strix Gaming WiFi DDR5 Intel LGA 1700 ATX Motherboard (and now a Z790 Carbon WIFI)
Intel Core i9-13900K Raptor Lake 3.0GHz Twenty Four-Core LGA 1700
G.Skill Ripjaws S5 64GB (2 x 32GB) DDR5-5200 PC5-41600 CL36 Dual Channel (and now 32GB x2 Trident Z5 DDR5 6400)
Samsung 980 Pro SSD 2TB M.2 NVMe Interface PCIe Gen 4×4 Internal Solid State
Corsair RMe Series RM1000e Fully Modular 80PLUS Gold ATX Power Supply
NZXT Kraken X73 RGB 360mm CPU Water Cooling Kit
Lian Li LANCOOL III RGB Tempered Glass ATX Mid-Tower Computer Case
Nvidia GeForce RTX 4090

The only way I can get this system stable is by using Intel Extreme Tuning Utility and setting my Core Power Ratio from 55x to 52x.

I’ve been back and forth to Micro Center with no luck. So far I’ve tried upgrading my motherboard to the Z790 Carbon WIFI, no change. I now just tried new RAM, Trident Z5 DDR5 6400, no change. Exact same behavior.

At this point it has to be the processor, right?

Thank you!

You need to do two things: Run more specific stress tests, targeting either the RAM (+ memory controller) or the CPU. And while doing that, apart from looking what errors out where, you need to monitor all the sensors. For the former, check my RAM thread under 5), it lists some RAM-specific stress tests. «Small FFTs» (torture test) in Prime95 concentrates on CPU stability, «Large FFTs» more on the RAM and IMC.

Then we can check the the sensors with HWinfo64. Run it and open «Sensors», then expand all sensors by clicking on the little <—> arrows on the bottom. Also expand the columns of the sensors a bit so everything can be read. Make it three big columns of sensors (or four, if the screen resolution is high enough). In the end, it should be a screenshot with all the sensors visible at once, like this:

Make sure your power plan in Windows is on «Balanced». Let it run in idle for a while (couple minutes), so the «minimum» baselines for the values are established. After a short time in idle, produce full CPU load with Cinebench R23, and after the 10 minute run when the CPU temperatures have stabilized at the highest level, take a screenshot. Then we get the full picture of what’s going on. You can also run it later during the even more taxing stress tests like Prime95, but first i want to see «normal» theoretical full load of all cores, similar to a rendering job and such.

If at any point the CPU temperatures get out of hand (approaching 100°C), stop the test early and take the screenshot then. Because the 13900K is a CPU with an extremely high power draw, making it close to uncoolable for all but the best off-the-shelf coolers, see here.

Thank you! Full transparency, I completely forgot I posted on the forums. I’ll start digging in now.

That to me says it’s the CPU. Especially after reading your Reddit post. Needing to turn the CPU down (assuming you’ve got sufficient cooling…..the X73 should be good enough for that……) just tells me the CPU is bad and unable to meet it’s specs.

As far as cooling…..my experience is quite different from other posters here. I’ve not had any issues cooling my 13900k, even doing benchmarks that aren’t made to be unreasonable.
And that’s with stock settings, unlimited power, etc…..I’ve only enabled XMP within my BIOS. So I dunno…..either I hit the silicon lottery……or my cooling is just that good (bear in mind, only an AiO stock cooler).
My sons 13900 works just fine with a MSI S280 cooler as well. No issues on stock settings with XMP enabled.

Yeah I’m really thinking that will end up being the case. I found a few posts stating that RMAing the chip was the fix. Seems like Late Fall had a bad batch. I’m going to troubleshoot a little longer with what citay was saying to do above but may just need to go to Micro Center and let them know. I have 2 year replacement plan with them — hoping it won’t be a huge issue.

You need to do two things: Run more specific stress tests, targeting either the RAM (+ memory controller) or the CPU. And while doing that, apart from looking what errors out where, you need to monitor all the sensors. For the former, check my RAM thread under 5), it lists some RAM-specific stress tests. «Small FFTs» (torture test) in Prime95 concentrates on CPU stability, «Large FFTs» more on the RAM and IMC.

Then we can check the the sensors with HWinfo64. Run it and open «Sensors», then expand all sensors by clicking on the little <—> arrows on the bottom. Also expand the columns of the sensors a bit so everything can be read. Make it three big columns of sensors (or four, if the screen resolution is high enough). In the end, it should be a screenshot with all the sensors visible at once, like this:

Make sure your power plan in Windows is on «Balanced». Let it run in idle for a while (couple minutes), so the «minimum» baselines for the values are established. After a short time in idle, produce full CPU load with Cinebench R23, and after the 10 minute run when the CPU temperatures have stabilized at the highest level, take a screenshot. Then we get the full picture of what’s going on. You can also run it later during the even more taxing stress tests like Prime95, but first i want to see «normal» theoretical full load of all cores, similar to a rendering job and such.

If at any point the CPU temperatures get out of hand (approaching 100°C), stop the test early and take the screenshot then. Because the 13900K is a CPU with an extremely high power draw, making it close to uncoolable for all but the best off-the-shelf coolers, see here.

OK so I ran the tests that I could to start providing some information. Since this is a new set of RAM and a new motherboard, with the same exact issue (literally no change) I decided to focus on the CPU related tasks first. I will post these then start digging into RAM. Here are my results:

System Summary

DURING Cinebench R23 with XTU Performance Core Ratio 55x (stock) **RAN FOR 1 SECOND BEFORE SOFT CRASH**

DURING PRIME95 Small FFT with XTU Performance Core Ratio 55x (stock)
No crashes but turned off after 5-10 seconds due to temps

DURING Cinebench R23 with XTU Performance Core Ratio 52x
Ran for about 30 seconds due to temps. I have finished it in the past with a score of 35000

AFTER Cinebench R23 with XTU Performance Core Ratio 52x

Full Bug Report for Cinebench R23 is too large to post but there is a familiar error in the huge log that I would receive when Fortnite, COD or WOW would crash:

Opened Scenes
    {
        Active Scene: 0x0000029132F13F80 "C:\Users\Das Neids\Downloads\CinebenchR23\resource\modules\cinebench\cpu\cpu.c4d"
    }
    Exception
    {
        ExceptionNumber = 0xC0000005
        ExceptionText = "ACCESS_VIOLATION"
        Address = 0x00007FF91D1AB6C8
        Thread = 0x0000000000002D6C
        Last_Error = 0x00000000
    }

Again this is if I have everything set to stock. I don’t receive this error and Cinebench R23 runs with a score of 35000ish if Performance Core Ratio is set to 52x down from 55x.

Your CPU cooling is completely overwhelmed with the 300W on a very small surface (as would be almost any cooling, other than a powerful custom loop). We have to get this under control by setting lower power limits. I linked this thread before which goes a bit more into detail on that, and also read this post and follow the links. This will hopefully guide you in the right direction. You could also look into reducing «CPU Lite Load» which is a good way of lowering the power draw without sacrificing any performance, but it has to be stability-tested. Lowering the power limits is something i’d do anyway. You should start with around 220W and see what kind of temperatures you see there.

I’ll get to work. You are wonderful.

Maybe I was mixing screenshots up but I also noticed I had to restart HWiNFO for it to pick up the new 200W from the 220W.
I was adjusting «Core Voltage Offset» in XTU. Maybe that isn’t a negative offset? No option to select a negative offset in XTU.

I recently purchased a Thermal Grizzly Contact Frame: https://www.microcenter.com/product/649280/Intel_12th_Gen_CPU_Contact_Frame and I recently (Saturday) applied Arctic-6 thermal paste. Maybe I goofed up the application? I no longer have the box for the NXZT but I’ll see if I can find a model number somewhere on the hardware.

I’ll try adjusting these things in bios. The only change I tried in bios was the CPU Lite Load. It is defaulting to Mode 9. I tried Mode 5 and blue screened in Windows.

I bought the cooler in Jan 2023 from Microcenter. Order details don’t tell me much unfortunately on specifics. The cooler part is making me a little nervous so I figured I’d reapply one more time ha. In the past 2 weeks I’ve probably reapplied 3 times (once because I was paranoid I left materials stuck on it, once for the thermal grizzly frame and another with the Arctic-6). The first two times I feel like it’s been squeezed out from the center. This is what it looks like now.

It looks like I used too much but could I be over-tightening the AIO as well pushing it out of the center? This pic looks like it filled the center the best but still might have been too much of both pressure and paste.

I’ll reapply with your recommendations then start adjusting in BIOS.

Also, do you have a venmo or anything? I’d love to donate some $$ for all of your help!! Buy yourself a case of beer or some coffeeeeessss!!!!

Way too much thermal paste. It has to be just a thin layer, not caked in the stuff. If you apply too much thermal paste, it can act as more of an insulator.

With the cooler’s screws having a defined endpoint, you cannot overtighten them. Instead, it’s necessary to tighten them all the way to the endpoint (in a cross pattern, a couple turns each), to reach the correct mounting pressure.

It could be good to try without the contact frame too, at this point.

Yeah I figured with how messy that one was ha.

One last question as I’m starting my bios trip, should I be doing all of this with XMP off then turn it on when stable or best to do it with it enabled? Thanks!