63 replies to this topic

[eniparadoxgma]

The good news (I am knocking on wood as I type this):

I haven't had any blue screens for like a week. Here's what I think fixed it:

I was also getting crappy errors when trying to play DoD: Source or Team Fortress 2 that would give me errors related to being out of "paged pool memory" whatever-t-f that is. SO, after googling for at least an eternity or more, trying innumerable fixes, etc...I finally found this one:



I recognized the fix from other threads and thought I'd tried it unsuccessfully. However, I entered the third option into the registry and I haven't had any steam errors or BSODs since. So (knock mfin knock) I think I found out what the problem was...kind of.

So, anybody know what the hell this paged pool memory issue is or why it was screwing me up?

[USM]

Good info enip!!!

[eniparadoxgma]

The Bad News:

Got the same Steam error last night. I think it has to do with running other programs while trying to start a Steam game.

The Good News:

Still no BSODs.

[m.oreilly]

heck bra, hope you fixed 'er.
i dunno if you use winguides tweak manager, but it has some neat options (i always install it when using xp):

http://www.pctools.c...ry/detail/1015/

Quote

Windows normally calculates the paged and non paged pool memory sizes using complex algorithms based on physical memory size

looks like you increased the page size, and it took care of your issue