Oops… noticed that the end of my initial post got truncated somehow. I’m not sure how the end of the message was lost, but sorry for the abrupt ending. At least all of the essential got through. And here’s proving I can end a message in a proper salutation!
Cheers!
Mike
Sorry to come up with something so simple, but I don’t want to ignore the obvious. When you did fresh installs of PS, did you reset prefs too? It won’t happen by itself.
Not sure about how it would function with 2 gigs. The point of the slider is to leave enough so that you don’t starve your OS. Most recommendations say no more than 75% should be allocated for photoshop. The purpose is so that you don’t starve your OS. I’m no expert, and if you’re convinced that you have enough for your OS, fine, but you might see what happens when you drop it to say 50 or 75%.
Peace,
Tony
Yes, it is possible for a third party plugin to leave Photoshop in a bad state. (we really try to not have that happen with Adobe plugins).
Sorry to start this thread up again, but I am having immense trouble with a brand new 3.0 P4 machine with an Asus P4P800 deluxe MoBo & (initially) 2GB of Corsair TwinX matched DDRAM, & now Kingston matched pairs. Similar problem to Mike’s with 2GB and a 250MB file, but PS 7 executes the filter that crashes & burns with 2 Gigs (diffuse glow) just fine with one Gig pair removed. No other changes to the system at all.
Ram allocation is set at 75%. (Same filter ran fine on the old P111 1.0 machine with 1.5 Gigs if SDRAM also allocated at 75%).
Deduction led me down the hardware issue track, but after reading Chris’s reply here about some filters taxing even a 2 Gig machine, I gotta ask – why does it work with 1 Gig (or, realistically, 750MB) and not with 2 Gig (1,500MB)?
Why does the event that happens with 2 Gigs stop the whole show with the "out of memory dialog", yet with 1 Gig less the thing just goes to scratch?
Fred.
Most likely because you have some bad RAM or a bad motherboard.
Some filters aren’t very good about how they allocate memory. Try running with a lower memory percentage (60% or 50%) and see if that fixes the issue. The filter is probably trying to allocate one huge chunk of memory and that may simply not be available.
-Scott
Thanks both for the replies –
Chris, the MoBo has been replaced once already, and the dealer tried the same setup on a Gigabyte MoBo with the same result – worked with 1 gig, failed at 2 gigs. So the dealer is now blaming Photoshop, & I’m relying on answers here to persuade him otherwise. Interestingly enough, 3 sticks (1.5 gigs) runs fine in single channel mode as well. It seems to be full slots running 2 gigs in dual channel mode that upsets the cart, even though the MoBo is rated to 4 gigs, dual channel.
I’ve already emailed him several answers in previous forum threads re PS running OK up to 2 gigs, but your answer regarding filters taxing a 2 gig machine was thrown back at me. Personally, it still stinks like a hardware issue to me, even though 3 different sets of matched DDR RAM have been tried on 3 MoBo’s. (RAM is 400Mhz PC3200 running on the 800Mhz fsb i865 chip board, as per manufacturer recommendation. Scratch is on 2x 120GB 7200 SATA drives as RAID 0).
Scott, I tried all the way down to 40% RAM allocation to no avail – 1 gig works, 2 gig doesn’t. I can’t understand why the filter crashes instead of going to scratch as it does with less RAM. Maybe it really is way-out bad luck that I am continually getting dodgy hardware.
Thanks again,
Fred.
It’s not Photoshop.
Yes, it is still 99% likely to be a hardware problem.
