BAM crash
Irql error blue screen in Win10 (which gives me headaches).
I build a brand new i7 system with a new ESI Juli@ card and a older spare Marian Trace Alpha a few months ago to use in 4 months from now for sound processing and streaming.
Loaded the system with Win7 which upgraded to Win10, so I decided to test this one, it was running 24/24/7 for 8 weeks and 2 days only Winamp and speakers.
So today, when I was tweaking some stuff in my sts files on my main computer, the old i7.
I noticed the new gig gave major issues in this order.
* right output channel quit to play from the ESI card.
* Software error that said card couldn't run in 192Khz mode, which was set in 48Khz (???)
* a buzz sound and the blue screen, which annoys me enormous with that ":(" emoticon.
* computer restarted after making the sys log file.
and everything did just run fine, I lost some settings in both Marian and ESI software.
I never experienced this with my older workstations I build in the past years.
After searching what the hardware error meanth it seemed to have a conflict with the ESI card and a network adapter.
I never had these errors before and it seems when you strip Win 10 from all restrictions, it rebuilds it back with every update (which are disabled) but seems they update it anyway.
I think I just switch over back to win7 or start to use Ubuntu, but problem with that is you can't use it in a 64bit system with a Intel processor. You can run it only in 32bit modus.
Anybody else have these issues with Win10? For pro users in my opinion a big fail.
Or a good alternative? Win 10 is good for users that only surf on the internet and it also depends on which machine it is installed (I have all Intel systems) a few runs ok, but in general it's just crap IMO
|