Jump to content
AIDA64 Discussion Forum

Squall Leonhart

Members
  • Content Count

    342
  • Joined

  • Last visited

  • Days Won

    3

Squall Leonhart last won the day on September 25 2018

Squall Leonhart had the most liked content!

Community Reputation

2 Neutral

About Squall Leonhart

  • Rank
    Advanced Member
  • Birthday 12/31/1986

Contact Methods

  • MSN
    danialhorton@hotmail.com
  • Website URL
    http://vba-m.com
  • Yahoo
    squall_leonhart86r

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Squall Leonhart

    nvidia display bug?

    This is resolved by 417.71+
  2. 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.
  3. yeah, there was an issue from 397.65 to 411.63.
  4. what driver have you got installed?
  5. Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.
  6. 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.
  7. Spectre patch reduces this benchmark.
  8. 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.
  9. 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.
  10. 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
  11. 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
  12. 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
×