Windows XP Memory problems

[WinNT511]

I am currently using Widows XP Pro SP2 with P4 3.4 2 MB cash, 160 GB HDD and 1 GB DDR2 Memory.

here is the problem when I have more then 15 windows open on my PC it locks up and this happens with about 500 MB of Ram available. I do not know what to do as this is causing un-necessary lock-ups on my workstation.

I have moved the page file to another partition on my Local HDD and the same effect is happening. I also re-tuned my performance optiosn and still the same results.

Is there some secret that I should know about With Windows XP and memory management.

Please advise,

Mike

 

[Freestone]

Testing the memory couldn't hurt.

Try memtest86 available at

http://www.memtest86.com/

Run it when you have time to spare as it does take a while.

Microsoft has a similar test at

http://oca.microsoft.com/en/windiag.asp

 

[WinNT511]

I will run the test but I had simualr issues with my old workstation as I do know and I think it is a problem with the way Windows XP Pro allowcates memory when running applications. As I do not have any issues on a Windows 2000 Pro machine.

Mike

 

[cdogg]

No, I don't think the argument about memory allocation would hold up in a programmer's forum. XP Pro and 2000 Pro are very, very similar OS's (2000 is NT 5.0 and XP is NT 5.1). Besides some cosmetic differences and additional features, the core of the system is pretty much the same.

1) Did you build this system yourself?

2) Did you check the CPU and motherboard temps in the BIOS?

3) Is it pretty easy to duplicate, or does it only happen on occasion when you have that many windows open?

4) Is the system overclocked at all?


Be sure that XP is patched and up to date. Download the latest drivers for your video, sound, and other devices. It could be a faulty power supply or overheating issue as well.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[linney]

Can you repeat this problem in Safe Mode, or in Normal Mode with a different user?

Anything showing up in the Event Viewer?

xp freeze troubleshooting
thread779-935320

 

[WinNT511]

Answers:

1) Did you build this system yourself?

Ans: New HP XW4300 (1 month)

2) Did you check the CPU and motherboard temps in the BIOS?

Ans: All are ok

3) Is it pretty easy to duplicate, or does it only happen on occasion when you have that many windows open?

Ans: Happens when I have many windows open, let I still have 500 MB available Ram when it locks up.

4) Is the system overclocked at all? (No)

**I had a old workstation thta did they same thing locked up with many windows open. It has to do with something with Win XP. I do not think it is a hardware problem.

Any ideas.

Mike

 

[BadBigBen]

Q: Does the LOCK UP go away after awhile or does it just STOP the OS completely?

**I had a old workstation thta did they same thing locked up with many windows open. It has to do with something with Win XP. I do not think it is a hardware problem.

at present I have 24 Windows open and am running a P2P software aswell as the FireFox, on which I am typing this message at present...

No lock up...

so it is not XP (Pro) as per say!!!

I would take a look more at the SERVICES and turn some of them off perhaps!




Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[WinNT511]

it just STOP the OS completely at times and sometimes it also will stop the application until I go into Task Manager to cancel the task then it is ok.

 

[djhawthorn]

Are you sure the program isn't hitting the CPU @100% utilization, making it appear the system is freezing (or running extremely slow)?

MCSE NT4/W2K

 

[WinNT511]

Yes the CPU is well below 100% (not even close)

 

[linney]

Anything workable here?

Things wont open

http://www.realtimesoft.com/multimon/forum/messages.asp?Topic=4408&tmpl=UltraMon

http://groups.google.com/groups/sea...number+open+windows+on+desktop+xp&qt_s=Search

 

[cdogg]

It could also be one of the programs you're using. Poorly written code can cause this. Like I said before, buggy drivers for your devices can also cause the issue, so make sure they're up to date.

It's not Windows XP, so you need to move on from that thought.

Now it might be your Windows installation - maybe something is corrupt in the registry or a DLL file. But that would only be a problem on your workstation and not Windows XP the OS.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884