Search:

Type: Posts; User: GoatHumper

Page 1 of 2 1 2

Search: Search took 0.00 seconds.

  1. A few points: the timings are already relaxed and...

    A few points: the timings are already relaxed and the voltages are already high (1.1v for VCCSA, 1.37v for DRAM, etc... the DRAM says it's meant to work with 1.35 so I'm reluctant to go much higher...
  2. Well... first off: it happens regardless of...

    Well... first off: it happens regardless of whether I wake it up via keyboard, mouse, or power button.

    Second, the reason I use suspend is precisely so I don't have to wait "too long" to get the...
  3. Ok so I had another episode, and I've identified...

    Ok so I had another episode, and I've identified the PCI-E slot that's blinking: it's #4 (PCIE_X8_4), and it has an NVME drive on it. Perhaps the PCIE bus needs a voltage boost? I already have a...
  4. After a few relapses, I've noticed that the LED...

    After a few relapses, I've noticed that the LED display shows "E1" which according to the manual corresponds to "S3 Boot Script execution" ... I wonder if there's a means for debugging what...
  5. I just did. It's been less stable these past...

    I just did. It's been less stable these past couple of days that I've messed with the voltages than before where I had just set Rampage Tweak to Mode 1.

    We'll see how this pans out. If not, I'll...
  6. Do you have similar "safe ranges" for me? :D ...

    Do you have similar "safe ranges" for me? :D

    I've set 1.35v for the DRAM, and that should be OK, but haven't touched the VCCSA yet - I'm thinking 1.1v would be my max (currently at ~0.8v)...
    ...
  7. I've upped the voltage to 1.35v. I had decided to...

    I've upped the voltage to 1.35v. I had decided to start lower because the manufacturer's specifications for the kit call for 1.2v. Ironically, I had the issue again this morning even after upping the...
  8. You lost me here... are you suggesting that using...

    You lost me here... are you suggesting that using motherboard defaults with no overclocking, and changing a single (apparently) "well-documented" value that fixes similar issues on other systems is...
  9. I might have spoken too soon. This morning it...

    I might have spoken too soon. This morning it happened again. I'll try upping the voltages as Arne suggested, and see where that gets me.

    Cheers!
  10. At this point I'm all but positive that the issue...

    At this point I'm all but positive that the issue is fixed. I'm glad I was able to find this fix - I had all but given up hope.

    Cheers, all!
  11. Well, the kit I have is QVL'd by the manufacturer...

    Well, the kit I have is QVL'd by the manufacturer against the mainboard. There's no "fine print" regarding which CPUs support which memory configurations anywhere on the Mainboard's marketing...
  12. Fair enough. But when one doesn't wish to have...

    Fair enough. But when one doesn't wish to have *any* oveclocking done, why would features such as this one try to do it automatically, in this case obviously leading to instability?

    Shouldn't...
  13. From the manual... So...there you go :)

    From the manual...



    So...there you go :)
  14. After today's use, with multiple suspend-resume...

    After today's use, with multiple suspend-resume cycles which usually resulted in one or two instances of the dreaded glitch, my confidence grows by the hour that this is indeed the cure to the...
  15. I'm letting the MB do as much automatically as...

    I'm letting the MB do as much automatically as possible - probably 1.35V since I think that's what the DRAM kit's XMP profile specifies. I'll keep you posted as I'm sure others will be interested in...
  16. Thanks!!! I found it, and set it to "Mode 1" -...

    Thanks!!! I found it, and set it to "Mode 1" - we'll see what effect it has.



    The kit is a QVL'd kit (G.Skill F4-2133C15Q2-64GRB, QVL'd as per G.Skill, see...
  17. Thanks, Arne!! But that's the thing - I'm not...

    Thanks, Arne!! But that's the thing - I'm not overclocking *AT ALL* - at least knowingly. DRAM is at its stock speed (2133MHz), CPU is at its stock speeds (3700MHz, 5930K), etc...

    So... yeah......
  18. Sorry to bump an old thread, but I'm having the...

    Sorry to bump an old thread, but I'm having the same issue and it's quite infuriating. I have the same "problem" as mwe3302 - I can't find a "Rampage Tweak" option anywhere in the BIOS - let alone an...
  19. Thanks!! As I said above, I can get everything...

    Thanks!! As I said above, I can get everything signed and running using the MOK from the installation if I import the key into the UEFI key DB. However, I'd just as soon avoid that since that's not...
  20. Forgot to mention: I'm on BIOS 3801. Cheers!

    Forgot to mention: I'm on BIOS 3801. Cheers!
  21. Rampage V Extreme can't enroll MOK in UEFI using Linux (Ubuntu Bionic)

    Hi!

    I've recently opted for enabling secure boot on all my computers, and success came easy with all of them save my primary (the R5E). In that box, I kept getting blocked by a failure to enroll...
  22. Replies
    10
    Views
    1,715

    This may be a defect that was fixed in a BIOS...

    This may be a defect that was fixed in a BIOS version (as of 3501, all subsequent BIOS versions are stable). My system would shut down without warning, and with no correlation to component...
  23. Replies
    62
    Views
    32,776

    I have more info on my issue related to 3504. ...

    I have more info on my issue related to 3504.

    The problem appears to be related to the M.2 SSD port. I had an SSD running there that, in order for it to run cooler and not thermo-throttle, I...
  24. Replies
    62
    Views
    32,776

    I have more info on my issue related to 3504. ...

    I have more info on my issue related to 3504.

    The problem appears to be related to the M.2 SSD port. I had an SSD running there that, in order for it to run cooler and not thermo-throttle, I...
  25. Replies
    62
    Views
    32,776

    Actually, rolling back to 3501 didn't solve...

    Actually, rolling back to 3501 didn't solve anything. When waking from sleep, Ethernet now doesn't come up (it did before I tried 3504)...perhaps a firmware update somewhere as part of the BIOS...
Results 1 to 25 of 45
Page 1 of 2 1 2