> My next question is if I use ASIO4ALL
Just don't :)

Iam using a behringer asio4all 64 bit driver it complements my behringer audio interface I've had no problems iam getting a crisp crystal clear output as well with no dropouts. It pays to choose carefully!

It's one thing to get sound from a interface, There is a lot more to it than that. Trust me, I've done all those dumb things in an attempt to make a Sound Blaster, and yes later on that little box with RCA in/out that Behringer shipped and called an interface work. ASIO 4 all might solve 1 in 10 peoples issues if absolutely no other solution is available.  
Things that also go wrong and you might not even be aware it's happening is your timing sync. Latency is your number one enemy in an audio driver. 
 
 I strongly recommend you put the old device to one side and upgrade to a modern USB/Firewire interface. It is the quick and clean solution.
Be very careful installing ASIO4 all it is not so easy to get rid of it.  

you do need to be technically-minded (i wouldn't expect my dad could install them correctly) but asio4all is definitely worth trying before spending money on something that may also have issues... 
if asio4all doesn't work for you, just uninstall it - though it seems some people may have had issues with that, it has never been anything other than totally straightforward in my experience: i used asio4all with an Alesis Photon x25 (crap asio drivers, so just let win see a generic usb audio device, add asio4all and voila!) and a lappy for years, with great results, on XP32, XP64 and Win7/64, and now using it with the onboard realtek on an asus lappy with win7/64 - all happily alongside asio drivers for an edirol ua-1000 - the beauty of digital is you DO get stuff for free :-)
and if you want get the most out of the older soundblasters (emu!), you need to use the kxproject drivers, as any fule no ;-)
good luck!

My first recording interface unit was an IO26.  I had various problems with it (and was using a T.I. Firewire chipset in the PC).  It wasn't causing the PC to crash, just flakey problems with what I assumed was the actual unit.  I replaced the IO26 with a Focusrite Saffire Pro 40 which is also a Firewire interface unit and all my problems that I had with the IO26 went away.
 
Is the PC crashing just by connecting the IO26 to the PC, without starting Sonar or having other recording devices connected?  I doubt that ASIO4ALL will really help with this issue.  The purpose of ASIO4ALL is to make a device that does not have ASIO drivers look like it does to the PC.   Windows 7 uses the same sound drivers as Vista, so I don't think having an older driver is the issue.
 
If you want to try reinstalling the driver that may help.  Suggest using a program uninstaller such as Revo Uninstaller to completely uninstall.  Physically disconnect the IO26 from the PC, restart the PC and then do a new install by first installing the IO26 software (driver) and only connecting the unit when the install program tells you.  Also, make sure you are using the "legacy" firewire driver in Windows.
 
Revo uninstaller pro trial version download: http://www.revouninstaller.com/
 

In case this is at all helpful:  I have the original version of Alesis iO|2, and it's working fine, EXCEPT its driver doesn't work with 64 bit.  A couple of years ago I begged Alesis for an updated driver, and after some dancing around in their replies, they finally said the unit only had one driver ever released for it, and no update was available.  They also admitted the driver doesn't work in 64 bit.  Their official solution was to use ASIO4ALL.

So, that's what I have set up, and having the two different drivers hasn't caused problems I'm aware of.  When I open Sonar 32 bit, iO is the driver that comes up.  When I open Sonar 64 bit, ASIO4ALL kicks in, and its the driver listed in the audio dialogue.  If, when Firefox is open, I open a stand alone version of something that needs audio, like the ARIA Player stand alone version, that's also when ASIO4ALL kicks in, because Firefox usurps the Alesis ASIO.  It's the same scenario if I open Sound Forge when Firefox is open.

If I'm working in Sonar, using ASIO4ALL, naturally that's the interface that opens when I click in Sonar's audio dialogue to adjust the interface latency settings.

For me, going back and forth between those two drivers, depending on the situation, has been pretty much seamless.

Randy

That's why I decided not to upgrade to a firewire interface, I've had no problems with my behringer uca 222 audio interface using asio4all 64 bit drivers the latency is great I've no timing issuses etc everything works mint no worries. Besides when your on a budget why splash out wade when its not needed!