• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

[GPU-Z Test Build] New Kernel Driver, Everyone: Please Test

QuietBob said:
The only thing missing is the UEFI checkmark on the first tab. Could be because I'm running a UEFI card with CSM enabled?
Click to expand...
Yes, CSM = no UEFI support required on the GPU
 
W1zzard said:
Yes, CSM = no UEFI support required on the GPU
Click to expand...
So the UEFI checkmark is now supposed to show whether UEFI mode is enabled or not, system-wide?
I thought it was to indicate whether the card's BIOS supports UEFI. Build 2.66.0 shows the checkmark for me, while 2.66.5 does not:

1752091228003.png
 
1752127961132.png

1752128048757.png
 
Everything is fine on the latest version with Windows XP and 8800 GTS
 
QuietBob said:
Email sent and also uploaded to the repo :)
Click to expand...
Confirmed, that BIOS supports UEFI

But meh, none of my cards here from that generation support UEFI, hard to repro
 
Last edited:
1752177694403.png
1752177717290.png


looks good.

EDIT:

1752208093050.png


gpuz throwing event log errors.
 
Last edited:
win11 24H2 (26100.4652) 64-bit
Core i7-14700H / RTX 4060 Laptop
2.66.5 version works all fine on both iGPU and dGPU.
 
Sabotaged_Enigma said:
yes, there are error entries in my eventlog too, but the software runs perfectly.
Click to expand...
As mentioned before these arej ust log messages, not actual errors. The error mechanism is just an easy way t oget logs pushed out. Will disable for release
 
Win 11 24H2, 64-bit, i9 9960x, RTX 3080 12GB - everything works fine :)
 
1752274490489.png
 
@W1zzard hypothetical situation, let's say this gpu-z error never got fixed, and bad actors wanted to exploit my computer. would blocking gpu-z in my firewall so it can never gain internet access prevent that issue no matter what?

fyi, I always block it in firewall, so just curious if it would have even mattered for me or not
 
2.66.5 - to validate I am using right build.

13700k
RTX 4080 Super FE
Windows 10 21H2 LTSC 64bit.

It seems to start a bit slower, but not noticed any issues, all sensors populating.

Given above reports, lookup works fine, REBAR reporting seems accurate. Reported clock speeds match up with older stable build I was using..
 
Last edited:
Space Lynx said:
prevent that issue no matter what?
Click to expand...
No, this has nothing to do with online connectivity

Basically: if you're running as admin you are able to break the OS kernel, which imo is not unexpected in the first place, but MS really wants to take that ability away from you. Still, GPU-Z shouldn't help to facilitate that.
 
Build in first post updated again to fix BIOS reading on pre-Windows 10 x64 machines (these have to use the old kernel driver, because it's no longer possible to sign a new driver that gets accepted by these older OS's)

Also turned off the event log "error" entries

@QuietBob
 
W1zzard said:
Build in first post updated again to fix BIOS reading on pre-Windows 10 x64 machines (these have to use the old kernel driver, because it's no longer possible to sign a new driver that gets accepted by these older OS's)
Click to expand...
Looking good, thanks for the update!

1752403733964.png
 
I tested version 2.66.6; works alright, load time is long though.
 

Attachments

  • 2-66-6.gif
    2-66-6.gif
    17.7 KB · Views: 10
NV28 has the same detect issues as R600 had :( (well, minus Rebar Enabled thing)

NV28.PNG

^No Core clock, no Memory Clock, wrong VRAM memory type.
Same system/OS as previously.
 
agent_x007 said:
NV28 has the same detect issues as R600 had :( (well, minus Rebar Enabled thing)

View attachment 407688
^No Core clock, no Memory Clock, wrong VRAM memory type.
Same system/OS as previously.
Click to expand...
But broken in public release too, so not an effect of the new driver architecture
 
You must log in or register to reply here.
Back
Top