Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About MageTank

Contact Methods

  • Battle.net

Profile Information

  • Gender
  • Location
    United States, Ohio
  • Interests
    Gaming, Computer Hardware
  • Occupation
    Slim Jim Enthusiast


  • CPU
    Core i7 8700k 5.4ghz Cinebench Stable (best kind of stable)
  • Motherboard
    ASRock Z370 Fatality K6
  • RAM
    32GB (2x16GB) G Skill Ripjaws V 3200mhz C14 (Overclocked to 3600mhz C14-14-14-28-CR2)
  • GPU
    EVGA RTX 2080 Ti Black Edition XC
  • Case
    Thermaltake Core P3
  • Storage
    Samsung 960 Evo M.2 500GB
  • PSU
    EVGA 850W Supernova G2
  • Display(s)
    Dell S2417DG 165hz G-Sync TN
  • Cooling
    Decent Sized Custom Loop
  • Keyboard
    Logitech G810 Orion Spectrum
  • Mouse
    Logitech G703
  • Sound
    Sennheiser Game One
  • Operating System
    Windows 10 Pro

Recent Profile Visitors

10,369 profile views
  1. I don't normally make requests like this, but after a recent fiasco with helping a friend recover data, I figured it would be best to consult others for some recommendations on diagnostic/recovery software. Long story short, I am looking some suggestions for software that can help diagnose hardware/software issues as well as assist with recovery should the OS be inoperable. There are no limitations in place, so even if it were to cost money, I am fine with that. Whichever software you consider best, I'll gladly take a look into. I am looking for software for the following: Data Recovery System Imaging / Drive Cloning / Data Backup OS Diagnostics (such as bluescreenview, Windows Update Troubleshooter, etc) Hardware Diagnostics (software to help diagnose specific pieces of hardware or a system as a whole) Safe Registry Cleaning Software (I distrust registry cleaners, but understand their necessity depending on the issues. One that supports creating backups of registry would be nice) Driver Update Software (Windows Update is fine for the most part, but can be quite slow for getting updates for other things. This is by far the least important, but figured I would throw it in if someone had a tool they recommend) The goal is to create a drive that I can use to assist friends/family members with their systems and hopefully leave them with tools to prevent any mishaps in the future. Some of the family members I assist are out of state, so it's a chore having to drive 5 hours to fix a simple issue, especially when they are up in the mountains with extremely slow DSL internet making remote connections nearly impossible. Any suggestions would be greatly appreciated.
  2. Just found the white sheets that may help clarify some of this: https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/6th-gen-x-series-datasheet-vol-1.pdf Page 35, Section 5.1: Now my interpretation of this is that VCCIO/VCCSA is still integrated to the IVR, as it's listed as voltage rails coming from the processor, not as voltage supplied by the board. VDIMM is still generated by the board and doesn't come into contact with the FIVR based on this interpretation, as it mentions one main voltage rail (VCCIN), and a second rail for the memory interface, calling VCCD (VDIMM). I could be reading into this incorrectly, so I'd appreciate a second pair of eyes to take a look at it. My original understanding was that Skylake-X's IVR functioned identically to it's predecessors that used it. If this is not the case, I'll need to go back and take another look.
  3. Last I checked, all of the HEDT chips had a FIVR (Fully Integrated Voltage Regulator) akin to what was on Haswell back in the day. Whether or not this is responsible for the per-core voltage variance, I cannot say for certain.
  4. I believe what @aaradorn was saying amounted to "The endowment of my nether region hath increased at this moment in time, for that I doth not deceive." That's about as close as I can get when translating his text to the Queen's English.
  5. On the very rare occasion, you get one that is extremely down to earth. My current CEO doesn't drive a fancy car or over accentuate his wealth despite the huge success of his company. He even holds the door open for people as they walk in and out. I can't say the same for some of my former employers, but it's definitely the way I would want to run a company. The sheer respect you command when you treat people like normal human beings is far more powerful than cracking a whip and expecting results. Sadly, I don't see this being the case in other parts of the world, where the job market is overly competitive and saturated with enough people to fill any roles.
  6. 1DPC doesn't refer to a physical trait of the board, but rather using only a single DIMM in each memory channel. For example: If you have a board with 4 DIMM slots, only occupy 2 of them, with one DIMM in Channel A, the other in Channel B. Every board supports a 1DPC configuration, however in order to support a 2DPC configuration, you would need more than 2 DIMM slots, so most standard ITX boards are out of question.
  7. That is true, however dual rank is also far more difficult to overclock due to the addition of dual rank tertiary timings that come into play. For someone experienced with overclocking ram, dual rank is almost always a better choice. For someone just starting out, I would recommend sticking to single rank and 1DPC. From there, upgrade to 2DPC, then if you still need capacity, move on to the larger dual rank DIMM's.
  8. Interesting. I know different board vendors list it as different things, such as ASUS referring to it as "DRAM Refresh Interval", but it's odd that they remove the option entirely on Ryzen boards. Curious as to what is controlling the recharge interval for RAM, or if they are following the old rules of 7.8usec. That rule basically takes your ram's memory clock (if running 3200, it would be 1600) and multiply it by 7.8. In this example, that would be 1600 x 7.8 = 12480. I'll get my hands on a Ryzen platform and investigate further.
  9. How in the world did your fluid reach 75C? Even with an 8700k at 5.2ghz and a 2080 Ti at 2100mhz, I have a difficult time getting mine to go much higher than my ambient temps.
  10. True, but it does serve to illustrate that the first launch of 14nm wasn't all that great, and it took some to progressively mature into something faster. I kinda like the L4 cache structure of those Broadwell S chips, and would like to see Intel return to that design in the future.
  11. Depends on the timing. Most primary timings have a negligible impact on bandwidth. The biggest timings that impact bandwidth are the tertiary timings. RDRD, unsurprisingly, can improve your read bandwidth if configured properly. The issue is, if you go too loose or too tight on the timing, and it impacts the way your RTL/IO-L offsets are training (This is for Intel, no idea what AMD calls theirs), you will end up losing bandwidth AND increasing your latency. Lower isn't always the best, it just depends on what the IMC will tolerate without breaking training values elsewhere. The thing to note is that your actual bandwidth can never exceed your peak theoretical bandwidth. For example: DDR4 3600 has a peak theoretical bandwidth of 57,600MB/s in dual channel. No amount of timing adjustments will ever let you exceed that value, however you can improve your bandwidth efficiency to get as close to that value as possible. The biggest metric for judging relative memory performance is overall Round Trip Latency. It is a culmination of every single timing as well as the frequency of the ram. You want to reduce that value as much as possible while maintaining stability. This will involve a balance of both ideal frequency as well as very tight timings. Another way to improve latency is by prolonging the time your ram remains active before a refresh, as well as increasing the speed at which it refreshes. So increasing TREFI to it's highest value (65535) and reducing tRFC as low as you can get it while maintaining stability, it's a free increase in performance assuming you can keep the DIMM's cool with some airflow. I really need to sit down and work on memory overclocking for Ryzen, I just don't know where to start. I want to make a guide that encompasses all aspects of memory OCing for Ryzen, but their IMC's differ dramatically when comparing Ryzen 1000 series to the current 3000 series.
  12. That's definitely a simple view of the process, but yes, that's be essential order. You want to avoid going into Windows until you've performed some basic testing in Memtest86 as it will help minimize the risk of OS corruption when your memory decides to flake out while Windows is doing something important. If you have a spare drive to boot from, it wouldn't hurt to use that and load some stress test applications to avoid any risk to having to reinstall your OS on the main drive. Also be sure to test memory performance in between your adjustments to make sure you are not going backwards in performance. AIDA64 offers a pretty decent testing catalog for memory tests, allowing you to test your bandwidth (Read, Write, Copy) as well as your latency. Again, prioritize latency. If you change a timing, and it reduces bandwidth but also lowers your latency, I would consider that a fair trade.
  13. Correct. While not really a stress test, you can do a few passes of Memtest86 to make sure the ram itself and memory controller agree upon the timing configuration you've dialed in. It won't tell you much about the board signaling disagreeing, but it's a start. Once you start to pound the memory/IO lanes of the board, you'll get an answer as to whether or not your system is actually stable. You can use your own stress tests of choice, but I personally use Prime95 for this, as you can change the FFT sizes to dictate exactly what you want to test, whether it resides entirely in cache (small FFT) or RAM (larger FFTs). I've heard that others use HCI Memtest with great success, however I myself am not too familiar with it. Friends of mine also recommend ASUS Realbench as a system stress test, which appears to be based off some of the later Linpack libraries. Just be mindful of your cooling solution if you go for a test designed to run hot. EDIT: Going to address your voltage question. Voltage will help if you are facing instability, but you also need to be mindful of scaling, as well as signal interference. Not all memory kits scale the same when it comes to voltage. Some will clock higher/run tighter after pumping extra voltage through it, while others may show no benefits whatsoever. You only really want to push voltage if you are on the edge of stability. Trying to force stability into something completely unstable by using voltage is likely going to backfire, and lead to further instability. I am not certain if this is true for Ryzen, but on Intel, pushing higher IO (VCCIO) and System Agent (VCCSA) voltages could actually cause instability compared to simply dialing it back or finding a specific sweet spot. Increasing these voltages put too much noise through the board, and could cause signaling issues, leading to instability. I know Ryzen has similar voltages, but I can't recall what they are. Someone more versed in Ryzen may be able to help there.
  14. I would strongly advise against pushing for 4000mhz on Ryzen for several reasons. The biggest being the infinity fabric (FCLK) would have to run at 2000mhz in that configuration in order to maintain the 1:1 strap. This is extremely unlikely as most people top out around 1900. If you ignore the 1:1 strap, your 4000mhz memory will be slower than 3600 or 3800mhz memory with a 1:1 strap. On all consumer platforms, latency is king. Unless your applications are optimized to take advantage of heavy memory bandwidth (AVX being the easiest example), you won't see much of a difference pushing strictly for higher frequencies on memory. That's not to say you shouldn't, as frequency and latency go hand in hand with it comes to calculating your total Round Trip Latency, you should focus more on reducing your latency even if it comes at the cost of actual bandwidth. There is a guide in my signature that goes over the basic principles of memory overclocking. It's not designed for Ryzen, but it should give you an idea of what you should be looking for. As for an actual guide, this might serve you well: https://www.techpowerup.com/review/amd-ryzen-memory-tweaking-overclocking-guide/ Understand, this isn't going to be a simple "change a few settings and I'm done" kind of process. This will take a fair bit of time to make sure that your adjustments are not only improving performance, but that they are stable after doing so. Prepare to devote a lot of time to trial and error as well as stress testing each change you make.