Jump to content
HWBOT Community Forums

Queen_Fiona

Members
  • Posts

    4
  • Joined

  • Last visited

About Queen_Fiona

  • Birthday 04/30/1990

Converted

  • Location
    Canada

Queen_Fiona's Achievements

Newbie

Newbie (1/14)

10

Reputation

  1. I tried keeping the Turbo power limits both at 240 and the TDC limit to 200, no joy. Sources have said pushing all three of these values to 300 (or higher!) might help. I could try increasing the voltage a bit, but my understanding is that it wouldn't help with this unusual problem; either it doesn't reach the multiplier due to current/power limits, it boots and has the multiplier but isn't stable, or it doesn't boot at all. Plus, Intel's 'brilliant' automatic settings for voltage overheated my chip at even modest clocks, so there's that. I mentioned I already enabled PLL override; I didn't disable it after testing, because of the very issue you just mentioned. I hope to push at least a couple of ticks out, since I seem to secretly have a good chip that stays stable and relatively cool at 4.4 without needing to touch the volts! (Admittedly, I have a half-decent cooler, but still.) ...also, I can't view your attachment due to my account privileges.
  2. After years of not overclocking due to issues with my previous motherboard, I'm currently clocking at 4.4 GHz on stock voltage consistently. This is pretty good, but I want to do better. Problem is, though I've raised the multiplier to 45, the processor will only reach 4.4. I mean, it's not the usual voltage issue, as it boots just fine as far as I can tell. The appropriate utilities show that the max multiplier is indeed set at 45, but running benchmark tests shows that it isn't surpassing 4.4 (and even fluctuates between 4.39 and 4.35). I had a similar problem before I got around by increasing my Turbo Boost Power Max and Short Power Max several times. However, it's set at 240 watts and that hasn't done anything over the 220 it was at the first time I pushed the multiplier to 45. I set the TDC Current Limit to 165, which didn't help either, nor did the Internal PLL Voltage Override. I'm sort of worried about pushing past this, because I don't know what's safe and what's chip-frying, or where any of the limits are. My board is a D77GA-70K, for the record, for a baseline in BIOS terminology. 4.4 is a pretty comfortable space to occupy, but Dark Souls III is a hungry beast indeed...
  3. Keyboard isn't really something I expected to be solved here. I might have something I can drag out if I find it, but that keyboard always had problems due to wireless reception issues and only worked sporadically on my last mobo for BIOS. That's not really relevant - in-OS adjustment will always be a hell of a lot more convenient. Also, as indicated, I tried several versions. v5.2.0.14 was one of them. I tried the latest v6.1.2.13, v6.0.2.8, and v4.2.0.8 (marked as SB compatible) as well, most of them from the version library. They all installed fine as an application and the benchmarks (and power limits, for some reason?) and everything work alright, it's just the drivers that would allow me to OC that seem to be the issue. In fact, there seemed to be little difference at all between the four versions, so it's probably just the driver installation problem. I did find a thread about a similar driver issue in the v6 series, but it was marked as fixed in the latest version (or close to it). Nothing seemed to help much. I've pulled 4.4 GHz out of stock voltage so far, which is encouraging me to go further!
  4. For whatever reason, my current keyboard will only work to enter the BIOS on a fresh boot...and only some of the time. If I reboot to enter the BIOS, I can't press any keys and therefore can't, making any kind of overclocking extremely inconvenient. Naturally, I want to install Intel XTU. I used it on my previous machine (actually just a different motherboard), and it worked fairly well, but it's completely failing me now. My current configuration is an i7-2600K, installed in a D77GA-70K, running Windows 10 Pro. This is one of Intel's own boards, from their Extreme product line, so it seems strange that XTU would have issues here. I attempted to install the latest version, without success. I could change the power limits, but nothing else. I tried manually installing the drivers in the folder, which changed nothing. I tried installing multiple older versions from your library and manually poking at their drivers, none of which worked - even the ones specifically marked as compatible with Sandy Bridge. The only clue I have is the error message given when I try to install the driver I believe is the culprit: iocbios2.sys, or the "IntelĀ® Overclocking Device Driver". Every other driver or prerequisite seems to install okay, even if I have to force it, but that one fails every time. Using the in-folder installer and the INF both say they succeed even though they don't. My last resort, which was trying to add the OC driver manually to Device Manager results in this cryptic error, which appears to be some sort of stock fallback that's been in NT-based Windows for ages: "The installation failed because a function driver was not specified." This is clear as mud, and Google wasn't much help - it seems to cover for all kinds of issues that don't seem to have much with the error itself. I hope this is enough information! If anyone has any ideas what might be happening, let me know.
×
×
  • Create New...