Boy, arent there any good tools out there to check if the memory is really the culpret?? I have been back and fourth on the whole memory issues on my PC for over 3 months now..First, i thought it was the HDD, then, i found out the the bios (686b)via chipset was ****ting allover mS OS'es and waited for all new patches to come out...Now months later,,,,here i am again and nothing seemed to fix all of the crashes and errors im still getting?? Im so burnt out about this whole thing..Here i am a 6 year PC vet, i hold about 15 different certs(not paper) I travel the US on various Technical issuse and i cant even fix my own PC, boy....Someone please give me a positive response....
Yes i know, ive already gotten an RMA from the vender, however, i will be down for two weeks..I am currently in the middle of developing my site and cant afford to be down...Thanks for your dry humor, i do the same thing sometimes.
Timbob505
07-11-2001, 09:34 PM
Try this, http://www.teresaudio.com/memtest86/ it has helped me identify memory problems before, and its free. I hope everything is working soon!
Good lcuk and let us know how it turns out!
Timbob
scripteaze
07-11-2001, 10:24 PM
Im DL now, will let ev1 know the results...Thanks for the posts guys...
surrealchereal
07-11-2001, 11:21 PM
There is also a real good program called doc memory, it will test your memory under various loads looking for failure, and identify it. But I have spent an hour messing with trying to find the site,
Its down. I haven't looked somewhere like downloads.com or tucows, but if you want it and can't find it I will be glad to send it to you. http://www.sysopt.com/forum/smile.gif It's only about 200 kb then just unzip to a floppy with system files on it, and reboot to the floppy. Email me, or anyone that would like it, and I will send it to you. I've recommended it before to rave reviews. http://www.sysopt.com/forum/smile.gif
surrealchereal
07-11-2001, 11:29 PM
Hmm, I have a stick right now I am going to contact Kingston about. For months we have been playing the what could it be? game, when the consensus here was I got a BSOD if I moved wrong, but nothing really concrete. BUT since I have pulled the bad stick that was identified one time only, and I have really put a stress on it, and (sorry no way I am typing that here, or the opposite will happen, and I'll be bummed. (hey it's happened before http://www.sysopt.com/forum/redface.gif) That's such a tough one, and not real believable.(ram)..... Lighten up on yourself dude! http://www.sysopt.com/forum/smile.gif
Michael Chiew
07-12-2001, 01:47 AM
scripteaze
Why do you need a memory tester just to get your act together. Procrastination will only prolong the pain and frustration. You've got to be decisive about this, friend.
I can't believe a 6-year PC veteran would sit on the issue of whether it's memory or not for 3 months. I would've lost my patience and gone out to get myself new ram to test the waters of uncertainty (ram is cheap these days).
If anything, I give you credit for patience.
You're not exactly clear about what the problem is. You mentioned crashes and errors. In what circumstances do these crashes take place. Can you be more precise with the errors.
Michael Chiew
scripteaze
07-12-2001, 06:46 PM
Ok, First of all,
AMD Thunderbird 1.200
30gig WD 7200 rpm UltraATA 100
52X rom
GA-7DXc Gigabyte Motherboard
256mb DDR
64mb ATI Radeon DDR
I do have a lot of patience and yes, i should probebly just send it in..At first, when i built the system i installed the OS[ME]((A.K.A **** on a stick)) and it went smooth. I was happy. Then, little things started to happen, like sparatic crashes and auto reboots. I was thinking,"hey" the CPU is getting to hot, so thats where i started, sending for the best thermal grease, the copper shims, an 80.00 bigass fan..Nothing, still did the crashing and reboots..i had been playing tribes 2 when most of the crashing was happening, well, tribes2 has a ton 'o bugs.I then thought it was the game
Waited for a bunch of patches to be released, still nothing..Then i thought, well maybe it was just a corrupted install, besides, ME-SUCKS!. I started a 2KPRO install and then i started getting CD write errors saying it couldnt find files on the rom, i got another 2k rom from a friend and the same thing was happening, I then thought well, it has to be the CDROM itself and that the other errors were not related..Well, to make a long story short, they are all related..I have problems installing any OS, no its not the HDD either,at first i thought it was because 2k SP1 didnt support ATA 100, i clocked mine down to 66 then 33, nothing...Also spent a whole shiznat load of time on WD's site and on the phone to make sure.. there were even bugs with the via chipset (686b southbrige) that conflict with DMA hogging between the mainboard and the CDROM, it wasnt that either...Im just burnt about the whole deal, i guess i was thinking i could fix anything..Its more determination then patience..Just writing about it here makes me steamed...Im just going to give up and send it in...
[This message has been edited by scripteaze (edited 07-12-2001).]
surrealchereal
07-13-2001, 12:47 AM
Scriptease, http://www.sysopt.com/forum/smile.gif gee it felt good to read your post http://www.sysopt.com/forum/wink.gif all the frustration, It was so apparent. Ahh I have a kindred soul. I call it the pit bull in me. You say "i guess I was thinking I could fix anything."
You know that you can fix anything! It sure amazes me when fellow Sysoptiens say to me, give up, take it in, get someone to do it. Sometimes I even say OK I'll do that if, or but. I even took a motherboard for a ride in the car once and into the shop, but she didn't get to stay. One took me 10 months, others suggested I use it as a Frisbee, putting green, or fix the hole in the bass boat with it. But when it was all said and done, I was the one dancing and singing when I beat it, it didn't beat me. Know what I mean? So heres my opinion
[b]Get another board, one with sound and video even. and a chip, nothing fancy just a cheapy. A hard drive, floppy and CDROM. Slap together another box. Ignore the other one. You'll go back, fix it, and then when it breaks again, you still have your little life box, http://www.sysopt.com/forum/smile.gif
Michael Chiew
07-13-2001, 07:19 AM
scripteaze
I was right about you, the patience I mean. But the giving up and sending it in is something else. I didn't think you have it in you to throw in the towel.
Surrealchereal's got the right attitude. It's fight the good fight and never giving up until the fighting's done. Then when you're victorious, you can do a song-and-dance routine. Scripteaze, you will have the last laugh.
Surrealchereal's suggestion to have another box fixed up is a good one. That's what I did, and generally do, when I'm faced with a machine who won't acknowledge me as the master. Takes time to tame it and tame it I always do.
What can I tell you about your problem that you don't already know. Your credentials are formidable (I took a peek at your particulars). What I am about to suggest will surely annoy you. Go ahead, call me mad, insane, blabber-mouth idiot. It doesn't matter. Sometimes you've got to go for it even when you're in the company of supreme masters of the PC fraternity.
Before I begin, let me say this. Some of my friends in Singapore (that's my hometown), have had problems with their operating systems, i.e., Windows ME and Windows 98. One had a system that froze because of Windows ME. When he changed it to Windows 98, the problem disappeared. He cursed ME just like you. On the other hand, I've heard accounts of Window 98 crashing a system, too. A change to Windows ME solved the problem. These people cursed Windows 98.
What I'm trying to say is that no OS is perfect, I guess. We live with it for the experience. We pay the price, of course.
Here goes my suggestion.
Remove every component in your system. That's right, take everything out - CPU, ram, motherboard, the whole works. And re-install.
Before you re-install, go through the CPU, ram, motherboard, video card with a big magnifying glass. I'm sure you know what you're looking for.
Pay close attention to the motherboard, yes, especially the motherboard.
If all seems fine, re-install. Stop when you've got the video card in (motherboard, ram, video card). Start your system. Do you still have those problems. If you do, your lot of troublemakers are already narrowed down. If it boots fine, re-install another component and test the system again. Do this until you come face-to-face with the beast that's causing you all that pain.
Proceed if all goes well with hardware. Then you know you've got a software issue. Some sort of incompatibility problem, I suspect. But I'm sure you're in a better position than me to isolate it.
And, yes, don't forget to check your power supply as well.
Happy hunting and don't give up!
Michael Chiew
Michael Chiew
07-13-2001, 07:20 AM
scripteaze
I was right about you, the patience I mean. But the giving up and sending it in is something else. I didn't think you have it in you to throw in the towel.
Surrealchereal's got the right attitude. It's fight the good fight and never giving up until the fighting's done. Then when you're victorious, you can do a song-and-dance routine. Scripteaze, you will have the last laugh.
Surrealchereal's suggestion to have another box fixed up is a good one. That's what I did, and generally do, when I'm faced with a machine who won't acknowledge me as the master. Takes time to tame it and tame it I always do.
What can I tell you about your problem that you don't already know. Your credentials are formidable (I took a peek at your particulars). What I am about to suggest will surely annoy you. Go ahead, call me mad, insane, blabber-mouth idiot. It doesn't matter. Sometimes you've got to go for it even when you're in the company of supreme masters of the PC fraternity.
Before I begin, let me say this. Some of my friends in Singapore (that's my hometown), have had problems with their operating systems, i.e., Windows ME and Windows 98. One had a system that froze because of Windows ME. When he changed it to Windows 98, the problem disappeared. He cursed ME just like you. On the other hand, I've heard accounts of Window 98 crashing a system, too. A change to Windows ME solved the problem. These people cursed Windows 98.
What I'm trying to say is that no OS is perfect, I guess. We live with it for the experience. We pay the price, of course.
Here goes my suggestion.
Remove every component in your system. That's right, take everything out - CPU, ram, motherboard, the whole works. And re-install.
Before you re-install, go through the CPU, ram, motherboard, video card with a big magnifying glass. I'm sure you know what you're looking for.
Pay close attention to the motherboard, yes, especially the motherboard.
If all seems fine, re-install. Stop when you've got the video card in (motherboard, ram, video card). Start your system. Do you still have those problems. If you do, your lot of troublemakers are already narrowed down. If it boots fine, re-install another component and test the system again. Do this until you come face-to-face with the beast that's causing you all that pain.
Proceed if all goes well with hardware. Then you know you've got a software issue. Some sort of incompatibility problem, I suspect. But I'm sure you're in a better position than me to isolate it.
And, yes, don't forget to check your power supply as well.
Happy hunting and don't give up!
Michael Chiew
SysOpt.com
Copyright Internet.com Inc. All Rights Reserved.