These days for 2 times I had strange problems, the first time I had left the pc with Amule started, but at one point the ntfs partition on which Amule's Incoming and Temp folders became inaccessible by the dolphin, I do not know why , Today I also had Opera and Amule started at some point I have connection problems then oPera does not turn off and it seems to be freeze, Ksysguard does not start but goes in freeze, htop the same thing, yakuake works and launch from there htop, i only see Flat memory and a lot of started work processes, so I generated the error log, and there are a lot of strange UFW Block messages that I do not know what they are, let me leave the log.txt if you have any ideas or suggestions
https://drive.google.com/file/d/0B7STSfjr_a4mY2toZlhOcWNwMTg/view?usp=sharing

Check for bad sectors, to use NTFS in Linux is not a good idea at all.

Thanks for the moment I've resolved disabling baloo and UFW, thanks to Crazy help on IRC

Though the topic is marked as solved i just want to mention that the next time you want to share a output or log, you better make use of the pastebin services that are mention in the Docs instead of using Google Drive....
https://kaosx.us/docs/

Pastebin did not work because the log was too long, otherwise as it does, but thank you for the suggestion😉
However even after disabling Baloo for the NTFS disk and also UFW in general, with Amule (Folders always shared in NTFS, I know I had to change: P) the issue of non-reading of the ntfs disk has reappeared

cd /run/media/lazy/589D19C3740C07E6
^@ lazy î‚° ~ î‚°  cd /run/media/lazy/589D19C3740C07E6
bash: cd: /run/media/lazy/589D19C3740C07E6: Il socket di destinazione non è connesso
 lazy î‚° ~ î‚° 

Obviously, if you reboot, it resolves

sudo blkid
Password: 
/dev/sda1: LABEL="Ripristino" UUID="3C785DB8785D721E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="523031bb-acb5-4c80-9869-8536e8b7346b"
/dev/sda2: UUID="445F-CA0C" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="0cfbdc67-b43b-4885-bf8b-15444d5f57b7"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="ff8c609c-ab3c-4553-b0e3-c9dd020adf34"
/dev/sda4: UUID="560617F50617D4B9" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5a26baf0-6c4d-41eb-8683-66bde37399f7"
/dev/sda5: UUID="E6D4974ED4971FBB" TYPE="ntfs" PARTUUID="31352532-9b86-4045-a649-40c61613a2a6"
/dev/sda6: UUID="589D19C3740C07E6" TYPE="ntfs" PARTUUID="a0ee21ed-522f-49fa-adc4-23f06573552c"
/dev/sda7: UUID="e75aff3b-b512-4e92-82ba-08120d32c018" TYPE="ext4" PARTUUID="42fcaf8f-2bb0-4926-bf03-dfcc6542305c"
/dev/sda8: UUID="d515ab9f-32bf-49a9-b062-7f9a298c2cce" TYPE="swap" PARTUUID="5466d8e4-effa-4b78-9fc7-251391b84f55"
/dev/sdb1: UUID="5f895acf-58fe-432e-ac2e-a748498b492b" TYPE="ext4" PARTUUID="0fb044f4-b3f0-41a2-9190-b378de6e815d"
 lazy î‚° ~ î‚° 

sudo fdisk -l
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 89990702-101F-4BB5-B774-B60CB7294A39

Dispositivo      Start       Fine    Settori   Size Tipo
/dev/sda1         2048     923647     921600   450M Windows recovery environment
/dev/sda2       923648    1128447     204800   100M EFI System
/dev/sda3      1128448    1161215      32768    16M Microsoft reserved
/dev/sda4      1161216  414140415  412979200 196,9G Microsoft basic data
/dev/sda5    414140416  415062015     921600   450M Windows recovery environment
/dev/sda6    415062016 1439678463 1024616448 488,6G Microsoft basic data
/dev/sda7   1439678464 1945303039  505624576 241,1G Linux filesystem
/dev/sda8   1945303040 1953523711    8220672   3,9G Linux swap


Disk /dev/sdb: 29,8 GiB, 32017047552 bytes, 62533296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5E61D351-BA84-4CED-8DF3-48E685CEB654

Dispositivo Start     Fine  Settori  Size Tipo
/dev/sdb1    2048 62531583 62529536 29,8G Linux filesystem


 lazy î‚° ~ î‚° 

-- Logs begin at Wed 2017-04-26 23:29:31 CEST, end at Fri 2017-08-04 14:21:10 CEST. --
ago 04 07:45:52 lazy-pc kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
ago 04 07:45:52 lazy-pc kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff99ac952bc510), AE_NOT_FOUND (20170303/psparse-543)
ago 04 07:45:52 lazy-pc kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170303/psargs-364)
ago 04 07:45:52 lazy-pc kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff99ac952bc510), AE_NOT_FOUND (20170303/psparse-543)
ago 04 07:45:53 lazy-pc kernel: kvm: disabled by bios
ago 04 07:45:53 lazy-pc kernel: kvm: disabled by bios
ago 04 07:45:53 lazy-pc kernel: kvm: disabled by bios
ago 04 07:45:57 lazy-pc ntpd[473]: bind(23) AF_INET6 fe80::25fe:53b0:d0b9:62f2%2#123 flags 0x11 failed: Cannot assign requested address
ago 04 07:45:57 lazy-pc ntpd[473]: unable to create socket on enp3s0 (4) for fe80::25fe:53b0:d0b9:62f2%2#123
ago 04 07:46:34 lazy-pc pulseaudio[2026]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the 
ago 04 12:33:33 lazy-pc kernel: kernel BUG at ./include/linux/highmem.h:196!
ago 04 12:33:33 lazy-pc kernel: RIP: get_page_from_freelist+0x313/0xb80 RSP: ffffbd4383b539c8
ago 04 12:39:59 lazy-pc systemd-coredump[3892]: Process 2883 (amule) of user 1000 dumped core.
lines 1-14/14 (END)