Under review

MD4-10 Blue Screen while Ethernet Disconnect

Dragos Popa 2 months ago in IQANdesign updated 1 month ago 3


We are using a MD4-10 (IQAN-6) as main controller for our vehicle. Recently, a bluescreen appeared while we were disconnected from the vehicle via the controller's ethernet port connexion; we were measuring. When it disconnected, I also felt a small static shot from my laptop (I don't know if this is related to the error but it is something I have noticed when it happened). The error code is os_error(0x1000002) with run fault pid 90131. I have looked on IQANForum and I have seen this error before but not from the same source.

We are fixing the wire ethernet connector on the vehicle but is this something that has a precedent ?

Have you seen this type of error before?

Image 3908

Thanks for the support.


Under review

That is interesting. 

When seeing the error code os_error(0x1000002), I am wondering if this might be an application that sends a lot of outgoing messages. You can provoke a similar error if you make an application that tries to send more than 100% on a CAN bus. 

Just disconnecting the Ethernet during an ongoing measurement should not cause this. But maybe there is a combination of factors. 

Hi Gustav,

Thank you for your support. I wanted to add some information to what we noticed surrounding this fault.

Am I wrong in stating that the "signal 6" comes down to the stopping of a process, either "drv_CanInt" or similar CAN driver?

I'm asking because this MD4 is the main controller for this system.

So this fault seems to have disturbed many other CAN communications when the MD4 froze,
to the point of requiring a hard reboot.

Sending more than 100% load on a CAN bus is an interesting test!
I'm wondering if this test could relate the hardware layer,
meaning that the rare occurence of a static discharge could overload the CAN bus?

I'm always worried with static discharge in general,
so any help to troubleshoot the cause is appreciated


Thank you Gustav for the interest. Our CAN channels don't go over 60% utilization in normal conditions. This issue never happened before even when the CAN channels were not optimized and the utilization was way higher than 60%. The element that ended up causing the error seems to be the unplugging but as you mentioned it might be a combination of factors since this type of unplugging happened before without any issues like this happening. 

As my colleague Christian suggests, could it be caused by static ?

Thanks again.