Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: MP-Ryan on January 17, 2015, 05:13:51 pm
-
Ryan: You know, this thing is long out of warranty and I've been pondering an upgrade anyway. I know these Core 2 Duo E8400s were overclocking superstars... why not?
Computer: Oh really? Can I have some popcorn? You tried this...
Ryan: Shush you. Boot to BIOS.
Computer: Are you really sure you want to do...
Ryan: MIB. There we are. OK, you run stock at 3.0 Ghz, let's try a modest bump to 3.2 Ghz.
Computer: I think you're forgetting...
Ryan: Shut up and save settings. Let's do this. Reboot.
Computer: Rebooted. Nope, I dislike this. Rebooting back to the old settings. Not going to say why though.
Ryan: Passive aggressive machine. *Googles E8400 OC settings* Hrmm, did I use a host freq you didn't like? Everything I'm finding says you should do 3.4-6 no problem.
Computer: I'm old, remember?
Ryan: Yes, and crotchety. OK, this setting seems to be reliably reported as not an issue even with a stock cooler, and you've got an upgraded one. This should put you at 3.4ish.
Computer: You're an asshole.
Ryan: You're a aluminum box and I don't care what you think.
Computer: You're forgetting something.
Ryan: I am not. This should work fine.
Computer: Remember 2008?
Ryan: *saves*
Computer: Remember why you're not buying Gigabyte motherboards anymore?
Ryan: ...
Computer: Faulty temperature sensor.
Ryan: Oh SHI.....
Computer: And now I'm going to report one of your processor cores at 98°C...
Ryan: ....TTTTTTTTTTTTTTTTTTTTTTTTTTT!!!!!!!!!!!!!!!!!!!!!!!
Computer: You know how your kids are napping?
*BEEEEEEEEEEEEEEEEEEEEEEEEEEEEP!
Computer (30 seconds of obnoxious alarm later): How's that going for you now?
Ryan: 3.0 Ghz is fine I guess.
Computer: I thought so.
-
There are days I feel like the most self-hating thing humanity has ever accomplished is the personal computer.
-
Isn't there a setting to disable or ignore the temp sensor alarms? Been forever since i played with a Gigabyte board but i seem to recall something like that. Not really sure though.
-
There are days I feel like the most self-hating thing humanity has ever accomplished is the personal computer.
"THIS SHOULD WORK!" -> things I scream at my department's laptops on a regular, if not daily, basis.
This really was my fault, though. I should have remember that temperature sensor was wonky and wouldn't let me OC.
Isn't there a setting to disable or ignore the temp sensor alarms? Been forever since i played with a Gigabyte board but i seem to recall something like that. Not really sure though.
There is. Or I can crank the alarm so high that it will never go into an alarm state. However... if the HS fan unit ever does die or have a problem, that's a good way to set my house on fire.
Reading a little further, it seems I may have to manually set the PCI frequency to hold at 100 to bump this, but frankly I can't be bothered at this point. A 200 or 400 mHz bump isn't likely to make much of a difference in overall performance in modern games anyway.
-
"THIS SHOULD WORK!" -> things I scream at my department's laptops on a regular, if not daily, basis.
Until I overwrote the firmware with DD-WRT my relationship with my Linksys EA2700 router was similar. My favourite was when it compelled me to end up shouting "I HAVE AN MCSA! WHY CAN'T I EVER CONNECT ANYTHING TO WIFI! EVEN IDIOTS CAN DO THAT!"
The problem was that the firmware was pretty **** to start with. Every once in a while it would decide to turn WiFi access off to half of the devices using it and only a reboot would cure that. But it was about to get a lot worse.
One day out of the blue it decided to update its firmware. It didn't ask. First I knew of it was when suddenly all my network addresses became 10.*.*.* when they used to be 192.168.*.*
Logging into the router I found the firmware had been replaced with Cisco's idiotic cloud-based system. Now as far as I'm concerned, the idea of having the firmware you need to access the Internet stored on the Internet is about as stupid an idea as trying to fly by pulling hard on your shoelaces, but Cisco had gone the extra mile by deciding that it was their business to control what I did with my router now.
Apparently they really didn't like the idea of me tainting the innocence of their router with films of naked ladies. (http://arstechnica.com/information-technology/2012/07/freeing-your-router-from-ciscos-anti-porn-pro-copyright-cloud-service/)
Reinstalling the old firmware was a pain in the arse cause even with the old firmware it had decided it liked its new IP address. It had moved in all its furniture and hung the pictures where it liked them and it would be damned if it was going back to 192.168 again. It took 5 reboots and the threat of being taken outside for a curbstomping to persuade it that 10.*.*.* was a dangerous neighbourhood, that it should look at all its lovely port LED lights and that it would be a shame if someone were to come along with a hammer and break them.
In the end though I had to install DD-WRT. There's only so much of having a router that thinks WiFi is a privilege that only my girlfriend's iPad should be entitled to that one man can take.
-
This is an entertaining thread :)
-
This is an entertaining thread :)
Aim to please ;)
Out of curiosity, I tried again at 3.2 this morning with the PCI frequency set to hold at 100. Still no dice. System boots, tries to do it's memory test, then says nada and reboots back to previous settings. I'm actually wondering if its a RAM issue rather than temperature problems at the lower OC. The RAM in this system has run on manual timings with an OC via overvoltage (which the RAM is specced for) and I'm thinking it doesn't like being adjusted back to a lower speed by the auto settings, which are recommended when performing an OC on this motherboard.
I mentioned it in passing in my original post, but I have been thoroughly unimpressed with this Gigabyte motherboard - Gigabyte's RAID controller was sketchy from day 1 (as in, mysterious disappearing disks from the RAID array, necessitating a switch to the Intel controller), the CPU temperature sensor misbehaves somewhat regularly, and the BIOS settings have never been terribly intuitive. I've had Asus boards before and always liked them, and I've heard good things about MSI, but it seems I'm not the only one whose feelings on Gigabyte are mixed.
EDIT: Sonofa.... further reading suggests that this motherboard doesn't like to OC when you have a more modern GPU in the PCIE slot. My GPU supports PCIE 3; the mobo was designed for PCIE. Bah, back to "can't be arsed to figure this out" mode.
-
I like ASUS and MSI too, would shoot for MSI at this time I think but research would be needed ofc. And of course perhaps Gigabyte got its act together, would research that too. It's been way too long since I've fiddled with hardware for purposes other than a quick fix / upgrade for a family/friend member.
-
My ASRock has been absolutely fantastic for overclocking. It's got my 2600k at 4.6 with a nice, convienent auto-overclock bios setting. Could probably do 4.8 which is the highest in the auto setting with no problem, but I don't see the need to. Might do it one day just for giggles and compare benchmarks.
Also, my previous two systems with Abit boards were really solid overclockers. My first system ever was a mobile AMD processor dropped in a abit NF7-S board and overclocked something like 80%. High end performance on the cheap!
-
Was that with liquid cooling? If not, i wonder how high you could get it with that!!.. :eek:
-
No, that's just a hyper 212+. $20. I had some overclock with the stock cooler, but I don't remember how high. I didn't try to find the limit though.