Re: [hlds] Client crash question
Hello, I am trying to launch a dedicated server but I don't see it showing up on my client when I search under LAN. Below is the output of the dedicated server. I see a few errors but am not sure how to fix it. Thanks. == 64.0 fps 0/16 on map de_dust2 Console initialized. Game.dll loaded for Counter-Strike: Source maxplayers set to 16 Network: IP 10.1.109.32, mode MP, dedicated Yes, ports 27015 SV / 27005 CL Executing dedicated server config file Incorrect price blob version! Update your server! ERROR: mp_dynamicpricing set to 1 but couldn't download the price list! Error: Material sprites/bubble : proxy AnimatedTexture not found! Section [Scenes]: 0 resources total 0 bytes, 0.00 % of limit (2.10 MB) Server logging enabled. Server logging data to file logs\L1006001.log L 10/06/2008 - 13:06:25: Log file started (file logs\L1006001.log) (game C:\s rcds\cstrike) (version 3531) L 10/06/2008 - 13:06:25: server_cvar: sv_voiceenable 0 L 10/06/2008 - 13:06:25: server_cvar: sv_cheats 0 L 10/06/2008 - 13:06:25: server_cvar: sv_pausable 0 couldn't exec banned_users.cfg couldn't exec bot.cfg couldn't exec mani_server.cfg L 10/06/2008 - 13:06:25: World triggered Round_Start Adding master server 68.142.72.250:27011 Adding master server 72.165.61.189:27011 VAC secure mode is activated. == ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
have u set sv_lan 1 ? 2008/10/6 Charles Chang [EMAIL PROTECTED] Hello, I am trying to launch a dedicated server but I don't see it showing up on my client when I search under LAN. Below is the output of the dedicated server. I see a few errors but am not sure how to fix it. Thanks. == 64.0 fps 0/16 on map de_dust2 Console initialized. Game.dll loaded for Counter-Strike: Source maxplayers set to 16 Network: IP 10.1.109.32, mode MP, dedicated Yes, ports 27015 SV / 27005 CL Executing dedicated server config file Incorrect price blob version! Update your server! ERROR: mp_dynamicpricing set to 1 but couldn't download the price list! Error: Material sprites/bubble : proxy AnimatedTexture not found! Section [Scenes]: 0 resources total 0 bytes, 0.00 % of limit (2.10 MB) Server logging enabled. Server logging data to file logs\L1006001.log L 10/06/2008 - 13:06:25: Log file started (file logs\L1006001.log) (game C:\s rcds\cstrike) (version 3531) L 10/06/2008 - 13:06:25: server_cvar: sv_voiceenable 0 L 10/06/2008 - 13:06:25: server_cvar: sv_cheats 0 L 10/06/2008 - 13:06:25: server_cvar: sv_pausable 0 couldn't exec banned_users.cfg couldn't exec bot.cfg couldn't exec mani_server.cfg L 10/06/2008 - 13:06:25: World triggered Round_Start Adding master server 68.142.72.250:27011 Adding master server 72.165.61.189:27011 VAC secure mode is activated. == ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
link with evidence on vista changes with PPM please. On Sat, Oct 4, 2008 at 4:23 PM, Richard Eid [EMAIL PROTECTED] wrote: In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed. The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most people find the need to fine tune that usage in increments of 512, but can be fine tunes in 16-32-64 bit increments if the program you are using recognizes this. Here is another link a bit more relavent(?) to Vista and explains the paging situation with 32 vs 64 bit O/S and covers some server 2003 instances. http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders tanding-pool-resources.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 1:23 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) On Sat, 4 Oct 2008 02:13:51 -0500, Luke Lewis [EMAIL PROTECTED] wrote: Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed. The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most people find the need to fine tune that usage in increments of 512, but can be fine tunes in 16-32-64 bit increments if the program you are using recognizes this. Here is another link a bit more relavent(?) to Vista and explains the paging situation with 32 vs 64 bit O/S and covers some server 2003 instances. http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders tanding-pool-resources.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 1:23 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via
Re: [hlds] Client crash question
The following link should explain it all. It seems that there is actually a limit(and since Vista SP1, a limit can actually be set, if desired), but not to the degree that previous versions of Windows have. For our purposes here, in running the servers and the actual game, those of us using Vista needn't worry about PPM limits. The PPM limit is equal to that of the available kernel-mode virtual address space. As for Saint K., I'd still give the earlier link I posted a shot...the one at halflife2.net. It's worked for countless numbers of people, and you describe a situation where you could easily run into problems directly related to it. Oh, that link... http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_vista -Richard Eid On Sat, Oct 4, 2008 at 11:26 AM, localhost [EMAIL PROTECTED] wrote: Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) On Sat, 4 Oct 2008 02:13:51 -0500, Luke Lewis [EMAIL PROTECTED] wrote: Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed. The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most people find the need to fine tune that usage in increments of 512, but can be fine tunes in 16-32-64 bit increments if the program you are using recognizes this. Here is another link a bit more relavent(?) to Vista and explains the paging situation with 32 vs 64 bit O/S and covers some server 2003 instances. http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders tanding-pool-resources.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 1:23 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus
Re: [hlds] Client crash question
Ok you're saying exactly what I was saying so thanks? And Richard thanks for the link, but it only shows that Vista still has the 4GB limit. Either way thanks for the link it did provide me with some knowledge. Either way I guess this is pointless now lol. Thanks Richard for your input! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Subject: Re: [hlds] Client crash question Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) __ Information from ESET NOD32 Antivirus, version of virus signature database 3495 (20081004) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
4GB limit on what? Maybe I missed something there. I thought we were talking about PPM and not Memory Management as a whole. Or has the conversation expanded? -Richard Eid On Sat, Oct 4, 2008 at 2:54 PM, Luke Lewis [EMAIL PROTECTED] wrote: Ok you're saying exactly what I was saying so thanks? And Richard thanks for the link, but it only shows that Vista still has the 4GB limit. Either way thanks for the link it did provide me with some knowledge. Either way I guess this is pointless now lol. Thanks Richard for your input! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of localhost Subject: Re: [hlds] Client crash question Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) __ Information from ESET NOD32 Antivirus, version of virus signature database 3495 (20081004) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Hi, I've tried the register edit, unfortunately its not working. I have checked the task manager for pool page memory usage, but everything is really low, all together it will barley top 2MB. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 7:59 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question The following link should explain it all. It seems that there is actually a limit(and since Vista SP1, a limit can actually be set, if desired), but not to the degree that previous versions of Windows have. For our purposes here, in running the servers and the actual game, those of us using Vista needn't worry about PPM limits. The PPM limit is equal to that of the available kernel-mode virtual address space. As for Saint K., I'd still give the earlier link I posted a shot...the one at halflife2.net. It's worked for countless numbers of people, and you describe a situation where you could easily run into problems directly related to it. Oh, that link... http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits _windows_vista -Richard Eid On Sat, Oct 4, 2008 at 11:26 AM, localhost [EMAIL PROTECTED] wrote: Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) On Sat, 4 Oct 2008 02:13:51 -0500, Luke Lewis [EMAIL PROTECTED] wrote: Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed. The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most people find the need to fine tune that usage in increments of 512, but can be fine tunes in 16-32-64 bit increments if the program you are using recognizes this. Here is another link a bit more relavent(?) to Vista and explains the paging situation with 32 vs 64 bit O/S and covers some server 2003 instances. http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders tanding-pool-resources.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 1:23 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000, which you can observe using System Information in Process Explorer. With Vista, you really don't have to worry about it. -Richard Eid On Sat, Oct 4, 2008 at 1:35 AM, Luke Lewis [EMAIL PROTECTED] wrote: Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent
Re: [hlds] Client crash question
I wouldn't trust Task Manager's numbers. Use Process Explorer instead. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx When you get it installed, press Ctrl-I to bring up System Information. It'll show you the real values of what's in use. 2MB seems extremely low for PPM usage. If you have time, post a screenshot of your System Information window. Also, in that HL2.net post, what value did you choose to use? -Richard Eid On Sat, Oct 4, 2008 at 3:28 PM, Saint K. [EMAIL PROTECTED] wrote: Hi, I've tried the register edit, unfortunately its not working. I have checked the task manager for pool page memory usage, but everything is really low, all together it will barley top 2MB. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 7:59 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question The following link should explain it all. It seems that there is actually a limit(and since Vista SP1, a limit can actually be set, if desired), but not to the degree that previous versions of Windows have. For our purposes here, in running the servers and the actual game, those of us using Vista needn't worry about PPM limits. The PPM limit is equal to that of the available kernel-mode virtual address space. As for Saint K., I'd still give the earlier link I posted a shot...the one at halflife2.net. It's worked for countless numbers of people, and you describe a situation where you could easily run into problems directly related to it. Oh, that link... http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits _windows_vista -Richard Eid On Sat, Oct 4, 2008 at 11:26 AM, localhost [EMAIL PROTECTED] wrote: Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) On Sat, 4 Oct 2008 02:13:51 -0500, Luke Lewis [EMAIL PROTECTED] wrote: Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about 3.5GB with 4 installed. The /Userva= switch has a max allowed usage of 3070 which is a full 3Gb most people find the need to fine tune that usage in increments of 512, but can be fine tunes in 16-32-64 bit increments if the program you are using recognizes this. Here is another link a bit more relavent(?) to Vista and explains the paging situation with 32 vs 64 bit O/S and covers some server 2003 instances. http://blogs.technet.com/askperf/archive/2007/03/07/memory-management-unders tanding-pool-resources.aspx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 1:23 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question In this case, physical RAM has little to do with PPM. Surely, 64-bit Vista makes a difference with RAM sizes above 4GB, but he's not running out of physical RAM, he's running out of PPM. In XP and earlier, you'll want to try to keep the PPM usage below 150,000
Re: [hlds] Client crash question
How to check your paged pool memory 1. Download and extract Process Explorerhttp://www.microsoft.com/technet/sysinternals/processesandthreads/processexplorer.mspx . 2. Run Process Explorer. Press CTRL + i to bring up the System Information window. 3. Run the game in a window. - Go to Steam's My games menu. - Right-click on the problematic game. - Select Properties General Set launch options. - Add -sw to the launch options. - Launch the game. 4. *Watch the System Information Kernel Memory (K) Paged Physicalvalue. * If the value exceeds 150MB, you are using too much paged pool memory. That's from: https://support.steampowered.com/kb_article.php?ref=5034-EIPV-6426 Sorry for another e-mail...I just wanted to point out how exactly you should be troubleshooting this issue. The portion that I bolded(if formatting makes it through the mailing list) is what you should be looking at. -Richard Eid On Sat, Oct 4, 2008 at 3:42 PM, Richard Eid [EMAIL PROTECTED] wrote: I wouldn't trust Task Manager's numbers. Use Process Explorer instead. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx When you get it installed, press Ctrl-I to bring up System Information. It'll show you the real values of what's in use. 2MB seems extremely low for PPM usage. If you have time, post a screenshot of your System Information window. Also, in that HL2.net post, what value did you choose to use? -Richard Eid On Sat, Oct 4, 2008 at 3:28 PM, Saint K. [EMAIL PROTECTED] wrote: Hi, I've tried the register edit, unfortunately its not working. I have checked the task manager for pool page memory usage, but everything is really low, all together it will barley top 2MB. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Saturday, October 04, 2008 7:59 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question The following link should explain it all. It seems that there is actually a limit(and since Vista SP1, a limit can actually be set, if desired), but not to the degree that previous versions of Windows have. For our purposes here, in running the servers and the actual game, those of us using Vista needn't worry about PPM limits. The PPM limit is equal to that of the available kernel-mode virtual address space. As for Saint K., I'd still give the earlier link I posted a shot...the one at halflife2.net. It's worked for countless numbers of people, and you describe a situation where you could easily run into problems directly related to it. Oh, that link... http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits _windows_vista -Richard Eid On Sat, Oct 4, 2008 at 11:26 AM, localhost [EMAIL PROTECTED] wrote: Not sure how you're using the word paging and you've also got a pretty important typo in your first sentence. On 32-bit OS, each process can have up to 2gig of virtual memory, and the kernel takes the other 2. On a 32 bit OS with the /3gb switch, the kernel only takes 1 gig, and _if the process has the correct flag saying it can use memory over 2gig_ (large address aware iirc), it can then use up to 3. On a 64-bit OS, the /3gb switch isn't necessary. Instead, if a process has large address aware set, it can address up to 4 gigs of memory. If not, still 2. As PPM is a kernel level thing, specifying /3gb switch on 32-bit OS will reduce the PPM size, and (unless you have large address aware programs that need the virtual memory, have no beneficial effect) On Sat, 4 Oct 2008 02:13:51 -0500, Luke Lewis [EMAIL PROTECTED] wrote: Actually the /3Gb switch enables 32 bit operating systems to page memory above 3Gb of memory rather that memory is physical or virtual. In 32 bit operating systems client services or programs once they have paged above 2GB per instance will crash. The 3GB switch for 32 bit operating systems allow programs to use up to 3GB of memory addressing per instance in fact with 3-4 GB installed into the machine you should see equal virtual memory with physical memory in most cases. In default configuration Windows will allocate 2GB for the operating system and 2GB max for all other operations such as services or programs. With the PAE switches, especially the /userva= switch you can allow the operating system to issue 3GB of paging/physical memory to each running instance allowing Windows to only use 1GB. Hence the reason all 32 bit windows operating systems only paging 4GB max. Depending on USB devices and how memory are mapped on those most installations of 32 bit (non-server) O/S's only will see a max of about
Re: [hlds] Client crash question
Vista does indeed suffer from the 4GB barrier that Windows XP has, unless you use the 64bit version of either operating system or use a server operating system. Note this is an article from 2005 so obviously Vista isn't inside this list but this is what I'm referring to. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx -Original Message- Sent: Thursday, October 02, 2008 9:02 PM Subject: Re: [hlds] Client crash question Vista doesn't have the same Paged Pool and Non-Paged Pool limits that previous Microsoft operating systems do. Unless I'm mistaken, there is no upper limit in Vista for Paged Pool memory. So it does matter what OS you are on. -Richard Eid __ Information from ESET NOD32 Antivirus, version of virus signature database 3494 (20081003) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com Sent Via http://www.gorillazsouth.com mail server. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Last time I had an issue like this was because of video drivers and virtual memory address spacing. Being on 64 bit you shouldn't have a virtual memory problem as Windows doesn't have a 2GB limit on 64 bit for applications. SO I would try looking elsewhere besides your ram, more specifically on the settings for your video card. If you are running the newest nVidia drivers I would stear clear of nhancer, and test all your card settings at lower rates because the newest drivers are a lot stronger than the old ones. And it wouldn't matter if he was on XP, XP64, Vista or Windows 98SE he would still have this problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Eid Sent: Wednesday, October 01, 2008 8:59 AM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question Give this a shot. http://www.halflife2.net/forums/showthread.php?t=131328 It's been quite helpful to a lot of people. By the way, with Vista, you would never have this problem. ;) -Richard Eid On Wed, Oct 1, 2008 at 1:44 AM, Ook [EMAIL PROTECTED] wrote: I've used XP64 for a long time, and it is rock solid. Very few things don't work with XP64. TF2 uses a ton of paged pool. It and Steam both use a lot of GDI objects. Tsk tsk tsk, Valve. Mirc and winamp and AVG don't use squat for resources. As much as resource pigs Steam and hl2.exe might be, they still don't use enough to cause problems. I can start TF2 with mirc, avg, and winamp running. And a slew of other things as well. Something else is wrong. I would suggest the OP open up task manager, add Paged Pool and non-paged pool to the sensor list, and see what is using resources. - Original Message - From: Anthal [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:07 AM Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds __ Information from ESET NOD32 Antivirus, version of virus signature database 3486 (20081001) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus
Re: [hlds] Client crash question
Give this a shot. http://www.halflife2.net/forums/showthread.php?t=131328 It's been quite helpful to a lot of people. By the way, with Vista, you would never have this problem. ;) -Richard Eid On Wed, Oct 1, 2008 at 1:44 AM, Ook [EMAIL PROTECTED] wrote: I've used XP64 for a long time, and it is rock solid. Very few things don't work with XP64. TF2 uses a ton of paged pool. It and Steam both use a lot of GDI objects. Tsk tsk tsk, Valve. Mirc and winamp and AVG don't use squat for resources. As much as resource pigs Steam and hl2.exe might be, they still don't use enough to cause problems. I can start TF2 with mirc, avg, and winamp running. And a slew of other things as well. Something else is wrong. I would suggest the OP open up task manager, add Paged Pool and non-paged pool to the sensor list, and see what is using resources. - Original Message - From: Anthal [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:07 AM Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
AVG caused me a lot of issues, and so I had to remove it. Try disabling that Regards 2008/9/30 Saint K. [EMAIL PROTECTED] Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Saint, You might try manually forcing WINAMP onto one specific core / affinity and perhaps try setting the priority to below normal and see if that helps. You might be seeing some sort of codec conflict too, if you have a custom codec pack installed, try temporarily uninstalling it and see if that helps. AVG has been flagged in the past as a problem, you might try one of the other free AVG programs - antivir from Avira has been getting some good reports. You get links / downloads to most of the free A/V programs in my toolkit: http://qsextreme.com/qs_toolkit I have an XP64 test system here, if I get a chance I'll see if I can recreate the crash. qUiCkSiLvEr === - Original Message - From: Saint K. To: 'Half-Life dedicated Win32 server mailing list' hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:13 AM Subject: Re: [hlds] Client crash question Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, == -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). On 9/30/08, Saint K. wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
I have XP x64, I have a few small error messages that come up sometimes but nothing bad. Most are suppose to be caused from SP3 not being installed, unlike 32 bit XP we cant get SP3 yet. I emailed Microsoft and they said theres no ETA if there ever will be one, they are working out the bugs and drivers... - Original Message From: Yatin Vadhia [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:18:19 AM Subject: Re: [hlds] Client crash question AVG caused me a lot of issues, and so I had to remove it. Try disabling that Regards 2008/9/30 Saint K. [EMAIL PROTECTED] Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
Thanks for the suggestions! I'll have a go at it tomorrow night! Saint K. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Ottalini Sent: Tuesday, September 30, 2008 8:40 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question Saint, You might try manually forcing WINAMP onto one specific core / affinity and perhaps try setting the priority to below normal and see if that helps. You might be seeing some sort of codec conflict too, if you have a custom codec pack installed, try temporarily uninstalling it and see if that helps. AVG has been flagged in the past as a problem, you might try one of the other free AVG programs - antivir from Avira has been getting some good reports. You get links / downloads to most of the free A/V programs in my toolkit: http://qsextreme.com/qs_toolkit I have an XP64 test system here, if I get a chance I'll see if I can recreate the crash. qUiCkSiLvEr === - Original Message - From: Saint K. To: 'Half-Life dedicated Win32 server mailing list' hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:13 AM Subject: Re: [hlds] Client crash question Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, == -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). On 9/30/08, Saint K. wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
XP x64 is based on the server2003 core, so x64 SP1 is comparable to 32bit SP2 etc On Tue, 30 Sep 2008 11:48:59 -0700 (PDT), DontWannaName! [EMAIL PROTECTED] wrote: I have XP x64, I have a few small error messages that come up sometimes but nothing bad. Most are suppose to be caused from SP3 not being installed, unlike 32 bit XP we cant get SP3 yet. I emailed Microsoft and they said theres no ETA if there ever will be one, they are working out the bugs and drivers... - Original Message From: Yatin Vadhia [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:18:19 AM Subject: Re: [hlds] Client crash question AVG caused me a lot of issues, and so I had to remove it. Try disabling that Regards 2008/9/30 Saint K. [EMAIL PROTECTED] Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
My problem was alot more basic than what's here, but what I did was uninstall all anti-virus programs I didn't use, and close all other internet connections. On Tue, Sep 30, 2008 at 3:04 PM, lists [EMAIL PROTECTED] wrote: XP x64 is based on the server2003 core, so x64 SP1 is comparable to 32bit SP2 etc On Tue, 30 Sep 2008 11:48:59 -0700 (PDT), DontWannaName! [EMAIL PROTECTED] wrote: I have XP x64, I have a few small error messages that come up sometimes but nothing bad. Most are suppose to be caused from SP3 not being installed, unlike 32 bit XP we cant get SP3 yet. I emailed Microsoft and they said theres no ETA if there ever will be one, they are working out the bugs and drivers... - Original Message From: Yatin Vadhia [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:18:19 AM Subject: Re: [hlds] Client crash question AVG caused me a lot of issues, and so I had to remove it. Try disabling that Regards 2008/9/30 Saint K. [EMAIL PROTECTED] Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit
Re: [hlds] Client crash question
I know this is not what you want to hear but if everything else fails then I would like to put in a good word for foobar2000. It's another music player that may or may not do the exact same thing. :) On Tue, Sep 30, 2008 at 9:41 PM, Jake E [EMAIL PROTECTED] wrote: My problem was alot more basic than what's here, but what I did was uninstall all anti-virus programs I didn't use, and close all other internet connections. On Tue, Sep 30, 2008 at 3:04 PM, lists [EMAIL PROTECTED] wrote: XP x64 is based on the server2003 core, so x64 SP1 is comparable to 32bit SP2 etc On Tue, 30 Sep 2008 11:48:59 -0700 (PDT), DontWannaName! [EMAIL PROTECTED] wrote: I have XP x64, I have a few small error messages that come up sometimes but nothing bad. Most are suppose to be caused from SP3 not being installed, unlike 32 bit XP we cant get SP3 yet. I emailed Microsoft and they said theres no ETA if there ever will be one, they are working out the bugs and drivers... - Original Message From: Yatin Vadhia [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:18:19 AM Subject: Re: [hlds] Client crash question AVG caused me a lot of issues, and so I had to remove it. Try disabling that Regards 2008/9/30 Saint K. [EMAIL PROTECTED] Hi, Thanks for the suggestions. I've already ran memtests, and all report being O.K. I also tried to increase my virtual memory, but that hasn't helped either. Besides Winamp, pretty much nothing is running at the moment I start TF2. The only things which are turned on are AVG (which is low on resources), mIRC and winamp. I could imagine something like this occurs on a heavy loaded machine, but this one is pretty much idle when the game is started. Cheers, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthal Sent: Tuesday, September 30, 2008 8:08 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
I have XP x64, run Winamp all the time, and have never received this issue. Saint K. wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Client crash question
I've used XP64 for a long time, and it is rock solid. Very few things don't work with XP64. TF2 uses a ton of paged pool. It and Steam both use a lot of GDI objects. Tsk tsk tsk, Valve. Mirc and winamp and AVG don't use squat for resources. As much as resource pigs Steam and hl2.exe might be, they still don't use enough to cause problems. I can start TF2 with mirc, avg, and winamp running. And a slew of other things as well. Something else is wrong. I would suggest the OP open up task manager, add Paged Pool and non-paged pool to the sensor list, and see what is using resources. - Original Message - From: Anthal [EMAIL PROTECTED] To: Half-Life dedicated Win32 server mailing list hlds@list.valvesoftware.com Sent: Tuesday, September 30, 2008 11:07 AM Subject: Re: [hlds] Client crash question XP x64 is notoriously buggy. Most things just don't work well in it. The Paged Pool Memory error is a common bug. If it happens less with LESS RAM, I'd run error checks on your memory. It could be that some of the sticks are bad, or are going bad. You may also want to increase the size of your virtual memory, and close any programs that may be memory hogs (Firefox, IE, virus scanners, etc). Saint K. wrote: Your so god damn funny... I wish we had more people like you on this list. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 6:09 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Client crash question dont run winamp! On 9/30/08, Saint K. [EMAIL PROTECTED] wrote: Anyone ells here experiencing the most utterly annoying bug that when you have winamp playing, and you try to join a TF2 game, you get 75% of the time a crash to desktop with some message 'running out of pool page memory' with some dodgy link to a steam website with a fix (which doesn't work). This only seems to happen on windows XP x64, on my 32bit install these problems are not present. Also when running on 2GB instead of 4GB the error happens a lot less. I've mailed VALVe about it a couple of times, but I get no response, so I thought I'd drop the question in here to see if anyone knows a fix other then the 'fix' on the steam page (some reg edit). Cheers, ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
