Archived

This topic is now archived and is closed to further replies.

Recommended Posts

In my new build, I'm using OCZ 777-24 but for some reason, it's showing up in CPUZ as 999-24. Any idea why this is. It seems to look that way in the bios as well? ASUS Rampage II and it's up to date.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

In my new build, I'm using OCZ 777-24 but for some reason, it's showing up in CPUZ as 999-24. Any idea why this is. It seems to look that way in the bios as well? ASUS Rampage II and it's up to date.
Go into your BIOS and set up the memory speed and timing correctlyMemory Timing is listed in CPUz if you dont know the cross from what CPUz listed to your BIOS, here it is:CPUz - BIOS - ValueCAS# Latency (CL) - DRAM CAS# LATENCY = 7RAS# to CAS# Delay (tRCD) - DRAM RAS# to CAS# Delay = 7RAS# Precharge (tRP) - DRAM RAS# PRE TIME = 7Cycle Time (tRAS) - DRAM RAS# ACT TIME=24Then set the DRAM speed to the nearest value to 1600 without going overQPI DRAM Voltage = 1.35DRAM Voltage 1.65In a clock you will not run the full 1600 unless you are running a high BCLOCK. The purpose of purchasing the 1600 memory was so you had room to clock. You will most likely end up somewhere between 1540 and 1600 in a clock and that depends on what the top end is on the system for stable clock.

Share this post


Link to post
Share on other sites
Go into your BIOS and set up the memory speed and timing correctlyMemory Timing is listed in CPUz if you dont know the cross from what CPUz listed to your BIOS, here it is:CPUz - BIOS - ValueCAS# Latency (CL) - DRAM CAS# LATENCY = 7RAS# to CAS# Delay (tRCD) - DRAM RAS# to CAS# Delay = 7RAS# Precharge (tRP) - DRAM RAS# PRE TIME = 7Cycle Time (tRAS) - DRAM RAS# ACT TIME=24Then set the DRAM speed to the nearest value to 1600 without going overQPI DRAM Voltage = 1.35DRAM Voltage 1.65In a clock you will not run the full 1600 unless you are running a high BCLOCK. The purpose of purchasing the 1600 memory was so you had room to clock. You will most likely end up somewhere between 1540 and 1600 in a clock and that depends on what the top end is on the system for stable clock.
Is it ok to have it the BCLOCK at 172? It passed the 1 hour test... also, how high should I take the BCLOCK?

Share this post


Link to post
Share on other sites
Go into your BIOS and set up the memory speed and timing correctlyMemory Timing is listed in CPUz if you dont know the cross from what CPUz listed to your BIOS, here it is:CPUz - BIOS - ValueCAS# Latency (CL) - DRAM CAS# LATENCY = 7RAS# to CAS# Delay (tRCD) - DRAM RAS# to CAS# Delay = 7RAS# Precharge (tRP) - DRAM RAS# PRE TIME = 7Cycle Time (tRAS) - DRAM RAS# ACT TIME=24Then set the DRAM speed to the nearest value to 1600 without going overQPI DRAM Voltage = 1.35DRAM Voltage 1.65In a clock you will not run the full 1600 unless you are running a high BCLOCK. The purpose of purchasing the 1600 memory was so you had room to clock. You will most likely end up somewhere between 1540 and 1600 in a clock and that depends on what the top end is on the system for stable clock.
Nick, I did exactly as you said with the timings. They show up correctly in CPU - Z but the memory selction options in DRAM Frequency have not changed. They were and are as follows:103513791724206924132758The only way to get the DRAM freq up to 1600 is by raising BCLOCK to nearly 200 which takes the clock to 4800 MHZ. Is that too high?

Share this post


Link to post
Share on other sites
Nick, I did exactly as you said with the timings. They show up correctly in CPU - Z but the memory selction options in DRAM Frequency have not changed. They were and are as follows:103513791724206924132758The only way to get the DRAM freq up to 1600 is by raising BCLOCK to nearly 200 which takes the clock to 4800 MHZ. Is that too high?
Change your BIOS setting for CPU Ratio to 20. With BCLOCK at 200 this will give you 4GHz. Then you should be able to choose a dram freq at 1600MHz (1604MHz if I remember it correct).Here is an article on i920 that might be helpful http://www.bit-tech.net/hardware/2008/11/0...l-core-i7-920/1

Share this post


Link to post
Share on other sites
Change your BIOS setting for CPU Ratio to 20. With BCLOCK at 200 this will give you 4GHz. Then you should be able to choose a dram freq at 1600MHz (1604MHz if I remember it correct).Here is an article on i920 that might be helpful http://www.bit-tech.net/hardware/2008/11/0...l-core-i7-920/1
Just to give you an update. When I set the QPI DRAM Voltage to 1.35 from AUTO and DRAM Bus Voltage to 1.65 it BSOD's every time with the following MACHINE EXCEPTION ERROR:Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: 9c BCP1: 0000000000000006 BCP2: FFFFFA80062D47A8 BCP3: 00000000BE000000 BCP4: 0000000000300136 OS Version: 6_0_6001 Service Pack: 1_0 Product: 768_1

Share this post


Link to post
Share on other sites
Just to give you an update. When I set the QPI DRAM Voltage to 1.35 from AUTO and DRAM Bus Voltage to 1.65 it BSOD's every time with the following MACHINE EXCEPTION ERROR:Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 1033Additional information about the problem: BCCode: 9c BCP1: 0000000000000006 BCP2: FFFFFA80062D47A8 BCP3: 00000000BE000000 BCP4: 0000000000300136 OS Version: 6_0_6001 Service Pack: 1_0 Product: 768_1
Study that article on OC:ing a 920. Contains detail information on the principle of OC:ing i7s and detailed BIOS setting information.When overclocking a CPU you need to be painfully systematic and thorough.First: Go for overclocking the CPU. Leave the memory at a low freq at this stage. OC:ing is a very time consuming process. When you've reach a stable OC with OCCT-temperatures below 80C, it's time to get the memory to 1600MHz. Second: Memory. You now have to find what multiplier and BCLOCK setting you need to set to maintain the CPU speed and get as close as you can to 1600MHz. Multiplier x BCLOCK = CPU Frequency.Here is NehalemCalc which might help you with the calculations http://www.softpedia.com/get/System/System...halemCalc.shtmlEdited: I got a lot of bluescreens before I reached a stable OC. That's normal procedure when you test what voltages you need to set.

Share this post


Link to post
Share on other sites
Study that article on OC:ing a 920. Contains detail information on the principle of OC:ing i7s and detailed BIOS setting information.When overclocking a CPU you need to be painfully systematic and thorough.First: Go for overclocking the CPU. Leave the memory at a low freq at this stage. OC:ing is a very time consuming process. When you've reach a stable OC with OCCT-temperatures below 80C, it's time to get the memory to 1600MHz. Second: Memory. You now have to find what multiplier and BCLOCK setting you need to set to maintain the CPU speed and get as close as you can to 1600MHz. Multiplier x BCLOCK = CPU Frequency.Here is NehalemCalc which might help you with the calculations http://www.softpedia.com/get/System/System...halemCalc.shtmlEdited: I got a lot of bluescreens before I reached a stable OC. That's normal procedure when you test what voltages you need to set.
It's not working... I set the CPU Ratio at 20 and BCLOCK at 200 and it won't boot no matter what. I even tried changing the numbers so I had 4.1MHZ on the CPU and lowered the memory to 1595 MHZ and it still wont boot. This is completly frustrating and I don't know what else to try. Right now I'm back at 172 BCLOCK and memory speed at about 1370, as I can't get anything else to work. I have the Nehalem calculator but I don't really understand all of it.

Share this post


Link to post
Share on other sites
It's not working... I set the CPU Ratio at 20 and BCLOCK at 200 and it won't boot no matter what. I even tried changing the numbers so I had 4.1MHZ on the CPU and lowered the memory to 1595 MHZ and it still wont boot. This is completly frustrating and I don't know what else to try. Right now I'm back at 172 BCLOCK and memory speed at about 1370, as I can't get anything else to work. I have the Nehalem calculator but I don't really understand all of it.
Obviously you expect an overclock to be a fast and mechanic activity. Change some settings in BIOS and off you go. I'm sorry but it doesn't work that way.Have you read the article about OC:ing the i920 yet?

Share this post


Link to post
Share on other sites
Obviously you expect an overclock to be a fast and mechanic activity. Change some settings in BIOS and off you go. I'm sorry but it doesn't work that way.Have you read the article about OC:ing the i920 yet?
I read the whole thing and what I'm trying to say is that I don't know how far is too far and don't really understand the issue of the voltages.. If I have BCLOCK at 200 and the multiplier at 20 why is it crashing? Is it the voltages? Everything is set to auto because when I raised it as per Nick's instructions, it wouldn't boot that way.

Share this post


Link to post
Share on other sites
I read the whole thing and what I'm trying to say is that I don't know how far is too far and don't really understand the issue of the voltages.. If I have BCLOCK at 200 and the multiplier at 20 why is it crashing? Is it the voltages? Everything is set to auto because when I raised it as per Nick's instructions, it wouldn't boot that way.
You have to be aware of the fact that two i7 965 CPU's don't need to be exactly the same. One might a little more voltage than the other.I'm not familiar with your mobo or your BIOS, which should be a pretty advanced one. OC:ing on my P6T is pretty simple.You have:QPI DRAM Voltage = 1.35DRAM Voltage 1.65What is your CPU Voltage?

Share this post


Link to post
Share on other sites

Wait a minute.. this is a 965?There is NO reason to change BCLOCK. Use the MULTIPLIER then memory speed will be 1600 no matter what CPU speed is setDISABLEIntel SpeedStep Tech DisabledIntel Turbo Mode Tech DisabledCPU Spread Spectrum DisabledPCI Spread Spectrum DisabledC1E Support DisabledIntel Virtualization Tech DisabledCPU TM Function DisabledIntel HT Technology Disabled <--- Hyperthreading (Note: Enabled for video encoding., disabled for coolest temp in clock as FSX has no i7 type HT support)Intel C-State Technology: Disable QPI/DRAM = 1.35v DRAM = 1.65vLOAD LINE CALIBRATION = ENABLEDVcore will be between 1.32 and 1.40v for 4GHz stable operation and you need to make damn sure the temp is less than 80c under a full load testYou must learn about clocking.. it is simple but there are rules to follow and I do not have time to walk people through all sorts of 1-2-3 steps right now, sorry

Share this post


Link to post
Share on other sites
Wait a minute.. this is a 965?There is NO reason to change BCLOCK. Use the MULTIPLIER then memory speed will be 1600 no matter what CPU speed is setDISABLEIntel SpeedStep Tech DisabledIntel Turbo Mode Tech DisabledCPU Spread Spectrum DisabledPCI Spread Spectrum DisabledC1E Support DisabledIntel Virtualization Tech DisabledCPU TM Function DisabledIntel HT Technology Disabled <--- Hyperthreading (Note: Enabled for video encoding., disabled for coolest temp in clock as FSX has no i7 type HT support)Intel C-State Technology: Disable QPI/DRAM = 1.35v DRAM = 1.65vLOAD LINE CALIBRATION = ENABLEDVcore will be between 1.32 and 1.40v for 4GHz stable operation and you need to make damn sure the temp is less than 80c under a full load testYou must learn about clocking.. it is simple but there are rules to follow and I do not have time to walk people through all sorts of 1-2-3 steps right now, sorry
Nick, I did everything you said to the T and did the OCCT test. It made it 35 minutes through the test, then BSOD. Temperatures were fine all the way through. The max was about 65C. I ran another OCCT test and OCCT created an error report that said "Error on Core 2" It didn't BSOD? I ran a third test and it went right to the end until the counter hit -0 and it said (Error Detected on Core#-1) Is there a Core# "minus 1" It didn't blue screen though...

Share this post


Link to post
Share on other sites
Nick, I did everything you said to the T and did the OCCT test. It made it 35 minutes through the test, then BSOD. Temperatures were fine all the way through. The max was about 65C. I ran another OCCT test and OCCT created an error report that said "Error on Core 2" It didn't BSOD? I ran a third test and it went right to the end until the counter hit -0 and it said (Error Detected on Core#-1) Is there a Core# "minus 1" It didn't blue screen though...
Final try at OCCT, it ran for about 20 minutes and had an error on Core 0. The system seems to be stable and running ok.... Do you think this could be an issue with OCCT?

Share this post


Link to post
Share on other sites
Final try at OCCT, it ran for about 20 minutes and had an error on Core 0. The system seems to be stable and running ok.... Do you think this could be an issue with OCCT?
It looks like with all those memory multipliers you showed that you have the 965. So you shouldn't even be raising you Bclock at all. Just use the 133MHz Bclock and DDR3 1600, that's it. Believe me, I have this chip. I've tried quite a few different combinations of Bclock and multiplier and all the higher bclocks were hard to get stable even at 1.40 vcore. That's using OCCT. Finally I settled on the standard 133MHz and 30x mult. Everest 5.00 shows this as one of the better performing settings too.Also you should be aware that on all the current revisions of core i7 chips, 920, 940, and 965, there are manufacturing differences in the Integrated Memory Controller that cause instability at higher bclocks and frequencies. This is according to an article Anandtech wrote a couple months ago. They tested different i7 920 chips, but advised that even the i7 965 can fall flat on it's face past 4GHz and no safe amount of voltage increase seems to help. But you gotta understand all this clocking stuff first. Hope you get it nailed down. DDR3 1600 and 4.0GHz should be attainable and rock solid stable on the 965.-jk

Share this post


Link to post
Share on other sites
It looks like with all those memory multipliers you showed that you have the 965. So you shouldn't even be raising you Bclock at all. Just use the 133MHz Bclock and DDR3 1600, that's it. Believe me, I have this chip. I've tried quite a few different combinations of Bclock and multiplier and all the higher bclocks were hard to get stable even at 1.40 vcore. That's using OCCT. Finally I settled on the standard 133MHz and 30x mult. Everest 5.00 shows this as one of the better performing settings too.Also you should be aware that on all the current revisions of core i7 chips, 920, 940, and 965, there are manufacturing differences in the Integrated Memory Controller that cause instability at higher bclocks and frequencies. This is according to an article Anandtech wrote a couple months ago. They tested different i7 920 chips, but advised that even the i7 965 can fall flat on it's face past 4GHz and no safe amount of voltage increase seems to help. But you gotta understand all this clocking stuff first. Hope you get it nailed down. DDR3 1600 and 4.0GHz should be attainable and rock solid stable on the 965.-jk
I did exactly as you and Nick N said. 133 Bclock with the multiplier to get to 4.00. Adjusted the voltages as outlined above and FSX runs fine, so does windows. Thje problem is is that it either halts the OCCT test or it finishes with an error in one of the cores. I just got the latest revisions of Real Temp and OCCT and I think i'll try it again. The only other thing I guess I can do is start reducing the multiplier.

Share this post


Link to post
Share on other sites
I did exactly as you and Nick N said. 133 Bclock with the multiplier to get to 4.00. Adjusted the voltages as outlined above and FSX runs fine, so does windows. Thje problem is is that it either halts the OCCT test or it finishes with an error in one of the cores. I just got the latest revisions of Real Temp and OCCT and I think i'll try it again. The only other thing I guess I can do is start reducing the multiplier.
OCCT was updated for the i7 but I never got any errors with either version. Nick's the guy you want to talk to to figure this out, he's just super busy with software goodies for us simmers otherwise he'd spend more time, he's spread pretty thin. I have the P6T Deluxe and the 965 and I'm happy to help if I can but I don't know the R2E very well. Let's see what the updated OCCT does.-jk

Share this post


Link to post
Share on other sites
OCCT was updated for the i7 but I never got any errors with either version. Nick's the guy you want to talk to to figure this out, he's just super busy with software goodies for us simmers otherwise he'd spend more time, he's spread pretty thin. I have the P6T Deluxe and the 965 and I'm happy to help if I can but I don't know the R2E very well. Let's see what the updated OCCT does.-jk
Here's another update... Since another test with the newest OCCT v3.0.1 ended in a Core 1 error, again, I reset the bios back to the factory config and the only adjustments I made were setting teh DDR3 to 1600 as well as the memory timing to 77724. I reran the test and it completed sucessfully without any errors over 1 hour. What does this tell us? Is it a voltage setting in the bios?

Share this post


Link to post
Share on other sites
Here's another update... Since another test with the newest OCCT v3.0.1 ended in a Core 1 error, again, I reset the bios back to the factory config and the only adjustments I made were setting teh DDR3 to 1600 as well as the memory timing to 77724. I reran the test and it completed sucessfully without any errors over 1 hour. What does this tell us? Is it a voltage setting in the bios?
I believe that if you tweak a bunch of stuff trying to get stable and it keeps failing then at some point going back and resetting everything is the right thing to do. In fact, reset the CMOS, take out the battery for a few minutes, put it back in, boot up and load BIOS setup defaults, then reboot again and your starting off from a clean slate. Go in and set all the onboard devices and disable all the BS you need to disable for overclocking (turbo, speedstep, vanderpool, etc) and make sure to keep the HW Prefetcher and Adjacent Cache Line Prefetch enabled. Reboot and then start tweaking:This is how it is on my P6T: Set the overclock tuner to XMP profile and disable the two spread spectrums, now reboot. Get back into the bios and make sure the memory shows DDR3 1600, if not set to 1600. Don't mess with the cpu yet. Make sure DRAM voltage is 1.65v (I have to use 1.66v, there is no 1.65) and the QPI is 1.35v. This should automatically be set by the XMP profile. If not then set to 1600 and reboot.Go back into the bios and check the DRAM timing control and make sure you have 7-7-7-24. If not then set it manually and reboot. Finally, set the cpu multiplier to 30x and don't touch the Bclock. Set the vcore to 1.375v. Reboot. Now run OCCT and let's see if it passes. Check temps with Realtemp (i7 realtemp version). You may need 1.40 vcore but 1.375 should do it. I usually run memtest when I first clock my RAM up to speed just to make sure I can boot into windows without corrupting anything. Assuming your RAM's stable then just run OCCT.-jkBy the way, I have that swiftech system too, it's a beauty isn't it? I got mine from Gary at Sidewinder.

Share this post


Link to post
Share on other sites
I believe that if you tweak a bunch of stuff trying to get stable and it keeps failing then at some point going back and resetting everything is the right thing to do. In fact, reset the CMOS, take out the battery for a few minutes, put it back in, boot up and load BIOS setup defaults, then reboot again and your starting off from a clean slate. Go in and set all the onboard devices and disable all the BS you need to disable for overclocking (turbo, speedstep, vanderpool, etc) and make sure to keep the HW Prefetcher and Adjacent Cache Line Prefetch enabled. Reboot and then start tweaking:This is how it is on my P6T: Set the overclock tuner to XMP profile and disable the two spread spectrums, now reboot. Get back into the bios and make sure the memory shows DDR3 1600, if not set to 1600. Don't mess with the cpu yet. Make sure DRAM voltage is 1.65v (I have to use 1.66v, there is no 1.65) and the QPI is 1.35v. This should automatically be set by the XMP profile. If not then set to 1600 and reboot.Go back into the bios and check the DRAM timing control and make sure you have 7-7-7-24. If not then set it manually and reboot. Finally, set the cpu multiplier to 30x and don't touch the Bclock. Set the vcore to 1.375v. Reboot. Now run OCCT and let's see if it passes. Check temps with Realtemp (i7 realtemp version). You may need 1.40 vcore but 1.375 should do it. I usually run memtest when I first clock my RAM up to speed just to make sure I can boot into windows without corrupting anything. Assuming your RAM's stable then just run OCCT.-jkBy the way, I have that swiftech system too, it's a beauty isn't it? I got mine from Gary at Sidewinder.
Can I reset the CMOS by just pushing the button on the back of the Rampage? I think that's what its there for?

Share this post


Link to post
Share on other sites
Can I reset the CMOS by just pushing the button on the back of the Rampage? I think that's what its there for?
You're very right. I just like to take that extra step to stop those gremlins, ya know. :( In your case it's not a bad idea. That CMOS bttn. is mostly a convience in case you lock up and can't restart. For starting completely new and chasing down bugs I like to take that extra step, even though the button is probably effectively doing the same thing.-jkHere's another good source if you haven't discovered it yet:http://support.asus.com/faq/faq.aspx?SLanguage=en-usFind the R2E forums. Read thru and see what people are doing with that board, what bugs they're having, what helps, what doesn't, what BIOS is working best. By the way, How's your BIOS revision? Up to date?

Share this post


Link to post
Share on other sites
You're very right. I just like to take that extra step to stop those gremlins, ya know. :( In your case it's not a bad idea. That CMOS bttn. is mostly a convience in case you lock up and can't restart. For starting completely new and chasing down bugs I like to take that extra step, even though the button is probably effectively doing the same thing.-jkHere's another good source if you haven't discovered it yet:http://support.asus.com/faq/faq.aspx?SLanguage=en-usFind the R2E forums. Read thru and see what people are doing with that board, what bugs they're having, what helps, what doesn't, what BIOS is working best. By the way, How's your BIOS revision? Up to date?
I'm a member on that forum but I don't recall seeing that thread. I'll have to check it out. Bios rev should be up to date although I'll check.

Share this post


Link to post
Share on other sites