Community Forums Archive

Go Back

Subject:Acid 3 Crashes in Win2K
Posted by: jobee
Date:6/15/2001 6:42:57 PM

Hi,

That's it. I'm getting this BSD with this title:

PAGE_FAULT_IN_NONPAGED_AREA

and then i have to reset the computer !

Never got this error with Acid 2.

I have latest drivers for every piece of hardware.

Does anyone is getting this problem ?

My System:

AMD Athlon 600 Mhz
256 Mb
MSI K7 Pro MOBO
RT2000 with MVT3
Sound Blaster Live! Value
NIC Realtek 8139
Windows 2000 Pro SP2
DirectX 8.0a with DV update
Sound Forge 5 build 117
Adobe Premiere 6

I've emailed technical support but I'm still wayting for an answer...and I need this thing fixed, at least a way to avoid this inconvenience...urgently !

Thanks,

jorge

Subject:RE: Acid 3 Crashes in Win2K
Reply by: MacMoney
Date:6/15/2001 10:31:54 PM

Hello
Im running Acid 3 Win2k sp2. Ive been on this system for about two weeks now and Not one crash I have a
P4 1.7ghz
640mb ECC pc800 ram
Intel MoBo
MOTU 2408 w/win2k beta 4 drivers
DX8a
Sound Forge 5
GW

Subject:RE: Acid 3 Crashes in Win2K
Reply by: BobH
Date:6/16/2001 1:04:06 AM

I've got a similar problem and similar hardware. I just installed Acid 3.0,
and it won't even get past the splash panel before it crashes on an illegal
memory reference.

SB Live!
Athlon 700MHz
512 MB RAM
Win 2K Sp2

Subject:RE: Acid 3 Crashes in Win2K
Reply by: SonicJG
Date:6/18/2001 9:24:22 AM

One of our beta testers reported having issues using ACID with an AMD K6 and SB Live, so I ended up doing some pretty extensive testing on this scenario.

What turned up was that there are definite issues between some AMD mobo's with Via chipsets and SB Live cards. From what I could gather regarding this, there have been known issues with K6 and the early Athlons and their motherboards needing to have their PCI latencies turned down, and also the SB Live cards are supposedly a bit more taxing on the PCI bus, which could account for this specific combination giving these results.

This issue showed up with other software programs as well, FWIW, producing kernel32.dll GPF's in FruityLoops, SF5, and Internet explorer (when a page contained audio).

Check these links for details:
http://www.viahardware.com/download/viatweak.shtm

http://www.viahardware.com/download/wpresourcepage.shtm

http://www.viahardware.com/talkback/988136616,78740,.shtm

http://viahardware.com/download/george/readme.htm

Another FWIW, BSOD's are generally a result of problems with hardware. Could be IRQ conflicts, problems with the BIOS, faulty device drivers, or perhaps something else.

Hope this helps.

Joel

Subject:RE: Acid 3 Crashes in Win2K
Reply by: jobee
Date:6/19/2001 10:39:10 AM

Thanks for your reply, but sorry to say that it really didn't help me at all...

"One of our beta testers reported having issues using ACID with an AMD K6 and SB Live, so I ended up doing some pretty extensive testing on this scenario."

Well, like i have said, my processor is a K7 not K6 !

"What turned up was that there are definite issues between some AMD mobo's with Via chipsets and SB Live cards. From what I could gather regarding this, there have been known issues with K6 and the early Athlons and their motherboards needing to have their PCI latencies turned down, and also the SB Live cards are supposedly a bit more taxing on the PCI bus, which could account for this specific combination giving these results."

I've posted in my specifications that my MOBO is a MSI K7 Pro (AMD Chipset) not VIA !

"This issue showed up with other software programs as well, FWIW, producing kernel32.dll GPF's in FruityLoops, SF5, and Internet explorer (when a page contained audio)."

I don't get those issues you've mentioned ! I've bought also SF5 and works very well indeed.


"Check these links for details:
http://www.viahardware.com/download/viatweak.shtm
http://www.viahardware.com/download/wpresourcepage.shtm
http://www.viahardware.com/talkback/988136616,78740,.shtm
http://viahardware.com/download/george/readme.htm"

They don't apply to my case...it would be a waste of time...

"Another FWIW, BSOD's are generally a result of problems with hardware. Could be IRQ conflicts, problems with the BIOS, faulty device drivers, or perhaps something else."

So, what do I have to do ? Get rid of this system I have and buy a certified system to Acid Pro 3 ? Wich one ?

I've emailed sonic support but didn't receive any help. Is this the kind of support sonic foundry has to offer for costumers that had spent $$$ with their products ? I really like Sonic Foundry way of doing software and it's very intuitive to work with Acid and Sound Forge and even with Vegas Video (it's a shame it doesn't work with my Matrox RT2000), so I have to use premiere 6, but I really expect much more from technical support. And each time I have a problem I can't wait at least 4 days for support. I'm still wayting for a answer to that problem.

regards,

jorge

Subject:RE: Acid 3 Crashes in Win2K
Reply by: S N C
Date:6/19/2001 11:56:20 AM

One of my machines has a similar setup:

AMD Athlon 850 Mhz
512 Mb
MSI K7 Pro 2A MOBO
Windows 2000 Pro SP2
DirectX 8.0a with DV update

I also used to run a Sound Blaster Live! card in the machine, but took it out, because it would cause BSOD at the slightest opportunity. The soundcard is now running happily in a WindowsME setup with Acid3.

I have 3 suggestions for you to try:
- Take out the soundcard and try running with only the onboard AC97 sound (this is quite easy and I would do it first).
- Go back down to WindowsME for the OS.
- Ensure that you have the latest creative drivers (I think they were recently updated).



Subject:RE: Acid 3 Crashes in Win2K
Reply by: jobee
Date:6/19/2001 11:05:27 PM

Hi,

Thanks for the support you all gave me. Acid is running well now. No more BSOD's. It was my NIC conflicting with only GOD knows what...I've changed it to another slot and now I can play with Acid Pro 3. :)

BTW, i've received an email from technical support, so now I'm feeling quite confident if anything goes wrong from now on.

Thanks again,

jorge

Go Back