Page 2 of 2
Re: Possible fix for STS 5000 BSOD?
Posted: Thu Jul 23, 2020 6:51 pm
by garyb
if you're using it and having a great time, then GREAT!
i have zero problems with that.
i am sure that work will continue, as even if that method works, it is far from optimal. close to optimal would be nice...
Re: Possible fix for STS 5000 BSOD?
Posted: Thu Jul 23, 2020 8:16 pm
by dante
well you always said Scope is not a Windows soundcard, so turning it off as such in device manager seems serendipitously appropriate
Re: Possible fix for STS 5000 BSOD?
Posted: Thu Jul 23, 2020 9:12 pm
by Peter Drake
Return of VDAT would be nice, but mainly because I still have a sync card and Adat BRC around.
There are plenty of other fixes and revisions far more important. It would be nice to know what's in the works for the future. At least to know when I can retire my separate 32 bit machine that runs a bunch of .wav-dependent stuff.
As always, I'm very grateful to still be able to run 20 year old hardware that does things nothing else can.
Re: Possible fix for STS 5000 BSOD?
Posted: Thu Jul 23, 2020 9:37 pm
by garyb
dante wrote: Thu Jul 23, 2020 8:16 pm
well you always said Scope is not a Windows soundcard, so turning it off as such in device manager seems serendipitously appropriate
well, no, it doesn't make much sense since the wave drivers aren't involved with STS operation, but....
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 4:19 am
by jpo_midigods
enjoying my sampler here. Its a beast instrument for sure! cheers,
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 11:01 am
by dante
How much RAM in your computer ?
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 2:45 pm
by jpo_midigods
2 Gb of RAM, I have aprox. 512 Mb for samples.
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 2:47 pm
by dante
That might explain it - x64 bit systems address > 4GB and that may be what crashes STS - when samples or code attempt to reside/execute above the 4GB address space.
So STS may work on x64 bit systems that have < 4GB RAM.
Valis / GB ?
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 3:51 pm
by garyb
win64 and less than 8gb?
i wouldn't want that.
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 6:07 pm
by dante
Exactly - no point to x64 really unless > 4gb. Unless you provision an x64 system with only 4GB to run STS and VDAT, with a view to chucking more RAM in when (if) Scope 7.x comes out w/- fix.
Or, chuck RAM in 4GB sticks that can be disabled when booting for an STS session then reboot with full RAM when running apps that need it. Based on the **theory** STS wont crash if the system can only see 4GB or less.
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 10:30 pm
by nebelfuerst
I had no problems with STS, VDAT running V5.1 on Win7/32 with 16G and PAE patch. No RAM problems, as each task can use up to 4G.
With V7 I get this KGParam-message and no sound on STS. So there must be a change between V5.1 and V7 which kills the STS but not a hardware/OS issue.
Re: Possible fix for STS 5000 BSOD?
Posted: Sat Jul 25, 2020 11:43 pm
by dante
Are you running V7 64 bit version or V7 32 bit version ?
Re: Possible fix for STS 5000 BSOD?
Posted: Mon Jul 27, 2020 3:12 am
by jpo_midigods
jpo_midigods wrote: Sat Jul 25, 2020 4:19 am
enjoying my sampler here. Its a beast instrument for sure! cheers,
Im sorry about misunderstandings, I am using STS on XP 32bits / 2Gb RAM so 512 Mb for samples maximum, for more than 20 years (remember Gigasampler? uh)
Was i was meant is I dont need more RAM since mi heaviest STS pianos has about 512 Mb of samples.
The Rhodes set im (was) using live is surprisingly 9Mb but it has parameters for filters and synth functions of STS that makes it a really powerful and playable instrument.
By the way, if anybody knows which are the maximum RAM for STS programs on XP 32 bits please let me know, thanks
cheers, jpo
Re: Possible fix for STS 5000 BSOD?
Posted: Wed Dec 07, 2022 12:23 pm
by nebelfuerst
Thanks again for this thread ! I just ran Win10 X64 with STS5000 and VDAT.
Short story: As melodyne only runs on W10 X64, I gave one of my pci-scope pcs a try.
On first install, scope 7 loaded sts5000.64 without problems.
Then W10 downloaded lots of updates and sts5000 gave me a blue screen.
The reason for this was the driver for the onboard soundcard, which wasn't present on first run.
So i disabled its driver and it seems to work.
I just tested a few minutes, but I was able to playback sounds with sts5000, record them with Vdat and play them back again.
Re: Possible fix for STS 5000 BSOD?
Posted: Wed Dec 07, 2022 12:35 pm
by astroman
That‘s an interesting find ...
Re: Possible fix for STS 5000 BSOD?
Posted: Wed Dec 07, 2022 1:29 pm
by valis
nebelfuerst wrote: Wed Dec 07, 2022 12:23 pm
Thanks again for this thread ! I just ran Win10 X64 with STS5000 and VDAT.
Short story: As melodyne only runs on W10 X64, I gave one of my pci-scope pcs a try.
On first install, scope 7 loaded sts5000.64 without problems.
Then W10 downloaded lots of updates and sts5000 gave me a blue screen.
The reason for this was the driver for the onboard soundcard, which wasn't present on first run.
So i disabled its driver and it seems to work.
I just tested a few minutes, but I was able to playback sounds with sts5000, record them with Vdat and play them back again.
That's interesting, my Scope box has no onboard audio so might give the BSOD risk a shot.