Jump to content

CalvinHobbesN7

Member
  • Posts

    26
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About CalvinHobbesN7

  • Birthday Jun 26, 1991

Profile Information

  • Gender
    Male
  • Location
    Colorado Springs
  • Interests
    Photography, Video Production, Gaming
  • Occupation
    Systems Administrator

System

  • CPU
    Intel i7-8700K
  • Motherboard
    Asus Z370-E ROG
  • RAM
    G.SKILL 2x16GB DDR4-4000 (F4-4000C19D-32GTZSW)
  • GPU
    EVGA GTX 1080 Ti FTW3
  • Case
    Core P5
  • Storage
    2x Samsung 970 EVO (1TB & 500GB)
  • PSU
    EVGA Supernova 850
  • Display(s)
    Samsung UH750
  • Cooling
    EKWB Custom loop (CPU Monoblock & GPU)
  • Operating System
    Windows 10 Pro

Recent Profile Visitors

330 profile views
  1. I'd say just kill it. If you've got an old one you don't care about then just make it a good-looking accessory.
  2. Even the smallest of things like a poor riser-cable can be affected by ram frequency. it's certainly been a learning experience!
  3. Aesthetics, since I'm using an RGB EKWB block to cool things down, and since Linus didn't have a problem using them to extend out to over 3.0 meters either (granted I'm using a far less superior one, I've since ordered a premium one used on his video at 30cm).
  4. I just hit the 5GHz Profile button, OR I've also simply changed to sync all cores to the 1-core limit ratio of 50.
  5. Fun story - I actually got both XMP and manual overclocking to function. The weird thing is I had to remove my GPU to do it. I created a new forum post regarding this new-found knowledge. Short version: I think it may be the riser cable I'm using, and others feel it may be a voltage problem. I think the two solutions (increasing voltage + better riser cable) are connected. Thank you for your input here!
  6. What is BLCK? I never intentionally altered/set this, I'm unsure if XMP did though - and I experience this problem with both manual DRAM changes and XMP profile application.
  7. Alright, this is a real headscratcher. I could really use an expert on this one. If you read my previous post, you'll know that I was having a very difficult time overclocking my RAM, both via XMP and by manually entering the DRAM timing, voltage and frequency settings. No matter what, my system would not OC the DDR4-3200 RAM past 2533. It failed POST every time. Some System Information: MB: Asus STRIX Z370-E CPU: Intel i7-8700K GPU: EVGA 1080 Ti FTW3 w/ 200mm Thermaltake Riser (more on that below) RAM: F4-3200C16Q-32GTZSW (Listed on the MB QVL) It turns out that RAM wasn't failing the POST test, it was the GPU. I have four POST lights for CPU, DRAM, VGA, and BOOT. The VGA light remained illuminated and would not turn off. According to the manual, that means it hasn't completed the test for that portion yet. I removed my EVGA GTX 1080 Ti FTW3 from the mix, applied the XMP for my 3200MHz RAM, and - to my shock and awe - it booted right up without a hitch. In fact it's currently running right now. I re-connected my 1080 Ti, and it failed POST. I reset the MB DRAM memory settings to their defaults, and it booted right up - 1080 Ti and all. NOW - BEFORE YOU TELL ME MY GPU IS BROKEN: You should know that this 1080 Ti has been performing remarkably under "normal" un-overclocked (and slight OC) RAM speeds between 2133 and 2533. My highest OC score in SuperPosition Benchmark with this same card via the baseline MB BIOS config is 23586. Now the real question: Why on earth is overclocking the RAM causing the GPU to fail during POST testing? The only possible explanation I can think of in my relatively little experience is that I'm using a shitty PCIe Riser cable. I currently have one in the mail to arrive on Saturday. But this... seems a little unlikely to me. If YOU know what's going on, then PLEASE. TELL THE WORLD. But most importantly, tell me below because this mystery seems unsolvable.
  8. What should I look for? See if individual sticks can make the 3200 speed? Also - you recommend trying each slot, and not just the MB recommended slot for running a single stick? That's 16 tests...
  9. I think that's interesting - I'm only using a single kit that contains 4x ram sticks so I'm not personally combining any kits together. Just using what G.Skill sold me. I'll get in touch with G.Skill to begin the RMA process, sounds like a pain in the ass.
  10. Do we know it's the RAM? Or could it be the processor (I've been successful at 5GHz OC)? Or could it be the motherboard? How do I know where the problem lies?
  11. I would RMA this RAM except that it passed the Memtest86 without a single error. That's... really surprising to hear and I wasn't aware of this. The default BIOS settings are even lower at 2133 or something. I can't get anything to work higher than 2533. Period. I took it up one notch at a time until it failed - 2600 is the first failure.
  12. Greetings, kind people of the internet! Everywhere I go, everything I watch, it seems that enabling XMP is a fast, stable, and easy way to get RAM running at its rated speed. Unfortunately enabling the default XMP profile causes the system to become unstable. Things to get out of the way: I carefully chose the RAM for my build from the official motherboard's QVL. The UEFI BIOS has been updated to the newest release, currently 0616. I can manually OC the ram to 16-18-38, 1.353V, and 2533MHz for a stable boot - but this is the maximum I've been able to achieve for a stable boot. I have manually attempted a 17-19-39, 1.36V, and 3200MHz boot, but this was also unsuccessful. In order to restart the system after raising the bar, I have to flip the PSU physically off, wait 10-15 sec, then boot - pressing F2/Del will open up the dialogue stating that a previous bios change may have caused instability. I have successfully run memtest86 at 16-18-38, 1.353V, 2533MHz, without any errors. SEPARATELY: I have successfully overclocked this processor to 5GHz and it is quite stable. Before attempting XMP or any ram changes, the BIOS is reset to default and there is no CPU overclock applied during my tests. Relevant system hardware MB: Asus STRIX Z370-E CPU: Intel i7-8700K RAM: F4-3200C16Q-32GTZSW Any information, tips, or thoughts on what the issue might be are most welcome. Thank you! -CalvinHobbesN7
  13. We tied on posting! I updated my previous post, and just wrote about how I was opting for 32gb of ram instead of 64gb (via a 8gb x 4 setup) I know what you mean about optimization. However I remember exactly what PS was using for ram for that image - it was 58GB of ram according to the Activity Monitor (was an Apple workstation, please don't shoot me! I've repented of this sin). That was very rare - I mean it was the first time hitting that ceiling and I doubt I've hit it since then. Thanks again for all your help, advice and willingness to share your knowledge! -CalvinHobbesN7
  14. XXX You know, I'm going to double-check on that by opening several of my largest files and watching what happens. XXX I do know I've hit the 64gb roof before with a single file - though that was a unique client job. I was never disappointed that my previous rig had it, that's for sure. XXX What are your thoughts on buying a 2x16 set, and buying a second of the exact same set later down the road if necessary? Stable OC? Potential issues? Definite issues? I'm just going to go with a 32gb x 4 setup. Thanks for encouraging me to do some better research and save some cash. Even 4k DaVinci Resolve users are happy with 32gb setups. If we ever meet someday, I'll use some of the dough I'm saving to buy you a drink. Cheers.
×