PlanetZ forums - scopeusers.com

A strange problem has just started happening with my beautiful new system....

Often - but not always - when I delete a device from a project my PC immediately reboots. No warning, no feeze, just reboots. Then XP warns that I have recovered from "a serious error".

This happens almost always when deleting Celmo gear. I get an immediate reboot 100% of the time when attempting to delete BasmannIII or Deep Blue from a project. In fact it may be ONLY with Celmo gear - I'll keep testing this to be sure...

It's not heat related, and happens whether I have other apps open or not. The projects can be large or small. I have reinstalled Pulsar to no effect.

Could it have something to do with the actual Bassman & Deep Blue devices ? Is anyone else using them with XP ?

Other than this rather serious problem everything is working 100%.

Any thoughts ?

Asus P4B266
P4 1.8 512K L2
2 x barracuda IV
512Mb DDR SDRAM

This could well be a video card problem, I have had a similar problem, but it happends generally not just when removing devices.
There are literally loads of things graphics related that could cause this problem.
And as pulsar relies quite heavily on the graphics, it could be the cause of the crash.
It could also be memory related, so try less agressive memory settings, ie lower cas ratings. Or disabling memory interleave.
Basically read your mobo manual and set most bios settings for stability instead of speed which pulsar doesn't particularly need.
Try limiting agp to 2x, disabled write combining in xp,
in the bios disable video shadowing, bios caching etc. These can cause problems.
Also if you have an option that says agp master wait state read/write try disabling those.
Make sure you have lastest drivers for everything. Look for reports of this sort of behaviour related to your hardware. Might be one small setting like agp driving value.

The video card ? That only effects Celmo gear ? I've heard of stranger things I suppose. Thanks for the tips Remixme, I'll ave a good poke around.

But is no one else using bassmanII or deep blue under XP ?

<i>(in another thread I said how well Pulsar was running and that I had a background feeling of dread that such flawless performance couldn't be real.... I knew such perfection couldn't be true )</i>


<font size=-1>[ This Message was edited by: Spirit on 2002-04-07 16:21 ]</font>

Spirit,

Your computer is crashing, and you have auto reboot on error enabled (as it is by default). To trace the problem back to the file or driver that is causing it, <a href=http://www.tweakxp.com/tweakxp/display. ... 33>disable auto reboot.</a> Then you will see a traditional blue screen message with a file name. Using that info we can figure out what the problem is, and how to fix it. I have never experienced this on my system, but I will download the Celmo demos and see if they are related.

Is it possible to disable also on win98 SE ?

I have the problem with Pulsarmixer that reboot the machine ( error in MSVCRT.DLL in 016f:7800d17d. )

i have the same problem with pulsar mixer,
when loading it or a project that contains it
(all my projects!).

some times the error is in "base.dll", sometimes in "msvcrt.dll", sometimes i get the crash when i save. it's only a pulsar crash, no blue screen, but this morning i couldn't load a project for 1/2hour!
then, after a while, everything worked very well.....
sometimes i suspect that the new preset management could be the cause, and if you think that the pulsar mixer has got presets for many things....(compression etc..)

the system is:
asus tusl2c
pentium3tualatin 1.26g/512k L2 cache
512MB mushkin rev.3 at normal (133) speed
win98se with internet remover v.6
matrox g550
directx 7a (i didn't intall d.x.8 from matrox
disk).
pulsar II, pulsar I, pulsar SRB I, all forced to irq 9, software 3.01, and nothing else in the busses.

the strange fact is that at the beginning, for about 3 weeks, all was ok, but recently the issue is more frequent.

ciao, alfonso.

P.S. could you please describe your systems?


<font size=-1>[ This Message was edited by: alfonso on 2002-04-08 16:16 ]</font>

Run the Library .DLL checker here:
http://www.microsoft.com/ntworkstation/ ... ibrary.asp

This will replace DLLs that have been overwritten by programs with 'excited install' routines.

Also run DXDiag (start, run type "dxdiag" hit enter) to make sure your DirectX isn't messed up. You can often times get a working MSCRT.DLL off of your original windows install CD which fixes the problem with MSVCRT.DLL or similiar.

is it for w98se too? the page seems dedicated to nt...

alfonso - I'm not sure but it seems to work fine on WinXP. Try this for Win98 "Microsoft System File Checker"

http://www.microsoft.com/windows98/usin ... echeck.asp

I've spoken to Celmar and he has the same system as me (!). He has also reproduced the error - usually when changing the number of voices on the device. I'll report any further developments.

Thanks for the tip Subhuman, I'll try to track it down.

Alfonso: that's EXACTLY what I had under Win98 (and couldn't solve) but it disappeared in XP.

<font size=-1>[ This Message was edited by: Spirit on 2002-04-08 20:12 ]</font>

Alfonso: there should be no problem. MFC components are the same in Win98 and NT. I hope it succeeds so you can continue making these wonderful patches.
Happy pulsaring
Micha

thanks a lot!
ciao.

The good news is that Celmo's Supreme synth (probably his best of all) doesn't cause this crash problem. Maybe because it's a later design ? It's a mystery that hopefully Scope/Fusion will wash away (that's optimism eh?).

Ah, but the beatuiful Supreme synth With that and the Prisma (well, and with Lightwave, FM4, Z0405, some ModV2 patches and vodka) I can easily survive this crisis.

So Spirit, which file gives the error when you disabled auto reboot on error?

The info is:

<b>scope.sys - address F824B14C base at F8243000</b>

Is that anything to go on ?