3 Users Commented In This Post

Subscribe To This Post Comment Rss Or TrackBack URL
colin_w says, March 25th, 2008   

Good example of troubleshooting BSOD. The first Podnutz podcast also deals with BSOD problems at boot up. Podnutz is a relatively new podcast on DIY computer repair. Well worth listening to:

http://podnutz.com/

Kirk says, March 25th, 2008   

sometimes , mostly motherboard is the damage when there’s nothing u can see in the monitor.

z0iid says, March 26th, 2008   

If you can boot into the windows recovery console, you can run “chkdsk /r”. You can run ntfsdos from the Ultimate Boot CD, but you don’t get the chkdsk options. You can just run it, but not in repair mode.

First attack for blue screens? F8 and select “last known good configuration”. Occasionally, this does actually work. If that doesn’t, I do an harddrive scan (using the Ultimate Boot CD) based on the manufacturer of the HD. This may take some time, but sometimes you will find that the hard drive is “failing” and should be replaced.

At this point, you can slave up the drive and backup important files. If the drive still isn’t “visible” as a drive letter when slaved up, but shows up in mass storage devices - then you may need to use recovery software. My software of choice is EasyRecovery Professional.

As Martin says, occasionally you run up against bad memory or a processor, but the majority of the time (and I do this for a large organization) it has something to do with the harddrive or filesystem.

Leave Your Comments Below
Hello, please leave your thought below

Please Note: Each comment will be manually approved by an admin. There is no guarantee that a comment will be posted. Please do not submit the comment multiple times.