Problems

Meh · September 17, 2004, 04:44 PM

I have recentley upgraded my comput to an AMD 2800+ chip. When I play games, they run for 5 minutes then quit and a blue screen comes up and says memory dump and stuff, contact your system admin. Im on Windows xp. Please help!

quasi-modo · September 17, 2004, 05:31 PM

Yuck! BSOD. I have never had this problem so I am kind of unfamiliar. The one time I upgraded my processor I upgraded my motherboard too, so I had to reinstall windows. Do you ever bsod outside of a game? Like when you start a program like photoshop or something? Put some load on the processor, but not on the video, like do some number crunching or something and see what it does. You overclocking? Whats your fsb now and what was the old fsb? Cpu ratio?

synth · September 17, 2004, 05:59 PM

Have you changed anything else besides the CPU?

Meh · September 17, 2004, 06:25 PM

Motherboard, to a PC Chips M848A AMD compatible. I also put in a new Heat Sink. I also have an ATI Radeon 9200SE graphics card.

quasi-modo · September 17, 2004, 06:32 PM

wait you changed mobo too? You need to reinstall windows probably then. Unless it is the same exact chipset, northbridge and south. Well even then I would recommend reinstalling. Most oss do not like it when you change the motherboard they were configured to in installation.

Meh · September 17, 2004, 06:34 PM

Should have mentioned I reformatted my hard drive and reinstalled and updated everything including drivers for each bit of hard ware, still no success.

quasi-modo · September 17, 2004, 06:37 PM

ugh. How many sticks of ram do you have? Are they the same brand and type? If they are different what are their bands, speeds, and cas latencies. I have had similar problems with two sticks of ram getting in arguments on a new motherboard. If it still isnt working, then I would try one or the other ram and see what happens, assumeing you have two different sticks of ram. Then I would try plugging parts that are compatible in another pc and reading compatibility charts from the motherboard manufacturer. This is more likely an issue with the motherboard then the processor.

Meh · September 17, 2004, 06:39 PM

1 stick of 512mb crucial Ram.

quasi-modo · September 17, 2004, 06:40 PM

got another stick anywhere in the house of ddr or whatever your mobo takes?

Meh · September 17, 2004, 06:45 PM

No, the motherboard I have is the newest, my old mobo used the older sticks same as my dads:(

quasi-modo · September 17, 2004, 07:19 PM

well my problem was I had ram with a higher cas in slot one and ram with a lower cas in slot two, when the ram in slot one filled it moved on to slot two and there was almost a vaccume created because of the lower latency I guess and it would create an instant bsod. It only happened in games when I would used up all of that first stick. I ende up having to get rid of the slower stick.

It only happens in game correct? Try crunching some numbers on it. Go to www.distributedfolding.com and download their number crunching junk, the text client ( ftp://ftp.blueprint.org/pub/distribfold/download/distribfold-current-win9x.zip ). Then run the mofo in real time. This will load up your proc and eat up your ram. Lets see what that does.

Skywing · September 17, 2004, 09:06 PM

Quote from: peofeoknight on September 17, 2004, 06:32 PM
wait you changed mobo too? You need to reinstall windows probably then. Unless it is the same exact chipset, northbridge and south. Well even then I would recommend reinstalling. Most oss do not like it when you change the motherboard they were configured to in installation.

Unless you switched from acpi to non-acpi or uniprocessor to multiprocessor, that shouldn't be necessary. Even then you can replace hal/ntoskrnl in advance and not have any problems.

If such a problem were the cause then he would not be able to boot successfully.

quasi-modo · September 17, 2004, 09:09 PM

Quote from: Skywing on September 17, 2004, 09:06 PM
If such a problem were the cause then he would not be able to boot successfully.

True, but changing chipsets will screw up any existing windows install. You can get away with no reinstalling windows if the chipset is the same, but I would not reccomend changing motherboards without a fresh install.

Skywing · September 17, 2004, 09:18 PM

Quote from: peofeoknight on September 17, 2004, 09:09 PM
Quote from: Skywing on September 17, 2004, 09:06 PM
If such a problem were the cause then he would not be able to boot successfully.
True, but changing chipsets will screw up any existing windows install. You can get away with no reinstalling windows if the chipset is the same, but I would not reccomend changing motherboards without a fresh install.

Not necessarily. If you make sure that any new drivers that need to be there for the new hardware to work are preinstalled ahead of time, the PnP manager should select the right ones at boot time and things should work fine.

quasi-modo · September 17, 2004, 10:41 PM

humm... I have never heard such marvels. Could this be the messiah?

. I would never experiment with what you are saying though, I like to reinstall. Its the best way to clean up the system. I just drop the newer versions of software into my moving kit and reinstall away. PS: I put SuSE back on my old hard drive, and I think I am going to use Konqueror for now on when I visit forums.... It highlights my spelling errors! The only problem is it is not as convenient as fire fox.

Problems

synth