Have I got the KT133A bug?

[MadTom]

Well, having a QDI Kinetiz 7E-A motherboard sporting a Duron 800 and 2x128MB of SDRAM and big problems. I mena the board is working fine but has a lot of hick-ups (can't explain it better). Even if playing solitaire the system stops for a second and goes on afterwards.

I'm runinng Win98SE and have tried a lot of different VIA 4-in-1's and even George's PCI patch (version 0.19). After applying George's patch the system is OK for a day or two (sometimes only an hour or two) but then it starts again...

I googled the web for a solution but it seems that no one has a solution for everyone (tried a lot of them...).

I hope you could help me.

Thanks in advance

 

[Peter]

There is no KT133A bug. What the public perceived as such was a mixture of Creative SB!Live having a PCI bug, and BIOS screwups in the early attempts of working around it.
Give your board the latest BIOS, if you got said sound card in it, change that.

 

[Aenslead]

All VIA chipsets have all kind of bugs in them. Bad Luck.

 

[Blain]

I had the KT133A bug before. I solved it buy getting an Iwill KK266R+.

Now I've got the Canterwood bug.

 

[Killrose]

My old Epox KT133a board never had a problem like that. Maybe you should try defragging your hardrive or something. Sounds like you have some app running in the background hogging resources.

Maybe try one of the spyware removal tools like Adaware.

 

[Peter]

Originally posted by: Aenslead
All VIA chipsets have all kind of bugs in them. Bad Luck.

So do all Intel, SiS, AMD and ALi chipsets. Don't spread FUD here.

The point is that KT133A has no bugs that are in any way relevant to actual use of the product.

 

[Shade4ever]

I had a KT133 (may or may not have been 'a') based system for a while, experienced the same thing. Eventually found out mine was due to a dying NIC, fixed by replacing it. Just my experience, it may be useful.

 

[Vette73]

Its not your chipset, its the OS. If you are still using Win 9X, upgarde to XP. Will work so much better.

 

[MadTom]

Thanks for all your help. It really coudl be the NIC.

Will see how the comp works without the NIC...