Jump to content
AIDA64 Discussion Forum

Squall Leonhart

  • Content count

  • Joined

  • Last visited

  • Days Won


Squall Leonhart last won the day on February 10 2013

Squall Leonhart had the most liked content!

Community Reputation

1 Neutral

About Squall Leonhart

  • Rank
    Advanced Member
  • Birthday 12/31/1986

Contact Methods

  • MSN
  • Website URL
  • Yahoo

Profile Information

  • Gender

Recent Profile Visitors

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

  1. Spectre patch reduces this benchmark.
  2. 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.
  3. Try disabling screen power management.
  4. 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.
  5. 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
  6. 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
  7. 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
  8. Don't mix up the issues Fiery, this bsod is occuring on 7 and 10 16299+17134
  9. 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
  10. 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.
  11. 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
  12. Yep, the point was interaction with the driver is necessary.
  13. 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.
  14. https://forums.evga.com/FindPost/2823774