blue screen and crashing problems

cc510

Junior Member
Mar 28, 2003
11
0
0
Hey all..I just replaced my old AthlonXP 1600+ with a T-bred B AthlonXP 1700+, and suddenly I'm having some problems. At default speeds, warcraft3 seems to crash after a short while, and when overclocked (2ghz, 166x12.5), it also crashes but with the addition of flickering graphics.

Now another program that I've been using seems to cause the computer to crash as well, and that is bittorrent (a p2p program). It seems that it will run fine for a little while, but then all of a sudden, it will give me a blue screen that says some bad pool something (couldn't catch it all before it restarted on its own).

Here is my setup for those who think might know what's up with my computer. My previous setup worked just fine (AthlonXP 1600+ overclocked to 1.6ghz at 133 x 12.5):

Antec TruePower 430watt PSU
Abit KR7A-133R (just flashed to BIOS ID CX after putting in the Tbred B, previous BIOS ID 9N)
AthlonXP 1700+ Tbred B (currently also at 133 x 12.5 just to test it out...not sure if it's an overclocking thing or just a general unstable thing)
512mb Crucial PC2100
512mb Crucial PC2700
All In Wonder Radeon 32mb
couple pci cards including sound blaster, and network card
4 hard drives, and 2 cd drives


Keep in mind that with all of that, except an older firmware for the motherboard and the AthlonXP 1600+ o/c to 1.6ghz, that everything worked fine.
If anybody's got some ideas and solutions I'd love to hear 'em..thanks.
 

EeyoreX

Platinum Member
Oct 27, 2002
2,864
0
0
Possibly a bad stick of RAM. Try running the same programs with only one installed and see if you can reproduce the crashes. If the first one works, try the second and see if that one causes a crash.

\Dan
 

Green Man

Golden Member
Jan 21, 2001
1,110
1
0
Go to the event viewer from administrative tools in the control panel and get the stop error info listed under applications.
 

cc510

Junior Member
Mar 28, 2003
11
0
0
hm...i checked the event viewer and it seems it didn't log the blue screen error i had around about the time it happened yesterday, and the only errors i see always say this:



"Unable to read the performance counter strings of the 011 language ID. The Win32 status returned by the call is the first DWORD in Data section.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."


anybody know what that means?

I think i'll try out the memory test later today to see if that helps.


 

cc510

Junior Member
Mar 28, 2003
11
0
0
Is it possible to ruin a stick of ram by overclocking past it's intended Mhz speed?

I think one of the first things i did (although forgot if it was THE first), was to try to overclock it to 2ghz (166 x 12.5). Having a 512mb pc2100 266Mhz stick of ram, and also a 512mb pc2700 333Mhz stick of ram, and the system bus at 333, would it have been possible that I ruined the pc2100 stick by doing that? But if I did, would it still be able to read the amount of memory, since even after that, it still booted up saying that I had 1gb of ram.
 

cc510

Junior Member
Mar 28, 2003
11
0
0
well i took out the pc2100 ram and so far so good. Nothing's crashed with bittorrent for a couple days now. I haven't tried war3 still so i'm not sure about that.
I haven't tried taking the pc2700 out and using just the pc2100 yet, but, well..since the problems are gone with the pc2100 out, I'm suspecting that it's just that stick..

Now i guess i need to see about getting that replaced from crucial :\
 

EeyoreX

Platinum Member
Oct 27, 2002
2,864
0
0
Perhaps the two sticks didn't get along? With one being PC2100 and the other PC2700. I know theoretically the PC2700 should just run at the lower 2100 speed, but maybe they just aren't playing nicely together?

\Dan
 

cc510

Junior Member
Mar 28, 2003
11
0
0
the thing is i overclocked without realizing the speed of the bus speed of the pc2100 stick (266, i overclocked so it was running at 333, the pc2700 speed).
I'm somewhat of a newbie when it comes to overclocking, which can be quite dangerous as I've heard and recently found out..