Odd thing is going on for me...

gtghmgtghm New
edited December 2003 in Folding@Home
Ok the one thing that was working fine before I reinstalled my OS on a fresh format c:\ was my 4 clients of fah....

But now I'm having a FILE_IO_ERROR problem which is described
here

It's got me stumped cause this machine and everything has worked great for over a year except for that stupid WDJB drive that let go on me... But mechanicaly the rig seems sound...

Had a virus and a trojan that I couldn't ever feel like I flushed completey so I did a restore of XP but started to get crash dumps and driver issues, XP Blue screens... not good... so I reinstalled the OS...

On this new install I have run the normal benches looped for hours all with out any problems... The only one that I guess I haven't run was memtest86, which I will if I need to, but I don't think I have any memory problems... Corsair ECC PC800 RDRram...
Pretty solid stuff...

The one thing that I might do is roll back to an earlier BIOS as updateing my BIOS is the only major thing that I did since I lost the WDJB drive...

Thing is the JB drive was part of a raid 0 in Dynamic disk configuration.... so I restored via DI 2002 the last back up of my system before the raid failure to a new 250gb JB drive... I figured that the crashes were from the fact that I moved my OS from one drive to the new 250gig drive and then restored the raid partitoins to the remaining space on the new 250... buit I reverted/restored to basic disks instead of restoreing to the partitions as dynamic volumes like they were when I backed them up initialy so I was thinking that, that was prolly part of my problem... But now FAH is giving me crap so I don't know what to think...

This install seems to be good but I admit that I have had one other issue that was..., I tried to install my copy of McAfee 7.0 and had problems... Scan scheduler function worked until the update was applied then it crashed... But I got a copy of Norton 2004 and it went in just fine... Go figure...

"g"

Comments

  • a2jfreaka2jfreak
    dawns his "Primesuspect" suit.

    check memory
     Houston, TX Member
    edited December 2003
    dawns his "Primesuspect" suit.

    check memory
  • gtghmgtghm New
    edited December 2003
    a2jfreak had this to say
    * a2jfreak dawns his "Primesuspect" suit.

    [url="www.memtest86.com"]check memory[/url]


    Memtest says the memory is good...

    Gotta be something odd with something else...

    A progy conflict, like maybe norton script blocker or something in nroton anti spam... could be a bad fah core version too.. saw that there were FILE_IO_ERROR probs with an earlier core version over at the fah community site... vers 1.4 I think I saw...

    latea,
    "g"
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited December 2003
    Well, could be a few things, now that you have eliminated the obvious. One, is insufficient RAM to decompress left free on the CPU you are using fro the failing unit, much less likely is a CPU with a faulty FPU or cche circuit in the die of one of the CPUs or defective RAM, you seem to have pretty much eliminated that, though RAM failures can be intermittent to start with as RAM dies. Is one CPU overheating gradually, so that the longer you fold since reboot the mroe IO's you get, or HD Overheating???

    Overheat errors, bad modem connect, busy modem when trying to download with ohtr clients all trying to download or upload at same time from within same box can confuse things, and limited total inbox resources might do this. See if you can get two clients assigned to one CPU, two to other, might be three clients fighting to use one CPU, one to use the other. Likely then would be first CPU with one unit would have a working client, next client loaded would grab resources off second CPU, third might get second CPU and be not fully reliable, and and fourth would get resource starved. try the failing ones and in fact all, on LOW priority and not IDLE, see if that is case. OTHER programs may then get resource starved, but this could in fact be a CPU load balance thing in part. Yuo DID reload the mobo CD drivers when you reloaded, right, or gewt latest drivers for your chipset from mobo mfr after relaoding XP???

    John.
  • hypermoodhypermood Smyrna, GA New
    edited December 2003
    Are you sure that each of your instances is using a separate folder and that machine ID's are correct?

    Check the link below with respect to the local flag. Once you have everything setup correctly delete the queue.dat file and let it run again.

    http://folding.stanford.edu/console-userguide.html
  • gtghmgtghm New
    edited December 2003
    Ageek had this to say
    Well, could be a few things, now that you have eliminated the obvious. One, is insufficient RAM to decompress left free on the CPU you are using fro the failing unit, much less likely is a CPU with a faulty FPU or cche circuit in the die of one of the CPUs or defective RAM, you seem to have pretty much eliminated that, though RAM failures can be intermittent to start with as RAM dies. Is one CPU overheating gradually, so that the longer you fold since reboot the mroe IO's you get, or HD Overheating???

    Overheat errors, bad modem connect, busy modem when trying to download with ohtr clients all trying to download or upload at same time from within same box can confuse things, and limited total inbox resources might do this. See if you can get two clients assigned to one CPU, two to other, might be three clients fighting to use one CPU, one to use the other. Likely then would be first CPU with one unit would have a working client, next client loaded would grab resources off second CPU, third might get second CPU and be not fully reliable, and and fourth would get resource starved. try the failing ones and in fact all, on LOW priority and not IDLE, see if that is case. OTHER programs may then get resource starved, but this could in fact be a CPU load balance thing in part. Yuo DID reload the mobo CD drivers when you reloaded, right, or gewt latest drivers for your chipset from mobo mfr after relaoding XP???

    John.

    Memory; Shouldn't be a problem with a gig of ram. The windows task manager shows that at any one point the average ram usage is running between 350K to 500K so I'm not even getting close to tapping the amount of ram I have...

    Heat is not an issue right now the case is open and both CPUs register in the 30c range.
    The HDs are fan cooled...

    Yeppers, I loaded the MOB drivers and stuff as usual...

    It was weird but after it scrolling through the error message a few times it figured something out and started grinding away...

    As of this morning all 3 clients were still chugging away, which was a first since I reinstalled everything...
    Dunno, won't feel like I'm out of the woods untill the WU's get posted to stats...

    Thanks for the help,
    "g"
  • gtghmgtghm New
    edited December 2003
    Ok all 3 clients finished wu's and reported... yea

    My #2 client cam up with that error again while trying to DNL and decompress the WU but after about 3 times it went and is currently crunching a way... So I think that its something in the new core/fah thing and rule out that its cause of my rig...

    Thanks guys,
    "g"
Sign In or Register to comment.