Squall Leonhart
-
Posts
382 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Events
Posts posted by Squall Leonhart
-
-
On the Titan, the VRM also covers the Fan, thats why some users found when they cranked the fan higher they hit the GPU boost limit and it throttled.
-
i found myself getting these as well, in Event Viewer, iirc, you will find the a warning mentioning the crash was due to the process being unable to read the drive it is on
i found these to occur significantly less (or basically not at all) by always remembering to return to the power management bar before closing aida to the tray
-
Seems to be ok so far, I guess the dump file helped?
Edit
spoke too soon, same crashes still happening, and i can rule out the Asus AsIO and AsUpIO as well
-
I'm just wondering how this mainboard distributes the PCI-E slots
the Rampage II Gene for example has 3 1x slots and a pci slot on the ICH10 while the 2 16x and 1 4x slot are on the x58
I assume since the R3E is utilising the Intel GB NIC integrated in the ICH, that the freed 1x slot allows it to serve the 4x slot from the ich?
Fiery, if you have this information it would be helpful for how i distribute my pci-e cards when i move from this Gene to the Extreme
-
too bad official websites tend to offer drivers that are so out of date they corrupt your hdd's after a service pack (no joke)
-
i am not having any problems with the gaming software.
but im not using inferior versions of windows, so.
-
Yep, thats where i got that crash.
dmp file link in pm
-
Yup, i can't use any version of Aida64 that has throttle monitoring, i do remember suggesting that it could be an option under stability settings.
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: SRV*c:\symbols\win7_64*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Wed May 8 15:59:14.000 2013 (UTC + 10:00)
System Uptime: not available
Process Uptime: 0 days 0:16:54.000
................................................................
......
Loading unloaded module list
...................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2570.2d60): Unknown exception - code c0000096 (first/second chance not available)
eax=00000000 ebx=00000000 ecx=00003933 edx=00003932 esi=0043b728 edi=00000000
eip=007cf478 esp=ab8717aa ebp=007cf42a iopl=0 ov up ei pl zr na pe cy
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010a47
*** ERROR: Module load completed but symbols could not be loaded for aida64.exe
aida64+0x3cf478:
007cf478 656c ins byte ptr es:[edi],dx es:002b:00000000=??
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for LgLcdApi.dll -
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/aida64_exe/2_85_2440_0/2a425e19/aida64_exe/2_85_2440_0/2a425e19/c0000096/003cf478.htm?Retriage=1
FAULTING_IP:
aida64+3cf478
007cf478 656c ins byte ptr es:[edi],dx
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 007cf478 (aida64+0x003cf478)
ExceptionCode: c0000096
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: aida64.exe
ERROR_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
DEFAULT_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION
MOD_LIST: <ANALYSIS/>
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
FAULTING_THREAD: 00002d60
PRIMARY_PROBLEM_CLASS: STATUS_PRIVILEGED_INSTRUCTION
BUGCHECK_STR: APPLICATION_FAULT_STATUS_PRIVILEGED_INSTRUCTION
UNALIGNED_STACK_POINTER: ab8717aa
LAST_CONTROL_TRANSFER: from 00000000 to 007cf478
STACK_TEXT:
007cf42a 00000000 55007cf4 c38b49e8 89f88bff aida64+0x3cf478
FOLLOWUP_IP:
aida64+3cf478
007cf478 656c ins byte ptr es:[edi],dx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: aida64+3cf478
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aida64
IMAGE_NAME: aida64.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 2a425e19
STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb
FAILURE_BUCKET_ID: STATUS_PRIVILEGED_INSTRUCTION_c0000096_aida64.exe!Unknown
BUCKET_ID: APPLICATION_FAULT_STATUS_PRIVILEGED_INSTRUCTION_aida64+3cf478
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/aida64_exe/2_85_2440_0/2a425e19/aida64_exe/2_85_2440_0/2a425e19/c0000096/003cf478.htm?Retriage=1
Followup: MachineOwner
---------
-
the RT OSD server can detect the currently used directx version.
-
-
Ah, i was under the assumption that they hadn't allowed 2 lcd's because of the scenario you mentioned (2x mono lcd's) not working here.
-
This is a logitech limitation.
-
yeah, errors start with 2320 (Access Violation at address FFFFFF)
-
This appears to have been introduced in build recently,
though i can atleast trigger it manually in 2327 by opening the summary page
newer versions do it at random, with 2341 having the highest frequency.
I expect it may have something to do with the Logitech LCD driver, as others have mentioned before.
I don't get them with build 2300 and build 2313
-
after installing my new 680, with that setting disabled the display would glitch itself before correcting and displaying normally.
so it doesn't seem to result in a actual gpu crash in every case, hmm.....
switching it back on momentary glitch though
-
1
-
-
This sensor has never been present on aida64 with GTX 680's.
-
So you want to put your computer at a risk of instabilities, locking up the smbus, freezing the LPC bus, etc.
-
I know the performance data can be accessed through WMI, however i cannot remember which subinterface.
-
Yep, im going to try aida64 in the coming days, i don't have frequent access to a laptop with that chipset.
-
Hi Fiery, this isn't a bug report as so much a notification that i have experienced SMBus hangs using some tools on laptops with a synaptic touch pad on the device otherwise (without the synaptic driver installed) marked as Intel® 7 Series/C216 Chipset Family SMBus Host Controller - 1E22.
I can readily reproduce this with CPU-Z and other cpu-id tools that access the smbus on the notebook in question (Toshiba P850, but it has been indicated to affect others), but have not yet had the chance to try and reproduce it under aida64
-
306.23 didn't have such problems, though i know some people got it into theirheads that 306.97 did.
-
this could be similar to what i was reporting before on the Memory pane, Fiery.
-
what else do you run when aida64 is running?
-
never had it just stop working, ever.
Access Violation errors in Random modules (or no module mentioned at all)
in Bug reports
Posted
It happens at any time in my case, possibly because i have Logitech LCD support enabled.