Hikvision cameras rebooting frequently - Data Overtime -- No stream for 20s

S

s1977

n3wb
Mar 17, 2025
5
0
UK
Hi All

I am looking for some knowledge or experience anyone has with the below errors. Basically 3 of my Hikvision DS-2CD2386G2-IU cameras are rebooting intermittently. They are updated to the latest V5.7.19 build 241207 version. They are setup on a Hikvision DS-7716NXI-I4/16P/S NVR, which also has other similar and other model cameras working smoothly without any issues. I have tried to search for this error online too, but not much information can be found.

I wanted to see if anyone has encountered/experienced in fixing this issue. I have attached the output here from the NVR log extract if that helps. Given other similar cameras have been working, i tried to export/import config data, but that hasn't worked and neither has re-flashing or physically resetting it. Changing the POE ports has also not helped, for I assumed that power could've been the issue. Any thoughts?

Code: 
----------------------------
299   2025-3-17 14:31:3
----------------------------
Major Type: Information
Minor Type: Stop Recording
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: D8
 
Camera: D8 stops recording. Record status: 
Record enabled: No
Event parameters: Disabled
Record type: Continuous
Stream type: Main Stream
Motion detected on camera: None
Alarm detected on camera: None
Amount of relate log: 0.
 
 
----------------------------
300   2025-3-17 14:31:3
----------------------------
Major Type: Information
Minor Type: Stop Capture
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: D8
 
Camera: D8 stops capturing. Capture status: 
Capture Enabled: No
Event parameters: Disabled
Capture type: Command Triggered
Motion detected on camera: None
Alarm detected on camera: None
Amount of relate log: 0.
 
 
----------------------------
301   2025-3-17 14:31:6
----------------------------
Major Type: Information
Minor Type: System Running Status
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: D8
 
Camera No.: D8
Stream type: Sub-Stream
Offline time: 25 seconds
Extra information: Connect error -- connect server err
 
 
----------------------------
302   2025-3-17 14:31:7
----------------------------
Major Type: Information
Minor Type: System Running Status
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: D8
 
Camera No.: D8
Stream type: Main Stream
Offline time: 24 seconds
Extra information: Connect error -- connect server err
 
 
----------------------------
303   2025-3-17 14:31:13
----------------------------
Major Type: Exception
Minor Type: IP Camera Disconnected
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: D8
 
Camera No.: D8
IP address: 192.168.100.9
Domain name: 
Protocol: HIKVISION
Management port: 8000
Channel port: 1
Transfer Protocol: Auto
Extra information: Data Overtime -- No stream for 20s
Channel name before offline: Camera 01
 
 
----------------------------
304   2025-3-17 14:31:19
----------------------------
Major Type: Information
Minor Type: IP Camera Connection Status
Local User: N/A
Host IP Address: N/A
Parameter Type: N/A
Camera No.: N/A
 
Camera No.: 8
Camera Status: Unreachable
 
Hi All

I managed to connect via a serial TTL connection yesterday and the messages before the reboot are as below. It looks like some partition corruption but this is not my area, so checking here. When I purchased these cameras, they had a DS-2CD2386G2-IU firmware (5.5.800_210628), but on checking the Hikvision Tools, where I can submit a serial no, it indicated that I needed to update the DS-2CD2386G2-IU(C) firmware (V5.7.19 build 241207). I installed the same and it works on all bar the 3 that are having these issues. Yesterday I also tried to check that theory and the messages after the firmware download from the TFTP server indicated a message stating "The platform is mismatch" and the update failed. So I think they are on the correct firmware now. For clarity, the issue was even with the old firmware.

My assumption is that one or more of the partitions may have either incorrect remnants from previous upgrades or something else. Would anyone be able to advise looking at the below? I have tried to check but is there a way to extract a firmware or config 9=(if that is indeed the issue) from the good cameras and onto these ones? Or alternatively if there is a way to reset the device fully so any such partitions are restored to factory, then I am happy to do so.

Code: 
Mar 17 16:56:53 bsp.warn kernel: [  410.599615] ERR:nvtmpp_vb_chk_blk_valid() blk corruption => blk_head_va=0x4090afc0 != blk=0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.599623] ERR:nvtmpp_vb_get_free_block_from_pool() Invalid blk = 0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.623966] ERR:ife_isr() IFE frame error!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.624208] ERR:ife_isr() IFE Buffer overflow!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.639556] ERR:nvtmpp_vb_chk_blk_valid() blk corruption => blk_head_va=0x4090afc0 != blk=0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.639565] ERR:nvtmpp_vb_get_free_block_from_pool() Invalid blk = 0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.663912] ERR:ife_isr() IFE frame error!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.664151] ERR:ife_isr() IFE Buffer overflow!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.679501] ERR:nvtmpp_vb_chk_blk_valid() blk corruption => blk_head_va=0x4090afc0 != blk=0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.679510] ERR:nvtmpp_vb_get_free_block_from_pool() Invalid blk = 0xa190afc0^M
Mar 17 16:56:53 bsp.warn kernel: [  410.703844] ERR:ife_isr() IFE frame error!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.704094] ERR:ife_isr() IFE Buffer overflow!^M
Mar 17 16:56:53 bsp.warn kernel: [  410.719446] ERR:nvtmpp_vb_chk_blk_valid() blk corruption => blk_head_va=0x
 
This is from the firmware update via TFTP. It does show the image updated and flashing successful.

Code: 
HKVS # update
Load kernel to 0xc700000 ...
<sbal_wb_aes_update>...decrypt
<sbal_wb_aes_update>...decrypt
<sbal_seboot>body_total_len=6518112
<sbal_seboot>verify success ##successful to load enc_uImage##
gzip_image_size  637548  image_size   c408a4
nvt_ker_img_ungzip_linux: gz_uncompress linux
nvt_ker_img_ungzip_linux: generating uImage header for linux
CHIP_1.
boot of image at addr 0x0C700000 ...
## Booting kernel from Legacy Image at 0c720000 ...
   Image Name:   
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    12847268 Bytes = 12.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
## Flattened Device Tree blob at 0c700000
   Booting using the fdt blob at 0xc700000
   Loading Kernel Image
   Loading Device Tree to 087dd000, end 087fffff ... OK

Starting kernel ...

l2cache:0
Disable MMU
Clear MMU
Uboot L2 cache aux val: 0x72420000
Uboot L2 cache prefetch ctrl val: 0x70000000
Uboot L2 cache ctrl val: 0x00000000
Done
SW2
Starting udev:      [ OK ]
create static device nodes under /dev dir
SYS_NOBACKUP:1
BLD_VER:1300746
Set output direction of gpio[109],value:1
done
SYS_NOBACKUP1
SYS_NOBACKUP_test
prepare_partition.sh SYS_NOBACKUP:1!
the device nobackup, don't mount app_sec!
the device nobackup, don't mount config_sec!
================================================
= !!  the  minisys  is  used  for  [ ipc ]  !! =
================================================
[ INFO][MIN]TFTP: TFTP from server 192.168.1.128
tftp: server error: (1) File not found

digicap.dav            0% |                               |   312k  0:03:57 ETA
digicap.dav            8% |**                             |  6424k  0:00:21 ETA
digicap.dav           17% |*****                          | 12736k  0:00:14 ETA
digicap.dav           25% |*******                        | 18968k  0:00:11 ETA
digicap.dav           33% |**********                     | 25256k  0:00:09 ETA
digicap.dav           42% |*************                  | 31488k  0:00:08 ETA
digicap.dav           51% |***************                | 38240k  0:00:06 ETA
digicap.dav           60% |******************             | 44904k  0:00:05 ETA
digicap.dav           69% |*********************          | 51576k  0:00:03 ETA
digicap.dav           78% |************************       | 58232k  0:00:02 ETA
digicap.dav           86% |**************************     | 64656k  0:00:01 ETA
digicap.dav           95% |*****************************  | 70792k  0:00:00 ETA
digicap.dav          100% |*******************************| 74360k  0:00:00 ETA
digicap.dav          100% |*******************************| 74360k  0:00:00 ETA

[ INFO][MIN]TFTP: Download File [OK]
[ INFO][MIN]BURN: ### chip_map = 1, chip_id = 1 ###
[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][261]:###### unpack source[0] bPackVerFlg=0x00,bPackDevFlg=2400050041111110011,iFirmMapFlg=0x00000001,iFirmKeyFlg=0x00f00000
[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][263]:###### unpack source[0] iFirmOffset=0x0000006c,iFileLength=0x0489dfff,iCheckSumU8=0x439ee147
[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][291]:###pack[0] iFirmFlg=0x00f00000,iPlatform=240,iDevMajor=111,iDevMinor=111,iLanguage=1
[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[0] szFileName=_cfgUpgClass,iFirmOffset=0x00002400,iFileLength=0x00000740,iCheckSumU8=0x39584566
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[1] szFileName=cfgExtendClass,iFirmOffset=0x00002b40,iFileLength=0x000000d0,iCheckSumU8=0xb99a766d
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[2] szFileName=Onion-OS,iFirmOffset=0x00002c10,iFileLength=0x00040478,iCheckSumU8=0x0175570b
###SHA_hash_initSHA_512!!!!
...[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[3] szFileName=G5_model.bin,iFirmOffset=0x00043088,iFileLength=0x00000004,iCheckSumU8=0x278081f3
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[4] szFileName=mdk_cfg.tgz,iFirmOffset=0x0004308c,iFileLength=0x00000004,iCheckSumU8=0x278081f3
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[5] szFileName=audio_254.wav,iFirmOffset=0x00043090,iFileLength=0x00000004,iCheckSumU8=0x278081f3
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[6] szFileName=app.tar.gz,iFirmOffset=0x00043094,iFileLength=0x00c07de2,iCheckSumU8=0x3e10560a
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[7] szFileName=uImage,iFirmOffset=0x00c4ae76,iFileLength=0x00720d40,iCheckSumU8=0x7d79417f
###SHA_hash_initSHA_512!!!!
..........................................................[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[8] szFileName=heop.tgz,iFirmOffset=0x0136bbb6,iFileLength=0x0045f296,iCheckSumU8=0xe2bae840
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[9] szFileName=g5_modules.tgz,iFirmOffset=0x017cae4c,iFileLength=0x0035576b,iCheckSumU8=0x26e18c45
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[10] szFileName=dsp_extres.tgz,iFirmOffset=0x01b205b7,iFileLength=0x002c2d43,iCheckSumU8=0x2248b5e3
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[11] szFileName=mpp_modules.tgz,iFirmOffset=0x01de32fa,iFileLength=0x00228deb,iCheckSumU8=0xe7e0ebf8
###SHA_hash_initSHA_512!!!!
Set output direction of gpio[109],value:0
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[12] szFileName=libhal_bsp.so,iFirmOffset=0x0200c0e5,iFileLength=0x000e4e30,iCheckSumU8=0x1feb8c81
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[13] szFileName=dsp_capability.tar.lzma,iFirmOffset=0x020f0f15,iFileLength=0x0002304d,iCheckSumU8=0xa4eea13d
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[14] szFileName=hw_resources,iFirmOffset=0x02113f62,iFileLength=0x0000b373,iCheckSumU8=0x2bd2ba01
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[15] szFileName=media_capability.tar.lzma,iFirmOffset=0x0211f2d5,iFileLength=0x000048b2,iCheckSumU8=0x3a6a7d90
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[16] szFileName=initrun.sh,iFirmOffset=0x02123b87,iFileLength=0x00002ea2,iCheckSumU8=0x92de909f
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[17] szFileName=solib.tar.gz,iFirmOffset=0x02126a29,iFileLength=0x0000230a,iCheckSumU8=0xb8f4d2d1
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[18] szFileName=light_resources,iFirmOffset=0x02128d33,iFileLength=0x000021e7,iCheckSumU8=0x7cc5d89c
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[19] szFileName=sensor_resources,iFirmOffset=0x0212af1a,iFileLength=0x000013f8,iCheckSumU8=0x76df7e17
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[20] szFileName=dsp_exres_uncompress.sh,iFirmOffset=0x0212c312,iFileLength=0x00001256,iCheckSumU8=0x19c0837b
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[21] szFileName=cap.json,iFirmOffset=0x0212d568,iFileLength=0x00000799,iCheckSumU8=0x12739d8e
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[22] szFileName=media_capability_uncompress.sh,iFirmOffset=0x0212dd01,iFileLength=0x00000600,iCheckSumU8=0x5eba4675
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[23] szFileName=icr_resources,iFirmOffset=0x0212e301,iFileLength=0x0000022a,iCheckSumU8=0xd3d1dee1
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[24] szFileName=media_init.sh,iFirmOffset=0x0212e52b,iFileLength=0x00000196,iCheckSumU8=0x079e7fef
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[25] szFileName=webLib.img,iFirmOffset=0x0212e6c1,iFileLength=0x00ec5000,iCheckSumU8=0x67a087b5
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[26] szFileName=model_facesnap_1.bin,iFirmOffset=0x02ff36c1,iFileLength=0x0034f234,iCheckSumU8=0x15591a43
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[27] szFileName=model_facesnap_2.bin,iFirmOffset=0x033428f5,iFileLength=0x0013e9f0,iCheckSumU8=0x789022ef
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[28] szFileName=model_facesnap_3.bin,iFirmOffset=0x034812e5,iFileLength=0x00101130,iCheckSumU8=0xbcd8437c
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[29] szFileName=model_facesnap_4.bin,iFirmOffset=0x03582415,iFileLength=0x0021c7d0,iCheckSumU8=0xacf5bb0a
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[30] szFileName=model_smart_1.bin,iFirmOffset=0x0379ebe5,iFileLength=0x0024fcde,iCheckSumU8=0x2b00d0e6
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_ERRO][src/firm_unpack_lib.c][firm_pack_decode][402]:###file[31] szFileName=model_smart_2.bin,iFirmOffset=0x039ee8c3,iFileLength=0x00eaf73c,iCheckSumU8=0xf707af98
###SHA_hash_initSHA_512!!!!
.[PACK][DBG_HINT][src/firm_unpack_lib.c][firm_pack_decode][340]:###pack num=1,decode succ=1,permit denied=0
[BSP MCU] digicap.dav update over, waiting mcu update ......

[ INFO][MIN]BURN: Write Flash [OK]
***** UPDATE COMPLETE *****


The system is going down NOW!

Sent SIGTERM to all processes

Sent SIGKILL to all processes

Requesting system reboot
 
Can't answer your question, but I've had nothing but problems since swapping out a pair of 2347G2's for a pair of 2387G2's. The 2387's will not, no matter what, trigger for intrusion detection. Line crossing works fine. Then the settings on the 2387's will randomly vanish - intrusion/line crossing markers, min/max box, encoding, frame rate, etc. I'm a pretty good hobby level tinkerer, so I know what I'm doing. It's not anything I've done, it's the cameras being assholes. Rebooting, resetting, firmware upgrades and downgrades did nothing.

Two days ago I took down the 2387's and put back the 2347's and they're working perfectly. I have heard from others - although not frequently - that the 238XG2's are very problematic. I know you have 2386's, but maybe a similar problem?
 
Thank you @fullboogie and @trempa92 for your responses. In my case I have multiple models connected to my NVR, some of which are 2386G2s, 2385G1s & 2347G1-LUs. Confusing thing is that whilst the 2385G1s & 2347G1-LUs are all working without any issues, it's not that the 2386G2s are all faulty. Indeed some of them are running properly without any issue, except for some. So it's very odd what has happened with these and their history of updates that I am not aware of.

Above was my take on the errors logged but I am happy to upload a full run log in case the error/issue is flagged further up in the chain. Also as I mentioned, I have atleast one 2368G2 camera that runs flawlessly on the same firmware. If extracting config/segments to replicate to other cameras may work, then I am happy to do so, just don't know what to copy where and how.at
 
Seems there is little knowledge of the issue I am facing. However does anyone know if I could do any further investigation/address issues if I have root access? I have root access.
 
You must log in or register to reply here.
Top Bottom