|
Post by cjgdsgrc50 on Jun 25, 2016 8:18:47 GMT -5
Hoping someone can help. I have an Asrock Z170 OC Formula with an I3 6100. On bios 2.03 right now but also tried 1.92. I have loaded all the drivers including Intel ME. Using win7 64 bit right now. I installed Asrock Timing Configurator and I can change the values in it but they are not applying as I have checked in cpuz. Any help would be appreciated.
|
|
|
Post by Macsbeach98 on Jun 25, 2016 17:06:16 GMT -5
Do these bios's allow base clocking of the I3 6100? If so try one that doesnt I would say thats your problem.
The I3 6100 I have got sucks to which a few people report the same thing. I wish I had of coughed up the extra dollars for the I3 6320
|
|
|
Post by cjgdsgrc50 on Jun 25, 2016 21:14:14 GMT -5
Thanks Pete. I think you are right but now i have a 04 post code and i cant get it to post even into the bios no matter what i try and i dont have any extra ddr4 or 1151 cpu to swap parts to see what it actually is. This sucks and my dice pot is coming this week haha.
|
|
|
Post by ozz on Jun 25, 2016 21:29:45 GMT -5
|
|
|
Post by Macsbeach98 on Jun 26, 2016 5:19:48 GMT -5
First try 1 stick at a time in different slots and see if it will post it only takes a small spot of debris to stop making one Memory contact making contact. If that doesnt fix pull the CPU and check all the socket pins for alignment. After that you will probably need another CPU to test further.
One other thing pull the battery over night to give it a long CMOS clear.
|
|
|
Post by mrpaco on Jun 26, 2016 7:39:42 GMT -5
Try like Pete suggested, also remove n re-seat any Video card(s) you have in. I had it happen many times if the GPU not seated right board wont post. You may wana also just for certainty, check all the connections to/from all your connected devices.
|
|
|
Post by cjgdsgrc50 on Jun 26, 2016 10:57:52 GMT -5
Thanks guys. I have tried everyones suggestions. No go. I will rma the ram. The board os outside of 30 days so if it ends up being that i will have to send right to Asrock. This will be the first time i have every rma'd anything.
|
|
|
Post by ShrimpBrime on Jun 26, 2016 12:55:09 GMT -5
I run my OC Formula at 12-14-14-36 2T at 1400mhz daily. Loose as a goose.
For the timing configurator, I cannot help. Never tried using it....
|
|
|
Post by cjgdsgrc50 on Jun 26, 2016 17:06:57 GMT -5
I had it running 32m at 13-15-15-28 1t, 48 49 6 6 rtl/iol at 3200mhz then tried changing rtl manually and thats when the 04 happend. Cant wait to get it going again.
|
|
|
Post by Macsbeach98 on Jun 26, 2016 17:39:20 GMT -5
Is that the best you could get out of the ram chris? Are they 4 Gig sticks sounds like D Die I have to buy a set of B Die soon I want this 12-12-12 @3866 or 4000
One last question what voltage were you giving the ram?
|
|
|
Post by cjgdsgrc50 on Jun 26, 2016 18:02:36 GMT -5
They are 4GB sticks cheap Patriot 3200mhz cas16. I got to that point without raising volts yet. Dont know how far they would have went haha. Hopefully once rma'd we will see.
|
|
|
Post by cjgdsgrc50 on Jun 26, 2016 18:03:38 GMT -5
It was at 1.35 volts
|
|
|
Post by Macsbeach98 on Jun 26, 2016 18:27:19 GMT -5
Its surprising they would of died then but anything can happen and usually does.
|
|
|
Post by georgekokovinis on Jun 29, 2016 17:36:26 GMT -5
It is a HUGE mistake to try and adjust memory timings in Windows. Unlike cpu adjustments, memory adjustments in the windows environment can and will instantly kill the IMC. Memory adjustments MUST ALWAYS be done in the bios.
AsRock Timing Configurator or Asus MemTweakit, are read only, despite stating otherwise. What has happened is the IMC is damaged. Not recoverable.
By the way, there is no way to damage ram sticks with 1.35V I have 5 sets of G.Skill B-die 3600 / 16-16-36 and can run them for hours and hours at 3866 / 12-12-12-28-1T with very tight seconds and thirds with 1.86V without any issue. I have two sets running on the M-OCF at 4000 / 12-11-11-28-1T at 1.95V. No issues. Cpu's used are I7-6700K, I5-6600K and I3-6320.
Best bios for the OC Formula is 2.10.
Good luck, but there is permanent damage done.
|
|
|
Post by cjgdsgrc50 on Jun 29, 2016 19:49:40 GMT -5
I figured that George from how it happened. I knew it want voltage as I see people running 1.8 on air. I didnt think it could happen like that from reading so much about how Splave and them guys adjust their rtls and all. Once i replace the cpu I will flash 2.10 and start at it again. Lesson learned. I will let the rtls/iol adjust themselves based off of cas,twcl and what not. Thanks
|
|
|
Post by georgekokovinis on Jun 29, 2016 20:19:10 GMT -5
If I may elaborate a bit further.
There is no issue with fixed RTL/IOL settings. Thing is that by changing them on the fly will most certainly harm the IMC, unless the cpu is under cold with volts to spare. What I mean - VccIO and VccSA AND VCPLL are directly connected with mem settings. If the IMC is protected from thermal spikes being under cold AND has reserves of voltages to overcome on the fly adjustments, it might be OK. When all this is done in the bios, the whole system goes thru recalibration upon reboot and if something is not correct it stalls and drops an error. Usually sticks at 55 or 4c. MRC must always be enabled in mem settings in bios so it retrains each and every time it reboots.
In general, the best idea and most secure is to spend some time in bios settings and not try to experiment with either Timing configurator or memtweakit. Personally I find these applications useless AND dangerous. I do not even adjust Vcore in Windows. Not mem settings.
Just my 0.02 cents
|
|
|
Post by cjgdsgrc50 on Jun 29, 2016 20:33:20 GMT -5
All the settings were done in the bios. I never was able to get timing configurator to change settings in windows. VccIO was at 1.2v and VccSA at 1.35. Vdimm was 1.35. CPU at about around -20c and mem had fans blowing on it. I had been steadily adjusting first and second timings down and letting mem train all night. Then I changed RTL's from 49/50 to 48/49 and thats when after F10 save and restart the board went right to Post code 04 and nothing would change that. But a damaged IMC is the only thing that kind of makes sense. I will get a G4400 just to change out cpu to see.
|
|
|
Post by georgekokovinis on Dec 14, 2016 20:34:41 GMT -5
I am very interested to revive this old thread and find out what happened. Reading your last post, I noticed something truly outrageous. 1.20 VccIO 1.35 VccSA
My friend, ARE YOU NUTS ?
The OCF and the M-OCF are notorious for overvolting EVERYTHING. These settings are used for 2x8GB of B-die mems running at 4000 / 12-11-11-28-1T / 6-4-220trfc-6-10 Read to precharge and write / 6-1 / TCKE 6, TCLW 9.
With 1.90V Dimm ++, and IMC under REAL COLD.
Your system will never boot - NEVER.
After resetting C-mos and supposing that no damage has occurred ( almost impossible ), with the mems you have you must go down to 1.10VccIO and 1.15VccSA in order to boot.
Dude, These boards are dangerous and not made for Patriott's 3200. They are made for business. Of course you can use them as nay normal board, but NOT with these settings.
DISASTER.
BTW, code 4 = early pre-initialization, which means that the mem controller can't even read SPD of mem sticks. 55 = Very bad. No memory installed.
Good luck, but better ask next time, before applying voltages.
These boards, as well as Asus Impact and M8E are PURE MACHINE GUNS, if treated correctly
If not, something dies in seconds. BE CAREFUL !
|
|
|
Post by blaylock on Dec 23, 2016 7:48:06 GMT -5
I can confirm for you that the ASRock Timing Configurator will not allow you to change settings on the fly and should only be used as a read only tool as George mentioned. I have the ASRock Z97 OCF and had the same issues. BIOS changes are always a safer and more stable way of working anyhow.
|
|
|
Post by Bones on Dec 23, 2016 13:02:58 GMT -5
I can't speak for the other versions of the software or boards used but it does work with my Z77 OCF at least.
I too have noted these proggys normally don't work right or at all so tweaking the BIOS is still the way to go with it.
|
|
|
Post by HW Team on Jul 8, 2018 3:42:57 GMT -5
|
|