Squall Leonhart

I believe its a handle leak, memory use doesn't suddenly balloon and GDI count isn't excessive either.

use HKLM just affects where the settings are written to, if the shared memory or gadget stuff was at fault it wouldn't affect it. try running without shared memory and without the desktop gadget. actually, i have a feeling its specifically Shared Memory causing the problem due to a mismanaged constants buffer

the only likely explanation i can come up with is that when run in SLI, the 460 would only mirror the contents of the adapter output on each card and only display one instance of each port. Though i have 2 displays connected to my 275, so the appearance of 4 adapters on 600 series cards may be specific to kepler.

i run with the logitech lcd enabled, and i don't have this problem. do you also have the shared memory feature enabled Sora, or the desktop gadget?

which page are you leaving aida64 minimised on?

are you looking at the summary page?

in VS it says The thread tried to execute an instruction whose operation is not allowed in the current machine mode. in all dumps for this particular crash

mrgreywater, CoreTemp has the wrong TJmax for that cpu, the 65nm chips are 90 http://www.tomshardware.co.uk/intel-dts-specs,news-29460.html

No its not a bug, an adapter is displayed for each dvi/display/hdmi port on the card

randomly after a while. and like i said, just on Motherboard\Memory i can have any other views/lists open for weeks on end and it runs fine its actually the drive i have all my games installed on, and none of those crash (barring the odd game bug)

aida64 initiates a driver when run, requiring admin elevation.

the Tjmax for SB is 95c the Tjmax for IB is 105c as long as you keep below this point it should be safe.

Raid enumeration + IRSTe 3.2 or IRST 11.2 are required IRSTe is not available yet

i should mention, i've also seen this on other Intel systems, those being 2 Pentium dual core notebooks, and also on a amd laptop while sitting on the memory tab, so i can't really tell whats going on. Maybe whatever function to access the page file stats is tripping windows up eventually?

Complete removing the driver also requires some registry work, as the driver installs a lowerfilter that is not removable via the limited inf uninstallation capabilities

Usually about the 75% mark, windows starts to aggressively page out what it can in pre-empt of more memory being needed

Sometimes i forget to switch back to one of the other pages after looking at the current memory stats (i mainly use it to see how much the page file is loaded). I was thinking it may have been a general exception or virtual alloc leak, but windows event viewer reported something much much different. Now thats a strange thing to report. The drive its on is still present in the system, i can subsequently restart Aida64 immediately after this crash and simply changing from the Memory page to any one of the others will have it work fine for ever after. Do you have any Symbols i could use in windbg so i can attach the debugger and get a crash dump?

Hmm, that flashing thing is very similar to the low memory scenario i was describing. are either of the Paged pools using alot of memory on the performance tab?

indeed. a friend of mine had to mess with his radeon drivers because of the lack of edid causing issues with digital scaling.

Check for any of your apps having a higher amount of memory used in the Commit column vs the Working set column (Windows only displays private bytes by default, so both of these need to be enabled in the columns configuration in task manager) if the commit column is a fair bit higher, it means part of the process's memory usage has been paged out to disk the Memory page in aida64 will also tell you how much Pagefile is being utilised too.

try the new 11.2.0.1006 drivers sora also how much ram d oyou have? maybe when you're gaming the windows components are paged out and you get excessive disk thrashing after closing the game

having 2 applications accessing smart at once can cause lag and heavy DPC in my testing.

Its definitely a driver bug then, Fiery if you could forward Arctucas's findings to intel it might prevent 11.5 finally landing with critical bsod issues.

the gadget is compiled, a simple hex edit will not be enough to ensure compatibility.

try reproducing the issue against Crystal Disk info 5 alpha