Search the Community
Showing results for tags 'quirks'.
Found 1 result
I've recently purchased Sager's new P9872-S laptop with Intel i7-6700K unlocked CPU and a single nVidia 1070 XMX GPU. Let me say that overall I absolutely LOVE this new machine, but I've discovered some strange hardware/BIOS type quirks that I'd like to discuss here. Note: I don't see a version displayed in my BIOS, but HWINFO lists a BIOS date of 10/19/16. The CPU is unlocked and supports overclocking. The stock BIOS also has a section for CPU overclocking. My CPU is quite happy running a moderate 4.5GHz OC across all cores with a 70mV undervolt (offset mode.) Yes it'll do the same clock at stock voltage but I've found that many Skylake CPU's do not need such high voltage as Intel has programmed them for - and my temps run much lower with the undervolt. So I set the undervolt with Intel XTU (I've also tried doing the same with Sager's own utility) and it runs beautifully until I reboot the system. At POST, BIOS then seems to reject the undervolt, forces a power-cycle, and sets CPU PL1 and PL2 power specs to very low "safe" levels. It also changes the negative voltage offset to a positive 70mV, indicating that it's trying to "error correct" the negative value. BIOS itself specifies a valid range of -500 to +500mV for the voltage offset here, and I can change it directly within the BIOS (and then it DOES actually stick through future reboots) but the BIOS does not allow me to enter a negative value here! Instead of -500 to +500, the actual values it allows for entry are 0 to +1000! And no, +500 does not actually equal zero, tried that and it really is +500. Also of note, I can change any multipliers in XTU or Sager's utility without the BIOS objecting but *any change* to the voltage offset gets rejected at reboot - even +1mV. Even applying +1mV and then immediately applying 0mV in either utility gets rejected on the next reboot so it's as if some checksums or something are not calculated the same way by XTU as they are by BIOS, causing a rejection of *any* voltage offset modification made by a utility rather than BIOS itself. Initially I set all my CPU core multipliers to 45x and all was good. Soon I noticed that any time I put the computer to sleep or hibernate, it would limit core speed to a maximum 42x after recovering, despite still reporting 45x as the CPU maximum. I tinkered with it for a while and eventually tried different values. Now I have ONE CORE multi set to 46x and TWO, THREE, and FOUR CORE multi set to the original 45x. That shouldn’t make a lick of difference versus 45x across the board but it does! 46, 45, 45, 45 sticks properly through sleep and hibernate; Weird right? I’m fine with the current settings as an effective workaround but I feel it’s still worth noting here. The VSYNC seems "lazy." I know this may be a driver or settings issue, rather than true hardware quirk, but it really bothers me - and the same behavior exists with nVidia drivers 368.xx to 373.06. Take Dirt Rally for example; I want it to run with VSYNC ON at 1080p, 90Hz. If I turn VSYNC OFF, my average framerate is about 200Hz, and never falls below about 110Hz, but with VSYNC ON it keeps dipping momentarily below 90Hz and skips frames! In a fast-motion racing game this is very distracting! I've observed this same behavior with the internal LCD and with my AOC 144Hz gaming monitor connected via DisplayPort. With VSYNC OFF, even with framerate limiter set at or just above my refresh rate, the game looks terrible so this is not an acceptable workaround either. Yes, the reported refresh rate is on target without VSYNC but there's terrible tearing and stutter. I've never experienced this kind of VSYNC dysfunction before; any thoughts? I have the 1920x1080 120Hz LCD screen. I wanted to set a couple custom refresh rates in nVidia Control Panel for racing games that really stress the system at 120Hz but I still want more than 60Hz. If the LCD starts out set at 60Hz and I test a custom resolution of 1920x1080 at, say, 90Hz, the screen goes kaput until it reverts back to 60Hz. However, if the screen starts out set at 120Hz I can then create any custom refresh rate in between 60 and 120Hz that I want. I wouldn't bother trying to fix this one as there's a perfectly functional workaround - it's just weird to me that starting frequency matters. Any thoughts on these quirks are welcome, and I’d be happy to try/test any good suggestion or curiosity you might have. Especially getting a negative CPU voltage offset to stick permanently, as well as any thoughts on the VSYNC laziness would be greatly appreciated. Thanks everyone!