Squall Leonhart
-
Posts
357 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Calendar
Posts posted by Squall Leonhart
-
-
There is no such security concern, the application run at user level permissions cannot perforrm any kernel level escalation, all it can do is read (and not write to) the aida64 driver.
-
I've put this towards a vanguard user to try and get a repro and then forward onto AMD, theres clearly an issue with a driver mutex or kernel memory corruption when the two software are paired that needs to be investigated from there end.
-
1
-
1
-
-
Your BSOD is caused by a defective CPU or cosmic waves, contact Intel for a replacement.
-
Sensor and GPU Sensor info latency is massive, report the issue to nvidia, I'll notify ManuelG of this thread and to be on the watch for the feedback.
https://forms.gle/kJ9Bqcaicvjb82SdA
You might also go further and perform the following
Use nsight to analyze your system for causes of hitching and stutters
https://developer.nvidia.com/blog/using-nsight-systems-for-fixing-stutters-in-games/Then follow on with these if it doesn't display a trigger or theres evidence the issue is in the nvidia driver.
Performance reports require the user to submit a gpuview or gpu-z log.How to generating an event trace log for GPUView to troubleshoot performance issues/low FPS/game stutter
https://nvidia.custhelp.com/app/answers/detail/a_id/3507/~/how-to-generating-an-event-trace-log-for-gpuview-to-troubleshoot-performanceCollecting GPU logs using GPU-Z
https://nvidia.custhelp.com/app/answers/detail/a_id/4749/extended logs can be put on a filestorage host like google drive and their share link mailed to driverfeedback@nvidia.com
For the LM78 sensor, disable EC (Embedded Controller) monitoring and iirc for this mainboard you turn Asus WMI on?
Your issue is basically caused by multiple utilities on the system hitting the same sensors at the same time which is neither a safe or performant thing to do.
Ie, don't run aida64 at the samet time as Hwinfo64, speedfan, corsair link etc.
-
1
-
-
These are listed as not supported on Processors that support either or both in some cases,
meanwhile HWInfo64 is logging the time the processor is in the C6 state just fine.
-
1
-
-
hi Fiery, I'm not on the affected platform but i can confirm that there are still users experiencing this in the wild.
See the users thread here on guru3D
https://forums.guru3d.com/threads/3700x-5700xt-crashs-everyday.436494/#post-5883244
Perhaps you might work with AMD to develop a safer API for their card interfaces?
-
By allowing the administrator account to set a persistent Start = 0x2 from within the Aida64 options, and change the task schedule to include the user account in the name of the Run at Startup task so multiple admins or users can choose to start it or not.
-
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
-
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.
-
Quote
Also, 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.
Please Explain: Asus ATK collision / sensors vanish when SpeedFan and Aida64 used together (Aisuite not installed, AsIO and ATK0 driver present)
in Hardware monitoring
Posted
I've seen it mentioned on a number of occasions that SpeedFan is safe to use with Aida64, however on Asus boards this isn't exactly the case.
When I have both running there is a high degree of chance that all the devices indicated to be accessed via ATK vanish.
Is aida64 and Speedfan accessing these via the ATK0 driver (ASACPI.sys)?
Systems in question are Rampage 3 and Rampage 4 extreme boards.