Game's crashin'
SockMonkey:
Hope this helps:
Here are the EA recommended requirements:
Supported video cards:
ATI Radeon(TM) series (8500 or better)
8500, All-In-Wonder 8500
9000, 9200, 9500, 9600, 9700, 9800
X300, X600, x700, X800, x850
SYSTEM REQUIREMENTS
-------------------
* 1000 MHz processor
* 256 MB RAM
* Windows(R) XP, Windows ME, Windows 98 or Windows 2000 Operating System.
* At least 1.5 GB of additional hard drive space (5.0 GB total is required if installing both The Sims 2 and The Sims 2 Nightlife at the same time.)
* A T&L-capable video card with at least 32 MB of video RAM.
Obviously you attempted this when you built your computer. After you thoroughly check out your video card status, check and/or adjust your virtual memory settings. I mentioned this to JenWarrem on another similar post - it's worth a try anyway.
Also go to AVGfree.com and download their free (not trial) version of the anti-virus scanner. They like to confuse the issue on the home page with all the advert noise. That's what I did when my McAfee expired and it has done a good job. The actual link is http://www.avgfree.com/doc/289/lng/us/tpl/tpl01
Anyway, just some thoughts.
FinkTheFuzzy:
Thanks for the suggestions you all. Shortly after posting, my computer crashed again...and again. I haven't really used it since. Before I put it in a corner, I did most of what was mentioned here. It's a bit much to explain it all here...but I eventually came around to checking my motherboard temp. Apparently it was overheating, so I turned up the fan on the heatsink. Once I did that, Sims 2 (minus OFB) stopped crashing and I didn't experience a restart...except for when I ran McAfee and Spybot scans.
I'm certain you're not supposed to run 'em together...but I didn't think that'd cause the system to restart. Problem with scanning the system was that it'd restart before the scan could finish. Same deal this time around, even though the Sims ran fine. Guess I'm hopin' that, once I hook it back up, I'll find that particular restart was due to only to simultaneous scanning by two seperate programs.
Anyhow, after that restart, I unhooked everything, bought myself some canned air, and got to dustin'. Geez...I made sure to meet the requirements for TS2 to a "T" but that isn't gonna save it from user error. All that dust building up in its little fans...I'll start it up once again this weekend and see how things go. If things still aren't working, I'm gonna resign myself to the fact that I can't fix this, and leave it to more able hands.
SockMonkey:
Quote from: FinkTheFuzzy on 2006 April 20, 04:57:13
Apparently it was overheating, so I turned up the fan on the heatsink...
...Anyhow, after that restart, I unhooked everything, bought myself some canned air, and got to dustin'
Oh Man, sorry about the dust clogs. I totally forgot what a problem those can be and I just finished doing the same thing to someone else's computer.
About the restarts and the McAfee: Do you have it set to automatically download the updates? - because that may be allowing it to auto reboot the system for you. On my system I have the tasks set to perform at different times and I set them to notify me only when updates are available, then I install and reboot when I am ready to do so.
Hope you get it to cooperate with you soon - <groan>I hate computer problems. Good Luck.
JaneSims:
One other thing to check is your ram. I had a ram stick go bad. It started out that the system would just turn itself off once every couple of weeks, then it got to be a few times a week. Then it became several times a day :/
I got new ram & since then I;ve never had a random shut down.
Jane
RainbowTigress:
I had the same thing happen to me recently. I was getting random errors trying to install programs and doing various things, and random BSODs. By default, Windows XP will automatically reboot on these BSODs, so you may never see them. But if you really want to have a clue what is going on, you can disable this so that you get the blue screen with an error message instead of it automatically rebooting. While sometimes the messages can be cryptic, they often give an error message which will give you something to go on, and I wrote down the error and entered it on Google. But the error I was getting meant it was a hardware conflict of some kind, and it could be almost anything. They mentioned things like bad RAM and hard drives going out, but it usually involves a lot of trial-and-error. And if you don't know how to reproduce the situation, you won't know if the problem is solved for a while.
So anyway, I could not figure out what was going on until my bro-in-law suggested removing one of my sticks of RAM. I really didn't want to do this because I had recently added a 512 MB stick to double my RAM, but I eventually did it. At first, I removed the newer stick because he said to think about any recent changes I'd made to the PC and when the problem started. It seemed my problem started soon after I installed the new RAM, but after removing it, I was still getting random errors. My brother in law had suggested loading the drivers from the CD that came with the motherboard, so I tried that. But when the machine rebooted, Windows wouldn't even load. I tried safe mode, and I tried using System Restore, but it kept locking up on me. I was just sick of the whole situation and went to eat dinner. The idea then occurred to me that maybe it wasn't the NEW stick, but the OLD one! I felt a bit better about that since it wasn't the one I just paid $40 for, so I gave it a shot. I pulled the old ram out and put the new one in its place, and voila, Windows loaded right up without a complaint! I was so relieved! Now I have to replace that stick because even though I've not had the blue screens and other errors, my system runs slow when I have several programs open which I use to do my work. But at least I know what the problem was now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page