PagedPoolSize fix and Vista? Other issues?

[rpeters83]

I tried the PagedPoolSize fix for curing the freezing/looping when playing HL2. So far in my limited testing it's fixed.

However, I'm curious if me changing it to 256 MB (from the default of 0 or automatic) will cause any issues down the road. Will it hurt performance of my desktop applications? Any other performance issues I may face with this change? Thanks.

Ryan

 

[Omnomnick]

Vista = fail.

Since its pretty brand new and everything has been fined tuned to XP, alot of things arent compatible with Vista or, they have problems when they are. For anybody that is thinking of upgrading to Vista, I would advise against for another few months, until it gets it feet on the ground.

 

[AtomicSpark]

Vista = fail.

Since its pretty brand new and everything has been fined tuned to XP, alot of things arent compatible with Vista or, they have problems when they are. For anybody that is thinking of upgrading to Vista, I would advise against for another few months, until it gets it feet on the ground.

You obviously have no idea what you're talking about. Please don't troll.

 

[AciD]

I tried the PagedPoolSize fix for curing the freezing/looping when playing HL2. So far in my limited testing it's fixed.

However, I'm curious if me changing it to 256 MB (from the default of 0 or automatic) will cause any issues down the road. Will it hurt performance of my desktop applications? Any other performance issues I may face with this change? Thanks.

Ryan

Page file is not 0 its just adjusted by OS by default.

 

[AtomicSpark]

Yes. Vista actually has decent memory management. It's SuperFetch fixes what failed in XP's Prefetch. This however doesn't make up for Vista's disappointments.

As to the original posters question, you probably shouldn't mess with the registry until guides get updated to be compatible with Vista.

 

[rpeters83]

Wow. 4 replies and not a single insight into my question.

First, I actually really enjoy Vista now that it has been patched. I prefer it way better than XP. I don't use it just for gaming, as I have a life and a career.

And I'm actually getting 77 fps on my Vista machine with every setting set to "max" and only on a stock ATI 2600 XT card, so there's no way I can say "Vista sucks".

Second, I know the page file is not 0. Zero is just the default value and is automatically adjusted by windows upon boot.

Now, can I PLEASE get some insight to my question? My guess so far is that those who replied have no idea what the fix does and shouldn't be replying in the first place. I assume that since I have Superfetch and Indexing running, Vista just needs a little more "bump" to increase that pool size, as so far, the registry trick is working and games have not crashed yet.

Thanks.

 

[PimpinPenguin]

I used that fix on XP for a few months and never encountered any issues. The issue was that too many shaders were using the pagepoolmemory and there wasn't enough of it on certain systems. Increasing manually fixes the problem although it's still recommended to set it back to default when you finished HL2.
Nicky have you used Vista? Or are you just listening to all the Vista BS that's going around

 

[rpeters83]

I used that fix on XP for a few months and never encountered any issues. The issue was that too many shaders were using the pagepoolmemory and there wasn't enough of it on certain systems. Increasing manually fixes the problem although it's still recommended to set it back to default when you finished HL2.
Nicky have you used Vista? Or are you just listening to all the Vista BS that's going around

Thanks! I actually just got the freeze again, but only for a certain map (it's a rather large deathmatch map). On pretty much every other one it didn't do it (so far).

Also, I don't recall this ever happening when playing the standalone games/episodes of HL2.

What could happen if I don't leave it at the default? What can happen to my desktop environment if I were to leave it at 256? Thanks.

 

[PimpinPenguin]

This problem has been fixed in the newer games, but when playing mods or custom maps it can still occur.
Your computer will be fine if you leave it at 256, raising it won't cause problem, it's only when you lower it then it can mess up Windows. How much Ram do you have?

 

[rpeters83]

This problem has been fixed in the newer games, but when playing mods or custom maps it can still occur.
Your computer will be fine if you leave it at 256, raising it won't cause problem, it's only when you lower it then it can mess up Windows. How much Ram do you have?

3 GB ram. (Vista 32-bit) it's a Q6600 core 2 duo and it plays the games beautifully.

I had a feeling it was just a couple maps that were doing it. This morning when I played before work it did it like 4 times in one large map but none in any others.

So 256 is good then? Will this value improve anything else I'm running (aside from just HL2/gaming)? Will having this custom value hinder anything or cause anything else to slow down)?

Again, thanks!

 

[PimpinPenguin]

The value won't improve anything else, only Source games seem to rely heavily on the pagepoolmemory so you won't see any improvement any where else. This Value also will not hinder anything thing else, application tend not to use much pagepoolmemory and 256 is more than enough for them. What ever you do, do not lower the amount as this will slow down applications and can mess up Windows.

If you want you can see what programs are using the pagepoolmemory and how much they are taking, Just go into task manager and click on view then select columns, in the list you will see "memory-paged pool" check the box and Task manager will show you how much each program is using.

 

[rpeters83]

Thanks! Last question. Is there a way to determine how much Vista would otherwise allocate on a normal basis if I set the value back to 0 (automatic)? Thanks.

:thumbs: