Win10 Crashing -EuCon Related?

[J-S-Q]

I've been getting a lot of blue screen crashes in the past few months. Sometimes my system will blue screen almost immediately after booting into Windows so I don't think it's necessarily DAW related (I use Cubase).

I'm not an expert with this stuff but when I look in the Windows Event Viewer, I pretty much always see Error messages that reference Eucon right around the time of the crash. See attached screenshots as an example.

I'm running Win10, an S3 and an Artist Transport. My firmwares are up to date. I have tried rolling back to Eucon 3.6.1 but the crashes still happen.

Can anyone suggest how I can trouble shoot this?

[Anthony_Anz]

Originally Posted by J-S-Q

my system will blue screen almost immediately after booting into Windows

usually this is driver related.. make sure you have the most recent network drivers for your network card/motherboard.

[J-S-Q]

Originally Posted by Anthony_Anz

usually this is driver related.. make sure you have the most recent network drivers for your network card/motherboard.

I thought I had the latest versions but I will re-check that.

[EddieJones]

The blue screen should have a message on it which says what caused the crash..try and take a photo and post it.

I dont think those EUCON errors are causing the crash (they are just networking errors)

[Anthony_Anz]

Originally Posted by J-S-Q

I thought I had the latest versions but I will re-check that.

Oddly enough video drivers can make windows crash immediately upon kicking over to the UI too.. check those as well..

[J-S-Q]

Looked at some of my drivers and noticed that the Firewire driver had been updated. I had trouble with this before and changed to the legacy driver which cured it but I'm guessing it was switched back by one of the Windows updates.

No crashes in the last 24 hours so I'm pretty sure I've solved it.

Thanks for pointing me in the right direction!

[Anthony_Anz]

Originally Posted by J-S-Q

Looked at some of my drivers and noticed that the Firewire driver had been updated. I had trouble with this before and changed to the legacy driver which cured it but I'm guessing it was switched back by one of the Windows updates.

No crashes in the last 24 hours so I'm pretty sure I've solved it.

Thanks for pointing me in the right direction!

Cool, glad you're up and running.. Yea, I had to switch my firewire drivers back to the legacy ones too when I first set my system up. I typically have Windows Updates turn off. Next time I run a manual update I'll be on the lookout for this!