📝 Step 1: Power Off and Reboot Method (Solves 90% of Problems)
This is the absolute first choice for troubleshooting all software faults and the most direct way to distinguish between software and hardware issues.
Applicable Symptoms: Completely black screen with no display, inability to log in to the backend web interface, malfunctioning smart alarms, and incorrect screen time display.
Operation: In the control room or power distribution box, completely disconnect the power to the camera > wait for about ten seconds > reconnect the power.
Results:
✅ Fault disappeared: This indicates that it was just an intermittent program crash, and the problem has been resolved.
❌ Fault persists: This indicates that it's not a simple program crash; continue troubleshooting.
🔍 Step 2: Check Configuration (For parameter-related faults)
If the problem persists after restarting, or if the screen displays but functions incorrectly, log in to the backend to check the parameters.
IP address not found/Image missing: Log in to the backend NVR and check if the device IP in channel management has reverted to the factory default value, or if it conflicts with the IP of other equipment in the workshop.
Recording time changed to 1970: Go to "System Settings" in the backend and check if Time Synchronization (NTP) is enabled, or manually calibrate it.
Smart alarm not triggered: In the "Smart Analysis" interface, check if the rules are still in place and if the bitrate is H.264 (enabling H.265 on some older models can cause smart functions to fail). Try re-enabling the rules.
Step 3: Clear cache/Change browser (for backend login failures)
If the page keeps spinning after you enter the IP address, prompts an incorrect password (even though you haven't changed it), or the page layout is messed up, this is a typical case of browser cache conflicts with old files.
Operation: Clear all browser history and cache, then close and reopen the browser. Alternatively, try logging in on a different computer or with a different browser. This method is particularly effective for login problems after firmware upgrades.
Step 4: Check if the core program truly failed to load (for frequent crashes)
If the problem is resolved after restarting in step 1, but recurs after a few hours, it indicates a deep-seated bug in the underlying firmware.
Advanced Troubleshooting: Try manually reloading the smart algorithm package in the background "Maintenance" interface. If the device repeatedly crashes when a certain smart function (such as a warning line) is enabled, try disabling that function and observe if the problem stabilizes. This can help you quickly determine if the crash is caused by algorithm incompatibility.
🚀 Step 5: Ultimate Solution-Upgrade Firmware (for deep-seated bugs)
If you have tried the above four steps and the device still crashes, restarts, or malfunctions repeatedly, then this is a typical "firmware defect."
Action: Download the latest firmware for your model from the official website and upgrade from the secure area. New firmware usually fixes various logical vulnerabilities in the old version.
