Nport Windows Driver Manager

[Elgin Carmona]

NPortWindows Driver Manager provides you the easiest way to add COM ports to access your devices. You need to configure the operation mode of NPort serial port to "Drvier/Real COM" mode first. The driver manager will send the broadcast packet to seach NPort servers on LAN and list out the result. The checkboxes on the left means the server which you want the newly added COM ports to map.

We needed to move one of our clients to a virtual enviroment after there GeoSCADA server failed, the original server connected to a Trio MR450 radio and Serial SMS modem. To interface to the serial devices now we have installed Moxa NPORT 5210 serial to ethernet devices and am using the REALCOM functionality on the server.

However from GeoSCADA we almost get an immediate error that indicates channel failed, no Write in Progress. In the logs is returned as 0x40000011. This happens with all serial channels and almost happens immediately.

The Geo SCADA drivers use Windows overlapped I/O for asynchronous reads/writes to serial ports. The "No write in progress" errors means that the serial port device driver (Real COM) has signalled an asynchronous write has completed but no write is currently in progress, so this is unexpected.

We've seen this same issue with Comtrol RocketPort and DeviceMaster serial ports. In this case the device driver signals each asynchronous write has completed twice - this is not standard behaviour for a serial port driver. Comtrol have a setting called 'Wait on physical transmission before completing write' which disables this non-standard behaviour. It might be worth asking Moxa if they have a similar feature in their Real COM device drivers.

Thank you so much for your answer, it was indeed a driver issue. Moxa has two types of drivers it seems that one is driven through their Administrative suite software the other is Windows Drivers Manager. We only had the Administrative Suite installed and not the Windows Drivers Manager. We only had the the first mentioned installed, installing the second piece of software allowed the drivers to show up in the OS device manager and immediately everything started working.

You need to go to Program Files, under the moxa folder. There should be an application called Npcom, you need to open that and under advanced settings update it as shown in the picture below. This worked for me hope it helps you as well.

The COM port numbers always seem to be taken up by something and although right now I only have 4 serial ports (3 over Bluetooth and one USB to RS-232), I have numerous COM ports set as in use. I'd like to clean that list up a bit.

Also it seems to me that from time to time, one of the taken COM ports gets freed up and then one of the devices I use will take that number creating confusion, since I'll have to go and hunt its com number in device manager.

Thanks for all the advice above. I wrote software to automatically clean up the Registry but though it did adjust the Hardware, Software, and Arbiter sections it did NOT remove the phantom COM port entries. Even a reboot with the "USB to 2Serial Port" device removed did not clean up the system properly.

And a right click on Computer / Properties / Device Manager / Ports shows only COM1. Right click on COM1 / Properties / Port Settings / Advanced shows COM1 with COM2 "in use" and COM3 "in use". All the other settings up to 7 that used to be "in use" are now freed up. So only the "Arbiter" setting seems to be telling the Win7 system what is really "in use". The Computer Management system has cleaned up the Arbiter, but not cleaned up the Software section...

If the computer reports that the driver package is in use by a currently installed device, then you must either uninstall the device first, or use the -f on the pnputil command to force deletion of the package.

If you do all that before loading the correct driver package and try to keep the Com device inserted in the same port rather than moving it around your ports you will have fewer problems with the Prolific driver.

Just load it up, click on "Display Mode", "Show only hidden/detached devices", Check "Ports" (which selects all the unused com ports), then click "Remove all checked", and confirm the removal when the warning appears.

I've recently (Jan 2021) updated my platform from an lga1155 to a AM4 system, and I'm running into display driver/dwm crashes which freeze what's on the screen but keep the PC running.

I can hear videos/games/chat continue, and I can manipulate them. I just can't see anything.

To gain full control back I have to turn it off with the PSU switch as just smothering the power button causes it to crash at the windows loading icon, the little pale blue one, but the system continues to boot to desktop behind a frozen screen.

Attached files:

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER91CB.tmp.dmp

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER922A.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER923B.tmp.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9245.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9255.tmp.txt

I cannot figure this out. I've rolled back drivers, uninstalled all I can and reinstalled them. Tried 3 different (current, last and a few versions back) Nvidia drivers using DDU each time.

I've run sfc/scannow and a few other commands to wipe and repair Windows update and check that all the Windows files are fine, they all report that everything is fine, or that they corrected something and when run a second or third time come up clean.

I've booted to safe mode a few times, not spent much longer than a few minutes there so I can't really tell if it happens in that environment.

I've rebuilt my W10 install USB stick with an updated version from the Windows support page and run Windows start up repair.

I've tested the RAM, using windows memory tester and also using 1 stick, 2 sticks in each socket

I've reseated the CPU, and also replaced the CPU with a new one

I've reseated the GPU a few times as it's a recently new build and I had to go back to my old one for a few days during a return window(old pc runs fine, no issues)

I've reseated all cables at both ends

I've remounted the motherboard to make sure nothing was touching underneath

Basically I've taken it all apart twice and put it back together.

I've use the DP to HDMI cables between 2 machines no issues

All hard drives have been used across both machines, no issues

I've faffed about uninstalling a much fluff drivers/software as I can. So many RGB things these days

I check temperatures and make sure they don't get too high. A bit much actually, I hate how spiky the ryzen chips are.

I've checked power draw for cpu and gpu, they seem alright.

I've mined some crypto fine, bit warm but fine.*

I can play games, watch videos, browse the web no issues*

I want to point a finger at the 20H2 update but I've no grounds to base that on.

I found a folder, C:\ProgramData\Microsoft\Windows\WER\ReportArchive, that has loads of AppCrash_dwm.exe folders, I assume logs? I can't view them as I don't have nor can I gain permission. Odd that.

I reinstalled windows the day after I finished putting this machine together, I think to fix this same issue, but obviously it didn't work and like I said, I put together a newer W10 install usb stick. It's the last thing I want to do but I'm willing to reinstall again. It's just a bit of a let down doing all that for the same issue to raise it's head again.

Been having the same problem myself, machine is only about 6 months old graphics card is less than a month. It also happened with the card that I had previously as well. Sometimes its right away sometimes its after an hour or two gaming, sometimes idling or browsing, i have tried nearly everything in the op and a scatter of other posts. it seems like this problem has been occuring for years atp and i havent seen any solid solutions only what seems like select situations. wondering if i missed something it has been a few months any answer or solution on this yet?

Windows 10 home CPU i9-10900K GPU geforce 3070ti two monitors 165hz

Same issue for me with AMD and RTX3060. Running Windows 10. Just tried the various fixes other than cable replacement. PC is about 8 months old and started doing this 3 months ago. Fan on CPU runs extremely high when this happens.

I built my machine back in August 2018 and only recently I started to have this problem.

The first time was on 2022-09-28.

I have the machine, as it is, since August 2018, and it has been extremely reliable.

I also have done everything one could think of to debug the problem.

The freeze ALWAYS occurred on Firefox 105.0.x.

I play games, some of them very demanding, lice DCS World for example, and the machine behaves beautifully.

The problem doesn't occur systematically, but it occurs only in Firefox.

Yesterday I closed DCS after a night flying and almost immediately opened Firefox. It took less than 1 minute for the freeze to occur.

I upgraded Firefox to version 105.0.1 on 2022-09-24 and the first time the freeze occurred was on 2022-09-28.

My best idea is that it is related to power management on the card, so I went to the NVidia Control Panel --> Manage 3D settings and noticed that Firefox was the only application with "Power management mode" set to "Adaptative", so I changed it to "Use global setting (Optimal power)".

The machine worked fine for a whole day, and I was starting to think I had solved the problem, but a few minutes ago it happened again.

Microsoft/NVidia; please, take your hands from under your ass and solve this problem.

3a8082e126