Overclock.net banner
1 - 20 of 27 Posts

rstolpe

· Registered
Joined
·
120 Posts
Discussion starter · #1 · (Edited)
Hi,
Ok - this is a long story but I'll try to summit it up.

When does it happen?
It's totally random sometime my computer are just in idle and I'm away from the computer, sometime it happens during light use and sometime during heavy use.
It has only happened one time with my new Asus board but it has happened multi-times with my old MSI board.
I have notice it one time and then my computer did micro freeze for one second but that was with my MSI board.
I don't get any BSOD as it's a corrected error.

Beside replacing almost every part of my computer I have done the following multi-times.
  • Re-Installed Windows with the latest
  • Memtest86 for 8 passes (12h) without any issues
  • Installed / updated the latest drivers for everything in my computer
  • Made sure that BIOS has Intel Default settings (turned off MCE, 120w , 56 sec and 250w is the settings and that is what Intel has as default)
  • The CPU does pass the Intel Diagnostic Test and so did also my first CPU that Intel did RMA
  • I did run sfc on C: and then it did repair some files.

Timeline what I have done
  1. Bought the 10900k 2020-08-01
  2. First WHEA error appeared 2020-09-22 the system did micro freeze for 1 sec only.
  3. Did RMA the CPU with Intel and I did get a new one.
  4. That one also gave me WHEA error
  5. Upgraded 2070 Super with 2080 Super
  6. Replaced my RAM Corsair sticks with G.Skill
  7. Replaced Mobo MSI MEG z490 Ace with a Asus ROG MAXIMUS XII HERO
  8. Replaced PSU Corsair RMx 850w with 1000w
But for two days ago I did get a WHEA error again, the exact same. And as you can see I have replaced everything beside my NVME drives.
I have 3 Samsung 970 Evo Plus 1TB's two is before I did get the first WHEA error and one after.
I guess that it can be so that Intel did send me a bad replacement CPU but that chance is slim.

This is what the WHEA error says and it's the same all the time - it's hard to pin-point as it says unknown error source.
Code:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Internal parity error
Processor APIC ID: 2

The details view of this entry contains further information.

Edit:
I have this RAM: F4-3200C14D-32GTZN-G.SKILL International Enterprise Co., Ltd.
One guy at Asus did ask me to try the XMP 2.0 config with it. (what's the difference between XMP1 and 2?)
I did run it at stock before.

I have not gotten any more WHEA errors since the one that I did get 2020-12-27 and that's THE ONLY one that I got on my Asus board.
As you can see in the history above I'm paranoid that this WHEA errors are getting started again. But maybe was it one time thing and that the XMP 2.0 are fixing the issue?

@Falkentyne maybe you or @shamino1978 know anything regarding this issue? Can It bee that from BIOS version 0901 to 1003 something regarding the XMP profiles has changed?
I have been running memtest86 for 12h (8-passes) without any issues.

Or do you think like Intel and maybe it's my NVME drives that causing it as I have replaced everything else in the computer? or is it just a one-time thing?

Just to bee clear this has only happened one on my Asus board. And I did not do anything special I did download a game and COD MW2019 was running in the background by mistake and I was not using the computer during this time it was standing on it's own.
 
Discussion starter · #5 ·
dont oc your cache. rams what you running dude.


theres ways arnd it.
I don't OC that's the thing. So then it's possible that it's a broken replacement CPU from Intel then?
I did get that WHEA 2020-12-27 and after that I don't have any more WHEA errors. But I'm just worried as my other CPU did also trough WHEA errors but whit weeks apart.

My other CPU did give WHEA with a week apart.

also what games you play?? minecraft?? ghostrunner with rtx??
I'm just playing COD MW2019 and scripting in PS etc.
 
Discussion starter · #6 ·
...
 
Discussion starter · #7 ·
Did you run a chkdsk on all the drives? I'd start there....
Yes, and it did find files to repair on C: did that and also sfc direct after I did get the WHEA error.
 
Discussion starter · #9 ·
@Falkentyne
are you running stock as in intel default press F1, enter bios. enable xmp ??
Yes I'm running stock as I stated XMP are not enabled.
I did press f1 and I also disabled MCE and I did put the right valvues for my CPU. I did write them in the original post.

The only thing that I can think of that was changing is that maybe 2 days before the WHEA I did update BIOS from 0901 to 1003 but it's the same microcode so it should not affect it.
 
its not
Yes I'm running stock as I stated XMP are not enabled.

The only thing that I can think of that was changing is that maybe 2 days before the WHEA I did update BIOS from 0901 to 1003 but it's the same microcode so it should not affect it.
since u are using maximus XII hero

go back to bios 0707

found a flaw on that board bios 09xx, 10xx

reported to asus fae already

it fails intel pricessor diagnostic tool test

at stock.
 
Discussion starter · #11 ·
its not
since u are using maximus XII hero

go back to bios 0707

found a flaw on that board bios 09xx, 10xx

reported to asus fae already

it fails intel pricessor diagnostic tool test

at stock.
The CPU are not failing the Intel PDT and my first CPU that I did RMA did not fail it either.

What's the flaw?
 
im on 1003 z490 hero, and i just ran the test and im not failing... maybe your ram needs to have XMP enabled? did you check with the Motherboard QVL becuase it may not be compatilbie until you enable XMP.. can you try a different power outlet. it could be interfernce from the outside, try differnt power cable. unplug ethernet and go wireless, try a different houses power plug. maybe its bad power. but im on 1003 with 0 issues 100% stress tested.. i did get WHEA Errors but i needed more voltage for my OC (5.1GHz ALL Core i9 10900kf) when i was at 1.35 i got WHEA while gaming for an hr, but at 1.365 no WHEA you need more voltage.

iv noticed somtimes power fluctuates, and you need to compensate by adding more voltage.. back when i had my i7 950 x58, during the summer i could run on lower voltage and be stable. then one winter hit i needed to up the voltage a little bit. try a differnt power cable.. try upping the voltage i doubt the bios has anything to do with it it most likely your power grid and it needs more voltage. or the wiring in your house but eather way WHEA errors is a sign of not enough voltage for the CPU.
 
Discussion starter · #13 · (Edited)
im on 1003 z490 hero, and i just ran the test and im not failing... maybe your ram needs to have XMP enabled? did you check with the Motherboard QVL becuase it may not be compatilbie until you enable XMP.. can you try a different power outlet. it could be interfernce from the outside, try differnt power cable. unplug ethernet and go wireless, try a different houses power plug. maybe its bad power. but im on 1003 with 0 issues 100% stress tested.. i did get WHEA Errors but i needed more voltage for my OC (5.1GHz ALL Core i9 10900kf) when i was at 1.35 i got WHEA while gaming for an hr, but at 1.365 no WHEA you need more voltage.

iv noticed somtimes power fluctuates, and you need to compensate by adding more voltage.. back when i had my i7 950 x58, during the summer i could run on lower voltage and be stable. then one winter hit i needed to up the voltage a little bit. try a differnt power cable.. try upping the voltage i doubt the bios has anything to do with it it most likely your power grid and it needs more voltage. or the wiring in your house but eather way WHEA errors is a sign of not enough voltage for the CPU.
Hi,
My CPU are passing every test it is. Nothing strange there. That's the issue in this troubleshooting as I can't find out what's the issue or force it to happen.
The WHEA error are coming random and sometime weeks a part.

The thing is that I did have WHEA with a different motherboard also and a replacement CPU - only thing left from the old setup is my nvme drivers that's why I'm wondering if it's possible they are the issue?
The main line in my house are good also the wiring as I have other stuff connected to the same outlet and I have made sure I'm not going over the W for the outlet. (switches, raspberry pies etc.)

One guy at Asus told me to try XMP 2.0 profile but what's the difference between profile 1 and 2? I always want to know as I don't want to just do things. As I understands it, profile 1 is Asus optimized and Profile 2 is Vender values?

Maybe this issue are not the same that I did have before, I don't know. Maybe this was something with my RAM and the BIOS update so I need to go with XMP 2.0?
I have this:
F4-3200C14D-32GTZN-G.SKILL International Enterprise Co., Ltd.


Edit:
Can you check in Event Viewer and then under Warning to see if you have any WHEA errors logged there?
 
Hi,
My CPU are passing every test it is. Nothing strange there. That's the issue in this troubleshooting as I can't find out what's the issue or force it to happen.
The WHEA error are coming random and sometime weeks a part.

The thing is that I did have WHEA with a different motherboard also and a replacement CPU - only thing left from the old setup is my nvme drivers that's why I'm wondering if it's possible they are the issue?
The main line in my house are good also the wiring as I have other stuff connected to the same outlet and I have made sure I'm not going over the W for the outlet. (switches, raspberry pies etc.)

One guy at Asus told me to try XMP 2.0 profile but what's the difference between profile 1 and 2? I always want to know as I don't want to just do things. As I understands it, profile 1 is Asus optimized and Profile 2 is Vender values?

Maybe this issue are not the same that I did have before, I don't know. Maybe this was something with my RAM and the BIOS update so I need to go with XMP 2.0?
I have this:
F4-3200C14D-32GTZN-G.SKILL International Enterprise Co., Ltd.


Edit:
Can you check in Event Viewer and then under Warning to see if you have any WHEA errors logged there?
they all dont dude. they are clueless about this error. they always attribute their game crash etc to the game since its very random.

ghostrunner rtx enables brings this error out in level climb onwards
minecraft was where most ppl noticed it

oced cache speeds up the error

@Falkentyne been talking about this error for years. just google and you will see his name popping up.

btw i asked to run that test cause last week somebody had an issue on hero bios 1003 but no problem bios 0707
 
Discussion starter · #15 ·
they all dont dude. they are clueless about this error. they always attribute their game crash etc to the game since its very random.

ghostrunner rtx enables brings this error out in level climb onwards
minecraft was where most ppl noticed it

@Falkentyne been talking about this error for years. just google and you will see his name popping up.

btw i asked to run that test cause last week somebody had an issue on hero bios 1003 but no problem bios 0707
But my WHEA errors are popping up during ordinary use also. (not gaming)
 
whea errors means ur CPU is not getting enough voltage... try manually setting you CPU voltage to 1.3, and your LLC to 4 or 5 and see if it goes away, also your power company's power may be a little dirty, i was getting errors at stock too and i had to up the voltage to stop the errors
 
Discussion starter · #17 ·
whea errors means ur CPU is not getting enough voltage... try manually setting you CPU voltage to 1.3, and your LLC to 4 or 5 and see if it goes away, also your power company's power may be a little dirty, i was getting errors at stock too and i had to up the voltage to stop the errors
One of the reasons can bee because of low voltage yes but it's not always the case. I don't think I have dirty main power here as I have not notice it with other devices. So your running Intel default and pumped the vcore to 1.3?
Do you have the same CPU and motherboard as me?
 
Disable all your power management features and processor steppings. I bet this error is happening due to the NVME and the pcie bus. Or the nvme is going bad.

you can use HDsentinel to check it out.
 
I ran into a similar ghost crash issue once before, replaced most of my computer before i discovered the source of the problem.

SSD was overheating. turns out those m2/nvme ssd overheat super easy (50-55C) worse, when they're reading/writing thier temps can spike almost 10C in seconds, so what you really need them down around 45-50C (or lower) to be safe. once i figured that out I ditched my kraken for the wrath spire cooler, kept the airflow over the ssd, and crashes vanishes instantly.
 
  • Rep+
Reactions: rstolpe
@Falkentyne
bro its like all your pages and pages of documenting this issue is ignored.
its all over the net.

these guys suddenly found this and think its nvme.

anyway i solved it for 10900k
52|50 4400c16

told the dude one part already. the other is ram third timings. he needs to figure that out himself

best to test this is ghostrunner rtx enabled level climb onwards. leave hwinfo open.
 
1 - 20 of 27 Posts