Overclock.net › Forums › Intel › Intel Motherboards › ASUS North America - ASUS Z170 Motherboards Q&A Thread
New Posts  All Forums:Forum Nav:

ASUS North America - ASUS Z170 Motherboards Q&A Thread - Page 132

post #1311 of 5779
Quote:
Originally Posted by error-id10t View Post

So you think others will avoid me? I enjoy ASUS too and have had them since Z68 days but man I don't push them like you while trying to tramp on new users.

See, I haven't figured you out. Raja get's paid to do this as all he is is a marketing manager. Praz is a mod at the ROG forum but you.. what are you? You were just a user at least in the past, but all your posts indicate otherwise nowadays which is why I'm asking you this.

Flattery will get you everywhere Mr Id10t. Maybe I just like helping others - even if that means correcting those who post their disgruntled experiences as whole grain facts when there is an explanation for most issues
post #1312 of 5779
Quote:
Originally Posted by Silent Scone View Post

How long did you leave the system for to train afterward? When I flashed to 0901 it took a good minute or two for the system to POST. It is early days, and updates to these routines and memory aspects are normally at the focal point of updates.
To what? smile.gif Train? Oops. Must be an error on my side but after the 2nd or 3rd reboot I just powered down and cleared the CMOS. Things worked fine afterwards.

So after the next BIOS update I should let the mobo reboot as many times as it needs to and then all will be fine? What if it never recovers from the boot-loop?

Cheers
post #1313 of 5779
Quote:
Originally Posted by FL00D View Post

To what? smile.gif Train? Oops. Must be an error on my side but after the 2nd or 3rd reboot I just powered down and cleared the CMOS. Things worked fine afterwards.

So after the next BIOS update I should let the mobo reboot as many times as it needs to and then all will be fine? What if it never recovers from the boot-loop?

Cheers

Always leave it to cycle even if unsure post flash. If it's still on the same q-code after several minutes, hold the power for 5 seconds to turn off and then re-attempt
post #1314 of 5779
Sure thing, mate. Will do so after the next BIOS update. Hope I didn't mess up anything by not letting it cycle...

Your help is greatly appreciated.
post #1315 of 5779
Quote:
Originally Posted by FL00D View Post

Sure thing, mate. Will do so after the next BIOS update. Hope I didn't mess up anything by not letting it cycle...

Your help is greatly appreciated.

No problem. If the system is working now then you are fine smile.gif
post #1316 of 5779
Quote:
Originally Posted by Silent Scone View Post

Flattery will get you everywhere Mr Id10t. Maybe I just like helping others - even if that means correcting those who post their disgruntled experiences as whole grain facts when there is an explanation for most issues

What happened to me being ignored..

Not sure how you got flattered by the previous post but ok I guess, I'm not intending to be rude so that's good. So you won't say what your agenda is? If you don't want to say that's fine, Praz didn't comment either. I have a great interest in users who are in the pocket..
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
post #1317 of 5779
Quote:
Originally Posted by error-id10t View Post

What happened to me being ignored..

Not sure how you got flattered by the previous post but ok I guess, I'm not intending to be rude so that's good. So you won't say what your agenda is? If you don't want to say that's fine, Praz didn't comment either. I have a great interest in users who are in the pocket..

lol rather tin-foil, but ok. I don't think I am the one with an agenda here, seeing as this is the second time you've attempted to flatten me - this time with me not-even being the one doing the correcting.

USB BIOS Flashback is by design fairly fool proof in the respect all you need do is add the image to a FAT32 USB dongle, and should be used when flashing back to a previous UEFI. Posting otherwise is misleading. This has nothing to do with having a brand preference or your undeclared love for me. I suggest we continue this entanglement in private, this is the last time I will respond to you here.
post #1318 of 5779
Quote:
Originally Posted by FL00D View Post

Thanks, Praz. You mean memory issue as in faulty modules? I'm asking becaus my modules work fine otherwise. Also tested with HCI.

Hello

My reply regarding a memory issue was based on your post quoted below. Memory rated for 2666MHz should be plug n' play. That you need to increase voltages, especially memory voltage, is indicative of memory optimized for the X99 platform. A two part UEFI update requires that the board partially boots for the second part of the update. Instability at this point can lead to an update failure. If USB BIOS Flashback is needed in the future I would suggest the following:

Boot into the UEFI with a single memory module installed and load optimized defaults. Save, exit and during POST access the boot menu by pressing F8. Once at the boot menu remove power. Reconnect power and perform the USB BIOS Flashback.

Quote:
Originally Posted by FL00D View Post

Hi All,

Is anyone here with 1.2v DDR4 modules experiencing issues with memory handling? There must be something wrong with the way the z170 Deluxe handles 1.2v modules. To start with, every time I update the BIOS I get code 41 and boot loop and I have to clear the CMOS to be able to POST. Also, in order to be able to set XMP (2666MHz CL 15 so nothing funky) I first manually have to overvolt VCCIO, SA and DRAM to 1.1375v, 1.1375v and 1.25 respectively. Once my comp POST'ed at these settings I can then bump back VCCIO, SA and DRAM to 1.0000v, 1.025v and 1.2v respectively and everything runs just fine.

Sometimes just loading a previously working OC profile can result in code 41 and then I have to go through the pain of first overvolting VCCIO, SA and DRAM, wait for the comp to POST and then can set everything back to previously working values. I have no idea why it's like this. I thought memory issues would be ironed out in the next BIOS update... Am currently on 1003.

Thanks
post #1319 of 5779
Right, I would like to clarify the issue I posted about in post #1202 ...About the Z170M-Plus

The Intel 750 SSD fails to be recognized if I turn the ASUS Tuner setting in the BIOS to off, and unlock the BCLK. Even if I leave the BCLK at it's default of 100, and OC using the core ratio, it will still fail to load. What's funny, is that I can OC by forcing the turbo clock up, and OCing the Cache/Memory is also possible without this issue.

It can't be a PCI-E clock issue, as the other two cards work in my system.
post #1320 of 5779
Raja lives? What with the BIOS 1003 (deluxe)? When you improve it?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › ASUS North America - ASUS Z170 Motherboards Q&A Thread