Post by jeanc on Dec 28, 2009 11:22:26 GMT
Hi,
Yesterday I had something strange. When I switched asio driver in cubase 5 to asio4all cubase suddenly hang. It has not done this before so 'something must have changed' (c).
I had to do a hard reboot but then my pc wouldn't start anymore, it got stuck right after the first bios message saying 'initializing usb devices'. After disconnecting my usb soundcard (tascam usb u122l) the pc would start up again but then after connecting the card again I got a BSOD.
I then had the idea of installing the card's drivers again, thinking that 'somehow' they got corrupted, and yes, after a reboot I could connect the card again and everything was ok.
I uninstalled asio4all but I am still very curious as to what has really happened. For one thing I have never encountered a pc hanging at the bios stage because of a driver not installed, only explanation is that that driver installed something on the card itself. Weird, never heard of that, but it's the only explanation me thinks.
This is obviously not asio4all's fault, because sometime ago I could switch all I wanted.
So for now I can't use asio4all anymore (until I reformat windows and start over), but for the sake of my peace of mind does anyone have any idea why those 2 asio driver conflict have caused such mayhem suddenly?
Yesterday I had something strange. When I switched asio driver in cubase 5 to asio4all cubase suddenly hang. It has not done this before so 'something must have changed' (c).
I had to do a hard reboot but then my pc wouldn't start anymore, it got stuck right after the first bios message saying 'initializing usb devices'. After disconnecting my usb soundcard (tascam usb u122l) the pc would start up again but then after connecting the card again I got a BSOD.
I then had the idea of installing the card's drivers again, thinking that 'somehow' they got corrupted, and yes, after a reboot I could connect the card again and everything was ok.
I uninstalled asio4all but I am still very curious as to what has really happened. For one thing I have never encountered a pc hanging at the bios stage because of a driver not installed, only explanation is that that driver installed something on the card itself. Weird, never heard of that, but it's the only explanation me thinks.
This is obviously not asio4all's fault, because sometime ago I could switch all I wanted.
So for now I can't use asio4all anymore (until I reformat windows and start over), but for the sake of my peace of mind does anyone have any idea why those 2 asio driver conflict have caused such mayhem suddenly?