Car Finance | Mortgage Calculator | Internet Advertising | Mortgage Calculator | Loans
Do You Agree or Disagree with this conclusion. [Archive] - PCMech Forums

PDA

View Full Version : Do You Agree or Disagree with this conclusion.


morriswindgate
01-25-2002, 09:55 AM
I was asked to look at a computer that was rebooting at the Windows desktop during the TSR load. The computer is a Micron outfitted as follows

Motherboard running Intel 810 chipset, Intergrated sound/video
Celeron 677MHz CPU Socket 370
20 Gig Seagate ATA 100 5400RPM Hard Drive
64 MB Generic PC133 RAM
Samsung 12x DVD
PC Tel WinModem
Running Windows ME as delivered.

When I first got hold of the PC, I cleaned out the dust bunnies and inspected for damage, which there was none.
I then plug the unit in and started it up (Windows ME). Post code was normal, as was the BIOS message Windows. When the OS started the desktop and during the TSR loading, it went to the "Restore Active Desktop white screen and then displayed a warning box with the message, "Run Time Error 62,,,Input Past End of File." If I clicked on anything the PC would re-boot. I also could not start Windows ME in Safe Mode since it would re-boot upon starting the Help Screen. This led me to believe that there was a script problem and windows would need to be reloaded. Also this computer had just about any Instant Message Program that is available along with Bonzi Buddy.
To reload, I used the Restore Disk that came with the computer. Everything in the install was normal until it got to where you fill in the User Name, which after filling in the user name and clicking Okay it rebooted. I removed the Modem and tried it again with the same results. On the re-boots, during the scandisk I started getting Long Filename Errors.
(This is where I screwed up by not running F-Prot for DOS) I next ran FDISK to delete and rebuild the partition, ran format, and then installed Windows 98 (Since I knew I could at least get into Safe Mode with it). Install went normal until the first start-up where you normally get the Monitor found and the desktop runs the first time, the damn thing re-booted. And I was still getting long filename errors.
I now did a little more in-depth hardware check and found all fans to be running normal and the power supply to be working correctly. I also tried a known good RAm in place of the installed stick, removed the CMOS battery to clear the NVRAM, and changed the hard drive cable. Reset the BIOS to the correct values and entered Safe Mode, ran Scandisk with a Surface check (No problems detected), corrected long filename errors, and restarted with it rebooting at exactly the same point.
At this time I did run F-Prot (Nothing), Ran the Seagate Disk Utility (Nothing Found), and then Ran Spinrite (Hard Drive settings in BIOS found to be reported wrong), Entered BIOS and set them manually, ran SpinRite again with nothing found.
Formatted the disk and ran spinrite, and it showed the Setting in the BIOS wrong. I went back into the BIOS an sure enough they were not the correct settings for the hard drive.
During the last two days I have wiped the hard disk with a Zero Wipe Program, FDISK, and reformatted in every way I can think.
My conclusion, is that for whatever reason, and I suspect it is a virus (possibly an older Win95 era one) that has damaged the Controller and/Or chipset in some way.
Agree or disagree?

HAL9000
01-25-2002, 10:59 AM
Tough call, maybe a failed part at the rather convenient time of your servicing. The only thing that I noticed that you didn't mention was the RAM. Have you tried a different stick?

Oops...edit that, you did try one.

morriswindgate
01-25-2002, 11:05 AM
also did a BIOS Flash.

HAL9000
01-25-2002, 11:08 AM
Maybe try that hard drive with that installation on a different machine.

Statica
01-25-2002, 11:10 AM
Couldnt it just be a defective BIOS chip? Have u tried replacing that?

Personally, I wouldnt try the HDD on anohter computer before eliminating the possibility of a virus. If it is a BIOS level virus, the replacement of BIOS chip should start you off with a clean slate.

reboot
01-25-2002, 11:22 AM
The symptoms are exactly those of the Win95_CIH (Chernobyl) virus, which craps out the BIOS, allowing only some 16 bit stuff to work, thus the LFN troubles...
If it's in the BIOS, it's time for a new one, as it's undetectable with a virus scanner at the hardware level. If it migrates to the HD, you'll find it (if you can get a successful boot to run a virus scan).