Squall Leonhart

The black screen is a very rare occurence, but the fan pwn polarity reversing tends to occur without much playing with, I once forgot i had gpu-z running and my GPU Fan' reversed pwm polarity while playing HL2 and the fan jumped up to 100% because the temp hit 100c, as the fan was running at 0 RPM. I was running Orbu2k's GPU Observer earlier and my fan reversed, last thing i saw before black screen was 100% @ 100RPM on LCD display and i got a black screen while doing some light gpu usage in a Flash video. I'm thinking the multiple sensors are causing the driver to crash without recovery. from what i've observed this issue is only likely to occur if both apps can monitor the gpu fan, since i used to run speedfan alongside Everest just fine for fan speed controlling, and speedfan can display GPU temps (in builds of speedfan that don't display gpu fan speed, 4.41) Other users have experienced this with Precision/Rivatuner vs Hardware Monitor/Everest (and now AIDA64) My configuration is a i7 920, Asus Rampage II Gene, EVGA GTX 275, Auzen Prelude 7.1, with 6GB of ram. that said, its perfectly fine when Aida or the other apps are run by themselves, but since people tend to like setting up fan configurations in afterburner and monitoring fps with precision/afterburner, etc its a bit of a problem when the gpu fan glitches out. Basically what im asking is if the access to the fan controller can be made a little bit more safer.... actually i was messing with nvidia system tools device rule awhile back to set up a custom fan scale and that would glitch up as well while everest was running (haven't tried in aida64) From what i've gathered the problem can occur when run along side GPU-Z Nvidia Inspector (or Orbu2k's GPU Observer Gadget which afaik just connects to the Ntune component in system tools) Afterburner, Precision or Rivatuner HW Monitor Nvidia System Tools

DO NOT use furmark to find stability. It is not a practical method and rarely ever finds a stable configuration. Play some shader and texture heavy games instead.

thanks, fixed

Task scheduler can be set to start the process without logging on.

1) Windows variant? 32-bit or 64-bit kernel? Windows 7 x64 2) Intel storage drivers version? 10.0.0.1046 WHQL, 10.0.0.1043 Beta, ICH10R (x58) 3) Disk drives configuration? Any RAID arrays defined? 3 Sata II drives in AHCI, no raid. 1 External via USB (detected instantly) 4) AIDA64 version and build number? Extreme Edition 1.00.1123beta I experienced this under Everest Ultimate v5.50.2253beta as well after installing the ISRT 10.1043 beta drivers, and it continues in whql drivers under AIDA64. The strange thing is, that the smart information is available immediately including the Temperature value. If i disable Low Level Smart access, the sensors are visible from the start, but the value for the External drive is gone.

I've noticed both in the previous everest and current AIDA64, that the latest intel storage drivers are causing the temp sensors to take longer to show up in Aida64(watching the LCD panel). Could be related to the SMART improvements that are rumoured to be in the driver, but was thinking maybe there was some way you could speed it up?.

should've posted this under brainstorming i guess.

Run at startup registers the app to the NT6 task scheduler which provides automatic elevation. None of your listed problems are reproducible.

on multicore chips, not all cores increase their clockrates/multipliers at once, currently AIDA64 only displays the Core clock and multiplier of the entire chip(single core?), when infact each Core (and even hyperthreads) can use individual seperate clock rates. the behavior im suggesting is like that of CPUID's Tmonitor (-T to display clockstates of hyperthreads).