No sound in some loadings Ubuntu 16.04.1

[Zepem]

There is no sound in some times loadings running Ubuntu 16.04.1
This happens about once every 5-7 downloads.
The error began to appear after upgrading to Ubuntu 16.04.
Nothing helps to solve this problem only to reload.

---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: a 3183 F.... pulseaudio
 /dev/snd/pcmC0D0p: a 3183 F...m pulseaudio
 /dev/snd/controlC0: a 3183 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=04d3b0ff-501f-4bd2-b8af-c276353ceef5
InstallationDate: Installed on 2016-08-29 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lo no wireless extensions.

 enp3s0 no wireless extensions.
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: BIOSTAR Group H61MLV2
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=26897f5f-d47f-4819-8d05-98c10b9d3e17 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
RfKill:

Tags: xenial
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: None
dmi.board.name: H61MLV2
dmi.board.vendor: BIOSTAR Group
dmi.board.version: 6.0
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.chassis.version: 6.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0:
dmi.product.name: H61MLV2
dmi.product.version: 6.0
dmi.sys.vendor: BIOSTAR Group

[Zepem (zepem)]

I am add archive logfiles /var/log.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1618846

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[Zepem (zepem)]

apport information

[penalvch (penalvch)]

Pipec, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Zepem (zepem)]

Hello!
The first time this error occurred in April 2016 when I upgrated Ubuntu 14.04 to Ubuntu 16.04. Fix it, I could not. So I back on Ubuntu 14.04. In Ubuntu 14.04 everything was working correctly before August 30, 2016 until not updated Ubuntu 14.04. The error began to appear in Ubuntu 14.04.
Now this error began to appear in Ubuntu 14.04 and Ubuntu 16.04.
I installed Ubuntu 16.04 and requested for help on a forum http://forum.ubuntu.ru/index.php?topic=278602.0 And now appealed to you.
About core test. I think that all kernel starting with Ubuntu 16.04 have this error.

[Zepem (zepem)]

Hello!
The first time this error occurred in April 2016 when I upgrated Ubuntu 14.04 to Ubuntu 16.04. I can not fix it. So I back on Ubuntu 14.04. In Ubuntu 14.04 everything was working correctly before August 30, 2016 until I updated Ubuntu 14.04. The error began to appear in Ubuntu 14.04.
Now this error began to appear in Ubuntu 14.04 and Ubuntu 16.04.
I installed Ubuntu 16.04 and requested for help on a forum http://forum.ubuntu.ru/index.php?topic=278602.0 And now appealed to you.

About cores test. I think that all kernel starting with Ubuntu 16.04 have this error.

[Zepem (zepem)]

I think. Last linux cores without this error its 4.2* in Ubuntu 14.04.4.
Ubuntu 14.04.5 and Ubuntu 16.04 * already contain an error.
Thanks for the help.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Zepem (zepem)]

Added log file no_sound.log. In which lists all boots Ubuntu with sound and without sound. Logged about 2 months.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Zepem (zepem)]

Solved. The problem with the sound was due to mount partitions.

Not correct /etc/fstab
UUID=ffe4fa9a-66f5-4656-8850-e61ff57f3157 /media/DATA1 ext4 errors=remount-ro,nofail 0 2

Correct /etc/fstab
/dev/disk/by-uuid/ffe4fa9a-66f5-4656-8850-e61ff57f3157 /media/DATA1 auto nosuid,nodev,nofail,x-gvfs-show 0 0

Don't see how that affects. I changed 22 July 2017. Almost a month of no errors.
I think I have solved this problem.

[Zepem (zepem)]

The problem remained, but began to appear less frequently. See log

15-07-2017 22:16:14 - no sound
16-07-2017 16:45:50 - no sound
16-07-2017 17:17:12 - no sound
19-07-2017 11:47:23 - no sound
22-07-2017 22:00:45 - no sound
21-08-2017 11:12:47 - no sound
09-09-2017 11:12:38 - no sound
16-09-2017 17:25:26 - no sound
03-10-2017 14:20:34 - no sound