$1,350 Core i7 build

[Cham]

Originally Posted by Envy

She's up and running, OC'd @ 4.02 ghz easily without breaking a sweat. I also got her a new sound card.

Did you name her too?

[ice]

Did you have to up any voltages?

[Envy]

Originally Posted by ice

Did you have to up any voltages?

CPU is running at 1.35 instead of 1.25. That's about it.

[Girryn]

What card?

I tried out an auzentech forte but it amplified the noise in my system too much so I went back to mobo audio. Anyone know how to fix the noise that occurs whenever you move a window or scroll through anything? Hell pretty much any movement on screen caused it, all I could come up with is something is making the PCIe bus very noisy.

[Cham]

Originally Posted by Girryn

What card?

I tried out an auzentech forte but it amplified the noise in my system too much so I went back to mobo audio. Anyone know how to fix the noise that occurs whenever you move a window or scroll through anything? Hell pretty much any movement on screen caused it, all I could come up with is something is making the PCIe bus very noisy.

Sounds like a possible grounding issue?

[Girryn]

All the info I ever found on ground loop issues had something to do with a receiver or external device, all I have plugged in is headphones and a mic

[Cham]

Originally Posted by Girryn

All the info I ever found on ground loop issues had something to do with a receiver or external device, all I have plugged in is headphones and a mic

Is your motherboard grounded properly?

[Girryn]

Not sure how to check for that and my poor googlefu leads me to topics troubleshooting failures to post because of bad grounding, my system runs fine other than the background noise that is responsive to onscreen movement. The noise is very low key and unnoticeable most of the time with the onboard sound.

[Envy]

So I woke up this morning and found that it had blue screened. Not sure if that was an OC issue or not. I'm not sure if I have the memory timings/voltage/ratios right, so that's probably what did it.

Where the fuck is Bard when I have questions? Jeez.

[ice]

If it were an issue with your CPU voltage/clock you'd more than likely fail to boot and instead just cycle continuously.

So yes, I'm guessing your RAM needs some more power to operate smoothly at whatever frequency you're overclocked to. Don't play with the timings unless your motherboard is trying to default to them something other than what the packaging says. If it's still causing problems though you can probably try to set the timings 1-2 higher in each value though and see if that helps.

The weak link of almost every system I've every tried to overlock has been the RAM =(

[Envy]

http://vip.asus.com/forum/view.aspx?...Language=en-us

This looks like a nice little guide. Gonna give that a whirl.

[Roor]

Are you using a temp monitoring software, these chips are notorious for running hot.

[Bard]

What are your temps, how stable are your v rails, what is the frequency of the ram, is the ram heatspreader too hot to put your finger on for long? It sounds like a cpu issue to me, but I would run a memtest32 boot disk to check the memory (you should always do this to make sure your memory isn't fucked when you get it).

.1 volts is sizable jump for a cpu. A lot of times you can fix a temperature issue and keep the same OC at a lower voltage. Otherwise I would settle for 3.9ghz at a much more manageable voltage (like 1.3 or less hopefully).

If your vcore fluctuates a lot this could also be the source of the problem. If this is the case you're never going to max out on your OC. Your choices in this case would be to return the mobo for a different brand (even though that's the best choice of mobo imo), or settle for a lower overclock with a lower voltage.

read:
http://www.xtremesystems.org/forums/...d.php?t=210480

There is some good information in there, but it's not all laid out....you kind of have to read between the lines of the conversation going on. It sounds to me like after 4ghz is where a lot of people start seeing stability issues on air.

The first thing I would do is find the OC that I can run stable at 1.29v. Then I would take in all the information I could, fix any heat issues, change any bios settings that needed to be tweaked, and push the proc a little more; while going no higher than 1.3v. Not saying you have to do this, it's just what I would do.

Also, from what i've read about the onboard memory controllers from intel, it probably would not be a great idea to up the memory voltage.

[Bard]

Just found this in that thread I posted:

"You guys that are running 4ghz, try using multiplier of 19 x 210, and you can probably drop your vcore down about .05 - .1.

I dont know if its just me, but it takes me around 1.375vcore to run 200x20 stable, but 1.275 to run 211x19 stable. LinX 20 loop stable, with 12 gigs takes about 30 mins a run."

[Envy]

Awesome, will do.

[Envy]

Working like a Champ.

Also, Windows 7 is pretty good shit. I have to say I like it quite a bit so far. I haven't found anything that's pissed me off (yet).

[Cham]

How does it compare with Vista? (Assuming that you've been running Vista).

[Envy]

So I haven't run any real benchmarks yet, but here's what I'm getting:

High Detail in WoW @ 1920 x 1080 res (i think?)

34-120 FPS in Dalaran. Depends on how bad it is. 34 Was super prime time crowded around the wintergrasp queue dude.

Normal questing out in the world = 180ish FPS.

Instances = 200-300 FPS.

Arenas = 300ish FPS.

Opening up a second full-windowed wow client on the other monitor doesn't seem to slow down the frame rate at all, either.

[Envy]

Windows 7 is more responsive than Vista. You'll know what i mean if you've used vista. There's often times that little circle mouse icon thingy when just doing stuff like navigating web pages, enabling options, or whatever.


Windows 7 there's really no hesitation. You click an option and it's done. You open a window and it opens. You log in and there's your desktop. No loading times, really.


I'm also using less resources to run Windows 7. In vista 64, just booting into windows would set me back 2 gigs of ram. In windows 7, I've got about 5.1GB/6GB free.

They still have that User access control shit enabled by default, but you can just disable it by running msconfig > tools and disabling it in there.

[Cham]

That's good to hear. I haven't bothered with Vista because of all the problems I kept hearing about.