XXHighEnd

Ultimate Audio Playback => XXHighEnd Support => Topic started by: JohanZ on November 12, 2007, 02:29:15 pm



Title: Disabling Virtual Memory can cause errors
Post by: JohanZ on November 12, 2007, 02:29:15 pm
Quote
I think the disabling of Virtual RAM was the tweak that fixed it

On a regulare base I had memory errors during XX usage. At a certain moment I was realizing that I had disabled the Virtual ram. Tweak from the past : http://imageevent.com/cics/v03theartofbuildingcomputertrnsp;jsessionid=t9hii13rc1.zebra_s

After enabling the Virtual RAM the memory problems are gone! So be aware of memory errors!

Regards, Johan


Title: Disabling Virtual Memory can cause errors
Post by: Calibrator on November 13, 2007, 06:08:13 am
G'day Johan  :smile:

I'm not fully understanding what you are saying here. If you are implying that you had 'memory errors' when you disabled virtual memory and that all was fine after you re-enabled it, that would only indicate that you had insufficient physical RAM memory available for your systems needs. If these 'memory errors' were caused by a physical defect in the RAM chips themselves then these errors would be evident regardless of whether virtual memory was enabled or not.

For my part, I haven't experienced a single glitch or stutter since disabling virtual memory several days ago. I am now confident I have solved that issue  :yahoo:

Cheers :smile:

Russ


Title: Disabling Virtual Memory can cause errors
Post by: JohanZ on November 13, 2007, 09:07:53 am
Hi Russ,

Quote
If you are implying that you had 'memory errors' when you disabled virtual memory and that all was fine after you re-enabled it, that would only indicate that you had insufficient physical RAM memory available for your systems needs.

Indeed, after the re-enabling of the virtual memory I've not seen any memory errors in a week. For me it solved a problem.

Regards,

Johan


Title: Disabling Virtual Memory can cause errors
Post by: PeterSt on November 13, 2007, 09:10:04 am
Can you be more precise on "Memory error" ?


Title: Disabling Virtual Memory can cause errors
Post by: JohanZ on November 13, 2007, 10:25:52 am
Hi Peter,

See http://www.phasure.com/index.php?topic=184.msg1145#msg1145

Johan


Title: Re: Disabling Virtual Memory can cause errors
Post by: PeterSt on November 13, 2007, 11:12:24 am
But Johan, something is not right here;

Although it would (at last) explain the "errors" you referred to in the other thread, the screen shots you have in there show virtual memory being present ("wisselbestand" = paging file) ...

Anyway, if this is what you mean, obviously you just ran out of physical memory.


Title: Re: Disabling Virtual Memory can cause errors
Post by: JohanZ on November 13, 2007, 12:12:32 pm
I have test it again. Disabled the usage of virtual memory and did a reboot of the system. See the screenshots. I don't understand the reason but you can still see the usage of virtual memory (wisselbestand=...)


Title: Re: Disabling Virtual Memory can cause errors
Post by: PeterSt on November 13, 2007, 12:29:56 pm
Ah, I see. So that's the physically allocated disk space then (currently used or not). But look at the bottom of the first screenshot. It says "Currently allocated : 0".

Thanks Johan.


Title: Re: Disabling Virtual Memory can cause errors
Post by: PeterSt on November 13, 2007, 12:41:50 pm
Remember, you should have memory space of (around) 500MB for Vista itself, plus 3 times the filesize of the largest track you play (can be 2 times only, depending on "situations"). Two subsequent tracks at full CD length would be a no go (but who has that :secret:).

Note that this "rule" does not incorporate the disabling of virtual memory. It's up to you now to find the limits, or better : up to your Vista (generally you are not the boss in there).


Title: Re: Disabling Virtual Memory can cause errors
Post by: PeterSt on April 07, 2008, 02:07:27 pm
Hmm ... Today I tried to switch off the paging file of myself. It appears to be impossible ...
To me it looks like that the OS will always be using it for itself. "Itself" does not mean XX, because when XX needs it, it errors (out of memory).