Recommended Posts

I've done several decent ones in my time:

1st: AMD Opteron 165 from 1.8Ghz to 2.8Ghz using DFI Lanparty UT NF4 Ultra-D & 2GB OCZ Platinum DDR400 RAM

2nd: Current spec, E6600 from 2.4Ghz to 3.5Ghz. Specs in signature.

CPU-z, ignore the voltage in CPU-z, its wrong, look at the voltage at the top of the screen on ASUS PC Probe II.

Benchmarks for E6600:

SiSoftware Sandra Lite XI : 25525 in Arithmetic

Orthos stable for 5 hours+

1M SuperPi: 15 seconds

overclock35ws5.jpg

sisoftko1.jpg

pi1milionti4.jpg

Thanks,

Garnett

  • 2 weeks later...

Well I know them Core 2s are all the rage in recent times, but I've got an overclocked Prescott running happily in my machine.

I pushed it as high as 121% (or 3.4ghz) but it wasn't precisely stable at that. Also I'm on air cooling and my paste is not so great.

So I run it at 3.2ghz, a modest 114.2% clock. I've got my RAM clocked just under typical DDR rates with a 1.6 multplier.

No fancy-shmancy screenshots to hand out. Oh well!

  • 3 weeks later...
  • 2 weeks later...

Core 2 Duo E6320 @ 3.01GHz (up from 1.86GHz). Temps: 40-44 degrees idle and 60 degrees load on both Tjunction and Tcase. Vcore: 1.44V.

Mobo: Gigabyte GA-P35-DS4. 430x7. Temps: 40-44 degrees idle, 50 degrees load.

RAM: 2x1gb GeIL Ultra PC2-6400 @ 430MHz, 4-4-4-12.

GC: 8800 GTS 640MB. 650MHz core (up from 500Mhz), 950Mhz memory (up from 800Mhz). Temps: 65 degrees idle, and I'm not sure about load temperature.

Stock cooling (yes, I will buy something better) and a lot of case fans.

Edited by kronix2

Intel Core 2 Duo E6300 @ 3.36GHz (480*7, 1920MHz QDR) on Scythe Infinity+Resistor @ 900rpm (Asus P5K-Deluxe)

Idle 47, Load 58 (Noctua NF-S12-800 back, Noctua NF-S12-1200 ULNA @ 600rpm front) - Seasonic M12 in Thermaltake Aguila. 1.3750V, ~1.3V vdroop - Orthos stable.

Here's my current setup, this is with my 2GB OCZ Platinum RAM:

http://valid.x86-secret.com/show_oc?id=210290

With my previous 1GB OCZ Performance RAM, I was able to OC the CPU to 2.7GHz Stable, of course with different mem clock, FSB, and HTT.

I can't get back to 2.7GHz with the 2GB kit, not sure why yet, don't have the time to attempt again

  • 2 weeks later...

Unlike most people here with Core 2 Duo's, I'll be yet another outcast with an AMD :p

My AMD Opteron 165 (stock 1.8ghz) is currently running at 2.57ghz on stock 1.35v vcore with a Tuniq Tower 120.

I think the temps are good because compared to stock speed, the load temp increased by just 2 degrees celsius.

idle temp: 39C

load temp: 51C with two instances of Prime95 running for 2 hours.

I'll run a 24h test the next day I'm working and if it remains stable, I'll push it a bit more. There's no rush :cool:

Here are some more overclocks that I have tested stable for my system (All 8+ hours dual orthos stable):

Intel Core 2 Duo E6600 L638F615 on a Zalman CNPS9700LED @ 2300rpm

@ 3.0GHz (9 x 333 1.300V)

@ 3.2GHz (9 x 356 1.375V)

@ 3.3GHz (9 x 367 1.425V)

Asus P5N32-E SLI Plus Motherboard - Bios 0801

2 x 1GB Corsair XMS2 PC6400 TWIN2X2048-6400 @ 400MHz 4-4-4-12 2T 1.9V

PNY nVidia GeForce 8800GTS 320MB @ 675/1026 on stock cooling

Edited by 12Iceman

New one :)

Intel Core 2 Duo E6600 L638F615 on a Zalman CNPS9700LED @ 2300rpm

@ 3.4GHz (8 x 425 1.4625V)

I just had to top the 3.36GHz that chconline got with only an E4300 and his beloved P5K Deluxe.

Edited by 12Iceman
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers like me was eager to get. And that main feature that developers will love it`s the ability to connect to LOCAL AI models running on Ollama. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!