Link Copied
Here is the screen cap of Intel Processor Diagnostic Tool that shows that Prime Numbers test runs only for 45 seconds :
Hi again Deivid,
As I mentioned in my previous reply, I found peculiar that IPDT would run a test in 2 minutes only.
I found the documentation for the IPDT command line tool to run Prime Numbers calculation.
So :
- I set in BIOS SVID Behaviour="auto" and "MultiCore Enhancement= disabled-enforce all limits".
- I launched IPDT command line tool Math_PrimeNum.exe and Prime95
/c/Program Files/Intel Corporation/Intel Processor Diagnostic Tool 64bit/Math_PrimeNum.exe -avx 2 -c -errstop -s 36000 -resultName /c/Users/laure/OneDrive/Bureau/PrimeNum_test_10min.txt
It seems that both crashed after almost 2 hours, see screen cap below.
What does it mean about the CPU if there is an ERROR/FATAL ERROR with those stress tests after almost 2 hours?
To those who are facing the same issue as this thread,
I have found a simple test to test for the not functioning core(s) if there is really any.
The idea of the test is to run the frequently faulty application/scenarios in every single core one by one.
0. By any means (most commonly task manager), find the process name that you want to test (right click process -> properties, name can then be seen) . For example, I will test on chrome so it is "chrome.exe" (msedge.exe for edge, etc.)
1. Download and open Process Lasso (https://bitsum.com/)
2. Open Options->CPU->CPU Affinities
2.1 tick "More strictly enforce default affinities" (not sure if that has an effect but I did)
3. Limit the process to run on one core every time by enter 1.process name, 2. CPU affinity (The index of core that you wish to use, one by one from 0-31, just test for 0-15 would probably be enough to find the bad core), 3. Add rule, 4. Click ok to apply the settings.
4. Open the process you entered after the settings are applied. To check if the process is really running on one specific core, you may see on the top right corner of the Process Lasso to see a nearly full occupying green bar, indicating that it is indeed using one core, like core 8 in my case. (Some more greens here because I am running other applications too)
5. Do whatever things that most likely to trigger the errors you usually have, for example open YouTube and watch a video. Just play a video for about ten seconds is enough to tell if the core is fine in my case.
6. Close the application after testing. Go back to CPU Affinities (step 2), test for next core (double-click existing rule to modify, remember to save rule after modifing.
7. Repeat step 2-6 with every single core. Occasionally you may see the error occured, in my case it is core #4, the fifth core starting from #0 , that by simply opening YouTube in Chrome will crash it with status_access_violation/status_breakpoint. At this point I can finally confirm that this is a problem related to, if not directly casued by, the CPU (i9-13900k).
The example screencap I am posting is repeating the test on core #4 with Edge since I am using Chrome to type this reply. Same as Chrome, within seconds of opening YouTube raised status_access_violation error, refresh and instantly another status_access_violation error raised, so on and so forth.
Hope you find this useful, and possibly assure yourself that we are the victims to our CPUs all the way.
For reference, my CPU batch number is X252M104T, has the most frequent errors triggered when running applications on core #4.
Citation: Idea come from https://community.intel.com/t5/Processors/browser-occasionally-displays-a-status-access-violation-error/td-p/1457802 where the author tested the core performances by other means and used Process Lasso to limit the bad core.
Thanks for the feedback Sibidharan, good to know!
@Alberto_R_Intel : what else is needed to offer to RMA ?
I've been suffering for 7 months, now...
Intel CPU Warranty is 3 years
I've been constantly checking posts here to check for updates. In a recent post regarding 13900k faulty core, intel staff tells the op to contact for RMA after a few discussions, and tells another op to email contact them in another post. I'd say they should be aware of the issue now. However, this post may be marked as closed by them so no more intel guy's attention. Maybe you should try direct RMA to catch their attention.
For now, I do recommand to use the free version of Process Lasso and set affinity rule to find the specific faulty core and ban it for good. (the process match in setting affinities uses Regular Expression, so a process match of * or *.* may apply the affinity to every single process to prevent any use of that core.)
Edit: I previosly only set affinities to heavily used applications instead of every tasks, I tried after I posted this, and it keep reporting error setting affinity to system tasks like svchost.exe (error log keeps logging). You may wish to only apply for the applications you commonly use, in that case Task Manager could be enough (I don't know if Task Manager is setting it permentantly, but Process Lasso does set it permentantly until rule being removed.) That makes my computer run without crashes eversince.
