Subject:Does this crash occur for anyone else?

Posted by: groovyone

Date:4/30/2008 11:18:34 AM

I'm using SF9.0c at the moment, simply because SF9.0e or SF9.0d won't install.

Open up a wav file - 1 second long from local harddrive.

Using Sony Pitch Shift - Pitch sound up 22 semitones - click OK
Select the first 200miliseconds and delete.
Select the first 300miliseconds and fade in (using fade tool in tool bar)
Without selecting anything, click normalize tool in tool bar - CRASH.

This is just one of many really simple operations which just hangs SoundForge 9 for me. I'm not using any external plug-ins at all to do these operations.

Same thing happens on a mix paste.

And occassionally on Save.

I don't quite understand how these core functions can cause such unstability.

DUMP FROM SAVE:

Sony Sound Forge 9.0
Version 9.0c (Build 405)
Exception 0xC0000005 (access violation) READ:0x40000000 IP:0x40000000
In Module 'Forge90.exe' at Address 0x0 + 0x40000000
Thread: GUI ID=0x125C Stack=0x12F000-0x130000
Registers:
EAX=014ca700 CS=001b EIP=40000000 EFLGS=00210206
EBX=00000000 SS=0023 ESP=0012fa54 EBP=00000000
ECX=00630047 DS=0023 ESI=012eb860 FS=003b
EDX=40000000 ES=0023 EDI=012eb8b8 GS=0000
Bytes at CS:EIP:
40000000: .. .. .. .. .. .. .. .. ........
40000008: .. .. .. .. .. .. .. .. ........
Stack Dump:
0012FA54: 0053FB37 00400000 + 13FB37 (Forge90.exe)
0012FA58: 014CA700 013D0000 + FA700
0012FA5C: 00000000
0012FA60: 012EB860 012D0000 + 1B860
0012FA64: 002F08EA 002C0000 + 308EA
0012FA68: 012EB860 012D0000 + 1B860
0012FA6C: 03850336 03040000 + 810336
0012FA70: 00000017
0012FA74: 00000001
0012FA78: 00000019
0012FA7C: 00000011
0012FA80: 00000001
0012FA84: 00000007
0012FA88: 00000008
0012FA8C: 00000009
0012FA90: 0012FB6C 00030000 + FFB6C
> 0012FA94: 5AD7DAF9 5AD70000 + DAF9 (uxtheme.dll)
> 0012FA9C: 5AD73CD0 5AD70000 + 3CD0 (uxtheme.dll)
> 0012FAB0: 5AD73C92 5AD70000 + 3C92 (uxtheme.dll)
> 0012FAE8: 7E41BE1C 7E410000 + BE1C (USER32.dll)
> 0012FAF0: 00435FD0 00400000 + 35FD0 (Forge90.exe)
0012FAF4: 002F08EA 002C0000 + 308EA
> 0012FAF8: 004360A3 00400000 + 360A3 (Forge90.exe)
0012FAFC: 00000004
0012FB00: 00000003
0012FB04: 00000004
0012FB08: 00000002
> 0012FB24: 7E41EB1E 7E410000 + EB1E (USER32.dll)
> 0012FB3C: 1600E2E5 16000000 + E2E5 (events.dll)
> 0012FB54: 7E431913 7E410000 + 21913 (USER32.dll)
> 0012FB68: 7E41EB1E 7E410000 + EB1E (USER32.dll)
> 0012FB80: 74730E6C 74720000 + 10E6C (MSCTF.dll)
> 0012FB90: 74730E71 74720000 + 10E71 (MSCTF.dll)
> 0012FBB4: 7475E548 74720000 + 3E548 (MSCTF.dll)
> 0012FBB8: 74730E78 74720000 + 10E78 (MSCTF.dll)
> 0012FBC0: 74730E71 74720000 + 10E71 (MSCTF.dll)
> 0012FBC4: 7E41EAD2 7E410000 + EAD2 (USER32.dll)
> 0012FBE0: 7E41EA7E 7E410000 + EA7E (USER32.dll)
> 0012FBF0: 7E41EA8D 7E410000 + EA8D (USER32.dll)
> 0012FC0C: 7E440477 7E410000 + 30477 (USER32.dll)
> 0012FC10: 7E41EA90 7E410000 + EA90 (USER32.dll)
> 0012FC18: 7E41EA8D 7E410000 + EA8D (USER32.dll)
> 0012FC1C: 7E41EBD3 7E410000 + EBD3 (USER32.dll)
> 0012FC28: 7E41EBE3 7E410000 + EBE3 (USER32.dll)
> 0012FC40: 7C90EAE3 7C900000 + EAE3 (ntdll.dll)
> 0012FC54: 74730DE9 74720000 + 10DE9 (MSCTF.dll)
> 0012FC58: 7E41EAA1 7E410000 + EAA1 (USER32.dll)
> 0012FC70: 004D474D 00400000 + D474D (Forge90.exe)
> 0012FC74: 7E41B619 7E410000 + B619 (USER32.dll)
> 0012FC78: 004D4759 00400000 + D4759 (Forge90.exe)
0012FC7C: 00121152 00030000 + F1152
0012FC80: A86E54E2
> 0012FC84: 0040FFAC 00400000 + FFAC (Forge90.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 005FEC7B 00400000 + 1FEC7B (Forge90.exe)
0012FFFC: 00000000

Subject:RE: Does this crash occur for anyone else?

Reply by: Geoff_Wood

Date:4/30/2008 3:33:03 PM

9.0e didn't for that for me just now. Other builds have all been very stable for me too, for that matter... Maybe there is something fundamentally screwed up in you Windows that causes both this and your install problem.

Have you try a Windows repair application to clean out the crud ? I've been using Norton Windoctor for years (run off the CD - NOT installed !) to clean up the dozens of system problems that appear over weeks.

Also have you logged your fault details through the official tech support channels ?

geoff