XXHighEnd

Hi Peter,

After 2 or 3 days of using XXHE (never switch the computer off) I get after a play-command the following message "Straight Contiguous Memory Allocation error 3-Lower SFS, reboot or choose another type (0:1450 Total result= 251658240). Music don't start to play. Lowering SFS from 10 to 1 has no effect. After the reboot all is working ok for a few days.

Any suggestions?

Best regards Johan

Hi Johan,

What is your Max SFS set to ?

Regards,
Peter

Max sfs=120

Hi Peter,

same here

with
 Max sfs=120
 Min= 10,00

Joachim

Johan, Joachim, this is VERY strange.
May it help ... my Audio PC runs for weeks and weeks without reboot and is used every day with (on estimate) 10 starts of Playback.

Do more people suffer from this ?

Thanks,
Peter

Caused by Underclocking?

Hi,

I think I have at least one very good reason : You leave the Audio PC in a state of XXEngine3.exe not running (this one keeps the memory allocated). So for example, when you receive an error because of sample rate mismatch ("Device can't play" and the like) and then think "oh well, let's call it a day", then tomorrow the contiguous memory required will have been eaten.

More situations of this may exist, like you killing Engine3 yourself (the Blue Led) or ... change the SFS. This latter is quite harmless because when playback starts XXEngine3 is killed and right after that (0.1 sec) restarted, but when you are low on memory right in between it can be eaten.

Btw, after the new Crack Detect procedure Engine3 is also killed.

People must know that it is the Max SFS which is rejected at some stage. Not the SFS itself. So the Max SFS reserves the memory ...

Peter

Hi Peter,

First: Best wishes for this new year.

I do not quite understand what you are trying to explain. Is there a solution for this Memory Allocation Error? I still have it every 2 days. I can only play further with the mixed contiguous memory setting. What other parameter can I change to solve this?

Best regards Johan

I've tried to free memory with the Garbage Collect button. After a week all seems to work ok, but in the afternoon the Memory Message again.  :old: Another thing I have noticed with this Garbage Collect ON every time after a PLAY command I get a Free Memory Message "Attempts: 11 Current CPU%........Continue?  YES/NO
see also http://www.phasure.com/index.php?topic=3706.msg39515#msg39515
When I switched Garbage Collect OFF, No Free Memory message again, but within 2 days the Straight Contiguous is back again.

Hi Johan,

I can't tell what you suffer from.
What I implied to say in my previous post is that you should lower the Max SFS. So if you use ~20 for your SFS, set Max SFS to the maximum you will allow yourself toying with. So if that is 30 for the forseable (boot) future, set Max SFS to 30.

Now you have at least quite a lot more memory available.

I am pretty sure you cause the system to have too few memory available, and then have XXEngine3.exe be killed by one or the other reason (can be something which goes wrong, with for example the Crack Detect being tripped - you will always get some sort of message). If now the system is eager for memory, it will right away occupy the contiguous space XXEngine3.exe *had* allocated, and then you're done.

Does lowering the Max SFS help ?

Regards,
Peter

Hi Peter,
I changed The max sfs to 30. Until yesterday all was werking ok. Today I had this straight contiguous memory allocation errormessage again.

During this period i have every day this Free memory message direct after a play command when Garbage collectie button is active.

Regards Johan

Hi Johan,

So indeed it must be related to something which keeps your PC busy and eats the memory.
The question could now be : does this bother so much to bother you ?  :)

Regards,
Peter

Hi Peter,

No, only every 20 day’s a reboot of the system. It takes a few minutes inclusieve placing and removing the harddisk. I like it more when i don’t have to do that.

Is there a solution for the garbage collect button?

Regards
Johan

Activate it again ... haha.
Maybe it can work now because of your lower Max SFS ?



I don't think it is about 20 days or such; it will be - after an amount of time (x days ?) - that you do something that makes the sound engine disappear (stop) and *then* the memory wil be eaten right away because it was pushing already (too few of it because of the for us unknown reason).

Did you consider to "reinstall" the OS by means of such a "Copy" file ? Backup / Restore (http://www.phasure.com/index.php?topic=3480.0)
It only takes the work of the copying, after knowing jow to access it (which means boot into one of the other OSes first). Then we can also see whether this is right from the start now, after aplying 2.09 to it. And of course write down your important settings before doing it all.
I am not saying that you *have to* do this, but we may learn something from it.

Regards,
Peter

Hi Peter,

Small update.
After Your suggesties to reinstall the OS, I switched back to W10-10586.0. So far all is werking ok, except “ garbage collect” still that message every time after a play command. Soundwise I prefere the latest OS W10-14393.0. Another difference I have seen more crashes/stops during a playback session in 14393. In 10586 I’ve seen less then 5 times stops during a playback in this period. But never that message “Straight Contiguous Memory Allocation error 3-Lower SFS, reboot or choose another type (0:1450 Total result= 251658240)”

Soon I will reinstall 14393 to test it again.

The XXHE PC uses 32 GB om RAM. I’ve red somewhere in your suggesties that 4GB is the minimum. To slow? I’m using a i7 4770K Hyperthreading On (8 cores)

Best regards,
Johan

Hi Johan,


Yeah, you read that from my post today, but possibly you misread that. I said : I recall that 4GB ever back was the minimum and probably this was with Vista or even XP.
It is by no means valid today. I just don't know.


Can you please qualify that ?
I mean, I don't know about "stops" as such without any error message. I also don't know about crashes which go without error message. And all I actually do know is that I use the same OS install(s) as you do (RAM-OS Disk) and that the really only reason for playback to stop is the "Crack Detect" tripping, which is too tight for 2.09 (will be wider in 2.10).
... But I use another PC ... Important ? to some extent of course Yes, but it would only be of real importance if a 100 people would jump in and tell they have the same issue.

Something else - and I suggested that recently - is that the Core Appointment can do wonders. What is required in which environment is beyond me though (I just am not able to know it).

Anyway ... by no means this is a message of "it is you and you must be doing something wrong". The contrary; I only try to indicate that all can be fine as it is, but with which settings it goes "off" I can't tell. Again, if a few more people would be able to confirm this, it would be far more easy to look in "a" direction. And I am here to work things out ...

Regards,
Peter

PS: To be complete, what I do know from the RAM-OS Disk is that the W8 install is not stable really. 10074 is also "so-so" by now, but doable. From the others I see no issues myself, nor do I hear from them.

Doh, my luck. Guess the version I'm using? ;)