Jump to content

owcraftsman

Members
  • Content Count

    24
  • Joined

  • Last visited

Everything posted by owcraftsman

  1. I can confirm it has been fixed with 5.95.4500 (stable) but it must be enabled. See image below for details.
  2. I have waited long enough been patient since June monitoring a couple threads here on the same issue. Rather than post in them like some others and be forgotten I issue this reset. I have a EVGA GeForce GTX 1080 Ti FTW3 ELITE GAMING BLACK, 11G-P4-6797-K2 Neither Aida64 ver. 5.92.4300 or 5.92.4391 Beta show 1/2 of the sensor data available through GPUz, Precision XOC or HWiNFO64 I saw it suggested in another thread where it works with Precision running and or newest Nvidia drivers. To be clear sensor data is missing whether Precision is running or not and the latest Nvidi
  3. With all due respect I tried exactly what you suggested 1st with no success I still could not get Adia64 Ex to start with windows. Currently I'm experimenting with not disabling UAC which I had done in the past since Vista immediately to avoid the hassel. It seems Windows has improved the interface because I have not been overly annoyed by it with either the upgraded version and my clean install version moreover I have not gotten the exceptions you refer to with Adia64 Ex enabled through registry and starting with windows. Eventually I will clean install W10 on this device but I offered this a
  4. There are few software programs I don't care to live without. One of them is Aida64 Extreme. I've been using it for the 20 years they've been around. Happy Anniversary! and here's to 20 more. cheers. After a recent upgrade to W10 x64 Pro from 8.1 Pro, Aida64 was no longer starting with windows automatically as I prefer. If this is you I have a fix. I tried many things to fix it, like uninstall> reinstall Aida64 Extreme, UN-tick the preference from Aida64 preferences dialog> then restart the tick it again and restart, adding it to the startup folder through RUN. shell:startup, disabl
  5. The way I did it the version that showed through the Aida64 > about > dialog was build 2706. It just revealed it self as a trial version vs the paid version. If you still think extracting it in to the aida folder would produce different results I will try that. The only real reason I didn't do that is I didn't want to loose all the time I've spent modifying the sensor panel. If I knew the way to back that up and restore ODS and Sensor Panel I'd be more inclined to give that a shot. There are two config files and a mem and manifest files all of which might need backing up just not sure ho
  6. Let me add that HWInfo64 has also corrected the issue of freezing with beta version 4.27.2040. The previous beta ver. with sensor panel open would freeze system when playing youtube video through browser and cpu core temp reports are still accurate as well.
  7. How do I install that there is no installer in the package Edit Okay I closed the current version 4.00.2700 then click on the application icon in the package you linked to and the trial version opened showing the 2706 build in the "about " appellate. Opened my browser and was able to play video from within it without a system freeze. However I will reiterate the same is true with the 4.00.2700 build where any of the 3.xx.xxxx builds the system will freeze when trying to stream a video from a browser. It appears the 2706 [trial version] has corrected the misreporting of haswell
  8. Not sure what of all the above worked I do know the most current edittion (4.00.2700) non beta has resolved the condition for me. Thanks a ton for all your effort and getting on top of this like you did.
  9. TY FIERY I will work on all the above and report back. There is aida, amd/ccc, Adobe flash and windows updates that I will perform 1st to see where it stands. From there I will log as best I can the results.
  10. Hello I'm here to report a bug with Aida64 v3.20.2656 beta. 1st the trouble: When I open anyone of three browser and attempt to play a video from youtube the system freezes when Aida64 and it's OSD is running. Only by using front panel reset or holding in the start buttom can I recover no amount of time resolves it. It happens overclocked and at optimized defaults. The same is true when running HWInfo64 > sensors The problem has left me with an unusable piece of software which I pay for yearly and have so for 8 or more years or before Aida took over. What I did to try a
  11. just an update I bought an Asus P8Z68-V Pro for testing I hooked up the same HDD w/windows on it from the MSI board other than the re-authorization widows requires all went well. When I run CPUz 1.58v on the new board I have no issue with aidia running which points to the MSI as the culprit of the issue. Still not sure if it's bios or drivers of MSI but the only difference was the mobo. I hope this helps.
  12. I'm in direct contact via email with Franck on this issue and offered a much help as I can which is not much. I certain they are working on it and will update here when the a final solution is found.
  13. Thanks for the link stasio. It's clear to me now that with this .ini edit CPUz is reporting VID but what does this mean. Do I have a defective sensor in this CPU? Is this problem limited to my setup only? Is it limited to MSI board? Why else would it hang when set Sensor=1? But this makes no sense because MSI "Control Center" & Aida64 seems to reads the vCore fine, at least it corresponds +/-.03v with what is set in the UEFI Bios. So the CPU Vcore is reporting which means I'm not sure what. I can only assume there is a problem with CPUz but I have not yet seen anyone else reporting the pro
  14. We I guess Im not positive I know shortly after I was ask to test the system using the Sensor=0 edit they sent me a CPUz.zi file to try and it didn't work so they are likely still working on it.
  15. The vCore & CPU Clock are displayed and changing as expected with turbo boost and EIST enabled. It hops back and forth between 1600 & 3400 .098v to 1.18v and cycles with regularity. All other reports seem correct as well and coincide with current hard sets in bios.
  16. Yes! I'm happy to report a work around for this issue provided by the developers. I'd like to thank them for quickly responding and getting on this issue for me and ultimately anyone else whom it has effected. If you edit the CPUz configuration settings changing the default "Sensor=1" to "Sensor=0" without the quotes of course it will fix this issue. This is the settings .ini found in the "Program Files" Folder on C:\. By saving this change it allows CPUz 1.58 to open and run normally while Aida64 is running. All tabs appear to be reporting correctly and the validation tool is working proper
  17. Today I was advised on the MSI HQ Forum by Global moderator Jack to try 1.56 and sure enough CPUz does start with Aida64 running using that version. Source:
  18. Unfortunately I don't seem to be getting any attention on this. If you know Franck would it be possible to bump him on my behalf. Any help appreciated TY
  19. I have relayed the suggestion here at the Canard PC Forum. Your effort is greatly appreciated!! I will update this thread when a resolution exist. TY Fiery
  20. I wish I could say that worked but it did not. I started by knowing CPUz worked with Aida 64 Extreme Ver 1.80.1450 uninstalled. Closed CPUz 1.8 Installed Aida 64 Extreme Ver 1.80.1450 Opened Aida and followed your instruction except I clicked apply before closing it and restarting my PC. After restart I opened Aida and enabled the OSD and setup as per-usual to start with windows. I then tried to open CPUz and the result is illustrated below. Edit: Please let me know if there is anything I can do to help resolve this issue.
  21. CPUz 157 & 158 fails to start freezes at initialization screen see capture below http://img827.imageshack.us/i/cpuznorun.jpg/ Things I have tried to correct the problem: Uninstalled deleted directories and reinstalled tried 157 & 158 32 & 64 Uninstalled/Reinstalled Chipset drivers Uninstalled Intel TPM Uninstalled Intel IME Uninstalled MSI Control Center Uninstalled Aida64 Uninstalled MSI Turbo Boost and all other MSI software Installed running as admin Manually added to AV allowed programs Set Full control to current user Ran as Admin and set to run as admin in prope
×
×
  • Create New...