\ DOCS \ Debugging

This page contains information about what to do in case of any problems. Following guide will tell you what to do if any problem appears. It will help you to analyze the problem and find a solution by yourselves or with our help. Off course, any cooperation with us could make the program much better and even more stable. Thanks.

In case of general problem you can consult our user documentation or faqs.

Contact email

In case of any problem, you can contact us here:

  • Please add description of what you exactly did and what exactly happened. For example: "When I set OUTGOING limit for Firefox to 100kB/s then my computer explodes and i have to buy a new-one."
  • Let us know about your system. Which version of Windows have you been using an optionally which other networking/security software have you been using?
  • Include all important attachements (event log, memory dump, message provided by the application etc.). If they are big, please compress them using any widely spread archiver (zip, rar etc.).

Event Viewer

In case something goes wrong, NetLimiter stores information about the event into System Event Log. From the command-line execute command eventvwr which opens system tool named Event Viewer. In Event Viewer, open folder named Applications and Services Logs and there you can find log file named NetLimiter. If you can find any information which seems to be important, save the log to a file and send it to us via email.

Some events could also be stored under Windows Logs \ Application or Windows Logs \ System. If you can find something important there, send the log to us as well.

The Event Log could be saved by right clicking it's name in Event Viewer and then choosing Save all events as from the context menu. Choose .evtx as the event log file format.

Failed Installation

If the installation process fails then the only way to debug it is to start it with logging ON. All you have to do is run the installer with command line netlimiter- /l*v "nl-inst-log.txt" which will generate nl-inst-log.txt log file. Please, send it to us.

More information about installation can be found here.

Crashed Client Application

Client program has several build-in debugging features which should help you to gather detailed information about the problem. In case of crash (unhandled exception) you should get some info about it. Please, copy this info and send it to us.

If you don't get any info from the application directly, then please use Event Viewer as described above.

Problems with Service

The most usual problem is that Service will fail to start and run. It will be indicated in NetLimiter Client as it won't be able to connect to Service.

Please check Event Viewer as described above.

BSOD (A system crash)

If this wretched thing happens repeatedly then the best way to help us is to send send so-called memory dump - a copy of your memory saved to a file by system after the BSOD. All Windows by default generate only small memory dumps, but is usually not much of a use (it does not contains enough details) and we prefer to investigate a kernel memory dump file.

Please, use this official guide to make it enabled or at least check if it is already enabled. The kernel memory dump file is by default located in Windows directory (usually at C:\Windows) and it is named as memory.dmp. Please, send us this file (compressed) with simple description. We prefer that you send it using any web file sharing provider like OneDrive or DropBox.


Yours Locktime Software