Overclock.net banner

24121 - 24140 of 45824 Posts

·
Overclocker
Joined
·
6,943 Posts
Can someone plz help me with the motherboard 4-pin pwm header? Yesterday when i tried to connect my 3 Noctua NF-F12 Industrial PPC 3 K rpm fans via an 3 way fan splitter to my CPU fan header on the motherboard and all was working well. After a few hours of gaming and other stuff the fans stopped working and the waterpump also shuts down to which my temps raised to 96 c and the PC shuts down to protect itself with code 8 on the LED display. When i restarted my PC the fans were spinning at 100% all of a sudden while i have PWM and silence mode enabled in BIOS. What could be the cause of this weird behavior? I would like to use my motherboard headers because they are PWM in order to ramp my Noctua fans down and ramp them up when needed. My fan controller is only 3-pin which is useless in my case.

Maybe @The Stilt Can look in to this plz?
 

·
Registered
Joined
·
1,455 Posts
Quote:
Originally Posted by hurricane28 View Post

After a few hours of gaming and other stuff the fans stopped working and the waterpump also shuts down to which my temps raised to 96 c and the PC shuts down to protect itself with code 8 on the LED display.
Code 8 is not a self-protection thermal shutdown, it's a CPU crash after which low voltage is still applied to the CPU. A thermal shutdown is a full shutdown with no POST code with power being turned (soft-)OFF.

And since pump-headers still can fail, here I go again @elmor: Lower the default MI Offset from 272 to something lower than 268. It's a dangerous default value even after you turned off Sense MI Skew by default.
 

·
Meddling user
Joined
·
7,423 Posts
Quote:
Originally Posted by hurricane28 View Post

Can someone plz help me with the motherboard 4-pin pwm header? Yesterday when i tried to connect my 3 Noctua NF-F12 Industrial PPC 3 K rpm fans via an 3 way fan splitter to my CPU fan header on the motherboard and all was working well. After a few hours of gaming and other stuff the fans stopped working and the waterpump also shuts down to which my temps raised to 96 c and the PC shuts down to protect itself with code 8 on the LED display. When i restarted my PC the fans were spinning at 100% all of a sudden while i have PWM and silence mode enabled in BIOS. What could be the cause of this weird behavior? I would like to use my motherboard headers because they are PWM in order to ramp my Noctua fans down and ramp them up when needed. My fan controller is only 3-pin which is useless in my case.

Maybe @The Stilt Can look in to this plz?
I use CPU_FAN to supply PWM to a GELID 4 in 1 cable, this runs 4x ThermalRight TY-143, the cable powers fans via molex. I use PWM mode in UEFI with my own manual curve.

Then I use CHA_FAN1 in PWM mode, Turbo profile, for a Arctic Cooling F12. Next CHA_FAN3 is used for 2x Arctic Cooling F9, PWM mode, Standard profile.

So far since Mumak fixed HWiNFO back in March I have never had fans stuck high or low, etc. That was my only issue/cause and fixed via Mumak/Elmor.
 

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by Timur Born View Post

Code 8 is not a self-protection thermal shutdown, it's a CPU crash after which low voltage is still applied to the CPU. A thermal shutdown is a full shutdown with no POST code with power being turned (soft-)OFF.

And since pump-headers still can fail, here I go again @elmor: Lower the default MI Offset from 272 to something lower than 268. It's a dangerous default value even after you turned off Sense MI Skew by default.
Yes it is actually. The CPU becomes unstable at 96 c which results in code 8 when it shuts down to protect itself.

My CPU overclock is rock stable in all of the tests for long period of time,and i don't mean gaming but like IBT AVX, PRime95 , AIDA64 etc.

What does this Mi skew ofset do?
 

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by gupsterg View Post

I use CPU_FAN to supply PWM to a GELID 4 in 1 cable, this runs 4x ThermalRight TY-143, the cable powers fans via molex. I use PWM mode in UEFI with my own manual curve.

Then I use CHA_FAN1 in PWM mode, Turbo profile, for a Arctic Cooling F12. Next CHA_FAN3 is used for 2x Arctic Cooling F9, PWM mode, Standard profile.

So far since Mumak fixed HWiNFO back in March I have never had fans stuck high or low, etc. That was my only issue/cause and fixed via Mumak/Elmor.
I think its HWINFO64 again just like on my other machine, i will try again with HWINFO64 disabled. If that doesn't work i probably end up buying an PROPER fan controller like the Aquacomputer Aqauero 6 pro.
 

·
Registered
Joined
·
241 Posts
Lol, when I started to stress my New stilt's safe ram timings with 3200mhz, at first it seemed very stable with those timings prime95 large ffts, I couldn't pass large ffts (without picking those timings) more than 10 minute or 5 minute before one core failure. With these timing at first I could stress test these over an hour without any issues at least with large ffts, but when I woke up today PC was crashed with code 8, I was like okay ?? What I've noticed with Ryzen that if I could pass particular stress test over 40min to 1.2 hour mark with no crashes (like large ffts) then I could easily run it over 10 hour no crashes.... It caught me by surprise as today when I tried to run it, first core failure happen in matter of seconds! second core fails just couple of secs after it... and one by one cores starts to crash, I Tried to blend test it and I was 20 mins away and almost all cores were failed, load was only 7% at time when I came back to my room....

I've tried to bump dram voltage from 1.4 to 1.5, tried and soc from 1.05 to 1.1, pll from 1.8 to 1.9 with no avail,

This is making me almost pop my eyes out, cores CAN't fail large ffts in matter of seconds cause I could run it over 1 to 2 hour before I fell asleep yesterday!
mad.gif
mad.gif
mad.gif


It doesn't make any frickin' sense....

Even at defaults dram timings large crashes at 3.2ghz 3ghz and maybe even 2933mhz argggh!

Can anyone help me before I explode, core overclocking was super easy compared when I started to hassle with dram overclock, I was at stable 3.9Ghz 1.36v llc3 and actually voltage were 1.33v when stressed and max temps 63c..
 

·
Meddling user
Joined
·
7,423 Posts
Quote:
Originally Posted by hurricane28 View Post

I think its HWINFO64 again just like on my other machine, i will try again with HWINFO64 disabled. If that doesn't work i probably end up buying an PROPER fan controller like the Aquacomputer Aqauero 6 pro.
Only my opinion.

I have used HWINFO for days at times. Only recently I did [email protected] run on CPU/GPU with uptime of 60hrs+, 0 issues from HWINFO. Regardless of my HW/profile, if HWINFO was sending Super IO chip loopy I would have the symptoms as I have same mobo as others.

I have spent more time stress testing / tweaking / using differing CPUs and early on differing RAM with this mobo than many members that say "oh it's a crap mobo/UEFI,etc".
Quote:
Originally Posted by hurricane28 View Post

My CPU overclock is rock stable in all of the tests for long period of time,and i don't mean gaming but like IBT AVX, PRime95 , AIDA64 etc.
Your long period maybe too short, may also be too low a setting, for example how your IBT AVX run was Very High (4096MB) and not high RAM set.

What was the length of time? did you do reruns?
 

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by gupsterg View Post

Only my opinion.

I have used HWINFO for days at times. Only recently I did [email protected] run on CPU/GPU with uptime of 60hrs+, 0 issues from HWINFO. Regardless of my HW/profile, if HWINFO was sending Super IO chip loopy I would have the symptoms as I have same mobo as others.

I have spent more time stress testing / tweaking / using differing CPUs and early on differing RAM with this mobo then many members that say "oh it's a crap mobo/UEFI,etc".
Your long period maybe too short, may also be too low a setting, for example how your IBT AVX run was Very High (4096MB) and not high RAM set.

What was the length of time? did you do reruns?
I always use HWINFO64 in the back ground because i REALLY like the program. I had this problem before on my 990FX system and an update fikst it for me.

I am not sure if its HWINFO64 or not, i need more testing for this. Maybe the EC senor is causing issues again? I disabled this sensor completely on my 990FX system as i had many problems monitoring from it and causes all kinds of problems.
 

·
Registered
Joined
·
1,455 Posts
Quote:
Originally Posted by hurricane28 View Post

Yes it is actually. The CPU becomes unstable at 96 c which results in code 8 when it shuts down to protect itself.
Again, it does not shutdown, voltage is still applied. Around 0.4 to 0.5 V if I remember correctly, which corresponds to full idle voltage using the Power Saving Windows profile that made the hose explode off my AIO pump.
 

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by Timur Born View Post

Again, it does not shutdown, voltage is still applied. Around 0.4 to 0.5 V if I remember correctly, which corresponds to full idle voltage using the Power Saving Windows profile that made the hose explode off my AIO pump.
Oke whatever, i can't use the PC than.. call it what you want, my PC shuts down because of temps NOT instability.. Your hose must have been weak all the time, hoses don't "explode" that easily.
 

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by gupsterg View Post

@hurricane28

From launch to date I have used HWINFO with ASUS EC enabled.
This is weird, it must be me than i guess..

I don't know what i am doing wrong than because every time when i monitor the EC sensor it appears that I have problems with it... maybe it doesn't like me and trolls me for whatever reason?
lachen.gif
 

·
Premium Member
Joined
·
2,738 Posts
Quote:
Originally Posted by lcbbcl View Post

@The Stilt
Do you have some ideas why i have this problems with Ram Slot? Post
Tried installing the DIMMs to A1 & B1 slots and both BankGroupSwap & BankGroupSwapAlternative controls work just as they should. Both of these options are currently only located in CBS, which means if you fail memory training these options will be reset to defaults. BankGroupSwap is enabled and BankGroupSwapAlternative is disabled by default, regardless of the DRAM configuration (1DPC, 2DPC, SR, DR). You could try increasing the "Mem Over Clock Fail Count" option to two or three.

Also HWInfo 5.55-3200 was reading the onboard DIMM temperature sensor just fine, when A1 & B1 slots were populated.
 

·
Premium Member
Joined
·
2,738 Posts
Few more DRAM timing presets:

Hynix AFR, 1DPC SR

"Safe"



- ProcODT 60 Ohms
- DRAM Voltage / DRAM Boot Voltage 1.340V (keep these syncronized at all times)
- VDDCR_SOC 1.025V

"Extreme"



- ProcODT 60 Ohms
- DRAM Voltage / DRAM Boot Voltage 1.405V (keep these syncronized at all times)
- VDDCR_SOC 1.025V

Hynix MFR, 1DPC SR

"Safe"



- ProcODT 60 Ohms
- DRAM Voltage / DRAM Boot Voltage 1.365V (keep these syncronized at all times)
- VDDCR_SOC 1.025V

"Fast"



- ProcODT 60 Ohms
- DRAM Voltage / DRAM Boot Voltage 1.390V (keep these syncronized at all times)
- VDDCR_SOC 1.025V
 

·
Registered
Joined
·
302 Posts
Its stable its stable at 3200 with @The Stilt timings
2x F4-3200C14-16GVK
 

·
Registered
Joined
·
302 Posts
Quote:
Originally Posted by The Stilt View Post

Tried installing the DIMMs to A1 & B1 slots and both BankGroupSwap & BankGroupSwapAlternative controls work just as they should. Both of these options are currently only located in CBS, which means if you fail memory training these options will be reset to defaults. BankGroupSwap is enabled and BankGroupSwapAlternative is disabled by default, regardless of the DRAM configuration (1DPC, 2DPC, SR, DR). You could try increasing the "Mem Over Clock Fail Count" option to two or three.

Also HWInfo 5.55-3200 was reading the onboard DIMM temperature sensor just fine, when A1 & B1 slots were populated.
Thanks for your answer but its not about failing to train,its post Ok.
But if i use A1 B1 Bankgroupswap its always Disable,even if i set manual Enable,and Hwinfo64 its not able to read my DIMM temperature.
A2 B2 work as you said.
This problem i have also at 2133Mhz witch its not a OC mode
 

·
Premium Member
Joined
·
2,738 Posts
Quote:
Originally Posted by lcbbcl View Post

Thanks for your answer but its not about failing to train,its post Ok.
But if i use A1 B1 Bankgroupswap its always Disable,even if i set manual Enable,and Hwinfo64 its not able to read my DIMM temperature.
A2 B2 work as you said.
This problem i have also at 2133Mhz witch its not a OC mode
BankGroupSwap is never disabled automatically.
DIMM temperature sensors are read through SMBUS, so any of the DRAM related timings cannot affect it.
 

·
Meddling user
Joined
·
7,423 Posts
Quote:
Originally Posted by hurricane28 View Post

This is weird, it must be me than i guess..

I don't know what i am doing wrong than because every time when i monitor the EC sensor it appears that I have problems with it... maybe it doesn't like me and trolls me for whatever reason?
lachen.gif
No idea chap.

I stated yesterday 3.9/3466 was evading stability in Y-Cruncher and IBT AVX custom 13312MB. Memtest, x264, RB and [email protected], I had 0 issues, even for reruns. I tried various combos and could not nail it.

So I knew I had tested others on 3.9/3333 Fast but not IBT AVX, so I went back to that profile to test it.



Fail.

Next up SOC.



Pass.

Rerun, fail, Q-Code: 8, lasted ~10min.

rerun_IBT_3.9_3333F.zip 18k .zip file


Bump VCORE from +50mV to +62mV.



Fail. Going to +75mV now.

Like I said before.

Some are not doing valid testing.

Some are pushing CPU / RAM MHz higher than platform can support.
 

Attachments

·
Overclocker
Joined
·
6,943 Posts
Quote:
Originally Posted by gupsterg View Post

No idea chap.

I stated yesterday 3.9/3466 was evading stability in Y-Cruncher and IBT AVX custom 13312MB. Memtest, x264, RB and [email protected], I had 0 issues, even for reruns. I tried various combos and could not nail it.

So I knew I had tested others on 3.9/3333 Fast but not IBT AVX, so I went back to that profile to test it.



Fail.

Next up SOC.



Pass.

Rerun, fail, Q-Code: 8, lasted ~10min.

rerun_IBT_3.9_3333F.zip 18k .zip file


Bump VCORE from +50mV to +62mV.



Fail. Going to +75mV now.

Like I said before.

Some are not doing valid testing.

Some are pushing CPU / RAM MHz higher than platform can support.
Thank you for the info, i will look in to this after i dealt with the pwm motherboard header.
thumb.gif
 

·
Registered
Joined
·
302 Posts
Quote:
Originally Posted by The Stilt View Post

BankGroupSwap is never disabled automatically.
DIMM temperature sensors are read through SMBUS, so any of the DRAM related timings cannot affect it.
I know that on auto its Enabled.
Using your RTC i saw that,long time ago you suggest to use A1 B1 for DR DDR and i test.
Then i saw that RTC read BGS disabled,and for some reason im not able to read Temp with Hwinfo.
Can be a hardware problem?Ram for sure its not faulty,A2 B2 work as they should.
 
24121 - 24140 of 45824 Posts
Top