Subject:Constant, Debilitating Crashes

Posted by: b_ville

Date:2/8/2005 5:22:53 PM

In a six hour work period ACID Pro 5.0 crashed about a dozen times followed by the error message below. Sometimes I could force the apps closed, others...the whole computer sits still. My most current strategy is restarting ACID about every 30 minutes. This seems to work...sometimes.

The crashes happen fairly randomly (clicking play, changing fx param, while playing, switching b/t windows, when I am not doing anything at all and the computer is sitting completely idle, etc.) ...

They occur with every kind of file (with reason, w/o reason, with midi, file w/o midi, 4.0 files, 5.0 files, with fx, w/o fx, etc.)..

In every system situation (anti-virus, w/o anti-virus, firewall, w/o firewall, internet, w/o internet, rewire master, rewire slave)...

I tweaked my settings till I was blue in the face...to no avail.

(As you can see I have spent an absurd amount of time troubleshooting this)

I have never had any problems with any sony/sonic foundry software on this computer until Acid 5.0.

I'm running Windows XP Home on a 3.0 Ghz Prescott, 1 Gig of RAM with a M-Audio MobilePre USB soundcard. I'm running ACID 5.0, Reason 2.5, Adobe Audition 1.5.


Below is one of many errors I received. They are all just about the same with the exception of a few, "integer divide by zero" errors.

The only option I have not tried is a reinstall...should I?

Please Help
-Dan

Sony ACID Pro 5.0
Version 5.0 (Build 265)
Exception 0xC0000005 (access violation) WRITE:0x88A0B4E0 IP:0x8A4470D
Thread: GUI ID=0xB40 Stack=0x11E000-0x130000
Registers:
EAX=7ffdf000 CS=001b EIP=08a4470d EFLGS=00010246
EBX=00000000 SS=0023 ESP=0011e4a0 EBP=0011e4c8
ECX=00000000 DS=0023 ESI=08a446f8 FS=003b
EDX=00000003 ES=0023 EDI=0011e503 GS=0000
Bytes at CS:EIP:
08A4470D: 00 14 05 E0 C4 A2 08 58 .......X
08A44715: C0 A4 08 00 00 00 00 BC ........
Stack Dump:
0011E4A0: 77D48709 77D40000 + 8709 (USER32.dll)
0011E4A4: 000D0272 00030000 + A0272
0011E4A8: 0000001C
0011E4AC: 00000000
0011E4B0: 000006A0
0011E4B4: 08A446F8 086C0000 + 3846F8
0011E4B8: DCBAABCD
0011E4BC: 00000000
0011E4C0: 0011E504 00030000 + EE504
0011E4C4: 08A446F8 086C0000 + 3846F8
0011E4C8: 0011E530 00030000 + EE530
0011E4CC: 77D487EB 77D40000 + 87EB (USER32.dll)
0011E4D0: 08A446F8 086C0000 + 3846F8
0011E4D4: 000D0272 00030000 + A0272
0011E4D8: 0000001C
0011E4DC: 00000000
> 0011E508: 7C90E9AB 7C900000 + E9AB (ntdll.dll)
> 0011E524: 77D70494 77D40000 + 30494 (USER32.dll)
> 0011E528: 77D48808 77D40000 + 8808 (USER32.dll)
> 0011E534: 77D4B368 77D40000 + B368 (USER32.dll)
> 0011E578: 77D70494 77D40000 + 30494 (USER32.dll)
> 0011E57C: 77D4B378 77D40000 + B378 (USER32.dll)
> 0011E588: 77D4B3B4 77D40000 + B3B4 (USER32.dll)
> 0011E5B0: 7C90EAE3 7C900000 + EAE3 (ntdll.dll)
> 0011E5D0: 77D4B31B 77D40000 + B31B (USER32.dll)
> 0011E5D4: 77D493C6 77D40000 + 93C6 (USER32.dll)
> 0011E5D8: 77D49385 77D40000 + 9385 (USER32.dll)
> 0011E600: 77D493DF 77D40000 + 93DF (USER32.dll)
> 0011E61C: 77D489D9 77D40000 + 89D9 (USER32.dll)
> 0011E620: 77D49278 77D40000 + 9278 (USER32.dll)
> 0011E62C: 00401CF8 00400000 + 1CF8 (acid50.exe)
0011E630: 0011E64C 00030000 + EE64C
0011E634: 00000000
0011E638: 00000000
0011E63C: 00000000
> 0011E668: 00417974 00400000 + 17974 (acid50.exe)
0011E66C: 00010274 00010000 + 274
0011E670: 00000000
0011E674: 00060396 00030000 + 30396
0011E678: 0011E750 00030000 + EE750
> 0011E67C: 004168F0 00400000 + 168F0 (acid50.exe)
0011E680: 0011E714 00030000 + EE714
0011E684: 00000000
0011E688: 00000000
0011E68C: 00000001
> 0011E6A0: 77D48709 77D40000 + 8709 (USER32.dll)
> 0011E6B4: 773F8B56 773D0000 + 28B56 (COMCTL32.dll)
> 0011E6C4: 773F8B56 773D0000 + 28B56 (COMCTL32.dll)
> 0011E6CC: 77D48BB1 77D40000 + 8BB1 (USER32.dll)
> 0011E6D8: 77D48832 77D40000 + 8832 (USER32.dll)
> 0011E6E0: 77D487FF 77D40000 + 87FF (USER32.dll)
> 0011E6EC: 77D48709 77D40000 + 8709 (USER32.dll)
> 0011E700: 004168F0 00400000 + 168F0 (acid50.exe)
0011E704: DCBAABCD
0011E708: 00000000
0011E70C: 0011E750 00030000 + EE750
> 0011E710: 004168F0 00400000 + 168F0 (acid50.exe)
0011E714: 0011E77C 00030000 + EE77C
> 0011E718: 77D487EB 77D40000 + 87EB (USER32.dll)
> 0011E71C: 004168F0 00400000 + 168F0 (acid50.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 00637390 00400000 + 237390 (acid50.exe)
0012FFFC: 00000000

Subject:RE: Constant, Debilitating Crashes

Reply by: Zacchino

Date:2/8/2005 6:01:52 PM

These crashes seems familiar to me...

Can we have a list of your running processes while making music with AP5, if possible ?

And a list of your most used VSTfx, DXfx, and VSTi.

Also, tell me if you have SP2 (for USB 2.0 as MobilePre is USB, and I don't trust USB especially for Audio). Tell us also if you have DMA enabled HDD... You can check it in your Device Manager, under IDE Controllers > Primary & Secondary IDE Channels' properties. It should be set to Ultra DMA Mode 1 or 2, or something like "non applicable", but not PIO mode.

It could also be caused by your graphic card (which graphic card do you have ?).

Also, is your mobile pre connected to the front or to the back of your comp ? It should be connected to the back (more power supply, more stable).

Subject:RE: Constant, Debilitating Crashes

Reply by: b_ville

Date:2/22/2005 2:55:07 PM

Long story short:

I took each of you inquiries and looked myself. I did find a couple things...all or one of them may have made it crash. I do have SP2, the only fx i'm running are sonic foundry (wave hammer) and sony (the rest), I run ultraDMA on both haddrives(more about this later), i've got an 'NVIDIA GeForce 2 MX' AGP graphics card.

I had a ghost driver running in the background for the motherboard's integrated sound card...removed software and disabled the sound card on the motherboardboard.

(preface: I have been having problems with the computer crashing during intensive tasks
prior to this and miscellaneous file corruption...I just thought it was windows.)

Found that I had doubles of all devices under IDE Controllers.........
(and i mean ALL of them primary, secondary, master, and one that i did not recognize)
Checked the BIOS and everything seemed fine.
I tried to uninstall them, but they came back everytime.
I tried to disable them...no luck.
THEN...I opened the computer......

(preface: i had this computer built down the street (at a fairly reputable place...i think) for
me. 80 GB HD & 150 GB HD)

the master HD was set to master(no jumper) and the slave was set accordingly.
HOWEVER...on this HD 'Master WITH Slave'...you need a jumper...i installed the jumper
it fixed the double IDE Controllers problem (and even got rid of the mysterious controller)

computer is running the best it has ever...except that ACID still crashes...less often though and only on a couple files (never new ones)...and i had to reinstall my MIDI keyboard controller b/c ACID couldn't/wouldn't find it.?.?.?.?

then i noticed that the ACID help files weer corrupted an unopenable...reinstalled ACID.

fixed the problem right?

no.

the ACID files were corrupted, but the .bak files were not...except for a couple

everything is fine now

so...in summation can anyone out there fix these ACID files (and do you need the music files to go along with it)

Thank you

Dan

Subject:RE: Constant, Debilitating Crashes

Reply by: Iacobus

Date:2/22/2005 6:07:24 PM

You can maybe try sending a couple to SPD's support. There's no guarantee though.

For better performance of your hard drives, you might want to check out a recent post of mine.

Generally, if things remain unstable, you might want to employ a brute force method and format your system drive now that you have the right configuration.

HTH,
Iacobus
-------
RodelWorks - Original Music for the Unafraid
Buy Instant ACID by JohnnyRoy and mD! Now!
mD at ACIDplanet

Subject:RE: Constant, Debilitating Crashes

Reply by: b_ville

Date:2/28/2005 1:50:52 PM

Thanks all...I follwed the recommendations of that post and some other research I did. Everything works fine...except I can't render any files unless it's the very first thing I do. But, I can live with that until the patch.

Dan

Subject:RE: Constant, Debilitating Crashes

Reply by: Klirrfaktor

Date:3/5/2005 3:20:57 PM

actually im having similar problems. whenever i use acid 5, it does crash after some time with such errors like above. sometimes i do even get a bluescreen or a bluescreen shortly after such crashes. i tried to disable all "small companies" plugins but that didnt help. but if we are talking about harddisk stuff.. im using a raid system and the asus p4p800-e deluxe mainboard (s-ata raid) and maybe it has something to do with that but i doubt it.
acid 4 is running very stable and so im not thinking its because of plugins or my hardware. actually i was not investigating more into details since i want to do music and ive got enough pc troubles to solve in my job. ;-)

Subject:RE: Constant, Debilitating Crashes

Reply by: pwppch

Date:3/5/2005 5:11:22 PM

What does the blue screen say caused the crash?
Could you fill out your system specs in your profile?

FWIW : A blue screen is caused by drivers or kernel level code. ACID cannot directly crash to a blue screen as it provides no drivers or kernel level code. It does interact with drivers and kernel code.

Peter