Win98 repeated explorer/kernel errors

[PacDemon]

I REALLY need help with this! It's my roommate's computer which I put together for him and things aren't going well. It worked fine for a few weeks then windows basically died.

Here's the config: AMD K6-2 400 Mhz, FIC PA2013 MOBO, 64 MB PC100 SDRAM, WD 8.4 GB HDD, Creative CDROM drive, ATI xpert98 Video, ESS PCI sound card, Lucent winmodem...

I think that's it. Any suggestions would be greatly appreciated! It starts up, rarely works, and gets explorer and kernel errors. The system is basically unusable right now.

I don't think it's a hardware problem, but if anybody knows of problems, please let me know.

THANK A LOT!!!!!

[Gentle Giant]

Try System File Checker.
From Run type sfc and enter. See if it finds a problem.

[Vampiel]

If it has a VIA/Apollo chipset then you need to d/l the via patch for proccessor's over 300mgz. I dont remember were I got it, but once you get it you may want to re-install window, when you do make sure you enable usb in bios (you can disable it when you are through installing windows, sometimes it causes prob's if you dont) then install the patch, its a 4in1 patch, but I wouldnt recommend installing the bus mastering that comes with it cause it causes even more problems, but the pci patch you pretty much need for the system to run stable.

[Vampiel]

If it has a VIA/Apollo chipset then you need to d/l the via patch for proccessor's over 300mgz. I dont remember were I got it, but once you get it you may want to re-install window, when you do make sure you enable usb in bios (you can disable it when you are through installing windows, sometimes it causes prob's if you dont) then install the patch, its a 4in1 patch, but I wouldnt recommend installing the bus mastering that comes with it cause it causes even more problems, but the pci patch you pretty much need for the system to run stable.

[Vampiel]

/

[This message has been edited by Vampiel (edited 10-15-99).]

[Gentle Giant]

If your problem is as Vampiel has sugested this is the link:
http://www.via.com.tw/drivers/index.htm

[PacDemon]

Thanks to everyone who replied. I decided to completely baby the system, so I downed the bus speed to 66 Mhz. Suddenly things were working. I put it back up to 100, but put the CPU (AMD K6-2 400 Mhz) to x3.5 and it was still working. I multiplied the cpu back up to 4 and the problems returned.

I also tried different memory and various bios/jumper settings. I hate to say it, but it seems like the CPU was the culprit all along. I am a huge fan of AMD CPUs (I've been using a K6 233 for three years!) and I've never had one do this to me before... I fear I may have gotten a remarked CPU. At any rate, I will contact the dealer monday to see what (if any) action I can take. Unfortunately I didn't have time to put the system together when I first got the parts, then it worked OK for two weeks, then I reinstalled windows, waited another week until it had problems again.... now it's past the 30 day RMA period.

Thanks again to all who replied. I think this forum is just great. I try to answer questions whenever I can to help people out.

[Vampiel]

remember the reason for the patch is so that it CAN run at high speeds stabley. Therefore clocking it down would also make it run stable.

[This message has been edited by Vampiel (edited 10-15-99).]

[PacDemon]

I did install the patch but it didn't help (actually, I'm sure it did fix other potential problems but my particular problem was still present).

The reason I suspect the CPU most of all is that Windows wouldn't even completely install until I clocked it down.

Thanks for all the advice everybody.

[Vampiel]

True, keep in mind it could be the MB doesnt handle the voltages/do the voltages correctly. try a diff MB with the CPU if you can then that would narrow it down to the one or the other.

[Butchk]

Are you sure the MOBO isn't the culprit. I had the same problem with a K6-2 450 chip. It wouldn't load windows properly, I kept getting explorer and kernel errors. As it turned out the MOBO couldn't handle the cpu or the ram set at pc100. I had to do the same thing you did down size the CPU speed and set the ram at PC66 then everything worked fine. It was a MOBO problem nothing else.