Hi guys, I seem to still be having rare
base.dll crashes, I thought I had managed to re-produce this tonight but no chance..
I would love to put a stop to this once and forall, It happened when changing midi channels on arpegg01 and 02, and also while working the preset menu's in sb404,
sometimes the crash happens when saving.
has anyone had this random base.dll crash
is there some magic fix?
fresh XP install
Lap 5.1
2xpulsar2's
sfp 3.1 (this happened before sfp 3.1)
regards
topaz
<font size=-1>[ This Message was edited by: topaz on 2002-05-08 19:41 ]</font>
<font size=-1>[ This Message was edited by: topaz on 2002-05-08 19:42 ]</font>
base.dll unpredictable crashes>
I am plagued by it especially under Xp, win98se for me is better at the moment after I took a stick of generic ram out, the one left in is generic too, so I've always put it down to that.
I actually feel that could be graphics related under 3.0 as it would happen more often in pulsar mixer and dynamixer, if the Vu's were enabled.
Now I'm not so sure, try and keep a record of when it happens, and what you did to make it happen. A few other users have had this problem.
I actually feel that could be graphics related under 3.0 as it would happen more often in pulsar mixer and dynamixer, if the Vu's were enabled.
Now I'm not so sure, try and keep a record of when it happens, and what you did to make it happen. A few other users have had this problem.
Add life to your days, not days to your life.
I swapped my card from one PC to another. Both had exactly the same specs, but just a slightly faster CPU. One PC was perfect, the other got base.dll crashes. I did have a single warez program
on the second machine. When I purged that it improved a LOT (but didn't go completely).
Please don't think I'm implying anything here, just my experience....
The real solution was to move to a P4 with XP. Since then no problems at all.
<i>(and no warez
of course!)</i>
<font size=-1>[ This Message was edited by: Spirit on 2002-05-09 08:47 ]</font>


Please don't think I'm implying anything here, just my experience....
The real solution was to move to a P4 with XP. Since then no problems at all.


<font size=-1>[ This Message was edited by: Spirit on 2002-05-09 08:47 ]</font>
-
- Posts: 294
- Joined: Mon Apr 15, 2002 4:00 pm
- Location: Seattle, WA
- Contact:
After all the tweakings I did, things are running MUCH more smoothly now, and probably gained about 20% performance out of Pulsar! I can't be more pleased! However, I occassionally (once in a blue moon) still get those Page Faults in MSVCRT.DLL. I even get an error on an <unknown>?! But, I haven't seen the BASE.DLL since - yet.
At this point, I'm at a loss; but, at least they don't pop up every other startups or exits - or even during a cold boot! I'm not sure if it is a RAM issue since I've changed that as well. I'm inclined to think that it's the video driver (ATI Xpert 2000). I was using the Rage Fury Maxx before I reconfigured my hardware and clean installed everything...
But all my theories regarding hardware configurations, BIOS, faulty components, and drivers are debunked since Pulsar 3.01 is working FLAWLESSLY under WinXP Pro (even with NO tweaks, ACPI, active network, running MS Office background apps, etc.)?! Pulsar hasn't yielded any of those Page Fualt errors under the XP side!
Unfortunately, tripleDAT only works under Win9x, otherwise I'd completely migrate to XP Pro.
You are not alone my friend! I just hope that upgrading to v3.1 will eliminate these Page Faults altogether(under Win98SSE).
Skoal!
[ADDENDUM]
By the way, THANKS to all of you who constantly give your expertise, inputs and suggestions! I'm glad to see the comradery in this community and the outstanding user-based support system! This is an attestation to the music tech industry that the CW community is a formidable force to be reckoned with! Keep up the great work!
TZS
<font size=-1>[ This Message was edited by: The Z Station on 2002-05-09 09:53 ]</font>
At this point, I'm at a loss; but, at least they don't pop up every other startups or exits - or even during a cold boot! I'm not sure if it is a RAM issue since I've changed that as well. I'm inclined to think that it's the video driver (ATI Xpert 2000). I was using the Rage Fury Maxx before I reconfigured my hardware and clean installed everything...
But all my theories regarding hardware configurations, BIOS, faulty components, and drivers are debunked since Pulsar 3.01 is working FLAWLESSLY under WinXP Pro (even with NO tweaks, ACPI, active network, running MS Office background apps, etc.)?! Pulsar hasn't yielded any of those Page Fualt errors under the XP side!
Unfortunately, tripleDAT only works under Win9x, otherwise I'd completely migrate to XP Pro.
You are not alone my friend! I just hope that upgrading to v3.1 will eliminate these Page Faults altogether(under Win98SSE).
Skoal!
[ADDENDUM]
By the way, THANKS to all of you who constantly give your expertise, inputs and suggestions! I'm glad to see the comradery in this community and the outstanding user-based support system! This is an attestation to the music tech industry that the CW community is a formidable force to be reckoned with! Keep up the great work!
TZS
<font size=-1>[ This Message was edited by: The Z Station on 2002-05-09 09:53 ]</font>
sorry, to add to this
I have no other s/w installed other than
WinXP/SFP3.1 and Lap 5.1
agp is, Matrox g-550
I have no other s/w installed other than
WinXP/SFP3.1 and Lap 5.1
agp is, Matrox g-550
On 2002-05-08 19:11, topaz wrote:
Hi guys, I seem to still be having rare
base.dll crashes, I thought I had managed to re-produce this tonight but no chance..
I would love to put a stop to this once and forall, It happened when changing midi channels on arpegg01 and 02, and also while working the preset menu's in sb404,
sometimes the crash happens when saving.
has anyone had this random base.dll crash
is there some magic fix?
fresh XP install
Lap 5.1
2xpulsar2's
sfp 3.1 (this happened before sfp 3.1)
regards
topaz
<font size=-1>[ This Message was edited by: topaz on 2002-05-08 19:41 ]</font>
<font size=-1>[ This Message was edited by: topaz on 2002-05-08 19:42 ]</font>
I had problems with base.dll on 3.01. I tweaked them down to happening just a few times and with reboot i could start working again. With 3.1 i'm getting them everytime i tried to load a midi controller preset. I've only been running it several hours trying to get familiar with the new layout. I was hoping the midi presets would solve the reassignment issue every time i load a synth in a new project. but for now doesn't look like it. i haven't started a new project with 3.1 yet but if the base.dll error only happens with midi controller presets i can live without them. perhaps i will get xp this weekend. some people have got rid of the problem that way.
JD
JD
well, xp upgrade from 98se and when i tried to load a midi controller preset, base.dll crash. now i can't even get xp to load the creamware midi driver. keeps telling me no driver installed. I even uninstalled pulsar in device manager, deleted scope.sys from windows, and reinstalled drivers with same error. but that is the least of the trouble. i will try a new video card, like on subhuman'm machines, a geforce. if that doesn't work, looks like a P4 upgrade.
It's seems a little bit late to answer..
but recently I've got a lot of trouble with this base.dll msvcrt.dll etc ... with tusl2 , PIII-S 1.26 ,512 Mo .
and I have discover that underclockling the ram solve TOTALLY the problem !!!. ( 133/100/33) . so for me it was definitely RAM related (sure now I avoid no-name RAM like the plague ...) .
but recently I've got a lot of trouble with this base.dll msvcrt.dll etc ... with tusl2 , PIII-S 1.26 ,512 Mo .
and I have discover that underclockling the ram solve TOTALLY the problem !!!. ( 133/100/33) . so for me it was definitely RAM related (sure now I avoid no-name RAM like the plague ...) .
I get these Base.dll and mscvrt errors frequently. Usually when I'm about to save. Last night it crashed but oddly continued functioning in the background. I couldnt see anything or control anything but audio was still be processed by SFP. When I tried to relaunch it it told me it couldnt access the hardware.
My machine is a P4 2ghz with 1024mb rambus running win98se and SFP3.1c. I have a cpu fan, a small case fan and 2 card coolers so Im pretty sure it isnt a heat problem.
Thankfully at the moment Im still learning it all and just playing around with it but I will need to solve this before I start doing anything serious with it!
I was planning to save the errors and send them to creamware. Ill try the memory underclocking trick for now though.
Pleased to see they have sorted the STDM errors since I rarely see them anymore.
My machine is a P4 2ghz with 1024mb rambus running win98se and SFP3.1c. I have a cpu fan, a small case fan and 2 card coolers so Im pretty sure it isnt a heat problem.
Thankfully at the moment Im still learning it all and just playing around with it but I will need to solve this before I start doing anything serious with it!
I was planning to save the errors and send them to creamware. Ill try the memory underclocking trick for now though.
Pleased to see they have sorted the STDM errors since I rarely see them anymore.