Home » The PARIS Forums » PARIS: Main » Unhandled exception coooooo5 at 0048c425 (Any suggestions on cause?)
| Unhandled exception coooooo5 at 0048c425 [message #107842] |
Fri, 13 September 2013 08:04  |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hi All, and Mike A., I hope you can help me out.
I am having an new issue that happens intermittently but frequently.
Upon trying to start Paris 3.0 lately, the project window gets partially drawn then I get the error: Unhandled exception coooooo5 at 0048c425
I have windows xp, on an amd athlon single core
2 eds cards, 2 c-16, 2 8in
I have Mike's latest driver, which corrected a blue screen error I was getting before I installed it, but the project window also comes up slower since then; but it had been working until I had to reload paris because it wouldn't start because of a missing vst plugin file and the unhandled exception problems seemed to start after that. Does paris not tolerate the native vst plugs well? I had never used them before.
After that, I tried an uninstaller to completely get rid of Paris before reloading it but the problem still occurs.
I noticed the error listed in the wiki, but it didn't give any possible solutions.
I would appreciate any suggestions.
Thanks!
John
John, Twin Cities, MN
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107864 is a reply to message #107858] |
Sun, 22 September 2013 04:39  |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Hi John,
I'm not sure if that is the right PACE installer or not. They've changed their website since the last time I downloaded the driver. If it isn't the right one, I'll dig out an older copy that I'm sure I have somewhere.
An IRQ conflict shouldn't cause a problem, but anything is possible. If one of the drivers that an EDS card is sharing an IRQ with isn't written well, it can cause a problem. But that is pretty rare these days.
A more likely scenario is bad ram. If PARIS reads a pointer address, and the value returned is off by one bit being flipped, you'll likely get an access violation. I used to do IT work, and I would always specify Kingston RAM for new builds. Bad ram can cause intermittent, weird errors that can take a long time to troubleshoot.
You can also try installing a copy of PARIS 2.1 just to see if the problems happen on that install, too. If they don't, then you know the issue is specific to the 3.0 config.
I hope this helps!
Mike
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107870 is a reply to message #107864] |
Sun, 22 September 2013 12:20 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hey Mike,
-Alright. I'll try this ilok license manager and driver app and see if it works. If it doesn't work, can I email you for the old pace driver? I still have your address.
-I ran memtest86+ for about 7 or 8 passes overnight recently and didn't get any errors. Could I still have ram issues?
-Question related to your paris installer: other than the drivers which you have obviously done a lot of work on, have you modified other parts of the paris program? The reason I ask is, I have a cd with paris 3.0 demo, that has the old pace drivers in it? So if I loaded that and then your drivers, would that work?
Thanks again!
John
John, Twin Cities, MN
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107871 is a reply to message #107870] |
Sun, 22 September 2013 15:40 |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Hi John,
Absolutely send me an email. I'll help any way I can.
I added a couple of visual c++ dlls to the PARIS PRO folder because I had to compile the PSCL in a newer version of Visual Studio to make it work under Windows 7. So, recommend using my installer, if possible.
I made no changes whatsoever for the PACE stuff in PARIS exe because Edmund didn't have time to answer my question when I asked him if I could. He did have time to tell me to be patient and stop asking him. I'm still waiting. The PACE driver that came with PARIS 3.0 should still work.
Talk to you soon,
Mike
[Updated on: Sun, 22 September 2013 15:46] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107878 is a reply to message #107874] |
Wed, 25 September 2013 22:28 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hello Mike,
-Ok so over the last few weeks, I reinstalled windows xp sp3 and paris, pace drivers, burned out a cdrom drive in the process. Thanks for helping me with all that.
-I downloaded your amp plug too,very cool, gonna use it as a vocal effect.
However,unfortunately, I am still getting the error I originally posted on this thread.
I looked for a default project.ppj in the paris pro folder and there wasn't one. I hadn't created one (you're not talking about the ppj template in the projects folder, correct?). I also created an empty folder for the VST path and that did not prevent the unhandled exception either. Recall that I ran 6-7 passes of a memory test with no errors.
1) When I boot paris it loads "untitled project" (are there any settings associated with "untitled project" that can be changed?.
2) Often when I launch paris, if I don't get the unhandled exception, I hear a loud chirping noise out of my speakers or headphones plugged into the MEC jack until I either close "untitled project", or open a saved project. But not every time. It occurred to me that creating a default project might prevent the chirping since it occurs right on launch and goes away when "untitled" project is closed or another is opened.
A project with about 25 tracks takes about 10 seconds to load.
Any other thoughts on these 2 issues? I'll take any ideas as I really don't know where to go from here.
Thanks again!
John
John, Twin Cities, MN
[Updated on: Fri, 27 September 2013 12:27] Report message to a moderator |
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107881 is a reply to message #107878] |
Sat, 28 September 2013 12:09 |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Hi John,
I have a couple of thoughts.
If you create a default project.ppj, that will become your new "untitled project." You can change any settings there that you want.
I was using PARIS this morning, and I think I was able to reproduce the error you first reported. It happened when I was running Windows XP in a virtual machine under Windows 7 64. I had 2GB of RAM allocated to the virtual machine. As soon as I shut down the virtual machine, the problem stopped.
I think this is happening because you are out of RAM.
On my system, I have 8GB, but the PARIS hardware can only see the first 4 GB. It seems that Windows 7 fills the RAM from bottom to top, meaning that if I have too much running, there will be no more RAM under the 4GB boundary to create the sound buffers.
Under Windows XP, there is a maximum of 4GB addressable, but you loose a whole bunch to mapping in video card memory, BIOS, etc, etc. You're usually left with less than 3GB, even if 4 GB is present in the machine. I've seen as little as 2GB left over on systems with a powerful video card.
The latest drivers do double buffering to allow PARIS to run under a 64 bit operating system. This means that PARIS now needs twice the memory for sound buffers that it used to need. There is just no way around this on a 64 bit Windows without getting access to the PARIS application source code. I never saw this error on my system or on any other system in testing, so I didn't think it was a problem to do the double buffering under xp. The double buffering offers that added advantage of better system stability in the event that PARIS.exe crashes. That may be a luxury that XP can't afford.
But because you are on a 32 bit Windows and don't need double buffering, there is a way around this. Try changing the name of PARIS.exe to PARIS_XP.exe, or anything you want other than PARIS.exe. The driver will no longer try to do double buffering.
Let me know if any of this helps.
If it does, I'll try to update the PSCL to detect the 32 bit OS and skip the double buffering. Or, I could add an option in the PARIS Control Panel.
Another way of fixing this might be to give windows 7 64 a try. It's absolutely fantastic and PARIS runs like a dream. And, I think the full retail version is still available, if Microsoft hasn't pulled it already to try to force Windows 8 down our throats.
I hope this helps, and I'm very sorry if my missing something has caused you a bunch of grief.
All the best,
Mike
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107882 is a reply to message #107881] |
Sat, 28 September 2013 13:43 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Mike, No problem, I appreciate all your help. I would be SOL without it, I'm afraid.
I only have 1GB of RAM. Should I add some? (Would I need more under windows 7 anyway?).
That being said, I don't think I ever got this particular unhandled exception until I reinstalled paris about 4-6 weeks ago, and I had been using your install and drivers for a month or 2 before that.
I will try renaming the paris.exe and see what happens.
Regarding Windows 7, I don't want to do it right at the moment, as I am right in the middle of trying to mix some projects for my band, but it isn't urgent. It's just disruptive to the creative process when stuff keeps breaking,limited time, blah, blah.... I'm sure you know what I mean. I used the system last night for a few hours a it was running pretty well once it launched without the unhandled exception and a project loaded. Again it took about 10-15 seconds to load 25 or so tracks with edits, some effects, etc 1 native plugin. The only error I got was when I was using the c16 wheel in jog mode going backwards and it didn't actually crash the program.
-Will Windows 7 run on My AMD AThlon XP 2600 and Nvidia Motherboard? Would I need more RAM (at least 4 GB ?) and or andy other upgrades?
-Would you recommend home premium, professional or ultimate version pf retail Win 7?
-The other thing is I use wavelab 4.01b to do some mastering on the same system. Would that run under Win 7?
-Would any other hardware conflicts, etc be likely to pop up? If it isn't likely to be too much of a pain, I may do it!!! I would love to have paris running in bit more stable manner if possible.
Thanks again for sharing your time and talents!
I'll let you know what happens with the name change.
John
John, Twin Cities, MN
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107883 is a reply to message #107882] |
Sat, 28 September 2013 14:49 |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Hi John,
One GB of RAM is pretty thin. I would add more. Probably no more than one addition GB if you are going to stick with Windows XP because it won't get used anyway.
I wonder if the errors started with a change in work flow, or possibly after a Windows update.
One of the problems with Windows is that it is designed as a file server, not a multimedia platform. Windows will use almost all available RAM to cache files, and send applications into the swap file to do it.
Check this out:
http://www.uwe-sieber.de/ntcacheset_e.html
According to this site, Windows will use almost a GB of RAM for caching files - and that's your whole system. I've found this to be true. I'd be working in PARIS under XP mixing various songs all day, and the system would get slower and slower and slower. Windows was keeping a copy of every sound file I had opened in RAM, and swapping PARIS.exe out to the hard disk to do it.
I haven't had any problem like this under Windows 7 with PARIS, but I did run into it again ripping CDs. I ripped about 50 CDs over several days, and Windows started getting slower, and slower, and slower. Every damn CD was still in RAM.
I've just started running a utility called SetSystemFileCacheSize. Here's a direct link to it.
http://www.uwe-sieber.de/files/setsystemfilecachesize.zip
But, it only works with Windows Server 2003 and up (Which includes Windows 7).
I'm not sure how Windows 7 will run on the XP2600 based system. I know that it was re-written to use lots of threads, which works better on a multi-core CPU, but worse on a single core CPU. I wouldn't attempt it with less than 8 GB, which probably rules out the XP2600 based system.
I like Windows Pro because it can be a remote desktop server, but the Home edition would work just as well for PARIS.
My suggestion for now is to maybe try this tool (which I haven't tried)
http://www.uwe-sieber.de/files/ntcacheset.zip
to see if it helps reign in the XP disk cache.
I'd add one more GB of RAM.
If NT cache set doesn't work out, I'd restart the machine more often to flush the cache.
Change the name of PARIS.exe and reduce the caching in the settings/configuration.
But, just adding another GB may fix this completely.
Maybe someone else can chime in regarding Wavelab on Windows 7. I'm using Adobe Audition 3.0, and love it. Adobe shut down the activation servers for it a few years ago, so if you create an adobe account, it's available via download to those who own a copy of either version one, two, or three. If you've misplaced your old serial number, they don't ask for it.
I hope this helps!
Mike
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107884 is a reply to message #107883] |
Sat, 28 September 2013 16:14 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hey Mike,
I've done some experimenting and think you may be right.
I have some done some windows updates so that may be part of the issue. I don't remember the exact timeline.
I tried renaming the exe and that didn't prevent the exception.
Then just to see what would happen, I created a default project.
doing so prevented the chirping noise I get when an untitled project loads but I got an error saying I don't have enough physical memory to load it, and then I got the same unhandled exception as before! It tried it again and it gave the not enough memory error but then it loaded "untitled project".
I tried opening a project and it loaded and played back but no audio!
So I deleted the default project. I may add it back after I add some RAM, because it appears to prevent the chirping thing.(which is super loud and annoying if the monitors are turned up a bit-yeah I don't turn the monitors on til after paris boots now, like I probably should have anyway)
Also, you mention the cache settings in paris config, and I looked at those earlier and they appear to be set higher than I had them before, I will try reducing them.
I am going to try to get this machine working for now cause I don't need anything more powerful in terms of track count, etc, and I am not up to building a new machine for Win 7 at this point.(may be I'll change my mind after I forget about all this fun I'm having.  )
Is it possible for paris converters to work with a native DAW program?
I'll work on this some more and report back. I think you've honed in on the issue. Thanks for taking the time.
Thank goodness paris has someone as knowledgeable as you working to keep it alive.
John
John, Twin Cities, MN
|
|
|
|
|
|
 Re: Unhandled exception coooooo5 at 0048c425 [message #107886 is a reply to message #107885] |
Sat, 28 September 2013 19:12 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
No need to apologize, what you've accomplished in your "spare" time is amazing. Keeping the system running on newer hardware and OS's is an understandable priority. If you get the converters working with another DAW, I would definitely consider getting a new machine for the paris converters. (As I have been toying with the idea of switching set ups entirely, but wonder how much I will have to spend on converters to not take a big step back in sound quality, and track counts for tracking- I would be happy with 12 tracks, so I can mic up a drum kit the way I want-like I can now).
Regarding the reverb, I've always wondered about a way to change the reverb return pan locations. I don't like not having control over that and how it sounds either.
It is so cool that you are working on this stuff. Keep it up and good luck. I will update you on how the system is running.
John
John, Twin Cities, MN
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107887 is a reply to message #107886] |
Sat, 28 September 2013 20:50 |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Thanks so much for being so understanding, John. I've absolutely done the very best I could at each step. It was easier to find time before I got married, had a daughter, and bought a house. But, this is important to me, and I love working on it.
The PARIS converters really do sound wonderful. So do its effects, though as I get better at recording sound, I use them less.
The only thing to come out in the last ten years that has looked interesting to me is Apollo. But, it's $3000, and my recordings wouldn't actually sound any better. Plus, in 5 years, an Apollo interface will be worth $500, and I'll probably be stuck on an old OS because the software got discontinued.
I'd rather spend that $2500 loss due to depreciation on mics - or the mortgage!
I'll keep working on keeping PARIS going for a long, long time to come. The corporate upgrade machine can stick it.
Cheers!
Mike
|
|
|
|
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107900 is a reply to message #107898] |
Sat, 05 October 2013 11:06 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hi Mike,
Well,
The Memory checked out ok with 4 or more passes over night.
The voltage for the ram is set correctly.
I'm not using any UAD stuff.
I have a cpu fan and 3 other case fans that all appear to be operating. Cpu temp is 104F.
-I'm not sure what I'm looking for with regards to looking at voltages from the power supply in the bios- could you clue me in on what I should be seeing?. There is an item for Cpu that is set to H/W (hardware determined?)
-There is a heading that says "v-core" and a bunch of different voltages.
I got the BSOD while paris wasn't running so I don't think it is anything with the driver. It was:
stop: 0x0000007f (0x00000001, 0x00000000, 0x00000000, 0x00000000)
update from today:
BSOD:
Page_fault_in_nonpaged area
STOP: 0x000000050 (0xfffffffff, oxooooooo1, 0x805669fd, ox00000000).
I looked up this code and read that it can be related to installing "faulty hardware". The ram test didn't show any errors but I am going to try taking one stick out at a time to trouble shoot the ram (and sockets)Starting with removing the ram in dimm 2 (since that's how it was configure before and I didn't get these error). Did you say I wouldn't get any extra benefit from more than 2GB total?
update 7pm: I'm getting this one over and over while testing different ram sticks and locations:
STOP: 0x0000008e (0xc000001D, oxBF804159, oxB12D48E, 0x00000000
Win32K.sys address BF8o4159 base at Bf800000 date stamp 5202f409
update 8 pm: got this one:
Driver_IRQL_not_less_or_equal
STOP: 0x000000D1, etc
I wasn't having these issues before replacing the ram, So are there any issues that could be caused by the new ram, other than it being faulty (hardware conflicts etc)? I know that the 2 old 512 sticks were in dimm slots 1 and 3,
I put in 3 1G sticks.(it was fairly cheap so just went ahead and got 2 two-gig kits and put 3 in)
I know this isn't an issue with your driver, but any ideas off the top of your head would be great, besides trouble shooting the ram itself, as I plan to do. If I can just get the new parts to play nice with the old, maybe I can focus on the music for a little while, and actually finish a mix! But I am running out of channels. Maybe I need Win 7 machine with 3 cards/mecs!
Your help is greatly appreciated and thanks again for all the work on the drivers!
John
John, Twin Cities, MN
[Updated on: Sat, 05 October 2013 18:08] Report message to a moderator |
|
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107904 is a reply to message #107903] |
Sun, 06 October 2013 08:20 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Hi Jeff,
Thanks for chiming in. )I am not a computer expert, but I am fairly methodical, so just trying to troubleshoot as best I can with the help of the nice people on this forum, given my limited knowledge of a computer's inner workings)
I have a K7N2 mobo with nvidia nforce 2 chipset.
It only has 3 spots for RAM.
2 slots are purple and one is green. According to the manual the green one supports 128 bit dual channel operation, when ram is inserted in it and one of the other channels. I was running it like that with my old ram and it seemed to work.
What your saying makes sense though, because I am getting all kinds of BSOD when using paris, but also occurred when not using paris, that I never did before AND the ram passed several passes of a memory test, so I figure some sort of hardware conflict? Either that or all sticks are bad (seems unlikely given the memory test).
When the problem started I had the new RAM in all 3 sockets.
So I've been trying 2 of the 3 sticks of RAM that I started with in different slots to see if I can get it to work. (I have one more stick but why introduce another variable, was my thought). I've tried every possible combination using the 3rd slot and have gotten errors every time. I started with that because it used to work.
I'm now testing 2 sticks in the first 2 slots and not using the one with dual channel support (this is the last possible combination), and it hasn't crashed yet, but I just restarted and the problem takes a while to occur.
So, I'm going to see if this works, and if so, just stick with the 2 GB. Mike thought more than 2 GB wouldn't benefit me much anyhow. (going to 1 stick seems pointless since that is what I started with- 2 512 sticks and I was getting not enough physical memory errors.) If the first 2 slots don't work, any other suggestions? Different brand of RAM?
Thanks again so much for your input.
John
John, Twin Cities, MN
|
|
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107906 is a reply to message #107905] |
Sun, 06 October 2013 13:16 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Thanks Mike and sorry for all the posts. It helped me leave a trail of evidence, though.
Thanks for the pic on the bios. I see what you mean, my voltages appear to be hovering around their intended values like yours with 2 ram modules in place. I didn't get any instructions with my ram, I'll see if I can find out if they should be run at a higher voltage. With 3 modules in place, if the ram were not getting enough power, could that have caused these issues or is it more likely a conflict with the ram and motherboard,etc as I mention below?
OK, so I've been testing 2 sticks of ram in slots one and two and leaving the third open. So far it's gone the longest without crashing. Though I believe I got the unhandled exception once, the one that I was trying to get rid of in the first place. But I've opened paris several times without it since. Paris seems to be running well once a project is loaded. Used wavelab for a while with no blue screen as well.
My motherboard manual said I could use all three slots. So it sounds like you guys are saying it doesn't necessarily always work? Is it because the 3rd slot is meant for the dual channel 128 bit operation and the ram isn't compatible? Because even with only 2 sticks of ram, if one was in that slot, I got the BSOD. I had one of my old sticks in that slot and never had these problems.
Thanks again all your help. I'll work on a mix and Hopefully 1 GB in each of the first 2 slots is the answer.
John
John, Twin Cities, MN
|
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107907 is a reply to message #107906] |
Sun, 06 October 2013 20:45 |
JohnG
Messages: 57
Registered: April 2013
Location: Twin Cities, MN
|
Member |
|
|
Here I am at 10:20pm.
No BSOD all day after putting the ram in slot 1 and 2 only. But the same unhandled exception is back intermittently upon launch of paris!
It didn't occur on launch of paris when I had 3 sticks in, but of course I would get the BSOD within 10-60 minutes or so, which we can't have.
But it does occur with 2 sticks of ram (which is all I can get to work without the BSOD), but still 1 GB more than I had before!! When Paris does load, again it does seem to function pretty well.
I am at a loss.
A few WAG's:
1)Could I have a bad eds card? I get that chirping noise upon launch. It goes away when I mute submix 2, which is running off card B. I suppose I could try switching the cards around? I hate to do it because every time I try something, something else breaks. What do you think about switching the eds cards around?
2)It seems strange to me though, that this unhandled exception would be a hardware issue, since it started after I reloaded the paris program few months ago, without doing anything with the hardware. But then I've reloaded windows and all my applications and yet it persists.
3) I could uninstall sp3, but I don't remember exactly when I installed it or if that would be a cause.
4)I have not loaded paris 2 yet to see if that has any issues. Is there any downside to doing that?
5) I could install 3.0 of the disc I have instead of your installer, and install just your driver, if that would matter?
I better go to bed.
Thanks again, have a great week.
10/14/13: I did several sessions of mixing and paris started without the exception, even though I haven't changed anything???
John
John, Twin Cities, MN
[Updated on: Mon, 14 October 2013 18:42] Report message to a moderator |
|
|
|
| Re: Unhandled exception coooooo5 at 0048c425 [message #107994 is a reply to message #107907] |
Wed, 11 December 2013 11:58 |
mikeaudet
Messages: 474
Registered: February 2009
|
Senior Member |
|
|
Hi John.
Try changing the name of PARIS.exe to PARIS1.exe. That will turn off the double buffering. It may be that the PC is too memory starved and slow to pull of the double buffering. (not that I'm trying to insult it).
I've been working with PARIS for the last couple of days while my daughter is in preschool, and I haven't had any of those issues. PARIS crashes once upon closing, but I traced that one back to PARIS.exe.
I hope this helps.
Mike
EDIT:
Also, turn down the disk cache size in PARIS. I was working with PARIS yesterday, and I noticed that I have over 600MB allocated to PARIS.exe. That's great on an 8GB system, but way too much on an older PC.
[Updated on: Wed, 18 December 2013 08:52] Report message to a moderator |
|
|
|
Goto Forum:
Current Time: Thu Apr 25 03:42:26 PDT 2024
Total time taken to generate the page: 0.02326 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
