Microsoft Code at Fault for Half of all Windows Crashes

Flamester writes "In a ZDNet Australia story, Microsoft is claiming that half of all MS Windows crashes are the fault of third party code, not their own. That is, according to Dr. Watson. The article also goes into the 'rigor in which MS tests their products before release'. "

Comments

Well, technically speaking,

[Mordant]

I guess MSBLASTER, Code Red, Nimda, SQL Slammer, etc. could be considered 'third-party code'. ;>

These numbers lie and are

[teamhasnoi]

not to be believed! It is well known that Dr. Watson has a weakness for liquor, and fraternizes with a known cocaine addict.

His conclusions are suspect, and so are his motives. It's elementary, really. Bill G should get Magnum P.I. or Simon and Simon to do this investigation.

SCO is responsible...

[macshune]

SCO is responsible for the other half of crappy windows code. This is why Microsoft was so eager to buy a license.

So...

[useosx]

...Slashdot poll: Is the cup half full or half empty?

Lines of code

[rf0]

I was googling for the 4 lines of C code that use to crash windows but came across this

Rus

Clarification of 'rigor'

[Obsequious]

'rigor in which MS tests their products before release'.

Hmm... What kind of 'rigor' is that, again? Rigor mortis?

They should steal better code

[bugfixer]

So I guess all of the crashes that I have experienced with Inernet Explorer can be blamed on the the third party software they stole from the University of California and Eolas Technologies Inc.

MS Blaster

[SpaceRook]

I think in the last day, the number of crashes due to Microsoft code has risen to 75%.

In other news...

[FattMattP]

In other news, the sky is blue.

Scene at MS HQ

[guacamolefoo]

Scene: Microsoft HQ
Present: Emporer Gates, DBallmer

Emporer Gates: Darth Ballmer, it has come to my attention that we do not possess 90% market share in certain aspects of our operation. Your performance diappoints me...

Darth Balmer: Ook.(1)(2)(3) [Hooo...haaa...hooo...haaa](4)

Emporer Gates: Our code causes only 50% of crashes, yet we control 95% of desktop computers...can you explain the ineffectiveness of our operation? Why are we lagging in this area?!?!?

Darth Balmer: Ook. [Hoooo...haaaaa...hoooo...haaaa]

Emporer Gates: Please put your army of flying monkey dark Jedi to work on this problem immediately. I expect results, Ballmer. You will not fail me in this, or you will be looking for bananas in the sodomy pits of the Hutts!

Darth Balmer: Ook! [Hoooo...haaaaa...hoooo...haaaa]

GF.

(1) Monkeyboy
(2) Librarian
(3) I'm aware that it should be "Ape-boy" if the Librarian is an Orangutan, but if you don't tell the Librarian, I won't.
(4) Darth Vader breathing sound

It's not a bug, it's a feature

[pherris]

John Dvorak ... works out that there are 25 millions blue screen crashes of XP per day.

25m per day? MS needs to start putting banner ads on them. During those nice long core dumps that could say something like "Special for today: upgrade to Microsoft Windows Server 2003 for only $999! Press your reset button to continue."

We would have the real numbers but...

[Anonymous Coward]

At Microsoft we were going to tell you who was responsible for the other 50% of the crashes but then our sql server database crashed on us.

CNN Poll

[Izeickl]

A poll at CNN here here shows how sometimes no matter what MS does a huge amount of people will be leaving themselves open to problems.

" How are you planning to protect your PC from the LoveSan Internet 'worm' affecting Windows-based PCs?

Going to load a patch from Microsoft 19%
Have already loaded a patch from Microsoft 39%
Doing nothing 41% "

Re:Uhm, right...

[clary]

If you weren't P.E. certified, you couldn't legally call yourself an engineer in Texas. No exceptions.

Must be a bitch finding qualified dudes to drive the trains. ;-)