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

hihihi8

Member
  • Content Count

    245
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About hihihi8

  • Title
    Member
  • Birthday May 01, 2000

Profile Information

  • Location
    Chicago, Illinois
  • Gender
    Male
  • Biography
    IB student from Beijing BISS International School

System

  • CPU
    Xeon E5-1680 v3 Engineering Sample - 8C/16T @3.2Ghz
  • Motherboard
    MSi X99A Godlike Gaming
  • RAM
    64 GB G.Skill Jipjaws 4
  • GPU
    980Ti x2 DIY Watercooled Reference Cards
  • Case
    TT Core P5
  • Storage
    Samsung 950 Pro 512GB
  • PSU
    Corsair RM1000
  • Display(s)
    Dual LG 34" Ultra Wide 3440*1440
  • Cooling
    Custom Hardline Loop
  • Keyboard
    Cherry MX Blues, OEM
  • Mouse
    Logitech G703 Lightspeed + Powerplay Charging Mousepad
  • Sound
    Bose Companion 20
  • Operating System
    Win 10 Pro

Recent Profile Visitors

1,153 profile views
  1. I have a reference 6900XT that i've set (via moar powa tool) to draw 370W right now. temperatures peaked at only 51c after 15 minutes of furmark. The PCIe power cables are only slightly warm to the touch (Two 18AWG 8pins, and no i'm not using the single that splits into dual-8pins). I read somewhere that these 8 pins should be good for 300W each, but molex set the standard to 150W due to concerns over cheap PSUs using cheap cable material. Would it be safe to go higher on the power limit, or would I damage something? The card in a big custom loop hence the low temps, vo
  2. Coolant temp is kept under 45c. The loop is controlled using an aquaero based off coolant-ambient delta. Certainly no overheating. imo there is no excuse for this to happen within 15 days of filling. Everything is gonna have to be disassembled fully and wiped down. F.
  3. My recent upgrade also involved a loop rebuild, during which pretty much overhauled the entire loop. My old loop used deionized with a silver kill coil, and I never had any real issues with it worth mentioning - coolant stayed clean and temps were good. - EK ROG CH8 Dark Hero Monoblock (new) - EK Monarch X4 RAM blocks (reused but with full disassembly cleaning) - EK 6900XT full-cover block (new) - Alphacool NexXxos UT60 480 RAD (reused, thorough flushed, left to dry fully before being refilled) - Primochill RSX Fittings - Primochill Res (new 360mm, forgot e
  4. just one of those radiators would be enough
  5. same for me. disabling c-states fixed it for me.
  6. im more concerned about the CPU's PHY degrading with those voltages since the VDDQ output buffer shares the same voltage as VDIMM and there's no way to change that.
  7. According to some feedback i've received, seems like this setup is pretty rough on the IMC – quad stick, quad rank b-die, tight timings
  8. does it reboot on idle? or under load? or both? Try disabling global C-states in the bios, you might need to dig around for that setting.
  9. Not sure about dead on arrival, but certainly a lot of ryzen 5000s that are plagued with instability and crashes. Check out the 40-page long post on the AMD forum, as well as the plethora of issues on the ROG forums regarding ryzen CPUs, 5000s included. It seems a lot of ryzen 5000s are not quite dead on arrival, but faulty and unstable. My 5950x will not stand global C-states being enabled. With C-states enabled, it will randomly crash to a black screen with post code 00 and power/reset buttons unresponsive during idle/low load every 30mins-3hours or so (with newest BIOS, everyth
  10. Aight, final update: disabling global C-states in the 3204 bios fixed it. 3204 out of the box was noticeably more stable compared to 3202, but still crashed on me a few times. Hypothesis: with C-states enabled, when the system is at low load or idle, the CPU aggressively undervolts the CPU to the point where one of the CCD's becomes unstable (since 5950x's all have one good-binned CCX and one poorer/average binned CCX -1usmus), hence explaining why the system only crashed at low load/idle and never under load. Disabling C-states has fixed the issue, or so it seem
  11. Report 7: I've got it pretty satisfactory and stable at the following: Global C-states disabled (or else this system crashes randomly and frequently when idling – prolly faulty CPU but whatever) Dram Voltage: 1.485v CPU_SOC: 1.15v Dram Freq: 3600 FCLK: 1800 tCL: 14 tRCDRD: 13 tRCDWR: 13 tRP: 13 tRAS: 28 tRC: 42 tRRDs: 4 tRRDl: 6 tFAW: 16 tWTRs: 4 tWTRl: 10 tWR: 12 tRDRDsCL: 3 tWRWRsCL: 3 tRFC: 288 tCWL: 14 tRTP: 8 tRDWR: 8 tWRRD: 4 tWRWRsc: 1 tWRW
  12. Has anyone tested to see if there is a difference between voltage probe points on motherboards and actual back-of-the-socket voltages? Don't have access to the PC currently.
  13. Ok so the memory OC wasnt the culprit of my instability after all. It was a bad beta BIOS. latest BIOS has been solid so far, will put the OC back in soon.
×