Bigbruin.com
Home :: Reviews & Articles ::
Forum :: Info :: :: Facebook :: Youtube :: RSS Feed
Search  :: Register :: Log in
View Single Post  Topic: Q6600 overclock details. 
Author Message
NoOne
Rated PG


PostPosted: Mon, 07 Jan 2008 20:42:04    Post Subject: Reply with quote

Ello my computer specs are:

Q6600 3.0ghz G0 | Running on Air
Asus P5W DH Deluxe | Zalman 9700
2x G.Skill 2(2x1)GB DDR2-800 | XFX 8800 GT 256mb
Raid-0 2x Seagate 80gb | Seagate 500gb | Maxtor 250gb
Silverstone DA750 | Dell 17" 1703FP | Thermaltake Armor

I've been able to run 4 instances of prime 95 fine for 7 hrs using 3x Long FFTs and 1x blend but when I play WoW it crashes the computer. It blacks out and I can't figure out why.

Temperatures hover around 69-70 during the first 6 hrs of the test, around 3pm 6-7th hour the 2 core temps hit 71-72, might be due to room temp. Temps did drop down to 65, 63, 61, 61 when prime95 was minimized to system tray.

AI Overclocking [Manual]
Cpu Frequency [333]
Dram Frequency [DDR2-834mhz]
Performance Mode [Auto]
PCI Express Frequency [100]
PCI Clock Synch Mode [33.33mhz]
Memory Voltage [2.00v]
Cpu VCore Voltage [1.3625v]
FSB Termination Voltage [Auto]
MCH Chipset Voltage [Auto]
ICH Chipset Voltage [Auto]
-------------------------------------------
Modify Ratio Support [Enabled]
Ratio CMOS Setting [9]
Microcode Updation [Enabled]
Max CPUID Value Limit [Disabled]
Execute Disable Function [Enabled]
Enhnaced C1 Control [Enabled]
CPU Internal Thermal Control [Auto[
Virtualization Technology [Disabled]
Speed Step [Enabled]
-------------------------------------------
Configure DRAM Timing by SPD [Disabled]
DRAM CAS# Latency [4]
DRAM RCAS# Precharge [4]
DRAM RCAS# to CAS# Delay [4]
DRAM RCAS# Activate to Preca [12]
DRAM Write Recovery Time [4]
DRAM ECC Mode [Disabled]
Hyper Path 3 [Disabled]
DRAM Throttling Threshold [Disabled]
Bott Graphic Adapter Priority [PCI Express/PCI]
PEG Buffer Length [Auto]
Link Legacy [Auto]
Reg Root Control [Auto]
Peg Link Mode [Auto]
Slot Power [Auto]
-----------------------------------------------

Nvm, i dropped the Dram Frequency to 667mhz and WoW hasn't crashed the comp yet. Disabled C1E, and Speedstep. I'll repost if anything comes up.

Update: So wow crashed the comp so I loosened the timings to 5-5-5-15. I'll repost if anything comes up.

Any Suggestions on how to add the aggressive timings back, or any specific changes I should make?

Would I notice much difference between 4-4-4-12 timing and 5-5-5-15 timing?

Also a few other comments I had were: from what I gather for the G0 stepping it seems like I'm using a lot more voltage to achieve my fsb.

At default values, instead of 2.4ghz its 2.13ghz.

Lastly if prime95 receives a windows unexpected error and not a prime95 error, is it the same issue? And should I increase the VCore to make it stable? Because I've been pushing the Vcore whenever that occurs.

From a stable 321x9, 642 mhz, at 1.3Vs, I pushed it to 333x9, 667mhz through a few zones of BSODs to Windows Prime95 unexpected Errors till it stabilized at 1.3625v.

Just ran 4 instances of prime95 for 12hrs and it came up error free, but when I ran 3dmark06 it blackout like WoW a few seconds in and had to hardboot. It crashed me as I was typing this sentence too. Maybe it has to do with my graphics?
View user's profile Send private message

Contact Us :: On Facebook :: On Youtube :: Newsletter :: RSS Feed :: FAQ :: Links :: Sponsors :: Privacy Policy
Copyright © 2000 - 2023 Bigbruin.com - All rights reserved