Official Seven Forums Overclock Leader boards [2]

Page 39 of 129 FirstFirst ... 29373839404149 ... LastLast

  1. NoN
    Posts : 4,167
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]

    Britton30 said:
    Here's some BSOD codes that may help when overclocking. These were compiled on and other forums, they aren't my findings.

    OC BSOD codes
    0x101 = increase vcore
    0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
    on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
    on i7 32nm SB, usually means too little vCore
    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
    Thanks Britton reminding this BSOD codes list.

    I would like to add one at the bottom of this list aswell, at least for Ivy Bridge.

    "0x7F = Setting the CPU to run at speeds above the rated specification can cause this error, try increase vcore"

    Got also this one "0xF4 (Critical object termination)" but do not know if its entirely due to overclocking. Could be power related failure of a connector.
      My Computer

  2. Posts : 24,479
    Windows 7 Ultimate X64 SP1

    Edited post.
      My Computer

  3. Posts : 3,118
    Win7 Home Premium x64 SP1

    crankypenguin said:
    Oh boy, I was too late, because I just did this I am done with OC for tonight. It's almost 2am and I want to catch a movie.

    CPU-Z Validator 4.0
    Great work on the oc Cranky, Good job mate
      My Computer

  4. Posts : 6,075
    Windows 7 Professional 64 bit
    Thread Starter

    Updated Cranky

      My Computer

  5. Posts : 13,576
    Windows 10 Pro x64

    A New Track Record

    And another New Track Record
    Last edited by AddRAM; 22 Apr 2015 at 17:51.
      My Computer

  6. Posts : 539
    Windows 7 Ultimate 64bit

    nice oc's AddRAM...
      My Computer

  7. Posts : 7,466
    Windows 10 Home Premium 64bit sp1

    Nice oc but damn that is a lot of juice
      My Computer

  8. Posts : 54,522
    Windows 10 Home x64

    You broke the 5GHz barrier Let's not break anything else

    A Guy
      My Computer

  9. Posts : 21,007
    Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10

    Ok looks like I ought to try it am running an i5 3570K at stock on an Asus P8Z77-V board I have the RAM set at 2400 so where do I go in the EUFI BIOS to ramp the CPU up say to 4GHz? (It's turboed at 3.7 now)
      My Computer

  10. Posts : 13,576
    Windows 10 Pro x64

    Ya I`m back to 4.2
      My Computer

Page 39 of 129 FirstFirst ... 29373839404149 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:05.
Find Us