• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Is my i7 13700k screwed?

Associate
Joined
22 Sep 2020
Posts
52
Hi, and thanks for reading. As the title says I was wondering if anyone could give me some help. My 13700k has been working fine since I got it about a year ago, but recently I've been met with some random BSOD and can't seem to figure out the cause.

I have my CPU on complete stock settings with XMP enabled for my RAM. When I do an OCCT test, I used the settings below. I get a message saying "CPU+RAM - 3 errors found on physical core #2"

OCCT test settings
Data set:Large
Mode:Normal,
Load type:Steady
Instruction set: avx2
Thread settings:Auto

I have also tried memtest86 to test my RAM with XMP enabled and have done 2 passes with no errors with my ram

Do I possibly have one of the unfortunate Intel CPUs that have been degraded due to the poor voltage supplied or oxidization issue?

Specs
CPU: i7 13700k stock settings
RAM: Corsair 4000Mhz CMK32GX4M2G4000C19
GPU: MSI 4070ti
MOBO: Gigabyte z690 UD DDR4, Bios version f29, I updated my MOBO as soon as the newer versions released
Windows 11 Pro: 23H2
 
Did you try OCCT with the ram at stock to see what the results there were?

Have you looked in windows event viewer to see if Windows is logging WHEA errors being recovered regularly?
 
Do I possibly have one of the unfortunate Intel CPUs that have been degraded due to the poor voltage supplied or oxidization issue?
Do you get access violation errors in Chrome or Edge?

Do apps/games crash?

Have you experienced file corruption, especially when zippng?
 
Did you try OCCT with the ram at stock to see what the results there were?

Have you looked in windows event viewer to see if Windows is logging WHEA errors being recovered regularly?
Thanks for your input. I'm currently running another OCCT test again, but without XMP enabled on my RAM. I'll update after the test to see if I get any errors again.

As to the windows event logger. This is a screen shot below, as to be honest I'm not too sure what I'm looking at LOL.


 
Do you get access violation errors in Chrome or Edge?

Do apps/games crash?

Have you experienced file corruption, especially when zippng?
Thanks for your reply

I haven't noticed any violation errors in Chrome.

Some games have been crashing at random such as BFV, BO6, and some other FPS games.

I haven't noticed any corruption when unzipping files.
 
Thanks for your input. I'm currently running another OCCT test again, but without XMP enabled on my RAM. I'll update after the test to see if I get any errors again.

As to the windows event logger. This is a screen shot below, as to be honest I'm not too sure what I'm looking at LOL.



You want to look down the source column and see if there are any which state WHEA-Logger as warnings or errors. Basically if you are logging errors like that then windows is logging regular instability which is not enough to cause a BSOD, but still could indicate a problem.
 
Last edited:
You could also download and run the Intel Processor Diagnostic Tool and see if it reports anything (although I've found it to be generally useless in the past).

 
Last edited:
You could also download and run the Intel Processor Diagnostic Tool and see if it reports anything (although I've found it to be generally useless in the past).

Thanks, I'll give that a go after I've finished the OCCT test with xmp off.
 
You could also download and run the Intel Processor Diagnostic Tool and see if it reports anything (although I've found it to be generally useless in the past).

I completed the intel diagnostic tool with a pass on everything. I also got no errors when doing the OCCT test again with XMP turned off.
I looked through the event logger and saw no WHEA-logger errors too.
Would this indicate that it's more of a RAM or MOBO issue I'm having?

Thanks
 
Last edited:
Would this indicate that it's more of a RAM or MOBO issue I'm having?
It is looking that way, if you keep XMP off and don't get any errors or crashes since that time.

4000 is high for DDR4, so maybe your CPU's memory controller is not happy.

The symptoms being errors in a processor core seems odd, but I'm not a RAM overclocker so I don't know if that's normal.
 
Hwinfo does whea errors too. You can enable xmp but run at ~3800. Assuming the problem can be reproduced in Oct you should know if you are in the clear.
 
I'd still do a short run without XMP and see if the BSODs go away - how often were they occurring, will you know soon?

If you do enable XMP Intel lists the max stock speed as 3200mhz so you could just run that?
 
Hwinfo does whea errors too. You can enable xmp but run at ~3800. Assuming the problem can be reproduced in Oct you should know if you are in the clear.
So can i just enable the XMP profile but then just change the RAM frequency manually to 3800, and I won't need to touch timings or anything?
 
Did you verify stability when you initially set it up? It could be IMC degradation if for example VCCSA is set too high on auto.
unfortunately, I didn't do any testing when I bought the parts I just left everything on default and enabled XMP, and since it worked fine I didn't bother. A bit stupid of me TBH LOL

Also, my MOBO doesn't seem to have a VCCSA sensor to check the voltages in HWINFO64
 
I'd still do a short run without XMP and see if the BSODs go away - how often were they occurring, will you know soon?

If you do enable XMP Intel lists the max stock speed as 3200mhz so you could just run that?
The BSOD aren't occurring that frequently, probably about 2-3 times max a month.
Now that I think about it, they have only really been occurring since I updated my BIOS the the latest version.
Which is supposedly the final version of the intel voltage fix according to the BIOS update description.
 
Think that might be under SA VID, at least it is on my z690.

Edit: Oh it says that's the requested voltage not the supplied voltage... check BIOS?
I checked in my BIOS, and it gives me the option to manually change the VCCSA voltage but doesn't show any current values.
I think my MOBO is too low-end to have such a sensor, unfortunately.
I've set my RAM to 3800Mhz with XMP enabled instead of 4000Mhz, and I'm going to test with OCCT again to see if I get any errors.

Thanks for your help it's been much appreciated.
 
So can i just enable the XMP profile but then just change the RAM frequency manually to 3800, and I won't need to touch timings or anything?
Should be fine as long as the voltage is good. If it errors you can drop it further. Without xmp it was running at 2133?
 
Back
Top Bottom