Mike, tomorrow a technician is going home to check on the computer but his first suggestion was that....a jumper cable got unplugged, moved or damaged. I hope is something fixable and not a permanent damage.
Andres
[a href=\"index.php?act=findpost&pid=52716\"][{POST_SNAPBACK}][/a]
To be honest, that sounds a little dumb. The technician sounds like hes spouting jargon at you.
OK... after all the flaming that took up most of this thread and didnt actually help Andres, i thought i'd register and hopefully provide some insight.
Let me just get one thing straight, i dont care which of you is right, which of you has been on the internet longest and which of you knows the most about computers. Its not the question here is it.
OK Andres, our house has about 6-7 pcs networked, including a few linux servers, this isnt relevant but what is, is the fact when 1 of these machines started blue-screening i decided to reinstall the machine... maybe its registry had corrupted or something.
This machine has particularly old hardware (1ghz athlon with old style 133mhz dimms) so, all should be good. Anyway, i was installing off the cd, and i received the same sort of errors, that files were missing, but you could still skip through the installation hitting return.
OK.. i thought maybe one of two things... maybe some files were being cached in physical memory then paged to the disk after a partition had been created (not sure if it does this, but i tried replacing the ram anyway).. no change on the installation...
I decided to call it a night, and the next day thought i'd try it again out of curiousity. Strangely enough it installed ok.. no errors.. Booted up fine, installed hardware, rebooted.. BSOD.. reboot, boots fine.. 10 mins later.. BSOD.
So i thought what else could it be... so i reboot the machine once again to find my SYSTEM and SOFTWARE registry are BOTH corrupt.
It was the Hard Disk Drive! It was paging stuff to the page file and unable to retrieve it properly causing these BSOD's, also when it saved the registry changes after modifications it was corrupting the registry. Now faulty ram could cause this also so thats why initially i went in that direction.
The machine has been fine since, no BSOD's, and its the machines the idiots in our house use, so its full of spyware too!