Comments on: Blue Screen http://chris.pirillo.com/blue-screen/ News and Reviews! Geek, Internet Entrepreneur, Hardware Addict, Software Junkie, Book Author, Once TV Show Host, Technology Enthusiast, Shameless Self-Promoter, Tech Conference Coordinator, Early Adopter, Idea Evangelist, Tech Support Blogger, Bootstrapper, Media Personality, Technology Consultant, Thicker Quicker Picker Upper. Tue, 24 Nov 2009 17:33:24 -0800 http://wordpress.org/?v=2.8.5 hourly 1 By: Calmguyhttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-488564 Calmguy Thu, 26 Jul 2007 21:16:19 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-488564 I myself have been visited by the Blue Screen of Death on numerous occasions. Namely, every time I switch my pc on. Nevertheless, I find just by updating each part of hardware thru its manuracturers site seems to prevent the son of a bsod from appearing. I myself have been visited by the Blue Screen of Death on numerous occasions. Namely, every time I switch my pc on. Nevertheless, I find just by updating each part of hardware thru its manuracturers site seems to prevent the son of a bsod from appearing.

]]> By: mackkiehttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16323 mackkie Fri, 18 Feb 2005 18:35:57 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16323 I think the \D part really should be ignored. The \Harddisk2\ part is the important one. \Harddisk0\ would be ide primary master. \harddisk2\ would most likely be secondary master. If it is a serial ATA drive, I have heard of some issues with the maxtor line of SATA drives causing this issue on intel ICH5 controllers. I think the \D part really should be ignored. The \Harddisk2\ part is the important one. \Harddisk0\ would be ide primary master. \harddisk2\ would most likely be secondary master. If it is a serial ATA drive, I have heard of some issues with the maxtor line of SATA drives causing this issue on intel ICH5 controllers.

]]> By: Matt Hartleyhttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16322 Matt Hartley Wed, 29 Dec 2004 17:19:50 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16322 Jeff, take another look again... <blockquote>To be honest, I don't think the controller is at fault and the likelihood of the cables being bad is not too likely. So this leaves us with the drives themselves. Still, where it starts to get sort of weird is the fact that it is reporting problems with multiple drives. Since it is highly unlikely to have issues with multiple drives, then could it in fact be the controller? Even though, things are almost pointing at something else other than the drives themselves, it might still be worthwhile to run a chkdsk on all internal drives along with using the diagnostic utilities that most hard drive manufacturers provide from their Web site. Since I do not believe that Chris has immediate access to a PCI Adapter Card IDE Controller that he can simply plug in and then leave the PC running all night to see if it is in fact, a controller issue.</blockquote> Jeff, take another look again…

To be honest, I don't think the controller is at fault and the likelihood of the cables being bad is not too likely. So this leaves us with the drives themselves. Still, where it starts to get sort of weird is the fact that it is reporting problems with multiple drives. Since it is highly unlikely to have issues with multiple drives, then could it in fact be the controller?
Even though, things are almost pointing at something else other than the drives themselves, it might still be worthwhile to run a chkdsk on all internal drives along with using the diagnostic utilities that most hard drive manufacturers provide from their Web site. Since I do not believe that Chris has immediate access to a PCI Adapter Card IDE Controller that he can simply plug in and then leave the PC running all night to see if it is in fact, a controller issue.

]]> By: Matt Hartleyhttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16321 Matt Hartley Wed, 29 Dec 2004 17:16:15 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16321 Jeff, Basically I said it was either the controller or the drives. The cable is almost for sure a waste of time. Since both drives seem to be acting up, the controller is a likely culprit, however it is not very wise to assume the drives fine as well. We seemed to agree about it perhaps being the controller, I still suggest he test those drives anyway though. Assuming is a dangerous thing. ;o) Jeff,
Basically I said it was either the controller or the drives. The cable is almost for sure a waste of time. Since both drives seem to be acting up, the controller is a likely culprit, however it is not very wise to assume the drives fine as well. We seemed to agree about it perhaps being the controller, I still suggest he test those drives anyway though. Assuming is a dangerous thing. ;o)

]]> By: peartreehttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16320 peartree Wed, 29 Dec 2004 15:10:43 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16320 Oh, yeah. About the TCP/IP thing. That's puzzling. I'm going to assume that you're not stupid enough to run without a firewall and anti-virus in place. So, I don't suppose a worm could have gotten in. That's what makes this excess of TCP/IP connections puzzling. Unless, of course, you run your local network on TCP/IP. Oh, yeah. About the TCP/IP thing. That's puzzling. I'm going to assume that you're not stupid enough to run without a firewall and anti-virus in place. So, I don't suppose a worm could have gotten in. That's what makes this excess of TCP/IP connections puzzling. Unless, of course, you run your local network on TCP/IP.

]]> By: peartreehttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16319 peartree Wed, 29 Dec 2004 15:02:51 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16319 Ah! A chance to hand out free advice! Sorry to say that I donÂ’t think Matt is right. Look at the pattern: hard errors from varying sources on the hard drives. Never one type of error from ONE drive. That makes the possibility of it being a real hard drive error very small. Ditto that for being a cable fault, although you donÂ’t really lay out the setup well enough to say. If both the drives producing errors are on ONE cable, then it makes sense to replace (or test by swapping in a replacement) the cable. If that doesnÂ’t stop the errors, then the most likely culprit HAS to be the IDE channel controller on the motherboard. You never really LIKE to think about replacing a motherboard, but sometimes you donÂ’t get a choice. Oh, yeah, IÂ’d also update any motherboard drivers, if there is an update available, and test it again. Now, that said, at least youÂ’ll have the chance to get some exciting new technology if you have to replace the mobo. And, YES, of course you run chkdsk on ALL the drives AFTER you resolve the problem. If the system is generating this kind of error, then doing it before fixing the problem is a waste of time. Ah! A chance to hand out free advice!
Sorry to say that I donÂ’t think Matt is right. Look at the pattern: hard errors from varying sources on the hard drives. Never one type of error from ONE drive. That makes the possibility of it being a real hard drive error very small. Ditto that for being a cable fault, although you donÂ’t really lay out the setup well enough to say. If both the drives producing errors are on ONE cable, then it makes sense to replace (or test by swapping in a replacement) the cable. If that doesnÂ’t stop the errors, then the most likely culprit HAS to be the IDE channel controller on the motherboard. You never really LIKE to think about replacing a motherboard, but sometimes you donÂ’t get a choice.
Oh, yeah, IÂ’d also update any motherboard drivers, if there is an update available, and test it again.
Now, that said, at least youÂ’ll have the chance to get some exciting new technology if you have to replace the mobo. And, YES, of course you run chkdsk on ALL the drives AFTER you resolve the problem. If the system is generating this kind of error, then doing it before fixing the problem is a waste of time.

]]> By: W!LL.i.amhttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16318 W!LL.i.am Wed, 29 Dec 2004 10:52:13 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16318 I have had similar situations with my dear ol' pc. Charming as the blue screen is with it's nice white font, it sometimes doesn't make nice (or clear) as to what the real problems are. After leaving my pc on all night, I woke up to a frozen system. I restarted and noticed my cd-rw drive was not even there anymore-? I checked my log files for errors, but nothing that seemed to have caused the crash that would make my cd-rw totally disapear. I am starting to wonder if that SP2 for Windows XP had anything to do with it, seems like it did the last time I installed it. Am I SP2 paranoid? W!LL.i.AM <a href="http://spaces.msn.com/members/williamlove" rel="nofollow">spaces.msn.com/members/williamlove</a> I have had similar situations with my dear ol' pc. Charming as the blue screen is with it's nice white font, it sometimes doesn't make nice (or clear) as to what the real problems are. After leaving my pc on all night, I woke up to a frozen system. I restarted and noticed my cd-rw drive was not even there anymore-? I checked my log files for errors, but nothing that seemed to have caused the crash that would make my cd-rw totally disapear. I am starting to wonder if that SP2 for Windows XP had anything to do with it, seems like it did the last time I installed it.
Am I SP2 paranoid?
W!LL.i.AM
spaces.msn.com/members/williamlove

]]> By: Anonymoushttp://chris.pirillo.com/blue-screen/comment-page-1/#comment-16317 Anonymous Tue, 28 Dec 2004 18:53:49 +0000 http://chris.pirillo.com/2004/12/28/blue-screen/#comment-16317 I have been a little bored by most of the current crop of webloggers and suddenly today I realised what I had been missing from the good old days. I think we need more of the original creative over the top weblogs. I have started a new campaign to bring back The Talking Moose. http://www.shadowcentral.net/2004/12/bring_back_the_.html I have been a little bored by most of the current crop of webloggers and suddenly today I realised what I had been missing from the good old days. I think we need more of the original creative over the top weblogs. I have started a new campaign to bring back The Talking Moose.
http://www.shadowcentral.net/2004/12/bring_back_the_.html

]]>