There must be a million reasons for a PC not starting. I thought I knew quite a few.
This particular PC would boot but, before starting Windows, there was a Blue Screen of Death (BSOD). The error message was Process1_Initialization_Failed and the STOP code was 6B.
Again, there are hundreds of these Stop codes and messages but there are websites that list most if not all of them. There are also loads of forums with messages from people who have had these problems before and, hopefully, sorted them. Generally, if you put in a stop code or error message, there are hundreds, if not tens of thousands of people similarly affected. Sadly, a code 6B query gave me less than 5 or 6, none of which were remotely useful.
I tried Safe Mode and it failed. I tried Last Known Good Configuration and it failed.
I tried a Repair installation and it failed - though I am still not sure. The XP system disc found the hard drive, found the right file system and found a correct partition table. It also indicated that it knew which partition held the XP system but instead of offering to repair it, it offered to reformat it! Bad news - since the owner didn't take backups.
Next stop - my trusty UBCD4Win - a portable version of XP that runs from a CD. This is an invaluable tool that I use frequently. It booted slowly but it always does and, when it had loaded, it too showed all the various drives with the right file systems. Superficially, it all looked good. However, when I started the hard drive diagnostics and chose ChkDsk, it immediately showed errors. And the errors kept on coming! Even worse, the errors showed file-names and they weren't only Windows system file-names, many of them were clearly data file-names.
I left it running and asked him to call me when it had finished.
After around 2 hours, it had finished and I rushed round to see what it said. Amazingly, ChkDsk had not only reported the errors but it had also appeared to fix them. I had set it running with the 'correct errors automatically' parameter set but I didn't really expect it to work.
At the end, it reported that it had fixed the Master File Table - a rather important system file. I don't know what had caused to MFT to become corrupted but, at least temporarily, it appeared to be ok. I left the owner with the advice to back up all the data files from the C: drive onto something more secure and, at least, to replace the drive. Although ChkDsk may have repaired the MFT on this occasion, I still didn't know what had caused the problem and, since he ran his business from it, I wouldn't trust it.
Sunday, 18 April 2010
Laptop keeps switching off!
Got a call this lunchtime from a new client - funnily enough, while he was getting off a bus!
Anyway, he said his laptop kept turning off - unasked. Sometimes it might last an hour or two and other times, it would turn off four of five times in a morning. As you can imagine, this was very inconvenient.
I had three or four thoughts.
A bit of head scratching followed, followed by a bit of shuffling of the laptop on my knees as, without noticing it, it was getting uncomfortably hot. Unconsciously, I had moved it to allow my knee to cool down. When I noticed what I had been doing, I checked the CPU temperature. They were showing 89°C - uncomfortably close to its maximum temperature.
Since it wasn't a fluff in the fan problem, the next places to look are other hardware and software. Since the fan appeared to spinning all the time at full speed, I checked what the CPUs were doing - Task Manager showed they were running at a high operating load - 80% and above. There was nothing to show in the Applications tab so I checked the Processes.
And there was a likely culprit - Google Desktop Search was running at 50% of CPU! For these of you who don't know what it is, it is a search engine that indexes, potentially, the whole of a PC's files, not just for file names but also for content. So, not only can you search for shoppinglist.doc but you can also search for butter or eggs or whatever was on your shopping list within the shoppinglist.doc document. Similarly, it can even index the contents of all your emails. It can be a lovely tool to have available - providing (a) you don't index too much and (b) your CPU can take the strain. This one couldn't.
Since the client wasn't there, instead of uninstalling it, I merely turned it off, rebooted and rechecked the temperatures.
Within a couple of minutes, they had dropped from nearly 90°C down to below 60°C - much more comfortable on my knees.
So, I don't know that I have fixed his switching-off problem but I bet I have.
Anyway, he said his laptop kept turning off - unasked. Sometimes it might last an hour or two and other times, it would turn off four of five times in a morning. As you can imagine, this was very inconvenient.
I had three or four thoughts.
- Power supply - sometimes power supplies get damaged or the wires get worn and the output is not what it should be. Generally, they will just fail but, I guess, there could be cases where it carries on going just enough to power up the laptop but not enough to keep it going.
- Power options - in the Control Panel, you can set what the laptop should do to save energy. I figured that these might be set ridiculously low or something. They are unlikely to act irregularly but worth checking.
- Fluff in the fans! - this was high on my list. People often sit the laptops on cushions, on the sofa or on the floor where the air intake can suck up dust and fluff. If enough gets in, it can reduce the efficiency of the fan resulting in overheating. If the CPU gets over its maximum working temperature, the BIOS will just turn it off to protect it. To contain the problem, laptops generally have a fluff filter on the way into the fan, so all that is needed is quick bit of housekeeping. However, there was a particular Dell laptop - I have forgotten the model - where the fluff filter was after the fan. So the fluff was sucked in by the fan and then couldn't escape! All that could be done was avoid putting it on the floor or cushions. It was fiddly getting all the fluff out but it worked fine thereafter.
A bit of head scratching followed, followed by a bit of shuffling of the laptop on my knees as, without noticing it, it was getting uncomfortably hot. Unconsciously, I had moved it to allow my knee to cool down. When I noticed what I had been doing, I checked the CPU temperature. They were showing 89°C - uncomfortably close to its maximum temperature.
Since it wasn't a fluff in the fan problem, the next places to look are other hardware and software. Since the fan appeared to spinning all the time at full speed, I checked what the CPUs were doing - Task Manager showed they were running at a high operating load - 80% and above. There was nothing to show in the Applications tab so I checked the Processes.
And there was a likely culprit - Google Desktop Search was running at 50% of CPU! For these of you who don't know what it is, it is a search engine that indexes, potentially, the whole of a PC's files, not just for file names but also for content. So, not only can you search for shoppinglist.doc but you can also search for butter or eggs or whatever was on your shopping list within the shoppinglist.doc document. Similarly, it can even index the contents of all your emails. It can be a lovely tool to have available - providing (a) you don't index too much and (b) your CPU can take the strain. This one couldn't.
Since the client wasn't there, instead of uninstalling it, I merely turned it off, rebooted and rechecked the temperatures.
Within a couple of minutes, they had dropped from nearly 90°C down to below 60°C - much more comfortable on my knees.
So, I don't know that I have fixed his switching-off problem but I bet I have.
Subscribe to:
Comments (Atom)