Jump to content

TwilightRavens

Member
  • Posts

    252
  • Joined

  • Last visited

Everything posted by TwilightRavens

  1. Try booting windows into minimal mode (selective startup) and see if the issue persists. Could also try Diagnostic startup, but I can't remember if it'll load the GPU driver or not.
  2. It sounds like either your RAM or fclk is unstable, but RAM will usually throw a bsod.
  3. $160 or less I would consider fair for a 980 ti, though yeah a 1070 would be better because of the 8GB of VRAM vs 6GB.
  4. Are there any background processes using the GPU?
  5. Have you tried DDU and reinstalling the drivers? and also making sure in the Nvidia control panel the power plan is set to adaptive.
  6. I’ll post a ZenTimings screenshot next time i’m at my computer. XMP calls for 1.35v, and the main timings are 16-16-16-16-36 was running 1.5v from when I was running 2 sticks at 3800 C14.
  7. Oh right, I forgot about that part for signaling quality on the motherboard, better sticks in the worse slots and bad ones in the good slots.
  8. fclk is synced to the memory frequency, so 1867 with 3733MHz RAM, and have validated stable fclk with 2 sticks at 2000Mhz (DDR4 4000).
  9. So as the title says I've been having a bit of trouble trying to stabilize an overclock of my RAM and was wondering if anyone could suggest anything I can try. Memtest errors within 5% into the test Specs: AsRock X570 Taichi Bios 4.80 (I am aware that the memory topology of this board is Daisy Chain and is geared towards 2 sticks of RAM, but I have heard it should still be able to hit 3800MHz) Ryzen 9 5950X 4 x 16GB G.Skill TridentZ Neo 3600MHz C16 (Dual Rank b-die) I am also aware they are different batch dates but I have validated them separately in 2 x 16 sets and they can hit 3800MHz) I've also tried: SoC up to 1.2v VDDP up to 1.1v VDDG IOD and CCD up to 1.12v and none of those were able to affect anything, and am I missing any voltages that I should be adjusting?
  10. 64GB of RAM is fun, don't actually need it nor would I recommend it, but I could run google chrome with a few tabs now if I actually used chrome and not firefox.

     

    Capture.PNG

  11. Yeah honestly I'm seeing two different speeds, CPU-z looks like its reporting 1866MHz and tack manager seems to be reporting 2400MHz. According to google, your CPU in that laptop supports up to 2400MHz and I assume its non XMP so you would need a JEDEC 2400MHz kit. For 16GB get this: https://www.amazon.com/dp/B01BU77LQW/ref=emc_b_5_t For 32GB: https://www.amazon.com/dp/B01BU77M4I/ref=emc_b_5_t Neither are JEDEC 2400MHz though as far as I'm aware. Can't guarantee that those will run at 2400MHz, but this would since this is JEDEC: https://www.newegg.com/p/0FC-00KP-00001
  12. WHEA error is usually memory related, so a good place to start would be to reset bios to default and run memtest86 if you can find a way to get around the no post, but honestly I'd blame the failed post on a dying mobo.
  13. Linux Lite is a Windows "feeling" version of linux, its probably one of my favorites because it works right out of the box without any tinkering. It also can run on a machine with 768MB of RAM and a 1GHz CPU.
  14. And people said I would never need 32GB of RAM pfffft, I'm tempted to get another 32GB around the holidays, we'll see.

     

    Capture.PNG.73e7138ebd08f74c53aab1edb8aa4956.PNG

  15. Liquid metaled the GTX 285 finally after human malware caused shipping delays on my Conductonaut and Fujipoly thermal pads (the 17w/mk ones). Regardless I’ve gotten around to assembling it and am in the process of benchmarking it. Will upload pics of the benchmarks if this gets 10 likes but I forgot to take pics of when i put the liquid metal on the die and resealed the ihs. I’ll say temps went down considerably, was bouncing off 80C stock at manual 100% fan to now maintaining 65C whilst withstanding a heavy overclock.

  16. She's ready for liquid metal next week! :D

    photo_2020-07-17_01-02-23.jpg

    photo_2020-07-17_01-02-19.jpg

  17. Delidded a GTX 285 tonight.

    photo_2020-07-17_00-19-08.jpg

    photo_2020-07-17_00-08-53.jpg

    photo_2020-05-27_23-21-36.jpg

  18. As the title says, though this was a bit more difficult than a typical CPU because I had to heat it up with my brand new heatgun I purchased today.
  19. see edit real quick if you wanna reenable write protection
  20. No problem, I'm glad it resolved your issue, I was a bit hesitant at first but once seeing what you described to me it pointed more to a vbios issue rather than something else messing with it. also if you wanna re-enable write protection just relaunch nvflash and do: nvflash --protecton or nvflash64 --protecton depending on which worked.
  21. hmmm looks like its write protected, after launching nvflash use this command: NVFlash64 --protectoff press enter and then attempt to reflash. Edit: If that command doesn't work use: nvflash --protectoff
  22. Let me know how it goes, it should be pretty straightforward, the only way to brick the card would be to cancel it in the middle of the flash or if you lost power. Other than that if the bios doesn't work it just won't correctly load the driver and in that case just revert back to the old bios and that usually fixes it. I've flashed my 1080 ti to an incompatible bios and that's basically what happened and it was fixed when flashing back. Also sometimes it may not be right away that you'll notice something is wrong so i'd hold on to that bios for as long as you feel the need to as a "just in case" it never hurts. Oh and after the flash you'll need to reboot your computer. If the fan issue still isn't resolved try DDU'ing the driver and do a clean install, if that doesn't work try an older driver to see if it's still affected, also check to see if MSI afterburner is up to date. Sometimes it can be the simplest of things. Also only use one GPU overclock tool, sometimes having 2 they can conflict with each other causing issues like that, but i'm pretty sure it was a vbios issue.
  23. It shouldn't be a problem, but just in case make a backup of your current bios using GPU-z and save it to a safe place in case it doesn't work, that way you can easily revert back to what you had.
  24. You could download that BIOS file, assuming that's the exact card you have, make sure device id and sub system id matchup (which from what I see they do but double and triple check behind me) and you can use a program called nvflash to flash that one, but make sure the card is not overclocked in any way before you flash. Here's a detailed guide on how to do it: https://www.overclock.net/forum/69-nvidia/1523391-easy-nvflash-guide-pictures-gtx-970-980-a.html
×