SM20 help, What do you think?

gtghmgtghm New
edited January 2004 in Folding@Home
Ok, I wanted to start a new thread because I thought it better for trouble shooting.

Here is what I did:
I re-soldered the cap again and now I'm almost back to zero. At least it doesn't go into a constant reboot mode.

I was inspired to try again by GHoosdum who mentioned that the board was fine when he took it out of his sisters machine.

Here is what its currently doing, maybe we can put our heads together and come up with the right soultion.

It wants to boot, I can tell. When I boot into the OS I get the black XP load screen, then it goes black but never quites get into the OS, it just stays at a blank black screen.

So I ran some memtest loops. I come up with some interesting results.
If I leave the CPU L1 and L2 cache enabled in the BIOS and run memtest full set of tests it locks consistantly on either test 4 or 5, both of which are cached. If I run the test with out cache meaning that it only loops tests 1,2, and 7 it will loop through with out any errors or lockups.

If I disable the cache in the BIOS and run the full set of tests it locks on the same tests, if I disable the cache option and it runs tests 1,2&7 it will loop fine, slowly, but it will loop.

If I slow the clock speed to 100Mhz I get the same results but slower, and if I boot it at XP 1600 I get the same results. Also I get the same sucesses and failures no matter which dimm slot I use.

The pattern I see is any time cache is used or tested it locks up.
According to the hardware monitor all voltages are normal and the CPU temp is around 30C. So its not an overheat problem.

I'm asking for all of the good PC doctors here to mull this because I'm sure that everyone that sent parts are sure or fairly sure that what they sent was working. I try to take every precaution when building rigs, but I am human and could make a mistake like everyone...

Not wishing to rial anyone or be accusing I was thinking that if I could out line my testing we might arrive a general consensis.

My thought is since there seems to be a direct corralation with the L1 and L2 cache and that its happend consistantly since I put the machine togther, that its the CPU not the memory or the board.

I can't test out my theroy tonight because I don't have a spare AMD CPU on hand... But either tomorrow or the next day I should be getting an AMD rig to look at that I might be able to use that CPU for trouble shooing in SM20 but I'm 100% positive that I will get the machine to look at.

In any case even though I don't have a CPU today/tonight to test I wonder what you guys think based on my testing?

I can try almost anything that you guys want except for swaping the CPU out right now. If I can get my hands on that other CPU I'll try it and post the results asap.

In the mean time I'm courious as to what you think.

"g"

Comments

  • edited January 2004
    "g", I will be sending out that KG7 to you today so you should have a known working board there for you by the end of the week I would imagine. If MrKwitko gets the ddr to you by the same time, you should be able to test with both boards.

    Another thought I had; when the other amd rig is in your hands you can drop that 1600 into it to see if it runs ok on that other rig.:)
  • gtghmgtghm New
    edited January 2004
    Thats fine, :) , but I was thinkin that if I get it working then your stuff can go to either SM21 or SMxx machine. I want to know before I ship the ram if its the MOB, CPU or what because the parts that are good can be recycled for other SM boxes.

    I was able to loop tests 1,2, and 7 (the no cavhe tests) sucessfully for over 4 hours, so I really think that the CPU is the problem and not the MOB.

    I was hopeing that some one else might read this and agree.

    BTW, Before I can run your KG7 I'll need a Video card and a NIC too. I don't know if those are on the way yet or not.

    Thanks,
    "g"
  • mmonninmmonnin Centreville, VA
    edited January 2004
    Yes you will get a vid card and NIC as well.
  • gtghmgtghm New
    edited January 2004
    Thanks mmonnin, I assumed so. :)

    Update, I am getting access to another AMD CPU today, I will try it and post the results later. Can we hold off until I try this other CPU?

    "g"
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited January 2004
    Um, do you have the VIDEO BIOS, RAM, or BIOS itself cached(If yes, turn THAT off, ditto video RAM caching, ditto BIOS caching)??? LEAVE BIOS and video uncached, leave L2 and l1 enabled, rerun memtest... If not, looks like bad or overheated CPU with wonky caching. Can you disable L2 cache only and get it to behave or not??? If still misbehaves, see if L1 only can be disabled and let us know results of both tests, OK??? If disabling caching of just one L level of cache disable fixes but thing runs slow, is CPU or too much HS compound.... Or AS on die other than on core.... Silver bearing HS compund CONDUCTS.... Ditto AS Alumina sometimes.

    --->//EDIT\ADD: Note, one other situation can cause a blank screen for aLONG time or infinitely.... For this to be true, ALL must be true:

    Older monitor, misaimed slightly to LEFT, or misaimed monitor aiming too far to LEFT.

    CD in CD-ROM drive.

    BIOS set in boot order to boot from CD-ROM before booting from HD.

    See. BIOSs, when checking for a CD boot sector, WILL show one little thing in upper left hand corner and nothing else.... A little underline cursor, flashing.... Misaimed monitor makes littel cursor show off left side of monitor, you never see it. Very dirty CD-ROM drive or scratched CD can make this seek take up to 15 min....

    Solution in this case, easiest, is to first alter boot order so HD boots before CD-ROM, then if still no go, power down, and unplug IDE connector and power connector from CD-ROM drive.

    John.
  • gtghmgtghm New
    edited January 2004
    gtghm wrote:
    Thanks mmonnin, I assumed so. :)

    Update, I am getting access to another AMD CPU today, I will try it and post the results later. Can we hold off until I try this other CPU?

    "g"
    Ok, well it appears to be the board. I got my hands on a new XP 2000 and I have the same problems that I had with the other CPU. Sorry guys, I really thought I could get it going.

    So send the new parts as soon as possible and I'll get her going again.

    Mr K, I'll box up the ram and send it to you either tomorrow or the nextday.

    Sucks, I really thought I could fix it. :(
    "g"
  • mmonninmmonnin Centreville, VA
    edited January 2004
    Well you tried anyway. I dont think I would have figured out the diabling of the cache thing out.
  • GHoosdumGHoosdum Icrontian
    edited January 2004
    I'm gonna have to say this board is a lost cause.

    I am truly sorry for letting the team down like this. :(
    --Rob
Sign In or Register to comment.