Search results

I also forgot to ask you something: I have seen some 13th and 14th gen cpus like '900k's having system agent power readings too. Mine doesn't seem to have that. It is located under the same cpu enhanced sensor.

Added the dgb file

So i tried the new v8.01-5420 build and the new readings are awesome given that my renesas controller dies when read by hwinfo, but is it normal that vcc power out is capped to 255? pic below. Thank you for the effort. I also contacted Gigabyte about the issue with the controller and they...

I disabled SMBus. Maybe gigabyte will release a bios, or a driver update that fixes this.

Well, it's our friends again: btw those lines just dissappeared as i stated when i started the thread becasue of the greyout

Is it normal that Hwinfo eats almost 10 percent of a 14700k with nothing else running? I am on a fresh windows installation and hwinfo is running defaults on everythihng. You can also see the greyout on those vrms. I disabled fast startup and the hang is not present anymore so it's fine.

Sadly, it did it again today after a full night of stress testing. I will just go back to what I did the first time i encountered the problem: Disable Fast Startup, and even if it does grey out, the system won't hang at shutdown. It is what it is.

Sure, the PC is now running prime95 on clu and memory and it's perfectly fine. I'll report back in the following days too.

I literally found the fix for my problems.... It is their logofail patch on the bios logo. I had to disable the post gigabyte logo in bios settings and everything works now. 0 Greyouts in 7 hours of harcore testing, no more hangs on hwinfo or other monitoring software, and also those weird...

It's closed. This problem was even before installing gigabyte 's software. I never used proprietary software for monitoring. I started using it as a last resort.

It seems to be replacing the dbg file every time i close the app. Well, this slower mode actually fixes every issue I have and i don't have to tweak anything. I don't even have that no video at boot problem I had with 1f checked. Is there something that I can tweak so I can disable debug mode...

So i restored to original settings, opened hwinfo in debug mode and in debug mode with all the settings on default even the first row of smbus checked, it doesn't do the greyout or the hang. Why is that???? I also attached the dbg file, maybe you can see something. I also noticed that in debug...

0 RGB. 2 fans only, cpu noctua, 14700k, 7900xt and nothing else. RAM from qvl perfectly stable. BIOS defaults, all official drivers installed.

The cool thing is that when using 1x, there is no greyout. All values are perfectly read with no issues. I wonder if this trick would fix the same greyout problems on my old Z390, as well as other people's similar greyout issue on the vrm sensor. Searching for a solution on my greyout problem, i...

Should I just go 1F as as minimum plus 1,2,3 from right to left, until i dont have that gpu blackscreen issue at login. Btw that issue barely happens. Btw isn't there a way to know what devices are on those addresses?

I tried playing with the boxes again by checking back the 0x row as it was on default plus 1F box and it did the grey out bug again, but it did not hang with 1F checked. So for me, I just can't use the first row(0x). After going back to 1F box, i had that no video at windows start as i had it...

yea, no problem. I like HWInfo and I just can't build or use a PC without having a glimpse on all those shiny rows. PS: I only have the 1F box checked. The default 0F row is unselected on my side after the testing.

Thank you!

yes, but it also worked just fine with all 1x row checked. It worked with the 7-f half too, but i had that weird no video at windows login bug. it owrked with 4,2,1 too(as in C,D,E,F).

Well, i am at the latest 1x box xF and it works just fine with just that active. Now i don't know if any single box selected in 1x row will do the trick and im too tired to test it. For now these are my findings. It's something in the 1x row.