OK - a few things am noting in your HW config that already puts you behind the eight-ball, performance wise:You may have 4GB RAM installed, but a 32-bit Windows install is only capable of using around 3.3 max - thus the " 3328 Megabytes Usable Installed Memory" notation
No listed GPU (Vid Card)
No info provided for RPM of hard-drives (or write speed), both of which are important considerations on a gaming box.
From a software side, do you have the right DirectX versions installed and up-to-date?
Also, although am not familiar with those particular games, but do know that already quite a few more recent game releases are simply not fully compatible with XP, and never will be, especially now as Win7 is far more optimised for usage as a gaming system.
kaninelupus
Practically a Posting Shark
860 posts since Jul 2009
Reputation Points: 357
Solved Threads: 52
Which Win x64 by the way? Remember XP x64 was 1st-gen move to the x64 environ, where have made the move to x64 in Win7 very smoothly.... anyhow.
The fact that things are crashing under high loads does suggest one of two likely factors - hardware or drivers. Now finally managed to source specs for your drives (took a while, but lopped the last sequence in the drive names provided), and both, being Caviar Blue's, should be more than up to the task. Vid-card also should be up to handling things (although you may still not be able to use max-resolution on high-resource games even still). I would however recommend checking that you have the latest display drivers, as updates often tweak both performance and stability.
Other component to consider is your RAM. Faulty RAM can cause all sorts of freezing and crashes. In the case where you have two sticks, it may be that is only shutting down when system is trying to use more memory than faulty RAM is capable of handling.
Easiest way to test, is shut-down Windows, remove one stick of RAM and reboot, and run problematic games. If issues re-occurs, try again with other stick. If RAM is functioning as it should, high loads should only induce sluggishness, not a complete freeze or crash.
Also consider that not all RAM is created equal. If you are using PC as a gaming system, you're best off investing in gaming-class RAM... G.Skill and Kingstone's HyperX series present the best options in this realm.
kaninelupus
Practically a Posting Shark
860 posts since Jul 2009
Reputation Points: 357
Solved Threads: 52
While it does sound like neither stick of RAM is all that healthy, it looks as if there may be other issues contributing.
Have you checked to ensure you have the latest drivers for your Vid card?
Also, while RAM is playing up, you might want to bump up the size of your Page File (virtual memory) to help carry the load
kaninelupus
Practically a Posting Shark
860 posts since Jul 2009
Reputation Points: 357
Solved Threads: 52
If looking to the software option, what applications are you running on the new box which was absent from the old system?
System crashes/freezing (especially when triggered by high resource loading), while yes can occasionally be caused by software incompatibilities, is usually a hardware-related issue. BTW, when your system crashes, is it Blue Screening, or simply shutting down? If BSOD'ing, what are the error codes displayed?
@Adamsappleone
Norton, while being a resource hog, shouldn't be affecting the system in this manner. You'd be seeing problems across the board if Norton was the likely candidate.
While installing SP3 is certainly advisable, I'm also not sure this is candidate either. While one or two of the games may have been updated in a manner which creates dependencies to the SP3 upgrade, it is highly unlikely that all the problematic game have done so. While the OP can certainly try this, would be surprised if this solved all the issues.
kaninelupus
Practically a Posting Shark
860 posts since Jul 2009
Reputation Points: 357
Solved Threads: 52
Hello, type this into run to open event viewer ,go to system it should show error ,it should give the bsod error numbers ,
type into run eventvwr.msc
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
I did not know which error was the right one so I just took a picture of them all.
I attached them to this post. Tell me what you think.
Kind regards,
-Smitty.
49th one from the top ,LOL
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
actually your quess is as good as mine ,
Anyone else !
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
Aha.
Hopefully someone will be able to identify the correct one..
Kind regards,
-Smitty.
double click on a few and see what info they give you ,only way to identify them is to open them
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
Use the time stamp as your guide - is difficult for us to guide you on this one as we don't know the exact time you last blue-screened.
As a tip, try pushing system to BSOD and look for an error code with a format similar to this:
0x00007f
Might be a different error code in your case, but this is the sort of thing to look for, and will be mighty helpful in pinning down the likely source of your problems. The BSOD should last long enough to write it down - even better, if you have a camera, take a photo of the entire screen and attach here, so we can pick out the relevant data. Also, directly after recovery and reboot from BSOD, open up event viewer and go to through the newest entries for any details provided.
kaninelupus
Practically a Posting Shark
860 posts since Jul 2009
Reputation Points: 357
Solved Threads: 52
to make sure computer doesn't reboot on bsod ,right clcik on mycomputer go properties/advanced /startup and recovery/system settings , and uncheck automatic restart
caperjack
I hate 20 Questions
13,069 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812