Squall Leonhart

when its done, fiery will release a build with the additions mentioned in the change log.

Translated.

use the task scheduler for this, you can set it to shut down the app after the report is done, or to stop the existing task if a new process is to be started

266.35 and .44 are both broken drivers, anything over 4xAA and you will get white screens, TDR's and bsods.

System tools for nvidia and CCC includes the capability afaik,

i rarely get violations, but it usually occurs if my G15 becomes unplugged... if anything.

i would have to disagree with this... there is enough tools adjusting fan speed now as it is. hell the driver can do it by itself if people would dump their precisions and afterburners and install the required software/

then you don't read enough websites, the switching between performance states can trigger a dpc spike, and HPET itself increases its average level during use. another cause of high DPC is the current intel raid drivers.

might not even be AIDA, HPET and Intel's enhanced C states also cause dpc issues.

do you have easy tune installed? i believe that installs a service which maintains a driver running in the background. it will help fiery to know if that plays a part.

RPM's will not display on GT200 cards if aida is accessing the nvidia card via the driver.

gigabyte has a history of implementing sensors and hardware in a weird manner.

this could be another access via nvidia driver issue?

Aida uses the windows task scheduling on Vista and 7 to start at logon, however it uses the account of the user that configured Aida, you can go into the task scheduler and change the logon user any user in task scheduler

alot of intel's WHQL drivers never end up on the main page. but they get released through OEM sites and usually end up on station-drivers.

there were at the least, 2 updates a month in between though

WFM.

latency monitor actually displays the driver at fault, and has extended DPC information including a DPC amount counter. Excessive DPC activity is just as problematic as high dpc spikes. the driver used is also more recently updated then dpc latency checker.

which RST 10 are you using?

in my testing, DPC Latency checker can actually cause dpc spikes under recent versions of windows.

Latency Monitor, that screenshot is useless it doesn't indicate which driver the DPC spike is from.

post a screenshot of latencymon. there are no instances of dpc spiking caused by the aida driver in my system.

usually this is caused by an issue with the Interrupt Request assignments.

spinup occurs when disk activity is performed, querying smart does not require the head to move from the parked position.

the LCD manager has probably hung.