FatBoyNL

Haha. Thank you as well for this fix, and adding these extra extra OpenAL extensions 👍 I'll have to check if all 'Soft n Loki' OpenAL extensions actually work as intended or advertised. Not exactly familiar with those yet. I noticed to see different Soft OpenAL32 DLL files in some game folders (STALKER Enhanced games, for example).

That just seems to work 'kinda' for the top 3 check boxes: most features still seem to be missing. I had the same result when I put the 64-bit sens_oal.dll file in the system32 folder, and renamed it to OpenAL32.dll 😇

When I first installed Win11 (and OpenAL), I noticed EAX wasn't available in supported games at all in the first place. And OpenAL info was missing in the old AIDA64 (32-bit). But I'm pretty sure I managed to solve both issues by replacing the (mixed-up) wrapper DLL (sens_oal.dll) files with the correct 32- and 64-bit versions (extracted from the original installer) in the appropriate folders. Can't the new 64-bit AIDA64 just "load/read/use/etc" the wrapper DLL (sens_oal.dll) instead of OpenAL32.dll for obtaining the correct OpenAL info?

Just return the PC to the shop where you bought it. Have them fix it properly or ask for your money back.

Same issue when using my built-in monitor speakers (connected through DisplayPort):

Just noticed that the Multimedia > OpenAL window in AIDA64 doesn't show the correct OpenAL Extensions anymore in the latest 7.99 beta build(s). I'm using a Creative Sound Blaster ZxR sound card. EAX effects are still working in supported games though, so this must a bug in the latest beta(s). I attached 2 screenshots showing this issue in AIDA64.

Thanks, the issue has been solved in beta .7823 👍 EDIT:

To me it seems all fonts are a bit larger btw than the last 'few' betas, just looking at the Computer > Sensor page for example. But that's a good thing imho. The release notes of this beta show "- font scaling" on top. Any chance this could be related?

Thanks, I'm using standard 150% scaling. And I see the same issue with CPUID Panel and GPGU Benchmark.

150% at 2560x1440. I'm not using font scaling (100%).

Latest .7820 beta seems to have some scaling or spacing or DPI issue within the cache & memory benchmark: EDIT: this is on Windows 11 26100.4482 btw.

Thanks, this looks perfect 👍

Thanks, the current firmware revision of my 9100 PRO is 0B2QNXH7.

EDIT: I guess we'll have to wait for Samsung to fix this.

Can't this be solved by using only both Temp Sensor values (and just leave the 'Temperature' value) and use them as T(high) and T(low) for determining the actual output values as shown by AIDA64? But for all Samsung NVMe drives only maybe? I don't know whether all other NVMe drives from all other manufacturers are using the same SMART data for temperature readings like this. Or is that about exactly what you're saying? That would make completely sense and I guess then we'll have to wait for new firmware like you said. EDIT: I think see your point now. Most programs like CrystalDiskInfo would use just 'Temperature' for their one-and-only Temp reading, so that should be the primary reading whatsoever. And then there's 'another' reading, but which one of the two... That's a problem. Still think this can be solved by simple math though 😜 Meanwhile, do you know any higher-tier support contacts over at Samsungs btw? I would like to offer my (nagging) skills to contact them about this, but I have the feeling their AI Support Chatbot just wouldn't understand me in that First Encounter 😇