Search results

This is a yellow flag. No post with DOCP means something is not going well with the RAM or the CPU mem controller. Why is your RAM in A1-B1. From your manual it should be in A2-B2 (page 1-10).

This wont work as the collision is most likely with the SMBus, not the Corsair service, so disabling "CorsairLink and Asetek support" option will not prevent this from happening. You will need to either disable the RAM monitoring in HWinfo or stop using iCue for the RAM. Sadly unless Corsair...

Mm that is weird. I assume you had deleted the previously created lines from your registry? At least it's an improvement, your Hotspot at 50.6c is I assume correct, so is your Junction temp at 48c. The issue seems to be with that the GPU temperature is creating a sensor named hotspot temp (but...

From the tuto: "The "X" represents a sequence number starting from 0, for example the first temperature value shall be named as Temp0.* So unless you have other customs sensors, your numbering is wrong Delete the registry lines you added previously and use this instead...

Hi Martin, I posted something in another thread but did not see any feedback. So instead, I will open a new thread since it led to a request. Right now, if a sensor that has been selected in the gadget section stop reporting or has an invalid value (either due to latency or other reasons), the...

I just tested a sensor with (invalid = over 0 ) and it indeed did what you said. . The issue is that the associated entries vanishes from HKEY_CURRENT_USER\Software\HWiNFO64\VSB which is where FanControl plugin gets the data needed. Would it be possible to keep reporting the last know values to...

Ok so now this created another type of issue. Everytime my RAM hit 47.75c, the sensor goes grey until the temperature is not at that value anymore, which it can stay at for a couples minutes. At this point, the fancontroller that rely on it already decided it is outside the acceptable delay (10...

Great, will be looking forward for it. Thanks!

Hi, I just found out that hiding (shift-del) sensors does not seem to fully disable them. I found out about this because I'm having weird Vsync/frametime/stutter issues with any GPU monitoring on, which gets resolved by disabling any monitoring on my GPU (Nvidia bug). During my testing, I ended...

Well I did some gaming test (avatar FOP, which is know to be quite well optimized, at least for frametime) and the result is that HWinfo64 GPU monitoring is somehow creating frametime spikes when Vsync is on. See below picture, on the top, with HWinfo64 GPU monitoring (1000ms pooling), it...

So disabling NVML does help a lot, but does not remove all stutter. To remove all stutter I need to also disable the GPU monitoring. My question is: Is it normal for GPU monitoring (without NVML) to cause some stutter?

With NVML + GPU monitoring both enabled: 110-117FPS With NVML Disabled but GPU monitoring enabled: 118FPS With NVML + GPU monitoring disable 120FPS

Unless I'm mistaken you are refering to this setting under Safety? It is already disabled

I'm glad I found this thread. I've been noticing weird microstutters in gaming since I updated to the latest Nvidia driver. Turning off NVML did help by removing the worst stutters in the blurbuster test, which was going up and down between 110 to 118fps on my 120hz monitor. But, it seems...

Hi Jhelmer, Sorry it took me a bit of time to answer. I`ve been quite busy. Ok so here are my answers: 1- Agreed, real use is by far the biggest/most reliable stability test. In real use, transient spikes (load going from low to high to low in very fast changes) will occur more than any...

Very hard to tell. Higher temp usually is either cooling issues (mounting of cooler, fans, thermal paste) or increase in power (voltage or current higher = higher power consumption). What are your voltages in the bios after enabling the EXPO profile? Also, the freezing after 10hrs is not...

I doubt it would matter since it seems like disabling DOCP fixed the issue (well as far as 10hrs of blend Prime 95 can be called stable after 10hrs, but that is another debate I don't feel like going into). But who knows, it might be a possibility. I would run Prime in large FTT instead of...

Hi Jhelmer, Ok so this is definitely a step forward. The possibilities you mentioned in this case are: Unstable memory chip (need new RAM hardware) Correct, since VDD/VDDQ ram voltage are pretty much at safe limit. Unstable memory controller (need new MOBO hardware) Incorrect, memory...

Hi JHelmer, DRAM VDD/VDDQ are your ram voltages and expected to go up to 1.4v based on your XMP profile. CPU VDDIO/MC is the CPU memory controller and is expected to go up, controlled by the Bios who will up it to match the DRAM VDD/VDDQ voltages. The 3 are expected to be in sync (you can run...

Firts thing that came to mind was transient load reboot. But then I noticed something when looking at your specs + troubleshooting steps. 7000X3D chips are sentive to SOC voltage. XMP/DOCP and EXPO RAM kits when their profile are activated will in most case have the SOC Voltage increaed by the...