Possible system instability?

N

NovaBurn

n00b
Joined
Jan 13, 2005
Messages
19
I just recently purchased and built a new A64 based system. After installing the parts and reinstalling windows for that nice squeaky clean feeling, I installed mobo drivers and all that system critical stuff first and then apps and then games. Soon after my reinstall of windows I got a STOP error for something, but was unable to catch it as the system reset itself immediately afterward. I figured "OK" it was just windows being retarded again. I proceeded to install HL2, BF2 and a few other games that I had yet to play at full glory on my previous system. I load up Homeworld 2 and play a bit of that, and after about 30-40 mins of play the game completely crashes. I figure it was due to the PDS mod I was playign and the massive amount of weapon fire effects and things that were going off that crashed it and not neccesarily a hardware issue. That night I leave the system on and run Folding@Home overnight to crunch some numbers with the new system (team 33 of course) and then I wake up the next morning having to reboot the system twice and uplug it and replug to get into windows. The D-Bracket said

| R G | G= green R=red
| G R |
which is saying stuck on processor initialization.

A little later of just normal use the system gives a STOP error again and resets. At this point I'm thinking "Wtf this isn't right." My previous AthlonXP system was rock solid and gave me issues, so I'm thinking something might not be right with windows. So out of sheer stupidity or boredem I try to see what my system can do in regards to OC'ing. I read Eclipse's OC guide posted to test my system. I got to the part where I was to test the limits of my CPU by incrementally upping the FSB/HTT from stock settings via clock gen until Prime95 died or the system crapped out. Well every single time I did that and got the FSB/HTT to 208-209Mhz the system would give a STOP error and shit out. I moved my pagefile back to C so I could see what the error is specifically. The errors that I was able to produce were:

http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmd_stp_swhw.asp

STOP 0x00000024
0x00000024: NTFS_FILE_SYSTEM (problem with ntfs.sys)
STOP 0x00000050


New System:
Antec TruePower 2.0 430w PSU
AMD64 3500+ 2.2Ghz Venice Core (stock speed/voltage)
Zalman CNPS7000B-Cu LED
OCZ Gold Series 1GB (2x512) PC3200 @ 2-2-2-5
MSI K8N Neo 4 SLI
ATI Radeon X800XL PCI-E 256mb w/ Cat 5.7
30GB Western Digital HDD (partitioned to C: and D:)
80GB WD HDD (single E: partition)
WindowsXP Pro /w SP2
Click to expand...

Temperature of the new system is not the problem as the CPU does not get above 45C at all. The temperature of the RAM is not hot and is normal. The BIOS is at default settings to run everything at normal speed with the ram at 2-2-2-5 and the 3500+ at 2210Mhz. I tried loosening up the timings to 2-3-3-8 and was able to get the HTT/FSB to 215 before the STOP error happened again.

Just recently tried playing some BF2 (20mins ago) I had BF2 die on me and have the video kill out and then had to hard reset the PC when everything was at stock settings. going on.

I also got a TRAP 0000006 Exception once about a 30 before writing the post (happened after I had to restart after BF2 crashed and thus forced me to reboot the system twice before getting back into post this.)
I ran memtest and memtest+ on the ram and it checked out fine. I also ran diag test on My athlonxp 1700+ system never gave me any type of problems so I'm at a loss of what is the 30GB hdd that I have and it passed ok.
 
I'd swap hard drives and install Windoze on the 80GB, because if it isn't the processor or the RAM, then it sounds like a hard drive issue. Run scandisk and see what it finds. Download and run the Western Digital Diagnostics.

You also might have a bum CPU if it gets stuck on processor initialization. And I don't mean to talk down to you, but make sure that you took any protective coating off the HSF before you put it on. Maybe you were so excited to get your new hud that you forgot to take it off :D
 
I've ran chkdisk 2-3 times with the /f tag and nothing is wrong (and to fix). I downloaded the Ultimate Boot CD and it had the Western Digital Diag tools, so that I what I used. And I doubt very much that the processor could be fried as I layed the top of it with artic Silver and made sure that the Zalman was firmly on and covered it properly. No plastic pieces left over from the installation are present anywhere.

I think that the processor initialization thing only happens when I attempt to OC and I get it too high or not configure the OC properly; and so since I'm not going to be trying to do that for a while I dont think its a major issue, I was just wondering if you guys had an idea? :confused:
 
Update:

Gotten a few more stop errors, this time whilst playing diablo2, not the most resource intensive game. I was alt-tabbing out to look at something and then I alt-tabbed back into the game, and then back out again causing a STOP error to occur and force a restart. I think that what the STOP error number was a:

0x0000007F

http://support.microsoft.com/?kbid=137539&sd=RMVP

This is starting to piss me off. I think that I'm goign to re-run memtest and see if my RAM is perhaps bad. Odd thing is I was using my new ram on my old system for about 2 weeks before using it on the new system (at 266mhz speed). Would that have not given the same issues if the memory was bad unless the errors would only be present at DDR3200 speeds?
 
Id try memtest86+'ing it for a night, Take one stick out, and run it, rinse and repeat..switch the slots, make sure everything is plugged in correctly..
 
You must log in or register to reply here.
Back
Top