Re: [Audacity-devel] (Windows 7) Runtime Error Program: (location) R6034 on launching Audacity.
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2010-03-20 20:33:07
|
| From Al Dimond <bus...@gm...> | Sat, 20 Mar 2010 11:10:10 -0600 | Subject: [Audacity-devel] (Windows 7) Runtime Error Program: (location) R6034 on launching Audacity. > On Saturday 20 March 2010 00:34:01 Gale (Audacity Team) wrote: > > Not 100% sure if this helps here, but I thought I should post. > > > > Using Win 7 x64, (only just got it, so not yet got round to > > updating via Windows Update) I grabbed a few zipped older versions > > of Audacity for reference. I got 1.3.3, 1.3.7, 1.3.8 and 1.3.11 > > Unicode Releases. All launched fine except 1.3.8. On executing it > > I had to wait a minute with nothing apparently happening except > > Avast! busily scanning. Then I get a system ding and a small error > > box "setup.exe cannot initialise resources". I OK'd that, but the > > error box came up another twice. On the third "OK" I get: > > http://www.gaclrecords.org.uk/R6034.png > > > > Is this happening during installation or when running Audacity? Or > when running Audacity at the end of installation? You mention > "setup.exe" in the last paragraph but then the linked image shows > "audacity.exe" (neither of those is actually the name of the > installer, of course... "setup.exe" could just be a hardcoded string > in the installer code). In spite of "setup.exe", this happens when launching Audacity itself, as it does with all the reports I've seen. In my case these were all zips (as I said), so I just unpacked, then double-clicked the program executable. > I've just read that more detailed information about Manifest errors > can sometimes be found in the System Event Log Viewer. Gale, can you > check that? You should be able to find the viewer by going to the > Control Panel and searching for "Event Log" in the upper-right search > bar, then clicking on the resulting "View Event Logs" link. Within the > log viewer I'm guessing you'll need to look under > "Windows Logs->Application" but I'm not totally sure about that. Here is what little appears under Windows Logs > Application (nothing relevant under "Setup" or "System"): Application error: Faulting application name: audacity.exe, version: 1.3.8.0, time stamp: 0x4a5e87a4 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x07100b4e Faulting process id: 0xca0 Faulting application start time: 0x01cac7f4853b0dc0 Faulting application path: E:\Audacity old\audacity-win-unicode-1.3.8\audacity-win-unicode-1.3.8\audacity.exe Faulting module path: unknown Report Id: 41a88484-33e8-11df-bbc9-0018f30bcd21 Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Windows error : Problem signature: P1: audacity.exe P2: 1.3.8.0 P3: 4a5e87a4 P4: StackHash_0a9e P5: 0.0.0.0 P6: 00000000 P7: c0000005 P8: 07100b4e P9: P10: Attached files: These files may be available here: C:\Users\Gale\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_audacity.exe_de551e8416ba59a874744a3f4ce1f3425b52f890_02420c2e Analysis symbol: Rechecking for solution: 0 Report Id: 41a88484-33e8-11df-bbc9-0018f30bcd21 Report Status: 0 I attach the file referenced above. > > I note I also get "Audacity has stopped working" at the end of it > > all, which is still reported even now when trying to launch. We > > usually assume this to be a sound device driver issue, but some of > > these on Win 7 could be R6034, but the user just reports the final > > error. > > > > Do you get the "Audacity has stopped working" error with all versions, > or just 1.3.8? Just 1.3.8. I launched 1.3.3, 1.3.7 and 1.3.11 Unicode Release without problem and ran them OK for a few minutes. Thanks Gale |