Squall Leonhart
-
Content Count
349 -
Joined
-
Last visited
-
Days Won
3
Posts posted by Squall Leonhart
-
-
Why In the change notes do you have the T10-8 identified as a Geforce RTX, when this nomenclature is a Tesla part.?
TU102 T10 Generation 8 Tesla board.
-
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.
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.
-
QuoteAlso, after completing an Aida64 GPU stress test the LED turned red. I have a Corsair PSU and Aida reads stats about the PSU through Corsair link although I don't have the Corsair link software installed. Could this have been to blame? Restarting the PC fixed the issue.
-
yeah, there was an issue from 397.65 to 411.63.
-
what driver have you got installed?
-
-
On 8/29/2018 at 12:09 PM, birdgg said:I take your response that I shouldn't assume AIDA64 causing BSOD? I thought this is a bug reports forum and I was reporting a BSOD that is reproducible, if I can not report that I doubt why this forum ever exists. On the other hand, have you read all posts that concludes anything and would you shed some light?
Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.
-
On 8/21/2018 at 12:22 AM, vabchgent said:So I have this Blue screen and it points directly at AIDA 64 . It only happens when my monitor is in sleep mode, am I in the right place. looks like it is being worked on and may be a Nvidia problem. Just making sure I am following.
CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x1E
PROCESS_NAME: aida64.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
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.
On 8/23/2018 at 4:41 AM, adriant42 said:Hi Fiery,
I tried Google but could not locate a forum/announcement that talked specifically about the BSOD monitor power management issue. I would like to keep track of this issue to see if there has been a fix. Do you happen to have a link that you can share?
Thanks!
There is no announcement.
12 hours ago, birdgg said:Hi Developers,
I saw this thread yesterday and was hoping the beta version will address the BSOD that I've experienced. However I got a BSOD in about 1 hour, I wasn't very sure that the BSOD in my case was relating to Windows 10 update that has been mentioned in other posts in this thread but what I can be sure is that whenever I have my computer idle with AIDA64 running, I will get BSOD within 1-4 hours. I'm not very sure what to provide to keep this issue on track but here's some basic information of my system and hopefully this can be fixed in coming stable version update.
MB: Asus B350 prime plus
CPU: Ryzen 1600
SSD: Samsung Sm961 and Evo 850
VGA: Nvidia GTX 980 TiYou 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.
New development!
Remember about aida64 and nvidia timer conflict? well i tried one thing, i changed "turn off monitor" option to never and guess what? for 3 days i didn't have BSOD-s so it was perfect, but last night i changed option to 20 miuntes, and guess what, during the night it had 5 BSOD-s after monitor was going off now explain me wtf is going on because i can't , i mean WTF!!
-
On 7/15/2018 at 12:36 PM, HeavyHemi said:I can confirm they are not gone. I will get a KMODE exception every single time if I forget and don't close AIDA64.
X99 FTW K 6850K
1080 Ti
Win10 1803 all updated and stable as a rock except for this. I've been paying for AIDA for nearly a decade. I'd hate to stop using it because of this. So..right now my paid until 1/30/2020 license is kinda useless. Long Live Lavalys
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.
QuoteNew development!
Remember about aida64 and nvidia timer conflict? well i tried one thing, i changed "turn off monitor" option to never and guess what? for 3 days i didn't have BSOD-s so it was perfect, but last night i changed option to 20 miuntes, and guess what, during the night it had 5 BSOD-s after monitor was going off now explain me wtf is going on because i can't , i mean WTF!!
-
They aren't gone, they weren't readily reproducible in the first place.
-
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.
-
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.
Why is a Tesla board listed as a Geforce in the change notes?
in General Discussion
Posted · Report reply
I see, well that would have to be a placeholder name, because the product is the Turing version of the Tesla T10 as shown running here