Jump to content
AIDA64 Discussion Forum

Squall Leonhart

Members
  • Content Count

    349
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Squall Leonhart

  1. looks like you need to run some form of converter on the bios before installing 2002
  2. the only time avg really worked properly was when it identified itself as a virus
  3. false positive, typical of avg's god aweful antivirus
  4. its a fault in the amd ahcidrivers install the Catalyst 12.6 SB driver
  5. It is true that the single core turbo multiplier requires C state tech, but in my case, its not related When a user sets a multiplier under the stock multiplier, the cpu will always run at that multiplier. I found my asus bios tended to jump to 22x single core turbo at times even when i had turbo boost off and the cpu set to 20x, and 4Ghz was needing to much voltage. in my case, my clock rate is attained from 200x19x. 20x is the normal multiplier for this processor, with turbo being 21x(all cores) and 22x(single core). My CPU is always at 3800mhz regardless of c-state tech (with high performance profile set) so the turbo ratio is not applicable here I have heard another theory about this which sounds more likely. Nahalem was designed with a quad channel partition in mind, but the consumer level parts are Tri channel only. When the cpu is completely awake, 2 of the cores fight over dram latching and result in a slightly reduced throughput. When the cores are able to enter the c state, only the currently active cores attempt to latch and higher throughput is obtained. This doesn't explain why SBE throughput is not improved with C State tech however.
  6. still reproducing a crash, took a big longer this time i think, i would blame my system, if it weren't for the fact it occurs on the other 64bit laptops i have around here
  7. that was a massive amount of GDI objects, xD, its no wonder it wouldn't open and caused the event viewer to be so sluggish hope its fixed in this new beta
  8. Yes, its normal AIDA64 has a small enough footprint that being paged out wouldn't really affect performance. that handle count isn't showing what i expected it would though. how many GDI objects are there after gaming?
  9. Yes, thats normal. even with DWM off the gpu is used for GDI acceleration.
  10. I believe its a handle leak, memory use doesn't suddenly balloon and GDI count isn't excessive either.
  11. 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
  12. 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.
  13. 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?
  14. which page are you leaving aida64 minimised on?
  15. are you looking at the summary page?
  16. 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
  17. 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
  18. No its not a bug, an adapter is displayed for each dvi/display/hdmi port on the card
  19. 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)
  20. aida64 initiates a driver when run, requiring admin elevation.
  21. the Tjmax for SB is 95c the Tjmax for IB is 105c as long as you keep below this point it should be safe.
  22. Raid enumeration + IRSTe 3.2 or IRST 11.2 are required IRSTe is not available yet
  23. 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?
×
×
  • Create New...