Sonicstage 4.3 crashes system when transfering
#1
Posted 14 September 2007 - 01:23 PM
I've tried using all kinds of "alternative" software and methods but some of them won't work on Vista and the rest of them won't support my MD player model. So at this moment there is no way whatsoever for me to transfer any songs to the player.
#2
Posted 14 September 2007 - 04:34 PM
some of them won't work on Vista and the rest of them won't support my MD player model...
Not to defend Sony or SonicStage, which has never exactly been user-friendly...but Vista broke a lot of programs, so save a little of your fury for M$oft.
Meanwhile, why not use Task Manager to check out what's running before you try a SonicStage transfer, and shut down anything you might not need. If you can see what's interfering with SonicStage maybe you can solve the problem.
#3
Posted 15 September 2007 - 02:40 AM
Edit: WOAH!!! Now I had Windows crash and show me a blue screen for a couple of seconds. It said something about a serious error and preventing damage to the data and it was doing something (counting percentages) and then it restarted...
I don't even dare to test anything with Sonicstage if my computer crashes and burns every time I try to transfer music.
Edited by Postal Pete, 15 September 2007 - 04:34 AM.
#4
Posted 15 September 2007 - 04:49 AM
What you could do is try and trap the error using Process Monitor to see what files / reg keys are being accessed. If you are getting a blue screen what is the exact error message?
#5
Posted 15 September 2007 - 07:41 AM
Bob
#6
Posted 15 September 2007 - 09:05 AM
#7
Posted 08 October 2011 - 12:53 PM
I am using Win7 64bit Pro, 8GB RAM, Radeon 4870, Phenom II 965, Gigabyte GA-890FXA-UD5, OCZ SSD Agility 2 (C;\ drive), 1TB Seagate 7200 rpm storage. Certainly no slouch of a system, but had no problems running multiple applications until installing SS 4.3 Ultimate.
Any thoughts?
#8
Posted 08 October 2011 - 01:24 PM
a. wonder if you need to turn off DEP?
b. is it possible that SS only crashes when swapping? Or when starved?
Just my $.02
#9
Posted 08 October 2011 - 01:43 PM
#10
Posted 08 October 2011 - 02:01 PM
#11
Posted 08 October 2011 - 05:53 PM
#12
Posted 08 October 2011 - 06:02 PM
- Completely remove everything including all drivers ("hidden") using the procedure outlined in the (now) famous post about RH1 slowdown.
- Make sure the MZ-S1 is unplugged and stays so.
- Once you have completely removed everything, recommend a complete reboot (remember the registry only gets properly backed up when removing things if you reboot). After that make a restore point (let's be thorough here!).
- Run your games etc with OTHER software and figure out if they are actually causing the grief. After all it may be that SonicStage is legit and the games are crashing it.
- Once you have got past that phase for a few days or hours, try reinstalling Sonic Stage but under no circumstances do anything that would cause a NetMD driver of any kind to get installed.
- If that works, try adding the S1 to the mix (with the netmd760.sys driver). Does it start to crash?
I don't see any other way to conclusively prove what is happening. I recall my son had a CPU or graphics card that was overclocked and it simply crashed Windows (this was XP and W2K both) all the time until the BIOS timings on the memory and such were slowed down.
Good luck, and we look forward to hearing of your endeavours.
#13
Posted 09 October 2011 - 01:49 AM
I consider myself above average tech wise and feel like a dope for not taking this basic step in the troubleshooting process.
Thanks for all the sound advice, glad to be part of this community!
#15
Posted 17 February 2012 - 11:56 PM
#16
Posted 18 February 2012 - 08:35 AM
1. What version of Windows exactly are you using (including how many bits and what level eg home, pro, ultimate)?
2. What minidisc unit are you using? And what format of MD exactly, is causing all the grief?
3. What is pitstop? Generally anti-virus programs will prevent installations from running in a large number of cases. At the very least it needs to be disabled for install. You can figure out whether it's possible to reenable it after install by simply trying it.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users













