08-02-2019 03:31 AM
03-20-2021 01:51 PM
03-21-2021 06:00 AM
Dinocoblue wrote:
One thing i have noticed since updating to 3602 from 3405 is that my idle power draw is significantly lower. I have the ROG THOR power supply that indicates total power draw. For version 3405, a 5800x and windows balanced power mode i was always drawing about 130watts idle and temps were in the low 40's to mid 40's. After 3602 and no other changes idle power draw is now 100 watts and temps are back in the high 30's so they definitely have made some changes with regards to idle power consumption. When turning power saving on temps drop right down to low/mid 30's and power draw goes down another 10 watts to 90 watts. Just something ive noticed with the new update fixing temp issues i was having. I have a 280mm AIO.
Note: I do understand all this power is not directly from the CPU, using HWinfo it highlights cpu idle PPT to be around 40 watts when writing this (google chrome open + ICUE etc).
03-21-2021 02:39 PM
Hi, had the same issue and for me solution was to turn off led light synchronisation of my motherboard (Asus) with EVGA 2080ti FTW3. I have Armoury Crate installed and there is a section that you can select which devices you want to control via AURA SYNC. Simply don't select graphic card and everything works fine.
Armoury Crate 3.3.7.0
EVGA 2080Ti FTW3 Ultra - 461.72
Precision X1 - 1.1.7
Windows 10 Pro build 20H2
Hope that will help. -Krezo
i think i have fixed my issue, ASUS Armoury Crate can control RGB to the video card, disable control and no issue, at least for the last three days. -SlevinKelevra1
Hey I am reposting to help you guys out with the nvlddmkm crashes as I had an extremely hard time figuring out the issues after RMA the card, replacing power supply, and attempting a lot of software troubleshooting including installing new windows 10 on 2 ssd's and problem continued until I did the following:
So what I did was change the Monitor power cord to my Main Surge Protector+battery, I know it's weird but I had it connected to Another port in the surge protector where it wasn't really protected and only pulled current from the main electrical outlet therefore causing problems sending a steady current to my system?. I have the cyberpower LX1500GU so perhaps it was causing not the pull the correct Electrical Current? it was based on a guys post from Tom's Hardware
Quote from the post:
"TL;DR See if you have to much power being used (from lots of plugs from devices) on your surge protector, and use less devices on the surge protector, or split them up on a different surge protector on a different plug (or put monitors only on their own surge protector) That fixed my issue."
^So that fixed my issue
In addition I did also Restored default settings for this power plan under windows 10 "Edit Power Plan Settings"
based on another link when you google " Fixing the Nvlddmkm Error (Display Driver Stopped Responding and Has Recovered) " it should be the first link.
Also Always keep your windows 10 up to date! Check for updates!
Oh also Krezo suggested that Asus Armory Crate fixed his problem by deselecting graphics card from Aura Sync in Sync devices.
so for anyone experiencing this nvlddmkm it might be due to your electrical outlet not pulling enough power correctly to steadily run your computer. I would suggest try connecting a few things separated even if it means running an extension cord for your monitors or devices. Or perhaps connect your equipment to another electrical outlet? not sure but it's worth a try with the addition of Restoring default power plan settings in windows, I hope this helps you as I struggled for months. -ATIXIUM
This honestly fixed everything. Moved some things to a different socket and decreased the amount of things on the surge protector and that fixed everything.
Can run both my monitors and everything without any crashes on anything or anything.
Thank you so much, I didn't even consider the problem being the amount of stuff in one surge protector. -NameUnknown72
New
I also experienced intermittent black screens. Considering that I have recently installed Corsair’s new version of iCUE, which can control the RGB of EVGA, I decided to turn it off for a period of time to test if this is caused.-wu0lei
03-21-2021 04:47 PM
Expletivium wrote:
Hi, here is a SOLUTION and a PROBLEM for people experiencing the following symptoms:
random signal loss
random display driver crashing
display turns off and on
game crashing
Event ID 14 "nvlddmkm"
It has been reported that Videocard RGB software is causing this issues and or Stable electrical outlet delivering enough electrical power to your computer.
SOLUTIONS COMPILE:
https://forums.evga.com/FindPost/3240806
https://forums.evga.com/FindPost/3244502
https://forums.evga.com/FindPost/3242727
https://forums.evga.com/FindPost/3244416
https://forums.evga.com/FindPost/3244427
03-28-2021 07:58 AM
03-30-2021 04:55 AM
Sinistercr0c wrote:
I've been on BIOS version 2606 for several months after having idle reboot issues on every later version, but I'm happy to report that version 3603 (beta) 'seems' to be stable. I haven't yet experienced any reboot problems (its been 5 days now) and CPU (TCtl/TDie) temps are a few degrees cooler than what I've experienced previously (down to <> 35° from <>38° at idle). I think thats down to more efficient/lower default Vcore voltage settings in the newer BIOS.
I've never had problems with the chipset fan speeds or temps...currently sitting at 55° with no fan, but as I run a Sabrent NVME drive with the big heatsink, I have the motherboard shroud removed to accomodate it.
I don't run the default D.O.C.P RAM settings, rather I manually set the RAM speed and major timings (Corsair LPX 3600Mhz with Micron dies) at 1:1 with the infinity fabric and have never had issues with RAM.
Everything else is default in BIOS. I get a score of 3727 in Cinebench on a 3600x with is a few points up from the 2606 BIOS but within margin of error, so at least I havent gone backwards with this BIOS.
03-29-2021 02:03 AM
03-29-2021 04:30 AM
03-30-2021 07:56 AM
Erwin05 wrote:
What i noticed with some bios's back is that the pc @ cold boot only starts up with Q- code AA and that windows 10 spotlight doesnt work anymore if the pc boots with AA.
With older bios's the pc boots AA or 04 and windows 10 spotlight did work, now it only works at a reboot.
03-30-2021 01:01 PM