In my case, at approximately the same time as Cymsdale, the game crashes during the turn when the first pioneer has been created, very early in the tutorial. Moving the mouse cursor from my sovereign to the city crashed the game and trashed my computer by forcing it to execute a catastrophic reboot! This has happened the two times I have tried the tutorial, on the turn when the pioneer was created.
My system has a Radeon HD 5870 card, with the most recent drivers. No other game that I have been playing on that computer for the past 2½ years has forced my system to reboot. As an example, I can tell you that I have been playing at "Warlock : Master of the Arcane" for over 965 hours (according to Steam), for the past six months, and it has never crashed! I play it in windowed mode, as is the case with the FE tutorial, with no multitasking with other programs which might create a conflict. A game that forces my computer to reboot is not one that I will risk playing, especially when there is a very stable one available in the very same genre.
What I found strange, the two times I tried the tutorial, is that I could not find the pioneer unit. I got the message that the pioneer had been produced, but I could not find it : it was not next to my city, and only the sovereign appeared in the unit list (top left). The two times the computer crashed occurred when I was moving the mouse cursor to search for that pioneer. It was perhaps somewhere, but the crashes did not give me the time to find it. If there is a bug which crashes the game because the announced unit is not effectively there, I do not understand why such a bug would cause my whole computer to abruptly reboot.
I am going back to W:MotA, and I will retry FE's tutorial after the game has been patched. I am sorry to have to say that I do not have the time and interest to playtest a game which causes a catastrophic reboot of my usually problem-free computer.