Fyew-jit-tiv Posted January 10, 2011 Share Posted January 10, 2011 Hi Fiery, Just re-installed system and installed latest Beta version and every time i launch or try to do something in Aida i get this message popping up (See Attached file) Question... Do you still have the same guys who worked Everest working on Aida? The reason why i ask is personally i have never experienced this amount of problems with Everest as i do with Aida. In fact for the 2 yrs I'd been using Everest i only remember contacting you once for a problem. In the last few weeks i have had nothing but problem after problem with Aida. Kinda feels like you got new people working on the software. Anyways let us know what you think about this new problem, I have installed Aida on a new OS install with no third party software. Regards Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 10, 2011 Author Share Posted January 10, 2011 P.S Here is another problem when i try to quit the program. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 10, 2011 Share Posted January 10, 2011 We have the same development team. You seem to be reporting issues that noone else finds, so I suspect it could be due to either some pecularity with your system configuration, or an extreme overclocking, or due to improper drivers installed, or ... I have no idea Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 10, 2011 Author Share Posted January 10, 2011 LOL...! Maybe its because i use my systems intensively, I work on these comps every day Fiery and i can assure you my comps run in tip top condition.. Maybe i should become one of your Beta testers seeing as I'm always finding something. Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 10, 2011 Author Share Posted January 10, 2011 Some info i have take from the event viewer Faulting application name: aida64.exe, version: 1.50.1219.0, time stamp: 0x2a425e19 Faulting module name: aida64.exe, version: 1.50.1219.0, time stamp: 0x2a425e19 Exception code: 0xc0000005 Fault offset: 0x0000452c Faulting process id: 0xe4c Faulting application start time: 0x01cbb103e8a994a0 Faulting application path: C:\Program Files (x86)\FinalWire\AIDA64 Extreme Edition\aida64.exe Faulting module path: C:\Program Files (x86)\FinalWire\AIDA64 Extreme Edition\aida64.exe Report Id: f862be54-1cf8-11e0-afc3-20cf308c267f - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-01-10T20:34:07.000000000Z" /> <EventRecordID>14581</EventRecordID> <Channel>Application</Channel> <Computer>HomeServer-PC</Computer> <Security /> </System> - <EventData> <Data>aida64.exe</Data> <Data>1.50.1219.0</Data> <Data>2a425e19</Data> <Data>aida64.exe</Data> <Data>1.50.1219.0</Data> <Data>2a425e19</Data> <Data>c0000005</Data> <Data>0000452c</Data> <Data>e4c</Data> <Data>01cbb103e8a994a0</Data> <Data>C:\Program Files (x86)\FinalWire\AIDA64 Extreme Edition\aida64.exe</Data> <Data>C:\Program Files (x86)\FinalWire\AIDA64 Extreme Edition\aida64.exe</Data> <Data>f862be54-1cf8-11e0-afc3-20cf308c267f</Data> </EventData> </Event> Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 10, 2011 Share Posted January 10, 2011 Thanks. Does the exception come up if you simply start AIDA64 with no hardware monitoring features (so Sensor Icons, LCD, OSD, Sidebar, Ext.Apps) enabled? Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 10, 2011 Share Posted January 10, 2011 i rarely get violations, but it usually occurs if my G15 becomes unplugged... if anything. Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 10, 2011 Author Share Posted January 10, 2011 Funny you ask that cause i was just checking to see what maybe causing it... It seems to be happening when OSD is activated. Im also getting display driver crashes too. Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 11, 2011 Author Share Posted January 11, 2011 Hi Fiery, with latest beta I'm unable to use with this system. Its seems to be interfering with the nVidia forceware driver (266.35), constantly getting a driver display crash with this beta version installed. the following info is taken from the event viewer based on the display crash. Hope this info helps. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Display" /> <EventID Qualifiers="0">4101</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-01-10T22:31:54.000000000Z" /> <EventRecordID>52287</EventRecordID> <Channel>System</Channel> <Computer>HomeServer-PC</Computer> <Security /> </System> - <EventData> <Data>nvlddmkm</Data> <Data /> </EventData> </Event> Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 11, 2011 Share Posted January 11, 2011 That seems like a ForceWare issue, and not an AIDA64 bug. Have you tried with the latest WHQL ForceWare driver? Have you tried ForceWare 266.44? BTW, what version of Windows do you have installed? 64-bit Windows 7 SP1 RC? Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 11, 2011 Author Share Posted January 11, 2011 Neither 266.44 or 266.35 are whql. and as far as I'm aware 266.44 is not an official nVida beta release not via there website anyways. only using win7 64. If i go back to version 1.50.1212 all is running OK. Soon as i run the latest beta i get this Violation & Display driver problem.! Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 11, 2011 Share Posted January 11, 2011 We've tested it with ForceWare 266.35 and GTX295, under Win7 64-bit SP1 RC. We've found no issues at all. Please try it with the latest WHQL ForceWare driver as well, or try to re-install ForceWare 266.35. Also, you may try to switch the option "nVIDIA GPU SMBus access through nVIDIA ForceWare" in AIDA64 / main menu / File / Preferences / Stability. Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted January 11, 2011 Share Posted January 11, 2011 266.35 and .44 are both broken drivers, anything over 4xAA and you will get white screens, TDR's and bsods. Quote Link to comment Share on other sites More sharing options...
Fyew-jit-tiv Posted January 12, 2011 Author Share Posted January 12, 2011 266.35 and .44 are both broken drivers, anything over 4xAA and you will get white screens, TDR's and bsods. Fully aware of that.. But seeing as i dont use my comps to run games it doesnt effect me.! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.