Squall Leonhart

No, that didn't seem to work. I found why though, devices on the ASUSTOR driver are treated as a Raid device, so RAID Smart needs to be enabled.

Easy, here you go. The drive is currently on the ASUS UASP driver, but Smart was also missing on the mass storage driver, regardless both could pass through smart to Crystaldisk, and I can also see the data in HD Tune, SSD-Z, etc. diskctrldump.txt raiddump.txt smartdump.txt I also have a cable based on the ASM1351 on order so i can get trim working on this ssd, so i'll likely be back with dumps for that too after it arrives lol.

Hey Feiry, i grabbed a UASP sata 3 adapter cable produced by startech it uses the ASMedia - ASM1153E https://www.startech.com/au/HDD/Adapters/USB-3-SATA-adapter-cable-with-UASP~USB3S2SAT3CB Aida64 is unable to pull smart data from the drive attached, but CrystalDiskInfo has no such problem. Need a dump to add support? if so which ones.

Fiery, the feature this user wanted is possible. The drive itself can report what SATA mode it is in, but not all do so and seems more likely when the Drive is Sata Rev3 / 6Gb with some exceptions being ODD's The utility SSD-Z implements it. Attached to Intel ICH10 sata Attached to Marvel SATA 6G Attached to JMI E-Sata

Interestingly enough, the fields are now visible, seems that this information is not presented by hotplugged drives?

This is resolved by 417.71+

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.

yeah, there was an issue from 397.65 to 411.63.

what driver have you got installed?

this might be fixed in 411.63

Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.

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.

Spectre patch reduces this benchmark.

the spectre patch is not responsible for the util issue here, the effect of the patch halves performance of fpu vp8.

Try disabling screen power management.

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.

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

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

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

Don't mix up the issues Fiery, this bsod is occuring on 7 and 10 16299+17134

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

never e ver keep corsair garbage link open, it is not a safe or stable program.

Totally different problem.

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