EVGA

Z390 Dark still worries me(CPU KILLED?)

Author
chowhi123
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2019/01/13 13:35:45
  • Status: offline
  • Ribbons : 0
2019/04/15 03:56:16 (permalink)
There has been a few thread back on Feb when many people asked about incident Z390 Dark Killed i9-9900k.

I believe this was a legitiment claim with poor evidence and lack there of. This incident actually happend during a livestream by Eyejoker. He is a South Korean reviewer who I believe is experienced enough not to make any false claim. His daily config before was godlike+i9-9900k which he regularly streamed played games. When he decided to upgrade his gear to Z390 Dark EVGA, by using I9-9900k that he had used without any problem. Once he made the upgarde to Dark, he noticed that there was glitch. He couln't OC his ram to 4600mhz CL18 just like he did on Godlike. His attempt to OC 9900K failed at 51(1.35v). When he had a hwinfo open his cup total error kept piling up.

So, he replaced CPU to an i7-9700k which worked fine. A few things that he suspect is the cpu stress test that he ran in bios or volt regulator failed on him.

I attached the linked to his video so you can check what really happend and how he did OC.

I want to know if this issue is something known or just a bad luck. THANKS!
#1

4 Replies Related Threads

    chowhi123
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2019/01/13 13:35:45
    • Status: offline
    • Ribbons : 0
    Re: Z390 Dark still worries me(CPU KILLED?) 2019/04/15 03:58:01 (permalink)
    https://youtu.be/kXvreCCuWcY
    #2
    Delirious
    EVGA Forum Moderator
    • Total Posts : 17474
    • Reward points : 0
    • Joined: 2007/11/15 13:34:04
    • Location: at my computer
    • Status: offline
    • Ribbons : 61
    Re: Z390 Dark still worries me(CPU KILLED?) 2019/04/15 08:00:21 (permalink)
    hard to tell.  Probably none of us speak Korean.    I did see the voltage downclock on load which created the blue screen in windows 10.  I'd bet he doesnt have some of the settings correct.  Maybe advanced power settings in the OS.  Should be set to performance.    But it's hard to tell by that video.       I didn't see any sort of CPU damage.    

    "Be quick to listen, slow to speak and slow to anger" 
    Affiliate Code XZUMV9TJW5
    Associate Code: 7PM43CU71IB2IAP
    education may be expensive but wait until you get the bill for ignorance
    A wise man once said that we can't make anyone feel or do anything. We can throw things into the wind, but it's up to each person to decide how they want to react, where they want to stand when things fall.
    #3
    xaviplisskin
    New Member
    • Total Posts : 13
    • Reward points : 0
    • Joined: 2018/03/10 16:21:03
    • Status: offline
    • Ribbons : 0
    Re: Z390 Dark still worries me(CPU KILLED?) 2019/04/15 08:30:26 (permalink)
    chowhi123




    I can't confirm 100% but I think all my problems with ram came from de uncore with multiplier at x47.
     
    now I'm testing with HCI at 1500% ( and going up) coberture with 4000 17-18-39 1T with uncore 46. This gen doesnt like very much to set ratio 1:1 with core/uncore. But that's my opinion
    #4
    xTemon
    iCX Member
    • Total Posts : 376
    • Reward points : 0
    • Joined: 2007/10/07 21:17:38
    • Location: Western Canada
    • Status: offline
    • Ribbons : 6
    Re: Z390 Dark still worries me(CPU KILLED?) 2019/05/05 13:28:39 (permalink)
    I didn't watch the whole thing; just sort of skimmed through. If I'm not mistaken he pulled it and tested it in the ASUS board after and was showing an L1 cache error on the CPU, but it wasn't by any means dead. Just no longer functioning properly.
     
    Chances are, the CPU and RAM were the same he used in the Maximus, so it was already well used. Also, you can't expect a CPU or Memory to function the same way on one board and another. You're going to get different results generally speaking. He probably should have been trying to find what worked best with the Dark, rather than trying to replicate what worked with the Maximus. Especially considering perhaps, the very different CPU and Memory configuration.
     
     
    #5
    Jump to:
  • Back to Mobile