Originally posted by: CZroe
By not answering truthfully and saying that they were messing around in the BIOS, there's no way it would take 30 seconds to fix because that WOULDN'T be the most likely cause. Being coy is not a good thing for a customer that wants it fixed.
Obviously, if it spontaneously gave that error, then it would most likely be a hardware failure or corruption. One easy way to test is trying it in another system, exactly like they did. If it clicked and locked up on another system with a known-good adapter then I, too, would believe the case to be "closed" and not worth charging the customer more hours to look for an alternate problem that DOESN'T explain the click and freeze. It would be dishonest of me to do that just to run up their bill. Dead hard drives click, lock-up, and cause the BIOS to report "No Operating System Found," but the deal-sealer is that dead drives do it spontaneously. BIOS settings don't spontaneously change themselves.
Their IT guy clearly gets off on asserting himself over them... that 30-second quote just proves it. It would take 30-seconds if you stupidly went straight to the BIOS to see if a customer changed something they just stated they did not change (they would know if they did as they would have directly attributed the inability to boot to the last thing they did). It's the same attitude half the people in this thread are giving off. It's just not logical troubleshooting without the customer admitting that they were in the CMOS/BIOS/"Strange Menu," etc. Hindsight is 20/20, so don't pretend that makes you "smarter."
Granted, I recently had a personal laptop that wouldn't boot right after a forced hibernation (battery died) and deleting the restore data would cause it to hang on the Windows XP logo with the animation pausing and stuttering and never progressing (oddly, pressing the power button repeatedly would make the animation progress one frame per press... weird!). Setting CMOS defaults didn't help. I've had that happen on many dieing hard drives, and it HAD been making a terrible noise for almost a year... the heads sound like they "drop and bounce" as if the accelerometer triggered them to do an emergency head park (spontaneously and often). It was still readable in an adapter and I had another SATA 2.5" HDD of the same capacity (120GB found on clearance for $23.99!). I had intended to migrate to it all along as a precaution due to the "scary noise" exhibited by the original drive, so I cloned it and encountered the same thing problem when booting up. I knew that that was likely in the event of corruption, and I had my CD ready to install XP again. It wasn't until I got a crash when trying to reinstall Windows XP on a brand new drive that I realized something else was the matter. With no option to clear CMOS, I reset defaults again, tested alternate settings, reseated memory, removed un-needed hardware, and held in the power button for 30-seconds with the battery and power disconnected, but nothing worked short of a full CMOS clearing by removing the CMOS battery. Bingo! Something corrupted in the CMOS when it had last hibernated and I simply had to go to more extremes than I should have had to go through (what happened to simple "reset" holes?). I had to use a toothpick to remove the CMOS battery's connector and the connector shroud shattered, so I had to use tweezers to connect the pins themselves.
This is a similar scenario in so many ways, but I followed a proper troubleshooting process.