Urg Bug.... consitant error

[Meaty-btz]

I am running a:
P III 1000/133, with FCPGA-2 design type
a abit VH6 motherboard
512 MB/133 PNY ram configured as such 256/128/128
an ati radeon 7200 agp or a Hurcules Geforce 2 MX AGP ( i have had problem with both)
SB Live Platnium ( first generation not 5.1)

Has any one under both 98 and XP had an almost timed crash ( i.e. it happens withing a specific time frame like 20 sec to 4 min after program start) whenever you are running a mem and 3d graphic intense opperation or running a 2d productivity app but with a large file being worked on ( i.e. 400+ MBs). If any sound is playing during the system hang i get the wonderful no heartbeat sound screeming at me. I have run most benchmark and hardware burn-in testing programs and can't reproduce the error. Commom programs that I have had crash.. ... every game that runs open GL or DirectX, Corel Draw 10 & , Photoshop 6.0, Lightwave 7.0, or occasionally during actually bios boot test it'll hang just after mem test but before hardware detect. But mostly it'll happen no matter what I am doing at the time as long as it is graphical.. I thought it was the video card and bought the ATI and still generating the same error. Tell you the truth I am stumped.

Meaty-BTZ

as an last note I did have the motherboard previously running a PIII 533 overclocked but the error didnt start till after I put the 1.0 PIII in the VH6

[Meaty-btz]

I wanted to reach stability on the P3 1000 before i oc'd it but if the VH-6 is really going south. I am gonna push it by OCing the P3 1000 as far as it can go. If the board is gonna fail. It should go into some kind of terminal burn-out, instead of this damed annoying untraceable crashing error.. FRY MB FRY!:mad:

[outhouse]

I had the same cpu and the same MB at one time and had no problems with it but i did have better memory [corsair] you will have no propblems maxing out the MB before the cpu as your fsb only goes to 150 which is a weak overclock for this cpu. I would have to think your problem is memory related as the only time i had a BSOD was when i tweaked the memory to far. What are your memory settings? If you want to change colors of the BSOD theres a program at techtv that will let you customize colors for your crashes but hopefully we can fix this problem. You can also go to www.rojakpot.com and go through there BIOS guide and set your PC up to meat your needs.

One note if your using win98 then you have to much memory i would just run the 256 stick first and see if that clears the problem, i think i would try this no matter what OS i had. When was the last time you reformated and did a clean install?.

[Yodums]

Check one ram stick at a time could also be a bad stick of ram.

[Meaty-btz]

Ok, here is a break down of testing..... Had problem start exactly at the same time I droped the 1 Ghz in the board.. 'bout a month ago. No new mem changes untill XP install.. .... about 2 weeks ago, fresh on blank HD and I droped a 256 Chip in the 0/1 slot, under 98SE mem config was 0/1-128 2/3-128 4/5-128 all PNY, so 384 under 98, ran fine. I dont get eny mem.. checksum errors during a mem burn-in test, which I ran last night for about 20 min... really working every bank and it detected NO errors. Still think its mem? I had that feeling.. Gonna rip out that ATI board and bring it back for some cash since my Hurc card is still ok, might as well run a stick by stick check untill I generate error or error stops I should say. What else can I do... yea the 1G/133 is a pretty weak O/C chip but its what I had avail at the time, So I am not complaining.. In about 3-4 weeks I hope to be retiring this System to my wife ( still need it to work) and getting a dual athlon XP 1600 system set up.. heading for the PC3300 DDR ram.. I have a P4 as well flying with PC/800 ECC mem too.. Can a man have too many PCs?? naaaaaaaaaa you just get a nice render farm for all those lightwave renders! woohoo! So for the record running in my house.
Oldest to newest
-PPro 200 4th Gen/128/20GB ( damn thing is 5 years old and is more stable than my new stuff!! go figgure.. this is my Linux server for the home)
-PIII 533 EB/256/30 ( the wifes computer.. made from gutted HP Pavillian Parts I got my hands on for realy cheap)
-PIII 1000E/512/30 lots of fun stuff ( but its an unstable cranky bitch)
-P4 1.8/512 PC800-ecc/ waayyy too much HD and lots of nice components running on an intel brand MB

-Athlon MP..... perhaps sooon

I wish I still worked for motorola, we had a DIMM tester and a logic anlyzer and all sorts of fun stuff like Yellow Books! gotta sign a waver to look at those fun things.

[Meaty-btz]

Oh yea! almost forgot.....
a mac.. yech!
and an IBM think pad 365X about as old as that PPRO, but the IBM sits in its tote bag for want of anything that i can think to do with it! still works though, but what can you do with a P100 and 16Mb of ram? in a laptop..

[outhouse]

Well the 1g p3 CPU is not that weak of a chip mines at 1292 with the vh6-2 honestly its your MB that is weak. Dont get me wrong its a good MB it just wont go above 150FSB and that is a weak overclock since most p3 1g's go much higher then that. I'm still wondering what your memory settings are like in BIOS though, with a little tweaking there you should be able to fix any BSOD's unless its a XP problem and that may be the case too but PNY is not one of the better brands so i wish you luck trying to pinpoint your troubles.

[Meaty-btz]

As in BIOS Mem config? meme is set to 8ns and mem bus clock rate is set to main clock, not main clock - pci clock. I pulled the sticks last night and lo and behold it works now.. apparently the 3/4 dimm slot PNY stick was just plain bad. so i stuck in one of my spair 128 sticks and now I am back to full 512 and no more crashes.... i wonder why the mem burn in test did not detect any errors though. But problem solved... BTW about PNY being not the best.. true.. but all my modules are running infineion chips which are not bad.

[Meaty-btz]

also the one module that was bad was prolly bad due to electrostaic damage, done by yours truly. I really should replace my static strap that I broke a few months ago.:beer: soo I am gonna have a cold one and enjoy a fully functional system.