Fiery

We've implemented the requested drag&drop LCD page reordering trick in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip Let me know how it works. Please note that at the time you perform the reordering, the page captions will be reordered as well, to indicate that you've performed a reordering. So e.g. after swapping Page 1 and Page 3, the page captions will look like: "Page 3 / Page 2 / Page 1 / Page 4". But, after you press the OK button and close the Preferences window, and reopen it again, the page captions will be restored to the default order of "Page 1 / Page 2 / Page 3 / Page 4". The pages content will however be kept as it should, so the content will be kept swapped.

Sounds great, thank you for letting us know about the resolution.

In our first test run under Win8.1 we've also attempted to install Frame Manager, but the installer failed. Frame Manager doesn't seem to be compatible with Win8.x at all, but the drivers work fine under Win8.x -- at least for us. We've installed the Mini Monitor device drivers using the drivers copied to \Program Files\Samsung\FrameManager by Samsung Frame Manager installer, and it worked just fine. In one of your previous posts you seemed to have indicated that it didn't work for you under both Win7 and Win8, but now you say it works fine under Win7? Just to make sure it's not a driver issue, please try to change the Mini Monitor drivers to the ones we're using. The driver version is the same with yours, but we've already got two different Samsung SPF driver sets, both with the same version, so you never know with Samsung I'll send you the download link to our drivers in private message. BTW, our "Plan B" for the Samsung issue is that we would implement an alternative driver path in our code, to let you use generic LibUSB drivers with Samsung DPFs. That may or may not help in your situation though, since -- if I properly understand what you wrote -- the device keeps disconnecting after 5 seconds even if you don't start AIDA64 at all. It could well be a driver issue that may be resolved with the LibUSB driver, but it is also possible that it's a hardware flaw that will not be resolved by a driver change. Anyway, if you have time and energy left to hassle with your SPF-87H, you can try our LibUSB solution soon. I'll send you a message once the LibUSB driver and the AIDA64 beta with LibUSB Samsung SPF support is ready to be test-driven.

In case the Mini Monitor device disappears from the system after that 5 seconds elapsed, even if you don't start AIDA64 at all, then it seems to be an issue that is related to the Samsung driver or the device itself. Have you tried to connect the device to another computer? Have you tried to check the Windows Event Logs, to see whether there's any reference to why the device gets disconnected? I'm starting to feel like your particular SPF-87H device has some hardware flaws... Maybe try updating the firmware. I'll soon run out of ideas

It's quite puzzling. Have you tried to connect the DPF to another USB controller? Have you tried to power the DPF off, power it on again, and switch the device to Mini Monitor Mode on the DPF, and see what happens when you start AIDA64?

Can you check what happens if you let AIDA64 switch the device to Mini Monitor Mode, but then you quickly close AIDA64, before that 5 seconds elapses? Will the device stay in Mini Monitor Mode? Something must be causing the DPF to switch back to Mass Storage Mode again, but I have no idea what could it be, as long as Samsung's own application is completely removed from your system. We've now double-checked with the same drivers you're using, under Windows 8.1 64-bit, with both a SPF-75H and a 800P DPF, and found no such issues you're experiencing. It works absolutely smooth on our test system.

Since you've got some kind of errors even with the AIDA64 kernel drivers disabled, and the error points to nVIDIA video drivers, I'd say your system is indeed not 100% stable. The BSoD's you get when running AIDA64 benchmarks may just be due to the system instability, and not due to a bug in AIDA64.

The issues will be fixed in the next AIDA64 beta update due in a day or two from now. I'll post the download link here, as soon as the new AIDA64 beta is available

Yes, that's the same driver we're using. Do you have any remaining Samsung devices in the Device Manager, under Display Adapters? If yes, then try to uninstall that, including removing its drivers.

It sounds quite odd. After the uninstallation, were all Samsung Frame Manager related files removed? Can you please check if there's any of them left under \Program Files\Samsung ? What version of Frame Manager did you have installed? Can you maybe check the driver version and driver date for the Mini Monitor driver? There're quite a few versions out there, and maybe you're not using the driver we've used for our test runs.

Thank you. Please let me know the exact configuration of your CPU and memory, like BCLK frequency, CPU core multiplier, and DRAM:BCLK ratio as configured in the BIOS Setup.

You're right, AIDA64 does not yet cover those points. We'll have to work on enabling proper detection in such environment as well. As for logon count, I suppose it doesn't count Microsoft account logins, that's why it doesn't increase with furter logons. Regards, Fiery

Don't worry, we'll sort it out Most likely the issue is caused by the collision between Samsung Frame Manager's main hardware polling process called sam_controller.exe and AIDA64. Please try the following: 1) Start Registry Editor (REGEDIT.EXE), and navigate to: HKEY_LOCAL_MACHINE\Software\Samsung\FrameManager 2) Check what value does the DeviceInfo field hold. If it's "00 00", then please switch the device to Mini Monitor Mode, and check it again. 3) Also check what USB device ID does your SPF-87H have assigned, on the Devices / USB Devices page. The device could be in either mode for that. I'm just wondering that because there are 3 different variants of SPF-87H out there, and it would be great to know which one have you got. 4) Try to kill the process called sam_controller.exe using Task Manager. That should take care of the collision between AIDA64 and Samsung Frame Manager, and let you use the DPF via AIDA64. If you don't want to use the Mini Monitor feature of your DPF for its intended purpose, then you may as well uninstall Samsung Frame Manager completely. It will leave the Mini Monitor USB device driver installed, so you will still be able to use AIDA64 with your DPF. 5) I'll send you something further in private message, but please only deal with that after the above 4 steps BTW, if nothing works out (which is unlikely), we already have a "Plan B" for Samsung SPF devices, so you will either way be able to use your SPF-87H with AIDA64. Thanks, Fiery

It will be sorted out in the next AIDA64 beta release due in 1 or 2 days from now I'll post a download link here once the new beta is available.

Thank you for the feedback, I'm glad you've managed to sort it out.

No, we're not planning to enable that. It would make configuration too complex and hard to follow for many.

T-Balancer bigNG supports 12 temperature inputs, and AIDA64 implements native support for it.

I've sent you your product key in private message.

Quite frankly, we don't think it would worth the hassle, simply because it's much better to use a background image that you can assign for any page. And if you want a plain, solid color background image, then you can make one using MS Paint for example, in 2 minutes

If you enable Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability (and then restart AIDA64), it should work with AI Suite. Regards, Fiery

Thank you for the feedback. Yes, just copy over, let it replace any existing files. But first, close AIDA64

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results here. Thanks, Fiery

We've tried to find the issue, but so far with no luck We would have to narrow it down to a specific part of the code to find the culprit. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Let me know if it triggers a BSoD or falls into and endless loop. Please also check if you experience any issues while viewing the following AIDA64 pages: - Commputer / Sensor - Motherboard / CPU - Motherboard / CPUID - Motherboard / SPD - Motherboard / Chipset

The log file is not re-created at each update, but only appended. That's why its header cannot be updated at each update. The stat file in contrast is re-created at each update, hence its header can be updated.

Does it hang on the Overclock page after it displayed "CPU Properties" line, so only that line is displayed on the Overclock page? Or is there any other lines displayed below that line before the hang happens, like "CPU Type" or "CPU Alias" ? Thanks, Fiery