On Tue, Oct 20, 2009 at 6:47 AM, Joseph L. Casale JCasale@activenetwerx.com wrote:
I called them and explained to them that I couldn't get it to boot -- they gave me instructions on reinstalling
So Windows is garbage because one support tech is an idiot? There are no idiots in the Linux world?
Support techs usually look up problems in the support database. But if you know of an official Microsoft fix for KSOD, I would be happy to take a look at it.
The KSOD "event" occurred after an automatic Windows update (which isn't all that uncommon I found out).
I have never had a bsod after windows update in 15 years? But then again, I test all my updates in a lab environment before my WSUS server pushes them out on mass.
Again, I think you're talking about Windows in a server environment rather than on the Desktop. Two different animals. Google "KSOD" some time.
Okay, what did they tell you about KSOD? Even if I can't fix it, I would at least like to know what really causes it. (There are a lot of theories out there.)
It wasn't a BSOD, it was high IO across a set of spindles with VSS "enabled and setup wrong" by my corp. What the entry tech (as it wasn't yet elevated) didn't know was specific details about how my fileserver was utilized which had an impact in my scenario. A seasoned colleague on the list who *just* went through it all gave me the tip.
I guess all Linux techs start out at Datacenter level:)
And, if you're an individual user, that's all the higher you're going to get. Thing is, if there is a solid fix for KSOD, Microsoft should publish it on their web site. Again, you're talking about server issues -- so it's like comparing apples to oranges.
Seems to me you're a little bit too sensitive here.
You're right, because that BS was just MS hate, not fact.
I didn't see the hate. I saw reality. I *often* see "reinstall" given as the final fix for Windows issues. I hope (am pretty sure) that's not the "fix" they give you on Microsoft servers, but it's definitely the "fix" you're given on Microsoft desktops.