NUC 11 Extreme Kit - NUC11BTMi7 LAN error code 43

[PRyan4]

Is there an issue with the latest LAN driver 2.1.2.3, my adapter keeps dropping out with:

"windows has stopped this device because it has reported problems. (code 43)"

I only noticed this since updating to 2.1.2.3 driver?

[Win7ine]

This driver is some kind of a joke. Just as previous 2.1.2.2, it omits WOL and other related features.

Only driver that works so far with the least issues is: 1.1.3.34.

[Alberto_R_Intel]

PRyan, Thank you for posting in the Intel® Communities Support.

In reference to this scenario, in the following link, you will find troubleshooting steps to attempt in order to try to fix this problem:

https://www.intel.com/content/www/us/en/support/articles/000026225/intel-nuc/intel-nuc-kits.html

If the issue persists after that, please attach the SSU report so we can verify further details about the components in your platform, check all the options in the report including the one that says "3rd party software logs":

https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91600

https://www.intel.com/content/www/us/en/search.html?ws=idsa-suggested#q=nuc11btmi7&sort=relevancy&f:@tabfilter=[Downloads]

Any questions, please let me know.

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi Alberto,

the LAN is enabled in the bios because it has been working fine until updating to the latest LAN driver 2.1.2.3.

I checked the ethernet cable, and it is fine and is a cat 6.

I have the latest 64 bios, and all the latest drivers, as well as the chipset latest.

I'm running win 11 pro 64 and it is fully up to date.

I rolled back to 1.1.3.34, and it worked fine for hours.

Then I updated to latest 2.1.2.3 again, and randomly getting "windows has stopped this device because it has reported problems. (code 43)". It seems to happen either on startup, or returning from sleep.

I'm back on 1.1.3.34 for now.

If you want me to go ahead with the SSU report, would you like me to update again to 2.1.2.3 again, wait for error, then do report?

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for providing that information.

Regarding your question about the SSU document, yes, if you have the chance, please update the driver to version 2.1.2.3, just to confirm that the latest driver version is currently installed. Once we received the report, we will do further research on this matter.

Just to make sure, is there any particular task that you do on the Intel® NUC that causes the issue?
Please provide the steps that you follow before seeing the error message.

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi

I've put 2.1.2.3 back on, and I reset bios to defaults as a precautionary measure.

I'm just waiting for it to throw the error code again before I send in the SSU document.

Restarted, shutdown and slept PC a few times, and of cause it's been faultless so far. (did it half dozen times before I raised this thread).

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for providing that information.

Yes, we completely understand, computers are usually like that, and for that same reason sometimes it is very difficult to reproduce an issue from our side as well.

It is great to hear though that the problem is currently not happening, maybe it got fixed after reinstalling wireless driver version 2.1.2.3.

Take your time to provide the SSU report, the thread will remain open for as long as you need it. I will be doing a follow-up in a couple of days.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello PRyan4, I just wanted to check if the issue persists and if you need further assistance on this matter?

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi Albert

Been a few days now, and my PC has been used many times, shut down, re-started, slept etc, and the LAN error:

"windows has stopped this device because it has reported problems. (code 43)" hasn't returned.

I'm still on 2.1.2.3 driver version. Haven't changed anything except roll back to previous version and re-install latest version a couple of times. Oh and I reset bios to defaults as mentioned in an earlier post.

I suppose you could close this for now and I'll see how it goes. Thanks.

Paul.

[Alberto_R_Intel]

Hi PRyan4, You are very welcome, thank you very much for letting us those results.

 Perfect, excellent, we are glad to know that the problem with the LAN seems to be fixed and now the computer is working properly after reinstalling wireless driver version 2.1.2.3. and resetting the BIOS to default values.

Thank you also for sharing the solution on this thread, we are sure it will be very helpful and useful for all the peers looking at this conversation.

Any other inquiries, do not hesitate to contact us again.

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi

Unfortunately the Lan error code 43 returned this morning.

Device manager showed an exclamation and error code 43. Control panel didn't even show the adapter.

Unplugging and plugging in lan cable did nothing.

Check lan cable connections with cable tester, all is good and it runs at 1Gb normally.

Had to disable and re-enable the adapter to fix. This has happened at least half dozen times since upgrading to 2.1.2.3

I have attched the SSU log.

Also, something which I haven't mentioned before, my wired microsft mouse randomly starts up with no mouse pointer.

Rebooting PC doesn't fix, I have to physically unplug and re plug in mouse.

Tried different usb slots at back of the NUC, tried another brand new microsoft mouse and it still does it once in every few boot ups.

I even gave the mouse to my son who has the exact same beast NUC setup and it never faulted.

I also had a USB HDD which randomly disconnected in the same usb slots. (I thought the HDD was dying but now maybe not)

I got around the mouse no pointer issue by using a wireless mouse fore now. The mouse "no pointer" issue has happened at least a dozen times till I switched to wireless mouse.

A few weird random things happenning with this NUC.

I'm wondering if I have a faulty Compute element.

I have stripped down NUC a couple of times to re-seat cables, SSd's etc hoping for a fix.

Also running the latest Win 11 pro with all updates, and NUC has all the latest drivers bios.

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for your response.

We are sorry to hear the LAN issue came back on your Intel® NUC.

In that case, we will do further research on this matter to try to find a possible solution for this specific topic. As soon as I get any updates, I will post all the details on this thread.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello PRyan4, I just received an update on this matter.

After reviewing the case and as you mentioned, you could have a faulty unit, taking into consideration that your son has the same NUC model performing with no problems. 

Based on that, we just wanted to check if it is possible for you to test this known working NUC in the same network, and also to try swapping the drives to check the behavior of both NUCs?

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello PRyan4, I just wanted to check if you were able to test the known working NUC in the same network and swap the drives to check the behavior of both NUCs?

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi Albert

I am still testing the good NUC shell at my place and so far no issues with LAN error code or mouse pointer not showing.

He immediately noticed issues with my shell, the fans running louder then his and some coil whine coming from the power supply which is quite load. I couldn't notice it but I have industrial deafness.

I will test another week, and wait for more feedback from my son who is using my NUC shell at his home.

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for sharing those updates.

Perfect, it is great to hear that so far there are no issues with the LAN error code or mouse pointer.

No problem at all, go ahead and take your time to do the tests and once you get the chance, let us know the results.

Just in case, I will be doing a follow-up on this matter in a couple of days.

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi Alberto,

"windows has stopped this device because it has reported problems. (code 43)" came back after I woke the NUC from sleep.

So this error has appeared with both mine and the borrowed NUC shell.

I've installed 1.1.3.34 again and will see how it goes. This error code only appeared with version 2.1.2.3, whether a coincidence, dunno.

If it helps I'm running Lan Cat 6 cable into a TP-Link TL-SG116 (16 port gigabit switch), which is connected to a Netcomm NF18ACV modem.

The lan error has only happened when either returning from sleep, starting or restarting the PC. It has never happened when actively using the PC.

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for sharing those details.

We are sorry to hear there are still issues showing in reference to the LAN performance on the Intel® NUC.

It is very strange though that the problem never happened when actively using the Intel® NUC just when returning from sleep, starting or restarting the computer.

No problem at all, take your time and once you get the opportunity please let us know the results of installing version 1.1.3.34, so we can further assist you.

Regards,

Albert R.

Intel Customer Support Technician

[Alberto_R_Intel]

Hello PRyan4, I just wanted to check if there are any updates on testing driver version 1.1.3.34 and if you still need further assistance on this matter?

Regards,

Albert R.

Intel Customer Support Technician

[PRyan4]

Hi Albert

I have my original NUC back and have been running LAN driver version 1.1.3.34 for 7 days now and no errors so far.

I will stick with this version and see how it goes.

Paul

[Alberto_R_Intel]

Hi PRyan4, Thank you very much for sharing those updates.

Perfect, excellent, it is great to know that you got your original NUC back and also that it's been running LAN driver version 1.1.3.34 for 7 days with no issues.

It seems the problem got solved, still, I will do a follow-up on this case in a few days just to confirm those details.

Regards,

Albert R.

Intel Customer Support Technician