Recent content by FearDC

Anyone?

Hi. Either I'm missing something, or OSD label position is incorrent in RTSS. Lets say we have two items enabled, GPU FAN1 (column 1) and GPU FAN2 (column 2), both have (customized) labels enabled. This is the result I get in game OSD: GPU FAN1 GPU FAN2: 1101 RPM 1102 RPM This is what I would...

Sorry for false alarm, it must have been related to Windows update. After another update everything is fine again. Damn dev beta channel, don't understand why I even joined it. :-P

Hi! Just updated my HWiNFO64 (free) portable to version 7.32-4900 and noticed great difference in CPU usage on Windows 11. It's constantly using 6-15% of CPU according to Task Manager. Not only Task Manager by the fact, I really feel that with overall Windows usage, things are getting more...

Yup, next build 25179 works aswell :cool:

Alright, tested all possibilities, nothing works. Windows seems to not load the driver on start no matter what. Only my solution above works if one wants to use HWiNFO meanwhile system is up and running, after that need to delete physical file and recreate service. I also noticed that HWiNFO...

Thats why I wrote following above: * So HWiNFO creates a service named "HWiNFO_171" in persistent mode? * Where did we get "HWiNFO Kernel Driver (v171)" from then? * Does HWiNFO set different service name and display name? Edit: I figured out myself. Service name must be "HWiNFO_171" in order...

Alright, so I removed all services and drivers, also HWiNFO64.INI. Started up HWiNFO64, went directly to settings, checked persistent driver and tried installing manually, without success. So I copied the driver manually to the System32\drivers and created service using my app, then started...

Yes, I can see that. But in order to do so you need to run the application, and in order to run the application, you need the driver being loaded. :D Where does HWiNFO put the driver when persistent is enabled? I will try something.

Alright, final workaround: 1. Make sure all old services are deleted 2. Make sure all physical driver files are deleted, not renamed, because Windows keeps track of the file regardless of file name 3. Extract driver file to any location (can be the same as last time) 4. Create new service...

Yeah, I did that yesterday. But you know how programmers are, need to make their own crap :-D Plus I never had experience of coding for services using Win32 API yet, good to get knowing it.

LOL. This is so weird. I've spent last couple of hours extending my tiny application for managing driver services, so when it was time to test it: Then I tried to stop it and then start again, the issue returned: All this crap seems to be about specific period of time. I didn't restart my...

Update: Yup, it does matter. If I name the service "HWiNFO Kernel Driver (v171)", it will fail to load: Reminds me of Visual Studio toolsets. :-D Update: I tested as you proposed Martin, to try loading it multiple times with different names, and indeed it's being blocked on next attempts...

@ Martin This is interesting. I have extracted the HWiNFO64A_171.sys by running HWiNFO64 on another system. Then I have written my own software to load the driver into Windows 11 build 25145, the software simply loads the driver and starts the service, nothing else: Now that driver is...

@ Martin One thing certainly needs to be changed in HWiNFO, is to perform an update check of application before loading any kernel drivers, and possibly displaying a message about critical update availability. Because lets say they have blocked your driver forever, by file hash or what ever...