Page 2 of 2 FirstFirst
1
2
  1. #21
    I am Murloc! Fuzzykins's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    South Korea
    Posts
    5,222
    Quote Originally Posted by Saithes View Post
    Nah I doubt it actually pushes 1.6v... most likely reading your DRAM Voltage for your VCore.
    HWM says Max Vcore is 1.63v. .-.

  2. #22
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Fuzzykins View Post
    HWM says Max Vcore is 1.63v. .-.

    Well, I guess in a month we'll know for sure if its at 1.63 lol
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  3. #23
    I am Murloc! Fuzzykins's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    South Korea
    Posts
    5,222
    Quote Originally Posted by Saithes View Post
    Well, I guess in a month we'll know for sure if its at 1.63 lol
    Hopefully in a month I'll have my new motherboard. I'm sending an angry letter to Intel. D:

  4. #24
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Fuzzykins View Post
    Hopefully in a month I'll have my new motherboard. I'm sending an angry letter to Intel. D:
    Didn't HWInfo32 report 1.2v? I know on a lot of B3 Boards both HWMonitor and CPU-Z report the DRAM or VTT Voltages for the VCore so the only way to get the right VCore is using HWInfo32.
    Last edited by Saithes; 2011-04-09 at 07:13 PM.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  5. #25
    I am Murloc! Fuzzykins's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    South Korea
    Posts
    5,222
    Quote Originally Posted by Saithes View Post
    Didn't HWInfo32 report 1.2v? I know on B3 Boards both HWMonitor and CPU-Z report the DRAM or VTT Voltages for the VCore.
    Lemme check.
    AH! 1.224. Phew. Had to fire up Prime95 though, my turbo wouldn't kick in. Damn you Firefox and giving my computer nothing to do.

  6. #26
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Fuzzykins View Post
    Lemme check.
    AH! 1.224. Phew. Had to fire up Prime95 though, my turbo wouldn't kick in. Damn you Firefox and giving my computer nothing to do.
    Yeah, I'd go by that... lol CPU-Z, HWMonitor, etc are most likely reporting your DRAM Voltage for the CPU VCore.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  7. #27
    Quote Originally Posted by Saithes View Post
    Nah I doubt it actually pushes 1.6v... most likely reading your DRAM Voltage for your VCore.




    4.6/1.32v 55-57°C load Haha.. Some CPU's react differently to voltage as well as different ambients
    Personal question Saithes. How stable is your overclock? Im currently not messing around with the BClock, but it looks like you eaked me out with it. 50x100 is pretty stable, running 90 degrees farenheit ambient and 120-130 under load (Cooler is corsair 2x120mm fans+copper heat piped aluminum heatsink).

    Notice is do say "PRETTY" stable. It BSOD's about every other day. I looked up the BSOD code and it said it was directly attributed to the VCORE. Either that or the memory. Memory tests show it is stable, and when i upgraded my BIOS to the 15xx series and turned on internal PLL overvoltage it increased system stability but I still get a BSOD every so often. ITS REALLY ANNOYING. I have maxxed out the VCORE on my bios at 1.54 with Ultra High. So its running around 1.55-1.56 on CPUZ. Cant remember all of my BIOS settings, but at this point im attributing it to either my processor not being one of the lucky few that can OC this far, or to early BIOS versions not being as stable.

    If yours is stable do you mind writing down or screen shotting your bios settings? Thanks in advance for any help you give.

  8. #28
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Elgand View Post
    Personal question Saithes. How stable is your overclock? Im currently not messing around with the BClock, but it looks like you eaked me out with it. 50x100 is pretty stable, running 90 degrees farenheit ambient and 120-130 under load (Cooler is corsair 2x120mm fans+copper heat piped aluminum heatsink).

    Notice is do say "PRETTY" stable. It BSOD's about every other day. I looked up the BSOD code and it said it was directly attributed to the VCORE. Either that or the memory. Memory tests show it is stable, and when i upgraded my BIOS to the 15xx series and turned on internal PLL overvoltage it increased system stability but I still get a BSOD every so often. ITS REALLY ANNOYING. I have maxxed out the VCORE on my bios at 1.54 with Ultra High. So its running around 1.55-1.56 on CPUZ. Cant remember all of my BIOS settings, but at this point im attributing it to either my processor not being one of the lucky few that can OC this far, or to early BIOS versions not being as stable.

    If yours is stable do you mind writing down or screen shotting your bios settings? Thanks in advance for any help you give.

    Here's a list of general BSOD codes that occur when overclocking sandybridge and what action to take.

    0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi
    0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)
    0X00000101 << Not enough Vcore Voltage
    0X00000109 << Not enough or too Much memory voltage

    Ai Overclock Tuner: Manual
    BCLK/PEG Frequency: 104.5
    Turbo Ratio: By All Cores
    By All Cores: 49
    Internal PLL Overvoltage: Enabled
    Memory Frequency: DDR3 1950MHz
    EPU Power Saving Mode: Disabled

    CPU Power Management:
    Long Duration Power Limit: 250
    Long Duration Maintained: 32
    Short Duration Power Limit: 250
    Aditional Turbo Voltage: 0.135
    Primary Plane Current Limit: 300

    Load-line Calibration: Auto
    VRM Frequency: Auto
    Phase Control: Extreme
    Duty Control: Extreme
    CPU Current Capability: 100%

    CPU Voltage: Offset Mode
    Offset Mode Sign: +
    CPU Offset Voltage: 0.125
    Spread Spectrum: Disabled
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  9. #29
    The Lightbringer Asera's Avatar
    15+ Year Old Account
    Join Date
    Aug 2008
    Location
    This side of an imaginary line in the sand
    Posts
    3,741
    Quote Originally Posted by Saithes View Post
    Didn't HWInfo32 report 1.2v? I know on a lot of B3 Boards both HWMonitor and CPU-Z report the DRAM or VTT Voltages for the VCore so the only way to get the right VCore is using HWInfo32.
    Hmm... HWInfo reports a 1.3761 vcore for me. @_@
    red panda red panda red panda!

  10. #30
    I. Love. You.

    Incorrect QPI/VTT is the code I have been given over and over. So when i get home im gonna have some fun bios alone time 8). Its dirty i know, but god these processors deserve it.

    Btw do you have qpi/vtt set to auto as well?
    Last edited by Elgand; 2011-04-09 at 07:38 PM.

  11. #31
    The Lightbringer Asera's Avatar
    15+ Year Old Account
    Join Date
    Aug 2008
    Location
    This side of an imaginary line in the sand
    Posts
    3,741
    Here's a list of general BSOD codes that occur when overclocking sandybridge and what action to take.

    0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi
    0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)
    0X00000101 << Not enough Vcore Voltage
    0X00000109 << Not enough or too Much memory voltage
    Random question, where can you get similar information for P55 systems and AMD systems?
    red panda red panda red panda!

  12. #32
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Asera View Post
    Hmm... HWInfo reports a 1.3761 vcore for me. @_@
    Most likely from Load Line Calibration... Try turning it down a level.

    Quote Originally Posted by Asera View Post
    Random question, where can you get similar information for P55 systems and AMD systems?
    Those are from http://www.overclock.net, but I'll see if I can dig some AMD/P55 ones up.

    Quote Originally Posted by Elgand View Post
    I. Love. You.

    Incorrect QPI/VTT is the code I have been given over and over. So when i get home im gonna have some fun bios alone time 8). Its dirty i know, but god these processors deserve it.

    Btw do you have qpi/vtt set to auto as well?
    Yep, my QPI/VTT is on auto. Normally on DDR3 2133 or 2400 people have to raise the VTT to 1.10625 or 1.12v to get the frequency stable. I'd also try to knock back your VCore since 1.5 is a bit high for 24/7 usage, but then again no one knows the maximum safe voltage for Sandybridge yet =P
    Last edited by Saithes; 2011-04-09 at 07:46 PM.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  13. #33
    The Lightbringer Asera's Avatar
    15+ Year Old Account
    Join Date
    Aug 2008
    Location
    This side of an imaginary line in the sand
    Posts
    3,741
    Most likely from Load Line Calibration... Try turning it down a level.
    Uhm... I only have two options for LLC. Vdroop high or low and that's it. lol. 1.3761v is within specs for the CPU though, so it won't kill it. I'll have to wait until I replace this board with a Z68 board later.

    Those are from http://www.overclock.net, but I'll see if I can dig some AMD/P55 ones up.
    Ah thanks... I can't stand their forums. ><
    red panda red panda red panda!

  14. #34
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Asera View Post
    Uhm... I only have two options for LLC. Vdroop high or low and that's it. lol. 1.3761v is within specs for the CPU though, so it won't kill it. I'll have to wait until I replace this board with a Z68 board later.
    Lol Why a Z68? =P It's just going to be a P67 with ondie GPU Support.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  15. #35
    The Lightbringer Asera's Avatar
    15+ Year Old Account
    Join Date
    Aug 2008
    Location
    This side of an imaginary line in the sand
    Posts
    3,741
    Quote Originally Posted by Saithes View Post
    Lol Why a Z68? =P It's just going to be a P67 with ondie GPU Support.
    I want quicksync. P:
    red panda red panda red panda!

  16. #36
    Moderator Cilraaz's Avatar
    15+ Year Old Account
    Join Date
    Feb 2009
    Location
    PA, USA
    Posts
    10,139
    Quote Originally Posted by Saithes View Post
    Here's a list of general BSOD codes that occur when overclocking sandybridge and what action to take.

    0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi
    0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)
    0X00000101 << Not enough Vcore Voltage
    0X00000109 << Not enough or too Much memory voltage
    0x124 is actually usually vCore, though occasionally VTT/QPI/VCCIO.
    0x9c is the one that's usually primarily VTT/QPI/VCCIO

    Quote Originally Posted by Asera View Post
    Linpack for me at 4.6/1.345v is like... 85 celcius. xD

    P95 blend is about the same. Weird cause my cooler isn't nearly as good as yours.
    I just ran a 5 pass of IBT with the new linpack. I hit 81°C on core #2, 80°C on cores #1 and #3, and 72°C on core #0. I think my absolute max during a 13 hour Prime blend was 74°C. Ambient is 21°C.
    Last edited by Cilraaz; 2011-04-09 at 08:45 PM.

  17. #37
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Quote Originally Posted by Cilraaz View Post
    0x124 is actually usually vCore, though occasionally VTT/QPI/VCCIO.
    0x9c is the one that's usually primarily VTT/QPI/VCCIO
    Lol Not from what 10-20 threads on OCN and TPU have shown in the last week alone =P On LGA 1156 and 1366 0x124 was more vcore, but with Sandybridge it is typically QPI/VTT.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

  18. #38
    Moderator Cilraaz's Avatar
    15+ Year Old Account
    Join Date
    Feb 2009
    Location
    PA, USA
    Posts
    10,139
    Quote Originally Posted by Saithes View Post
    Lol Not from what 10-20 threads on OCN and TPU have shown in the last week alone =P On LGA 1156 and 1366 0x124 was more vcore, but with Sandybridge it is typically QPI/VTT.
    Odd, considering OCN is where I've been reading what I said, but whatever. 0x124 was also a cry for more vCore during my overclock.

  19. #39
    Herald of the Titans Saithes's Avatar
    10+ Year Old Account
    Join Date
    Feb 2011
    Location
    Mun
    Posts
    2,719
    Here's another list for everyone:

    http://www.overclock.net/intel-cpus/...code-list.html

    Quote Originally Posted by HaMMeR=GoM=
    BSOD codes for overclocking
    BSOD Codes for i7 x58 chipset
    0x101 = increase vcore
    0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
    0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
    0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
    0x1E = increase vcore
    0x3B = increase vcore
    0x3D = increase vcore
    0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
    0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
    0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
    0x109 = Not enough or too Much memory voltage
    0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
    0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

    BSOD Codes for SandyBridge
    0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
    0x101 = add more vcore
    0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
    0x1E = add more vcore
    0x3B = add more vcore
    0xD1 = add QPI/VTT voltage
    “0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
    0X109 = add DDR3 voltage
    0x0A = add QPI/VTT voltage
    Cilraaz, we'll just agree that its equally either Since that's the consensus.
    Last edited by Saithes; 2011-04-10 at 07:56 AM.
    Intel Core i7 5820K @ 4.2GHz | Asus X99 Deluxe Motherboard | 16GB Crucial DDR4 2133 | MSI GTX 980 4G GAMING | Corsair HX750 Gold | 500GB Samsung 840 EVO

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •