Page 1 of 2

Auggie Exception Errors on Startup

Posted: Mon Apr 10, 2017 3:41 pm
by ds463
Like most sticking points, if at first you don't unstick, ask someone else to lick the problem.
The problem: Auggie at startup throws an exasperation code 0, the attached dialog may not be readable.
I have Auggie installled on a Windows 10 machine. Tried compatibility mode of all flavors, and
reinstalled with win32.dlls. Same errors. The first error in the dialog is ntdll file is not available.
Tried running Auggie as administrator. Tried to turn off the debugger on Visual Studio 2015.
No Luck. Need a point in the right direction. Thanks. Dave

Re: Auggie Exception Errors on Startup

Posted: Mon Apr 10, 2017 9:32 pm
by BobL
Dave;

Is this an older pc? Can you post your system specifics so we can compare?  I also had issues with Auggie using my older WInXP 32bit, solution for me was to use a 2.5Ghz cpu or better, lots of ram and Win7 or greater. Hope this helps..

Cheers
Bob

Re: Auggie Exception Errors on Startup

Posted: Mon Apr 10, 2017 10:55 pm
by ds463
Nope, my laptop is a Levono Thinkpad, new last December, running Windows 10 Pro.
16 gig ram,  i7 processor, 2.6 gHZ.
I will send more details shortly.
Dave

Re: Auggie Exception Errors on Startup

Posted: Mon Apr 10, 2017 11:08 pm
by ds463
Here is the list of error messages in the issued at startup:
A:377842
C:c0000005
base:OnClose 002727D0
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00377842)

00377842 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0042AEF4)

0042AEF4 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0042AD09)

0042AD09 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0042AC55)

0042AC55 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00367F00)

00367F00 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00367EAB)

00367EAB (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0027043A)

0027043A (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00310963)

00310963 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00311E51)

00311E51 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0030D4AE)

0030D4AE (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0030DC7C)

0030DC7C (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 7749D2B3)

7749D2B3 (USER32): (filename not available): SetManipulationInputTarget

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 7747E88A)

7747E88A (USER32): (filename not available): DispatchMessageW

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 7747E4C0)

7747E4C0 (USER32): (filename not available): DispatchMessageW

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 77489910)

77489910 (USER32): (filename not available): InSendMessageEx

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 778308C6)

778308C6 (ntdll): (filename not available): KiUserCallbackDispatcher

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 77482E99)

77482E99 (USER32): (filename not available): CreateWindowExW

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 77482D38)

77482D38 (USER32): (filename not available): CreateWindowExW

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 6B81A64B)

6B81A64B (AcLayers): (filename not available): GetHookAPIs

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0031341F)

0031341F (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0030E9DD)

0030E9DD (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00360EA1)

00360EA1 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00361538)

00361538 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00371BA1)

00371BA1 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0041AB26)

0041AB26 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0035E615)

0035E615 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0035E592)

0035E592 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0041D3F7)

0041D3F7 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00314A54)

00314A54 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 003148A0)

003148A0 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0035EB45)

0035EB45 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 002619A4)

002619A4 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 004970ED)

004970ED (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 0046D475)

0046D475 (Auggie): (filename not available): cpSweep1DNew

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 771F62C4)

771F62C4 (KERNEL32): (filename not available): BaseThreadInitThunk

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 77820FD9)

77820FD9 (ntdll): (filename not available): RtlSubscribeWnfStateChangeNotification

ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 77820FA4)

77820FA4 (ntdll): (filename not available): RtlSubscribeWnfStateChangeNotification

Hope this helps.
Dave


Re: Auggie Exception Errors on Startup

Posted: Tue Apr 11, 2017 2:29 am
by ArtF
Hi Dave:

  Have you tried using a different start profile? Or does it do it with
any profile? Are you trying to start full out Auggie or just the vector
processor module from within Gearotic?

Art

Re: Auggie Exception Errors on Startup

Posted: Tue Apr 11, 2017 3:58 am
by ds463
  Have you tried using a different start profile? Or does it do it with
any profile?
Not sure what a start profile is, but I have tried to get Windows 10 to resolve compatibility issues. I have also tried to start Auggie in Windows 8 and 7 mode. Same error dialog.

Are you trying to start full out Auggie or just the vector
processor module from within Gearotic?
The vector processor module works within Georotic. I am trying to start full out Auggie to work with the PoKeys Controller.

Thanks much, Dave

Re: Auggie Exception Errors on Startup

Posted: Tue Apr 11, 2017 11:51 am
by ArtF
Dave:

  As the program starts up it asks for a profile name,  does it crash with any profile selected, or if a new
profile is created?

Art

Re: Auggie Exception Errors on Startup

Posted: Tue Apr 11, 2017 3:07 pm
by ds463
My previous attempts included creating a profile, opening an existing profile, and cloning a profile. This morning, I deleted all the profiles created before and named a new one. Same result. Crash with same messages.

I am no computer expert, (in my working days I employed folks to help out), but perhaps there is something to do with access privileges to the System32 directory. The first error messages look for ntdll, and then Kernel32. For these errors the "file name is not available".  The next errors look to Auggie, also the file name is not available. I am running windows defender for security. Perhaps is defender prohibiting calls to System32?

Just a SWAG. (Scientific Wild Ass Guess) Oh, the mysteries of Windows.
Dave

Re: Auggie Exception Errors on Startup

Posted: Tue Apr 11, 2017 5:59 pm
by ArtF
Dave:

Did it install to C:\Gearotic as the default calls for? Did you run the end section to install the VC support
files?

Art


Re: Auggie Exception Errors on Startup

Posted: Wed Apr 12, 2017 3:04 am
by ds463
Just to make sure, I uninstalled Gearotic and Auggie, then ran a fresh reinstall using the default directory (C:/windows/) and 32bit VC redistributables.
Same result. Gearotic runs fine, Auggie no.
I was able to get a debug message from windows when I clicked the "X" on the error window instead of "OK"
Attached is a screen shot.

Looking in the installed apps listing I see many VC++ x86 redistibutables.
VC++ 2008
VC++ 2010
VC++ 2012
VC++ 2013 - 1
VC++ 2013 - 2
VC++ 2017

Is Auggie looking at the wrong file?

Dave