Squall Leonhart

Aida64 has worked on both v1 and v2 of the G15 since everest.....

@Fiery, - Is the nvidia NVAPI bugged again to be getting all these issues?

Update the Asus bios update the asus atk0 drivers update the intel drivers. This is not reproducible on my MOBO: ASUS Rampage II Gene CPU: Intel I7 920 (@3.8) Memory: 6 GB Corsair Dominator 1600 C8 Graphics: Evga 275 GTX OS: Windows Professional 7 64Bit (with SP 1) HDD: WD 500GB, 1TB, Samsung 1TB, Seagate 2.5" 500GB Keyboard: Logitech G15

or some updates to the tests i guess.

also, do not initialise aida64 while the card is loaded, it can hang the driver or cause a TDR (in the worst case). and although both apps should now be local mutex's, you should minimise the usage of both afterburner and aida64 at the same time.

next time, please consider searching. Disable Nvidia GPU Smbus access through nvidia forceware in the Stability config screen. if some stuttering remains after this also disable the multigpu fan access and gpu fan speed measurement. its a bug in the drivers it seems.

Arctucas, do you see any difference in the CPU tests? my cpuphotoworxx, zlib and aes results have increased as well

the selected VTT is not always the VTT being used. Asus boards seem to use less than the selected while evga uses more.

i guess theres a bug in nvidia's NVAPI again or something.

im trying to get a friend to replicate my findings, but so far the benchmark cache and memory tool doesn't seem to be affected by it, its only the benchmark module in the aida categories list. Arctucas reproduced otherwise, and my own testing follows his findings (note to self, don't report bugs after a 3 day stint of gaming) It was actually brought to my attention by a post @ http://www.xtremesystems.org/forums/showpost.php?p=4024584&postcount=8 Im not sure whether to conclude this as a bug in AIDA or a side effect of not being able to shut off cores bouncing the benchmark thread about. but yeah, i've sat there hitting refresh trying to get more than 16xxx once and the most i got was close to 17k, this change is a consistent 19xxx.

Just realised theres a 4GB/s reduction in the benchmark module with it disabled vs enabled, this is not reproducible in Sandra. i7 920 D0 @ 3.8Ghz / Corsair Dominator 1600 6GB.

works for me.

works as it should for me. tried not running it via xpmode?

i have not lost my SATA drives as well with the newest version either.

that could be it, i do have a 3d screensaver that runs while my system is locked. i'll wait and see if it happens again, it might be just a random 1 off.

I left my computer on overnight and came back to it having only 800MB free, when i left it was around 1.5-2GB free. completely exiting aida64 freed back up to 1.8GB's.

alright, it randomly crashes atleast once a day when left on the memory pane.

afaik, refresh just refreshes the currently known stats, it does not do a full repoll of the hardware.

So far, so good

im almost always on the latest beta , thers always something someone reports that could apply to my config, and yeah, i did have a USB hdd plugged in previously.

i don't think the oem's are accepting the boards for RMA until the fixed boards are in circulation.

Last night, the HDD's i set in the LCD Items or misconfigured themselves. Usually restarting AIDA resolves this, but i decided to take a look at the LCD config screen and found that the device assigned to that LCD item was not selected, and that one of the others had changed the drive it was assigned too. Only the HDD temps i assigned were affected. The only thing i could put it down to, was i had virtualbox running at the time. The temps themselves did not disappear from smart at all.

Potential fix for Intel Raid hitching on RST drivers. Note, there is a verified issue with Pioneer DVDR-212D optical drives with RST 10. http://www.station-drivers.com/forum/viewtopic.php?p=10484#10484

could work on a G15 as well, each page button switches between 2 tabs?

only the G15 LCD. And i have been running without problems while not leaving AIDA sitting on the memory pane. If i change it back to the Memory pane, it will eventually either crash or raise an out of thread resources error, and performance monitor will show that 111 threads are in use. Normal usage is 4 threads.