Results 1 to 4 of 4
  1. #1
    ROG Guru: White Belt Array orcinus PC Specs
    orcinus PC Specs
    MotherboardRampage V Extreme 3504
    Processori7-5960X @ 4.585GHz strap 125, BCLK 131
    Memory (part number)F4-2800C16Q-32GRR@13-13-13-33-CR1-BCLK 131,
    Graphics Card #1TITAN Xp
    Graphics Card #2TITAN Xp
    Sound CardAsus Xonar Essence STX
    MonitorDell UP2715K
    Storage #1SM 960 Pro 2TB RADI1
    Storage #2SM 960 Pro 2TB RAID1
    CPU CoolerEKWB custom 2x480mm + 1x560mm
    CaseCaseLabs Magnum STH10
    Power SupplyCorsair AX1500i
    Keyboard Logitech G710+
    Mouse Logitech G900
    Headset Sennheiser PXC550
    OS Windows 10 Enterprise 64 1701
    Network RouterAsus AC88U

    Join Date
    Oct 2014
    Reputation
    10
    Posts
    106

    "MEMORY MANAGEMENT" blue screen on SA 1.05V and otherwise stock

    So, today I've just set my system to stock and turned XMP on as usual - default values used except for SA voltage to 1.05V since otherwise it is not really stable in sleep.

    Some time into desktop usage (no load almost) the machine just blued out on me with MEMORY MANAGEMENT error. After that each consecutive boot produced unexpected screen tearing. I've reset my BIOS to defaults (back button) but tearing was still there. Ultimately I've turned my monitor off DisplayPort 1.2 to 1.1 and started the machine again - everything worked fine.

    Now, I'm not sure if that has anything to do with DP 1.2 or me turning the screen off and back on, or why would such an exception or change do any kind of tearing to the screen. My video cards seem fine, they're brand new and worked for a month now without an issue never being overclocked or abused in any way. Few boots before this occurrence worked fine as well.

    I'm using an LG 34UC97 3440x1440 and dual GIGABYTE G1 GTX 970. Latest Nvidia official driver and Windows 8.1 updated (for some time now so no error should pop up at that side).

  2. #2
    Tech Marketing Manager HQ Array Raja@ASUS's Avatar
    Join Date
    Apr 2011
    Reputation
    161
    Posts
    7,454

    The issue could be memory or GPU driver/monitor related.

    If the memory XMP is over DDR4-2133 then technically the system is running an overclock. As with all overlcocking, the voltage required and the ability to be stable with vary from CPU to CPU.

  3. #3
    ROG Guru: White Belt Array orcinus PC Specs
    orcinus PC Specs
    MotherboardRampage V Extreme 3504
    Processori7-5960X @ 4.585GHz strap 125, BCLK 131
    Memory (part number)F4-2800C16Q-32GRR@13-13-13-33-CR1-BCLK 131,
    Graphics Card #1TITAN Xp
    Graphics Card #2TITAN Xp
    Sound CardAsus Xonar Essence STX
    MonitorDell UP2715K
    Storage #1SM 960 Pro 2TB RADI1
    Storage #2SM 960 Pro 2TB RAID1
    CPU CoolerEKWB custom 2x480mm + 1x560mm
    CaseCaseLabs Magnum STH10
    Power SupplyCorsair AX1500i
    Keyboard Logitech G710+
    Mouse Logitech G900
    Headset Sennheiser PXC550
    OS Windows 10 Enterprise 64 1701
    Network RouterAsus AC88U

    Join Date
    Oct 2014
    Reputation
    10
    Posts
    106

    Quote Originally Posted by Raja@ASUS View Post
    The issue could be memory or GPU driver/monitor related.

    If the memory XMP is over DDR4-2133 then technically the system is running an overclock. As with all overlcocking, the voltage required and the ability to be stable with vary from CPU to CPU.
    This happened on a system that worked just fine at 4,7GHz and 4,9GHz overclock, memory at 1T and such. After full reset and new overclock (XMP3000) everything is back just fine. This episode is - strange.

  4. #4
    ROG Enthusiast Array funky29cro PC Specs
    funky29cro PC Specs
    MotherboardAsus Rampage V Extreme
    ProcessorIntel I7 5930k
    Memory (part number)Kingston HX Predator 4x4gb 3000mhz HX430C15PB2K4/16
    Graphics Card #1Asus HD7970-DC2-3GD5
    Sound CardAsus Xonar DGX
    MonitorLG 24GM77-B
    Storage #1Samsung 840 Pro 512gb
    Storage #2WD 1TB Blue
    CPU CoolerCorsair H100i Push&Pull
    CaseThermaltake Urban S71 Window
    Power SupplySeasonic Platinum 1000w SS-1000XP
    Keyboard Logitech G110
    Mouse Logitech Proteus Core G502
    OS Windows 7 Enterprise Sp1 x64
    Network RouterZTE ZXDSL 931 on fiber

    Join Date
    Aug 2013
    Reputation
    10
    Posts
    38

    I would suggest go manual on memory , it seems that your cpu does not like high system memory voltage as it was described in haswel e oc manual writen by rog experts here . Some cpu can handle memory with low sys agent other with high ,set manual where u would turn xpm ,give memory 130% power and extreme optimization ,1.360-1.370 voltage on main page , on timings set your correct timings and on eventual memory voltage 1.350v for both chanels ,now set sys agent in offset mode + and start adding 0.010v evey time until it boots and ,when it boots stress test if it fails ad again 0.010v and so on u get it good luck .

Posting Permissions

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