Jump to content
AIDA64 Discussion Forum

Squall Leonhart

Members
  • Content count

    327
  • Joined

  • Last visited

  • Days Won

    2

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
    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. Don't mix up the issues Fiery, this bsod is occuring on 7 and 10 16299+17134
  2. 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
  3. 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.
  4. 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
  5. Yep, the point was interaction with the driver is necessary.
  6. 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.
  7. https://forums.evga.com/FindPost/2823774
  8. Squall Leonhart

    AIDA64 and Aorus Graphics Engine doesn't work

    Gigabyte are using a nasty mutex access, as usual :\
  9. Squall Leonhart

    Asrock X370 Taichi Fan Spin Up Bug

    oh, there is previous feedback
  10. Driver feedback to https://surveys.nvidia.com/index.jsp?pi=6e7ea6bb4a02641fa8f07694a40f8ac6 dump file to driverfeedback@nvidia.com
  11. Squall Leonhart

    Asrock X370 Taichi Fan Spin Up Bug

    you are mixing system management utilities.
  12. dump file must go to nvidia and feedback provided with system details, this is an nvidia driver bug. PS: it comes up as being in ntkrnlmp.exe here, all changes based on the application scanning the dump.
  13. Turn hpet on, This is a platform bug where timers slowdown after resuming from sleep.
  14. Squall Leonhart

    Page file details may randomly glitch

    This topic involved a crash in the application that occured when it was left on that page of aida64, this has been fixed for a long long time now. PS: Don't turn off the page file, windows can't do some things with one turned off, such as allocate large virtual blocks (whether it intends to fill them or not). Set a Min/Max pagefile instead.
×