Jump to content
AIDA64 Discussion Forum

Squall Leonhart

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Squall Leonhart

  1. Squall Leonhart

    Add Current Dma Mode To The Ata Pane

    I've been looking through Aida, and can't seem to see the current DMA setting on each drive.
  2. Squall Leonhart

    nvidia display bug?

    This is resolved by 417.71+
  3. Squall Leonhart

    Add Current Dma Mode To The Ata Pane

    Something strange with AIDA64's support of this. It seems aida64 lacks the active udma field on some drives declaring them to be running in MWDMA 0 or 2, meanwhile HDD Scan and HD Tune both agree that the current active mode is UDMA6 for those drives, and buffered read tests come back as expected.
  4. yeah, there was an issue from 397.65 to 411.63.
  5. what driver have you got installed?
  6. Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.
  7. it doesn't point directly at anything. otherwise it would be FAULTING_PROCESS: Nvidia has made no mention of whether they have reproduced the issue with the reproduction steps so far. There is no announcement. You should read all posts within a thread before assuming something. There will not be a fix for this bsod coming from Fiery's side.
  8. Squall Leonhart

    Page file details may randomly glitch

    during extended aida64 usage, the page file details in the memory section may double up the info displayed... for instance, it displays the used/max items twice.
  9. Spectre patch reduces this benchmark.
  10. Squall Leonhart

    FPU VP8 not using 100% of CPU

    the spectre patch is not responsible for the util issue here, the effect of the patch halves performance of fpu vp8.
  11. It's not really Fiery's fault, but there some new information Re the cause It was a bit premature to mark this thread fixed just because an issue with 1803 was found and worked around, some of us are not even on Win10.
  12. They aren't gone, they weren't readily reproducible in the first place. https://forums.geforce.com/default/topic/1061921/geforce-drivers/announcing-geforce-hotfix-driver-398-46/post/5833546/#5833546
  13. Testing 4652 under 17134, none of the clocks under Overclock update, everything under CPU Speed is now a static number I'm creating a feedback so Microsoft can follow up and implement a safe mutex for accessing the timer, Microsoft shouldn't be adding unsafe 'features' that cripple existing utilities. https://aka.ms/AA1ovm3
  14. As much as nvidia cannot reproduce it, im still convinced it is a driver bug, i've seen it reported with users running evga precision, kombustor, aida64, gpu-shark a combination of aida64 and gpu shark running at the same time brought it on in 4 days, aida64 alone a week. Considering this rides on the tail of nvidia fixing the GDI leak, its suspicious. Testing 4652 under 17134, none of the clocks under Overclock update, everything under CPU Speed is now a static number
  15. Don't mix up the issues Fiery, this bsod is occuring on 7 and 10 16299+17134
  16. Start command prompt in admin mode Execute the following command: verifier /standard /driver nvlddmkm.sys If you haven't already enabled for kernel dump, Could you please follow the steps here: http://mywindowshub.com/how-to-configure-windows-10-to-create-dump-files-on-bsod/ and enable "Kernel memory dump" under System failure region Reboot the system Get a repro Zip dump and upload it on google drive, mail a share link to driverfeedback@nvidia.com
  17. Squall Leonhart

    ASUS ROG Maximus X Code fan sensors missing

    never e ver keep corsair garbage link open, it is not a safe or stable program.
  18. nvidia are still claiming no repro, so i think they are missing a particular configuration requirement to bring it out. They might need one of our cfg files and sensor panels or whatever
  19. Yep, the point was interaction with the driver is necessary.
  20. Squall Leonhart

    What is nvidia even doing :|

    r397 fixes one thing and breaks everything else on windows 7, any sensoring app you open leaks GDI objects Aida64 included (as of 397.55)
  21. This issue is occurring in the nvidia kernel driver, your isn't hasn't been fixed its just gone into a really random occurance cycle. A process cannot cause a bsod, a driver would have been flagged that was loaded by the process but it might be wrong too (as different utilities can be more or even less correct about analysing dump files with the symbols available. 397.55 or earlier are not affected by this, so if you're on 397.64 or .93, theres your culprit.