I just don't get it. This error keeps coming back and I'll start in safe mode and eventually only load the plugins that don't crash. Once it opens successfully, I save the project thinking that that will solve the problem. The project will either open about 20% of the time with no problem, or hang indefinitely, or give the guitar rig 3 crash error. Is there a limit to how many instances of a plugin you should have? It's just tempermental at best.
Here is the crash error:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Description:
Faulting application sonarpdr.exe, version 16.0.2.243, faulting module guitar rig 3.dll, version 3.1.1.10, fault address 0x00253d33.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 6f 6e ure son
0018: 61 72 70 64 72 2e 65 78 arpdr.ex
0020: 65 20 31 36 2e 30 2e 32 e 16.0.2
0028: 2e 32 34 33 20 69 6e 20 .243 in
0030: 67 75 69 74 61 72 20 72 guitar r
0038: 69 67 20 33 2e 64 6c 6c ig 3.dll
0040: 20 33 2e 31 2e 31 2e 31 3.1.1.1
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 32 35 set 0025
0058: 33 64 33 33 0d 0a 3d33..
And this is when it hangs:
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 10/25/2008
Time: 2:53:22 AM
Description:
Hanging application SONARPDR.exe, version 16.0.2.243, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 53 4f 4e 41 52 50 SONARP
0018: 44 52 2e 65 78 65 20 31 DR.exe 1
0020: 36 2e 30 2e 32 2e 32 34 6.0.2.24
0028: 33 20 69 6e 20 68 75 6e 3 in hun
0030: 67 61 70 70 20 30 2e 30 gapp 0.0
0038: 2e 30 2e 30 20 61 74 20 .0.0 at
0040: 6f 66 66 73 65 74 20 30 offset 0
0048: 30 30 30 30 30 30 30 0000000
I have no clue what I could be doing wrong. Obviously, the program is going to be useless to me if this is how it is going to behave. I'm really going to be ticked if I get deep into a project and then this kind of thing happens and all the work is compromised. I'm in a "problem solved! --> wait, now the problem is back for some reason" loop. Is there any kind of explanation of this issue anywhere? I can't find it and I'm totally clueless and losing faith. (I don't want to be that customer)
As far as system, I'm running XPsp2, 2 GB RAM, Athlon 64 3200+ 2.0 GHz so it should be able to handle this, I assume.
post edited by mirk - 2008/10/25 14:37:53