Jaguar XJ Super Sport goes all Blue Screen of Death on us

Modern cars are no mere mechanical devices. They're pervasively monitored and controlled by dozens of computers linked by internal vehicular networks so complex they put your average PC to shame.

So it came as no surprise that very recently, the Jaguar XJ Super Sport we were testing -- one of the most fastest, most thrilling, most technologically advanced cars on the planet -- suffered the dreaded Blue Screen of Death. Fortunately, that was the only kind of crash we experienced.

Usually, hitting the car's power button causes its beefy 503hp supercharged V8 engine to roar into life. On this occasion, the roar was replaced by an eerie silence and absolutely no response from the XJ's entertainment, guidance or instrument systems. Its 8-inch infotainment display and the foot-long computer screen it uses in place of a speedometer were both as dead as a dodo.

Our first instinct was that we'd exhausted the car's battery by watching too much Eminem on its integrated DVD player, so when the friendly Jaguar Assist recovery man arrived an hour after we called, we expected him to slip on some overalls and take a look under the bonnet.

Instead, we were told the problem was far more complex and to get to the root of it he'd need his laptop, some bespoke software and a wireless dongle.

So off he went, connecting one end of a cable to a USB port on his trusty Panasonic CF-18 ToughBook, and the other end to the XJ's OBD-II (On-Board Diagnostics 2) port on the bulkhead beneath the steering wheel. Once hooked up, he tapped a few buttons on the laptop's touchscreen and fired up Jaguar's bespoke vehicle-diagnostics software. The tension, from our perspective, was palpable -- diagnosing crashes in Windows Vista was certainly never this exciting.

Over the minutes that followed, the software analysed every one of the car's digital systems in search of a problem. The culprit could have been any number of things -- the Bosch-supplied, Linux-based infotainment system, the Visteon-supplied virtual instrument display, a heat-ravaged processor, an errant mouse somewhere in one of the car's hundreds of miles of wiring, or the dodgy contents of a CNET UK memory key in one of the XJ's two USB ports.

Like most computer crashes, the true cause couldn't be determined on the scene. Instructions beamed down from Jaguar Towers via the laptop's Wi-Fi dongle suggested further diagnostics were required back at the factory.

We weren't about to let the car go, however. We loved it too much and besides, we had a Car Tech video to finish. As luck would have it, we'd parked somewhere inaccessible by tow truck, so our engineer postponed the factory diagnosis, and attempted a quick reboot to get us back on the road.

Curiously, whatever problem caused the XJ to crash also caused it not to respond to the laptop's reboot command, meaning we had to treat this £90,000 Jag like we do our janky old HP laptop: we disconnected the battery, killed the power and restarted it manually.

It's important to stress that this sort of problem isn't restricted to Jaguar cars -- any automobile that relies on computer hardware and software is at risk of similar crashes.

We need only look as far as Toyota, which issued a software update to alleviate problems with its braking system, or Volvo, which recalled 26,000 cars worldwide due to faulty software that caused engine problems in its T6.

Your car could be next. One recent estimate suggests that the typical luxury saloon now contains over 100MB of binary code spread across 50-70 separate computers, each of which communicates over one or more shared internal networks. Something, somewhere, will inevitably go wrong.

Admittedly, we'd never trade a car's advanced systems to return to the dark ages. Electronic fuel injection, electronically deployed airbags and GPS systems with integrated satellite transmitters are all a part of our modern lives, but this sort of event raises the question: are we becoming too reliant on electronic gadgets?

What do you think? Have you experienced a similar crash? Are you worried about the influx of technology in modern cars? Let us know in the comments below then take a look through our photo gallery above to see how the drama unfolded.

Comments 48

Add your comment

jamesfed's avatar

jamesfed 12 August, 2010 23:48

Gonna be intresting when the cylons take over our cars :D (or am I the only BSG fan who thought of this).

Anonymous's avatar

Anonymous 14 August, 2010 15:38

Question: did the car's systems work OK after the manual reboot?

Anonymous's avatar

Anonymous 14 August, 2010 15:46

So, where's the picture of the _ACTUAL_ blue screen of death?

Anonymous's avatar

Anonymous 14 August, 2010 16:00

I disagree with the notion that GPS (for example) is "part of our modern life". All these accessories are NOT required parts of a car. Many of them are forced into the car by regulatory meddlers, but most of them are just an attempt to increase margins.

Anonymous's avatar

Anonymous 14 August, 2010 16:06

Brittish crap with crappy software from Redmond. What do you expect?

Anonymous's avatar

Anonymous 14 August, 2010 16:15

Lol did you read the article? Linux on the Infotainment System but nowhere any sign of Windows exempt the diagnostic laptop. Don t get me wrong, ich hate Winodws and love Linux but the thing i hate most are trolls ...

Anonymous's avatar

Anonymous 14 August, 2010 16:15

an update to a computer system is NOT comparable to a computer system crash. And computers, reliable ones, have been controlling things in our lives for decades. Thanks to Microsoft, rebooting your car is probably going to become as common as hitting Ctl-Alt-Del.

FYI, there are computers flying airplanes, controlling air traffic, in healthcare systems, microwave ovens, heating and A/C systems and much much more. They are just not running Windows or Microsoft software.

Anonymous's avatar

Anonymous 14 August, 2010 16:17

There's no mention of any actual BSOD (the monitors were blank), or Microsoft software. The only OS specifically mentioned is Linux.

What's up with the misleading and potentially slanderous article title?

Anonymous's avatar

Anonymous 14 August, 2010 16:54

"your car could be next" oh no it couldn't. It's an austin mini. Mind you, I was hit up the bum by a van on Thursday. He cracked his numberplate. I've got £3k worth of repairs...

Anonymous's avatar

Anonymous 14 August, 2010 16:57

What "misleading and potentially slanderous article title" are you referring to? Is it that BSOD is so common on a Windows machine that you automatically think of Windows when you hear the words BSOD? A BSOD can happen on any computer, not just a Windows machine. Although, I will admit, it happens far more frequently on a Windows POS than any other system I'VE ever used. :-) BYW, Windows wasn't mentioned in the title at all some I'm not sure why you think it's a "misleading" title.

Anonymous's avatar

Anonymous 14 August, 2010 16:57

Salad!
Learn to photoshop lol

Anonymous's avatar

Anonymous 14 August, 2010 17:15

...one of the "most fastest"...

Where did you learn your English?

Anonymous's avatar

Anonymous 14 August, 2010 17:20

This is one of the worst articles I've ever read. Your car wouldn't start. It's absolutely, 100% a lie to call that a BSOD. First of all, BSOD clearly refers to windows, named as such because of the color of the kernel fault screen windows shows during a failure. Even if you had decided to extend that to some other OS which happened to make a blue screen, I'd understand. Except you had no screens, no blue, nothing. You had a car that wouldn't start. You also exaggerated Toyota's software fix, which wasn't to fix a brake problem (which was confirmed to be entirely false) but to add features to calm a public so deranged by bulls*** technical lies such as yours they don't have a chance of judging reality. This sensationalist crap belongs in a supermarket magazine.

Luckily, your store got picked up on Slashdot because someone else believed the title, and now 10's of thousands of people are reading this, realizing what a f****** scam you are, and letting everyone they know to avoid Cnet like the f****** plague.

Good day sir.

Anonymous's avatar

Anonymous 14 August, 2010 17:28

What a load of s*** this article is. A blue screen of death is a windows only error screen which is blue with white text. It is not a general crash of any sort of software on any os.

Anonymous's avatar

Anonymous 14 August, 2010 17:38

From the article:

"It's important to stress that this sort of problem isn't restricted to Jaguar cars -- any automobile that relies on computer hardware and software is at risk of similar crashes."

Should read:

"It's important to stress that this sort of problem isn't restricted to Jaguar cars -- any automobile that relies on computer hardware and *Microsoft Windows* software is at risk of similar crashes."

You guys will have LOTS of similar stories once this is common enough that hackers do this through the car's Bluetooth connections -- or -- as encumbering as it can be[come], you can write stories which more accurately portray the risks in the unlikely event that the shared reality enables readers to understand the details, becoming informed consumers. This is the only thing that could potentially reduce the likelihood of actual life-threatening risks should these things happen when the car, or rather it's computer, is in a position where compromise is life-thretening. I know it sounds paranoid, but in this case it's really not that big a leap to understand.

Anonymous's avatar

Anonymous 14 August, 2010 18:10

"most fastest", where did you learn how to write. Seriously, a BSOD, with no Windows OS and no error output at all, I think you might be taking your anti-windows bias a bit far.

Anonymous's avatar

Anonymous 14 August, 2010 18:19

hahaha...your "beefy 503hp supercharged V8" goes nowhere while my brother's '83 Toyota pickup - carburetor, no computers - continues on down the road. EMP? Bring it on!!! :-)

Anonymous's avatar

Anonymous 14 August, 2010 18:32

Author: Take a writing course and a ethics in journalism course.

Anonymous's avatar

Anonymous 14 August, 2010 18:32

"It's important to stress that this sort of problem isn't restricted to Jaguar cars -- any automobile that relies on computer hardware and software is at risk of similar crashes."

How about adding - "It's also important to stress that we have no idea what Operating System(s) other than the entertainment system's Linux are in use, but we figured it would be more attention getting to mention BSOD. We probably could have asked the tech or pursued it with Jaguar but it's so much easier to just blame Microsoft and be done with it."

Anonymous's avatar

Anonymous 14 August, 2010 18:53

I was going to suggest Coverity to the folks who wrote the buggy software.. but I'm not sure Coverity can help Rory with basic English grammar..

Anonymous's avatar

Anonymous 14 August, 2010 19:16

what's next, spyware removal & registry cleaners for our cars??

Anonymous's avatar

Anonymous 14 August, 2010 20:24

This article makes me feel dead inside. It's not a BSOD. Hell, the car doesn't even run Windows, if the article is to be believed.

Better headline is "Jaguar XJ Super Sport Needs Swift Kick To Buttocks To Start" or maybe even "Jaguar XJ Super Sport Has Power Button Issues".

/.

Anonymous's avatar

Anonymous 14 August, 2010 20:46

SOMEONE IS WRONG ON THE INTERNET! ATTACK!

Wow.

I can't believe how riled people get at the mere mention of "blue screen of death" when it is not in relation to Windows. So, a car running Linux breaks and it's probably one of the internal controllers or some buggy software; big deal. I'm sure if the author had called it a kernel panic, nobody would be this annoyed. Relax.

Anonymous's avatar

Anonymous 14 August, 2010 20:46

Ford and Jaguar run Windows for a lot of things - *probably* this thing is windows related. Seen all the ads for "sync"? That's winders.

Anonymous's avatar

Anonymous 14 August, 2010 20:59

My typical luxury saloons contain various video games, and electronic dart machines, sometimes air hockey. Are you suggesting that they're all likely to crash, or does saloon mean car in England?

As for the BSOD whiners, the article may be a bit sucky, but I feel he's fine calling it a BSOD, it's sorta windows specific, but everyone uses it as a general thing.

Anonymous's avatar

Anonymous 14 August, 2010 22:27

I wish people would not get so keyed up and nasty about inconsequential details, such as whether BDOD refers to Windows. Clearly the author was using the term in a general sense to mean a system crash.

Now to the issue raised by the article: Is it a concern that computer programs exist in more and more of the things that we depend on?

The author does confuse one issue that needs some clarification: The author says, "are we becoming too reliant on electronic gadgets?", whereas the article is about a software crash. There are electronic gadgets that don't have software. This distinction is important.

I do agree that the increasing pervasiveness of software is something to be concerned about. Software is generally not designed in a manner that ensure reliability, whereas electronic gadgets without software are. When electronic circuits are designed, analysis is performed that maps all of the states of the circuit. The circuit cannot get into an undefined state (crash). This is not the case with software: software is not designed using state analysis. This is why software tends to be so unreliable.

Software for real time systems should be designed using high reliability techniques. It sometimes is (as in airplane control systems), but I suspect that for automobiles it is not.

Anonymous's avatar

Anonymous 14 August, 2010 23:18

Just to correct one of the comments which says "the car is running Linux": the article only says the infotainment system used Linux, it doesn't mention what any of the other computer systems are running.

Also, while it's possible that a crashed infotainment computer brought the whole system down, it seems more plausible that it was some other more critical system that would have caused a complete breakdown.

Anonymous's avatar

Anonymous 15 August, 2010 00:52

vxWorks is typically the OS used in embedded systems like this
smaller kernel than linux, saves on RAM costs

very tiny embedded systems have no memory protection, so rogue applications can easily crash everything

Shame on Jaguar, their testing missed this bug, no pizza for the QA department.

Wow the technician on the scene with all his gear could not diagnose the problem,but here are a whole bunch of smart alecs who have apparently figured it all out from this article!

Anonymous's avatar

Anonymous 15 August, 2010 01:11

It would have been better to be less greedy and give the car back to Jaguar so they could have analyzed the fault. Now there is no solution for it and it might happen to other cars. Well done.

Anonymous's avatar

Anonymous 15 August, 2010 01:40

Driving a 1971 Type 1 VW. Paper maps, flashlight and spare batteries in glove box. Bottled water, jacket, boots, tools and blankets, spool of wire, fuses, various connectors, oil and brake fluid in the trunk. Not too worried.

Anonymous's avatar

Anonymous 15 August, 2010 05:44

Comparing this to the Toyota problem is foolish. Toyota uses a fully embedded real-time system (perhaps ITRON?), Vista is neither fully embeddable nor real-time. Whoever chose to use Vista to run the car was an idiot; I find the prospect of the OS not being real-time alone extremely frightening. I've never been particularly interested in Jaguar cars, but after reading this I'll be sure to avoid them completely.

Anonymous's avatar

Anonymous 15 August, 2010 05:59

you should file a lawsuit because the manufacturer put you in danger of death, that car is a ticking time bomb waiting to happen, I am sure the nexst BSOD will be on the high way and you will inevitably crash, die and killa at least 5 others, so get a lawywer and make sure you never buy crap again

Anonymous's avatar

Anonymous 15 August, 2010 06:31

.

Yes... I want a car with points, a coil and a battery for ignition.

.

Lights are nice too.

.

And perhaps a wireless.

.

Computers? Lines of code?

.

forget it.

.

Anonymous's avatar

Anonymous 15 August, 2010 06:49

"What do you think? Have you experienced a similar crash? Are you worried about the influx of technology in modern cars?"

I look forward to the follow-up to this story.
As for the crash - not entirely, but owning a 1997 Mercedes I am wary of the computers in that car, not looking forward to 2010 cars..

I am not worried about the influx of technology, but the influx of unreliable-and-unproven technology.

Anonymous's avatar

Anonymous 15 August, 2010 09:34

Well i got a C4 GP that has had it's moments but it has to be said that is/was down to a bit of bad design it used to die it does not any more water gets into places and causes havoc silicone grease works wonders

As for the naming of the article i think CNET need to go away think again and come back with a more correctly worded title BSOD is windBloWs thing ther is NO BSOD in Linux Chances are one of the so called RTOS embeded systems had a benny and cut the power to the Linux based infotainment system

Anonymous's avatar

Anonymous 15 August, 2010 09:56

... and then there's this tripe:

"Modern cars are no mere mechanical devices. They're pervasively monitored and controlled by dozens of computers linked by internal vehicular networks so complex they put your average PC to shame...One recent estimate suggests that the typical luxury saloon now contains over 100MB of binary code spread across 50-70 separate computers, each of which communicates over one or more shared internal networks."

100MB of code and 50-70 "different computers" communicating over a network? And that's supposed to put my PC to shame? Try multiple CPU cores, GPU cores, caches, discrete devices, etc. all communicating over shared buses. Add to that a lot of multithreaded applications and you get quite the complicated little machine, not something easily "put to shame" by a car with embedded devices. What a silly article this is ...

Anonymous's avatar

Anonymous 15 August, 2010 14:47

Well. Things like that just happen... they happen today and did always since we knew cars!
While today you just need to use your mobile phone and wait one hour to get support, in the times when there were no embedded systems you were just lost ... or a car mechanic expert...

Anonymous's avatar

Anonymous 15 August, 2010 15:46

--- quote ---
quite the complicated little machine, not something easily "put to shame" by a car with embedded devices.
--- end quote ---

Yes, but the point you're missing: your computer, for all its complicatedness, is made by ONE company, and (most likely) runs an operating system written by ONE company. That is a total of TWO companies that have to interface. In a car, with 50-70 separate computers, there are at least 10-20 different companies building the hardware and software (article mentions Bosch, Visteon as examples), and all it takes to fail is that one of these do not communicate correctly with the others.

In the world of subcontracting, a car manufacturer tells Bosch (or whatever) that they need "device to do XXX". Bosch creates a device like this that works on several different cars. All the car brands use a different combination of subcontractors. Now you can begin to appreciate the complicated situation...

Anonymous's avatar

Anonymous 15 August, 2010 16:05

"The culprit could have been any number of things -- the Bosch-supplied, Linux-based infotainment system [..] or the dodgy contents of a CNET UK memory key in one of the XJ's two USB ports."
*cough*bulls*** *cough*

If those were the causes Jaguar is the dumbest car manufacturer... in the world.

Anonymous's avatar

Anonymous 15 August, 2010 17:40

It's always amusing when desktop computing experts try to write about embedded systems. Here are a few facts about embedded controllers in automobiles. First, any car less than fifteen years old uses computer control for at least its engine, transmission and radio. Without the first two, it would be impossible to meet requirements for fuel economy and tailpipe emissions over a wide range of operating conditions. These days even the least expensive auto uses two dozen or more processord.

Second, with vanishingly few exceptions, each electronic module is a closed system that can only be reprogrammed with special equipment. The idea of introducing a "car virus" via an entertainment or phone connection is laughable. If nothing else, opening any computer in the auto to third-party software is seen as a threat to manufacturers' cash flow.

Third, the modules that make the car run do not run Windows, Linux or likely any other full-fledged operating system. The constraints are memory size and real-time performance. Look for widely known OSes only in the navigation system, voice recognition module and possibly the radio.

What really happened to the Jaguar? From Rory Reid's description, we'll never figure it out.

Anonymous's avatar

Anonymous 15 August, 2010 18:02

Bad story. I can't find any mention in literature about this car model using Windows. So it can't be the BSOD.

As a person who has done work on cars (software) for Volvo and Jaguar (they were both part of Ford once) testing is pretty damn good (or it was 5 years ago). If they have followed Volvo's approach there is a back bone high speed communications bus that essential systems and "added value" crap systems share. So conceivably a problem from one main system could bomb the watchdogs on other parts. Lots of the systems often talk to each other with a rotating key as part of the watchdog security set up.

Be interesting to know what it was. But I really can't imagine car makers putting Windows in, despite what might be thought the license cost is a lot even on a £50k item as it probably shares a lot with cheaper models and potentially across other (say Ford models). Result it's a cost on millions of items in the life time of the models. They will avoid such a high component cost where they can.

Few cars up to about 5-7 years ago had any OS in any systems. They take too much resource.

RSM37's avatar

RSM37 16 August, 2010 02:46

Glitches are not uncommon or easy to fix. Our Benz SL refused to start for months.. it also declined to open the door using the remote. Sometimes the auto lock does, sometimes it does not.
,
But after $2,000 in rewiring.. all seemed fine, till one day I got out to post a letter, motor running, just twelve paces over and back.. raining cats and dogs.. pushed the door closed to just the first latch.. and before my eyes the auto lock feature kicked in.. the keys inside..

Fortunate to have friends who could fetch me to go get the other fob so I could get in. Tried to mimic the event for weeks.. nothing.. Reread the manual (124 pages) twice.. this is an undocumented 'feature.'

Six months passed when one day I realized the trunk was not closed and went back before pulling out to close it .. the door closed to the first latch.. and the locks went down.. nothing in the manual about this auto lock feature with motor running.. but hey.. British Heritage and a German car.. should have known.

These cars are far too complex and expensive.. plus so many diversions.. which probably cause the accidents some features prevent. As another post said.. all this stuff justifies 'value' added.. and a nightmare as systems fail or glitches turn these cars against us.

Lets hope that some of this will go away when all electric is what they will sell. Microwaves work as too cordless drills, blenders and egg beaters. Give engineering to the simple appliance makers.

Anonymous's avatar

Anonymous 16 August, 2010 14:45

Cool the fridge down all of you. Look, the headline read: "...goes all Blue Screen of Death on us" - it DOES NOT saying, nor does the article, that the car experienced the BSoD. It is a reference to the more pop culture now than tech reference to machines blue-screening when an error occured.

Anonymous's avatar

Anonymous 16 August, 2010 20:49

Not quite BSOD's with my previous Merc E-Class, but that thing had so many electrical glitches - usually resolved by stopping, turning off and restarting that, in the end, I couldn't live with it. Speed limiter jamming on, engine management warning light (dealer said ignore it, no fault found - it will go away!), transmission sticking. infotainment shut-down - I'll stop there but belive me there were many other problems!

Ironically, I changed it for a Jag XJ8 (previous model) and after 3+ years, and not totally free from problems, it is still streets ahead of the M-B!

Anonymous's avatar

Anonymous 17 August, 2010 14:26

"Too dependent" on technology? How far back in time do we have to go in order to reach the point where we are not "too dependent" on technology?

How about 1990, when every business had to have a fax machine. How about 1970, when every large corporation had to have a mainframe.

How about the 1950s, before most of your readership was born, when jet travel and television were becoming commonplace.

How about the 1860s when the telegraph and rail travel were indispensable to the free enterprise economies of the UK and the US?

At any of those points in history if you then arrest development or, worse, roll it back, the consequences are significant.

Regards,

James Mireles
Houston, TX

Anonymous's avatar

Anonymous 20 August, 2010 20:29

So where is the content here? So far you could have made this story in 2 lines.

While reviewing a Jaguar, it didn't start (apparently due to a technical problem).
We called jaguar and they didn't even understand the problem, nor do we.

End of article.

What happened to reporting? Where are your experts?

Anonymous's avatar

Anonymous 3 September, 2010 00:45

Windows, rubbish on desktops and laptops, rubbish in cars. When will people learn? Just cos there is a lot of it about doesn't mean its good, just well marketed

anonymous's avatar

anonymous 3 September, 2010 01:10

I have a XJL Supercharged that I purchased on 18 Aug - had a similar problem - not everything went down - just the audio, nav system and video along with some intermittent issues - no left rear turn indicator, trunk closing button works occasionally. After a day in the shop and finally a hard reboot all seems fine - I wonder if it is time to put a large on/off switch on the main battery terminal so we can make this a DIY thing.

Post your comment

Make your comment count. Log in or register to skip the 'Are you human?' question and get an avatar

Will not be displayed with your comment

Copy the letters and numbers to prove that you're human. You won't have to do this if you log in or register

Your comment must comply with the Terms of Use

About CBS Interactive

Copyright © 2012 CBS Interactive Limited. All rights reserved.