Jump to content

Squall Leonhart

Members
  • Content Count

    356
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Squall Leonhart

  1. Yep, system is in signature, Windows is 64bit. it was originally reported as affecting GPU Caps Viewer's OGL and OCL tests.
  2. I'm reporting this here because i know you have contacts in nvidia who can get a fix for this, The same hang occurs in GPU Caps viewer when closing a OGL/OCL test window in thread nvoglv32.DLL!DrvValidateVersion+0x7450 and is reported as also affecting Heaven Benchmark. The hang is resolved by terminating the instance of nvoglv32.DLL!DrvValidateVersion+0x7450 with no constant cpu usage.
  3. That is not the case, as if i terminate the aida64 process and start it again it will load without issue. This is only occuring since 2766 and higher. 2700 did not have this issue.
  4. what drivers and mainboard related software do you have installed
  5. wait.. what? Aida64 should always request permission to launch as it requires elevation (Task Scheduler being the only way to silence the uac prompt)
  6. Was this related to my post months and months ago about the smbus being hung by certain apps? (cpu-z being one of them)
  7. Every once in awhile with the latest beta version of Aida64, i am seeing it take a long time to create the tray icon and when it does so the icon is blank and does not open the GUI when clicked. on a bad start Stack looks like ntoskrnl.exe!KiSwapContext+0x7a ntoskrnl.exe!KiCommitThreadWait+0x1d2 ntoskrnl.exe!KeWaitForSingleObject+0x19f ntoskrnl.exe!KiSuspendThread+0x54 ntoskrnl.exe!KiDeliverApc+0x201 ntoskrnl.exe!KiCommitThreadWait+0x3dd ntoskrnl.exe!KeWaitForSingleObject+0x19f win32k.sys+0xcd8f7 win32k.sys+0xcd999 win32k.sys+0xe044e ntoskrnl.exe!KiSystemServiceCopyEnd+0x13 wow64cpu.d
  8. if your system is running properly, the LGS lcd driver and LGS software should be loaded before aida64 (aida64 operates on a delayed task schedule)
  9. Devices read via the Megatek megabattery driver seem to display what i assume is 2-2.5 their actual stats - atleast for the Charge rate. for example, the system in my sig, i doubt uses 340-350w at idle, and i highly doubt it uses 760w under load to necessitate equivalent charge rates. (a hx620 would OCP at around 730w when brand new, and mines not...) I expect that the charge value actually in this case also doubles as the current load value when not on battery, of which on my currrent ups (Upsonic ES 1500va/938w) my system loads it to about 14%, which is closer to 131w. Also, the
  10. GPU-Z can still crash(white/coloured screen) a Kepler GPU if opened along side Aida64, I've confirmed this first hand. HWMon can still crash a gpu (black screen or fan speed unreliable) if run along side aida64, precision, etc on Fermi gpu's (not sure about kepler).
  11. Is it running when you attempt to open Aida64?
  12. the lag comes from the CPU starving the graphics driver, so yes.
  13. I noticed in the new beta This has caused SM5/Dx11 hardware to be reported as SM4.1 / DX10.1. 3.00.2500 vs 3.00.2505
  14. AIDA64's benchmark utilises more of the entire cpu at any one time than the stability/benchmark utilities you mentioned.
  15. Thank you Fiery I don't see an option for it under Stability, so does it only get measured when a OSD or LCD has the related item enabled? edit: found it under Hardware Monitoring
  16. random modules, so its probably related to my thread, and possible throttle monitoring.
  17. Excellent, this improves the debug information generated as well i'll upload the dmp file in a little while
  18. It happens at any time in my case, possibly because i have Logitech LCD support enabled.
×
×
  • Create New...