I understand the confusion and thank you for your meaningful discourse on this subject.
Not searching applies to questions with definite answers a lot more than problems. That is not to say you should not search for your problem, but that if there isn't a 100% correlation, and/or the thread has gone stagnant, we will not fault you for creating a thread. I may be out of line here, but I don't think we have ever seen D-Link comment that we have too many similar threads.
Yes, I am a D-Link employee. Anyone who had a badge below their name with a title like "Tech Engineer" is D-Link staff. I was also slightly ahead of myself to classify this thread as meaningless (this diversion is proof of that), I do however feel that the comments I made as to why the thread is helping no one were just. I wholeheartedly believe you would receive a whole lot more relevant attention from myself and others if you started a thread relevant to just your issue.
To address the apparent lack of D-Link involvement I am going to try to explain the D-Link approach to these forums. This is a place where the community can come together to help each other and discuss their particular issues. The D-Link staff are here as moderators, we are not expected, nor could we treat every thread like it was a tech support call. We do help when and where we can, but our expectation is that this will eventually become a place where customers can help each other, as well as a cornucopia of knowledge. At no point should any thread have the expectation of D-Link involvement.
As for your code 10, it has been a long time since I have worked with adapter cards (hence why I mod the business class product boards). But as I recall it can be either a driver or a hardware issue, with a strong preference twords being a hardware issue. Tech Support should be able to bring this to resolution in short order.