SK43G Problem - HELP!

splice

Golden Member
Jun 6, 2001
1,275
0
0
I have several clients with SK43G computers that all seem to be getting the same problem.

They all have the same setup
Shuttle SK43G (latest BIOS)
AMD Athlon 2500+ (Barton)
Optorite DVD+-RW
512MB Crucial PC2700 DDR
80GB Seagate SATA
Windows XP SP1A (latest drivers)

So, every once in awhile (randomly) they get a MS error message (the one that asks for you to submit the error to MS). MS says it's a driver issue and there is nothing they can do. Of course, all the information relating to the error doesn't point me to which driver threw the error! The computer seems rock stable both before and after the error occurs. Anyone have some insight as to what it could be? I'm at a loss.

 

Randar68

Junior Member
Mar 9, 2004
2
0
0
Having similar problems:

SK43G
160 GB Hitachi SATA HD
XP2500+ Barton Core (333 MHz)
Radeon 9600 2556 MB
Plextor 52x CDRW

1) Tried Crucial DDR400 RAM at 333 MHz, tried 2 different 512 MB modules
2) Tried 128 MB stick of DDR 333
3) Tried 2 different Mushkin 512 MB stick of CAS2 PC-2700 at 333 MHz and relaxed CAS settings

During every test I try with Memtest86, test 6 results in failures. I get resets during games and when I'm just playing MP3's...

either there is something wrong with my CPU or there is something wrong with the memory bus layout on the mobo.

I'm getting pretty impatient, especially after, at my protest, I RMA'd my memory only to have the same problems...
 

splice

Golden Member
Jun 6, 2001
1,275
0
0
Are you running with the on board audio? After doing some reseach and investigating, I'm inclided to believe it's a problem with the audio chip and/or drivers for it.

I also returned one of the RAM sticks and replace it with a stick of Kingston 512MB PC2700. Seems to happen less frequently, but still occurs.
 

splice

Golden Member
Jun 6, 2001
1,275
0
0
Also, I know there are issues with the SK43G and Radeon cards, check sudhian.com and amdmb.com.
 

splice

Golden Member
Jun 6, 2001
1,275
0
0
It could also be a problem with the motherboard and Barton cores. All of the posts I've seen on this problem the person had a Barton proc (including all of mine).