Freeze due to spoolsv.exe

Hi All, I am here for two reasons:
Firstly, to tell everyone that my Firefox is freezing due to some issue with spoolsv.exe and when I reset spoolsv.exe (from command prompt: "net stop spooler" - then "net start spooler") all is OK again; in the hope this will help someone else as "Freezing" appears to be an issue with a lot of people...
Secondly, does anyone know what this issue is and how to solve this?
Some months ago I loaded the wrong printer driver into my computer and spoolsv.exe became unstable. I cleared all printer drivers, replaced the spoolsc.exe file from a backup and deleted the appropriate keys in the registry. This mostly solved the issue. Every once in about a fortnight, spoolsv.exe crashes out with an error but re-starts with no issues. So I know there is something glitchy about but this doesn't cause issue with other programs.
I am running Windowes XP sp3 with the latest Firefox and updates.
Thanks.
Firefox 18
* Next Generation Java Plug-in 10.13.2 for Mozilla browsers
* NPRuntime Script Plug-in Library for Java(TM) Deploy
* Foxit Reader Plug-In For Firefox and Netscape
* Shockwave Flash 11.5 r502
* VLC media player Web Plugin 2.0.2
* Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
* DRM Netscape Network Object
* Npdsplay dll
* DRM Store Netscape Plugin

Thank you for the reply Iamjayakumars,
Unfortunately I have tried the process suggested in the link before posting this request and went the extra step of clearing the registry keys as I described.
This issue only manifests with firefox. Is there any other information I can give to helps solve this issue?
Thank you.

Similar Messages

Laptop Toshiba P50-A-K9M often freezes due to unknown reason

Hi,
My Toshiba P50-A-K9M constantly freezes due to unknown reason. My OS is Windows 7 64-bit.
Initially I thought that it was due to overheating. However, when I enabled CPU temperature monitor I noticed that freezes happen even if the temperature is relatively low (39%).
My second guess was about memory. But Windows memory diagnostics passed without any problems.
I can't confirm it but I've a feeling that it happens on CPU intensive tasks but it's not linked to particular program.
I had freezes while compiling an Android application, other times it was during browsing in Google Chrome... I even had a freeze when only File Explorer and Image VIewer were running in foreground.
Could you help me with this problem?
Thanks,
Leonid

Try removing one of your memory sticks and run it that way. Try one at a time and in different memory slots to fully test your memory.
Run a boot time virus scan
Run a full disk check to test the hard drive.
S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!****

Memory Leak on SpoolSv.exe

Hi
I have a Windows 7 x64 (Ultimate) running on my laptop. Weeks ago i started noticing weird errors like: "memory low", can not start virtual machine. I wasn't running special memory consuming programs. "A reboot a day keeps the troubles away" was my temporary workaround.
When i started digging into the problem, i noticed that memory usage of the process spoolsv.exe was rather high. I have a screenshot of my task manager showing that the "Private Working Set" and also Commit Size is very large.
In the meantime, I have read in another post about a general memory leak in Windows 7 where they suggested using the driver verifier, but it didn't gave me any clue. I uploaded the screenshot of the driververifier.
When the process is skyhigh in memory usage, i can kill it. But a few minutes later i have taken these screenshots from the process explorer.
1) SpoolSv is using CPU. Apparently it is not only consuming RAM but also CPU power.
2) spoolsv.exe graph
I am not printing, or have not printed since days (and several reboots).
Normally I wouldn't care about (temporarly) high memory usage, but it really never drops... Other programs do crash because the lack memory (like videodriver or skype).
Has someone any idea why this process slows down my pc and keeps getting bigger minute after minute?
Kind regards
Please click 'Mark as Answer' on the post that helped you.

Hi DamPee,
In addition, I would like to suggest you perform the following steps to check the issue.
Clear Printer Spooler Files and Restart the Spooler Service
=================================
1. Click Start, type "Services.msc" (without the quotation marks) in the Start Search box and press Enter.
2. Double-click "Printer Spooler" in the Services list.
3. Click Stop and click OK.
4. Click Start, type "%WINDIR%\system32\spool\printers" in the Start Search box and press Enter, delete all files in this folder.
5. Click Start, type "Services.msc" (without the quotation marks) in the Start Search box and press Enter.
6. Double-click "Printer Spooler" in the Services list.
7. Click on Start. In the Startup Type list, make sure that "Automatic" is selected and click OK.
What’s the result?
Arthur Li - MSFT

Officejet Pro L7555 Hangs when printing,windows error msg - APPCRASH,spoolsv.exe

I have an OfficeJet Pro L7555 all in one printer.
I have tried and the same result on 2 different computers.I have reinstalled the entire software on one of the computers - result is still the same.
I just scanned a page to a pdf file and it did that ok.
What happens is:
1) i click to print and the job get sent to the printer,it starts to print and somewhere on the first page is halts sometimes with the page partly out of the chute where a completely printed page would land.I just tried to print 1 page and it did not print that page but a page that i was trying to print last night.Last night i switched the Printer off and also pulled the power plug out.
2) it then usually tries to print the other pages,halts along the way and starts again,and the last time, it did not even print all of the whole page,and i can also get blank pages.
3) and i get a Windows popup error box that says APPCRASH and the application is spoolsv.exe, i think,and options to find a solution online or to close
The printer is about 2 yrs old and i do not use it very much,so i dont think it is wear and tear and worn out parts,but is there something that needs replacing that is routine? But I am suspecting a memory problem on the printer though.Is this possible?? as it has printed a page that i was trying to print last night and it did it twice instead of printing 2 different pages and i suspect it is having a problem with the memory of what to print.
Thanks for any help in advance

Added Info for original posting:
Windows 8.1 64 bit OS. Dell box shipped with Windows 8 and upgraded to 8.1 via the Windows store. As stated in original post, computer is Dell XPS 8700, I7 cpu with 16 gbs of RAM.
Happy to answer any more specific questions.
Richard

Spoolsv.exe excessive network activity

I've noticed on one user so far that there is a TON of data going across the VPN to our print server (uses about 1mb of his connection). Total 3Gbs this morning. I went to our print server, opened up resource monitor and found that the spoolsv.exe is the
process that is using the data. His laptop isn't the only one doing this. There are also internal users that this is happening to. He has nothing to print, and the other users don't have anything printing or in the queue either. You can tell when a user
that is working correctly, prints. The data spikes until the print job is finished sending. The users that are having this problem is constantly sending data, both send and receive.
has anyone else ran into this problem? I've looked all over the internet and found some users that have had the problem but nothing to fix it. I can shutdown the spooler service, but once it's started again the data starts to flow. I've done that on both the
clients and the server. I've also made sure to check/clear the queue on both the server and the clients.

Based on my experience, usuall the resource related issues on spoolsv.exe mostly caused by the drivers. Please try to install the driver from Windows Updates, or please try to upgrade the 3th party printer drivers.
“Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”

System freezes due to hard disk problems only on Linux (not windows)

Intro/context:
Recently i've bought (about 2 months) a new laptop, a Lenovo G50-70, which came with Windows 8.1. As i had no interest on that OS, i formatted the disk and installed only Arch Linux. During that time i experienced system freezes which i had no idea why they were happening. As time went by, i found disk errors on system logs related to hard drive. I searched those errors and almost everything i found was that my hard drive had problems, so i decided to use my warranty. But first, i installed the original OS back again. And after using it a couple of weeks, i didn't experiencie any problem with my hard drive (on Linux it was really frequent). Now i've installed Arch Linux back, along with original Windows 8.1, having dual boot. There is no disk problem when using Windows, but when on Arch, i have the same errors and problems i used to have. So i assume it may be related to kernel or some confniguration issue.
I also haven't noticed any relation between system freezes and system use. I mean, it can happen either under light or heavy use.
tl dr: system freezes randomly for some minutes when using linux due to hard drive problems. The problem doesn't happen on windows.
What i've done so far:
The first period i was on Arch, i run smart (long and short), fsck, and hdparm tests. And nothing (no errors). Searched for bad blocks, and nothing. When back on windows, i also run tests on hdd and found no problems, except some sector reallocation not-that-nice indicators. These problems occured at the end of the first arch installation period. But still i currently experience no problem on windows.
I've also tried setting libata: noncq, 3.0G, noacpi, noapic kernel parameters, and had no result.
Changed BIOS setting from AHCI to Legacy, and no result. Also updated BIOS and no result.
I found no firmware update for this hard drive.
So i don't know what other thing i can try. I want to emphasize that there is no problem, no freezing, when running Windows, so i don't think it's a hard drive issue.
Info:
Hard drive is a Toshiba 2.5" HDD MQ01ABD100 5400 rpm.
Some logs i've recollected all this time:
journalctl -xfa --system
abr 21 13:51:13 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 13:51:24 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 21 13:51:24 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 7
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 13:51:24 echoes kernel: ata1.00: status: { DRDY }
abr 21 13:51:24 echoes kernel: ata1: hard resetting link
abr 21 13:51:24 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 13:51:24 echoes kernel: ata1.00: configured for UDMA/100
abr 21 13:51:24 echoes kernel: ata1: EH complete
abr 21 14:01:40 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 23 pio 512 in
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 22 pio 512 in
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:02:01 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 21 14:02:01 echoes kernel: ata1.00: failed command: SMART
abr 21 14:02:01 echoes kernel: ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 18
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 21 14:02:01 echoes kernel: ata1.00: status: { DRDY }
abr 21 14:02:01 echoes kernel: ata1: hard resetting link
abr 21 14:02:01 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 21 14:02:01 echoes kernel: ata1.00: configured for UDMA/100
abr 21 14:02:01 echoes kernel: ata1: EH complete
abr 21 14:01:51 echoes udisksd[627]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_Y44MT611T: Error updating SMART data: sk_disk_smart_status: Input/output error (udisks-error-quark, 0)
dmesg
[55661.023028] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 frozen
[55661.023034] ata1.00: failed command: READ FPDMA QUEUED
[55661.023040] ata1.00: cmd 60/08:78:18:08:c0/00:00:4b:00:00/40 tag 15 ncq 4096 in
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[55661.023042] ata1.00: status: { DRDY }
[55661.023046] ata1: hard resetting link
[55666.358537] ata1: link is slow to respond, please be patient (ready=0)
[55671.053813] ata1: COMRESET failed (errno=-16)
[55671.053819] ata1: hard resetting link
[55676.389438] ata1: link is slow to respond, please be patient (ready=0)
[55678.897149] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[55681.320305] ata1.00: configured for UDMA/100
[55681.320319] ata1.00: device reported invalid CHS sector 0
[55681.320349] ata1: EH complete
[55729.969443] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
[55729.969588] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
dmesg
[102884.889930] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[102884.890305] systemd[1]: Unit systemd-journald.service entered failed state.
[102884.890333] systemd[1]: systemd-journald.service failed.
[102885.560745] systemd-coredump[28916]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.5bf9a012fed048ce8975998cf3c3c20e.6705.1427990901000000.
[102885.860957] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/system.journal corrupted or uncleanly shut down, renaming and replacing.
[102921.797810] systemd-journald[28919]: File /var/log/journal/b130c96d1371445d9ddeb40c51c77dd6/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[104179.117363] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[104179.117369] ata1.00: failed command: READ FPDMA QUEUED
[104179.117375] ata1.00: cmd 60/08:00:48:88:8b/00:00:4d:00:00/40 tag 0 ncq 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[104179.117377] ata1.00: status: { DRDY }
[104179.117381] ata1: hard resetting link
[104184.453382] ata1: link is slow to respond, please be patient (ready=0)
[104189.149114] ata1: COMRESET failed (errno=-16)
[104189.149121] ata1: hard resetting link
[104189.469276] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104189.952982] ata1.00: configured for UDMA/100
[104189.952989] ata1.00: device reported invalid CHS sector 0
[104189.953004] ata1: EH complete
[104508.223792] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104508.223798] ata1.00: failed command: SMART
[104508.223803] ata1.00: cmd b0/da:00:00:4f:c2/00:00:00:00:00/00 tag 2
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[104508.223806] ata1.00: status: { DRDY }
[104508.223810] ata1: hard resetting link
[104509.984601] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[104510.698126] ata1.00: configured for UDMA/100
[104510.698157] ata1: EH complete
One of the latest and worse
journalctl -xfa --system
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:00:e0:d6:75/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:08:08:d8:75/00:00:00:00:00/40 tag 1 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:10:30:d9:75/00:00:00:00:00/40 tag 2 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:18:58:da:75/00:00:00:00:00/40 tag 3 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:20:e8:e5:75/00:00:00:00:00/40 tag 4 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:28:80:db:75/00:00:00:00:00/40 tag 5 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:30:68:dd:75/00:00:00:00:00/40 tag 6 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:38:90:de:75/00:00:00:00:00/40 tag 7 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:40:b8:df:75/00:00:00:00:00/40 tag 8 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:48:90:e1:75/00:00:00:00:00/40 tag 9 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:50:98:e3:75/00:00:00:00:00/40 tag 10 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:58:c0:e4:75/00:00:00:00:00/40 tag 11 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/c8:78:28:b9:2a/0b:00:4e:00:00/40 tag 15 ncq 1544192 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:80:b0:4b:c0/00:00:4f:00:00/40 tag 16 ncq 4096 out
res 40/00:ff:80:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:88:90:4b:80/00:00:50:00:00/40 tag 17 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:90:98:22:81/00:00:50:00:00/40 tag 18 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:98:00:0e:00/00:00:5f:00:00/40 tag 19 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a0:00:08:80/00:00:5f:00:00/40 tag 20 ncq 4096 out
res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:a8:80:08:80/00:00:5f:00:00/40 tag 21 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/10:b0:08:0b:81/00:00:5f:00:00/40 tag 22 ncq 8192 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:b8:70:c8:75/00:00:00:00:00/40 tag 23 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c0:20:c9:75/00:00:00:00:00/40 tag 24 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:c8:88:c9:75/00:00:00:00:00/40 tag 25 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d0:58:ca:75/00:00:00:00:00/40 tag 26 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:d8:a0:ce:75/00:00:00:00:00/40 tag 27 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e0:68:d3:75/00:00:00:00:00/40 tag 28 ncq 4096 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:e8:90:d4:75/00:00:00:00:00/40 tag 29 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1.00: failed command: WRITE FPDMA QUEUED
abr 22 12:57:11 echoes kernel: ata1.00: cmd 61/08:f0:b8:d5:75/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: ata1.00: device reported invalid CHS sector 0
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 12 88 d7 c0 00 04 d0 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 310958016
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 36311758 (offset 8388608 size 2695168 starting block 38869906)
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995128
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995129
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995130
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995131
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995132
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995133
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995134
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995135
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995136
abr 22 12:57:11 echoes kernel: Buffer I/O error on device sda2, logical block 19995137
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4b dd 39 88 00 01 78 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1272789384
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 34999445 (offset 0 size 192512 starting block 159098720)
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x06
abr 22 12:57:11 echoes kernel: sd 0:0:0:0: [sda] CDB:
abr 22 12:57:11 echoes kernel: cdb[0]=0x2a: 2a 00 4e 2a b3 e8 00 05 40 00
abr 22 12:57:11 echoes kernel: blk_update_request: I/O error, dev sda, sector 1311421416
abr 22 12:57:11 echoes kernel: EXT4-fs warning (device sda2): ext4_end_bio:317: I/O error -5 writing to inode 35001016 (offset 0 size 2232320 starting block 163927845)
abr 22 12:57:11 echoes kernel: ata1: EH complete
abr 22 12:57:11 echoes kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
abr 22 12:57:11 echoes kernel: ata1.00: failed command: CHECK POWER MODE
abr 22 12:57:11 echoes kernel: ata1.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 25
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
abr 22 12:57:11 echoes kernel: ata1.00: status: { DRDY }
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: COMRESET failed (errno=-16)
abr 22 12:57:11 echoes kernel: ata1: hard resetting link
abr 22 12:57:11 echoes kernel: ata1: link is slow to respond, please be patient (ready=0)
abr 22 12:57:11 echoes kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
abr 22 12:57:11 echoes kernel: ata1.00: configured for UDMA/100
abr 22 12:57:11 echoes kernel: ata1: EH complete
Current smart status:
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.1-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABD...
Device Model: TOSHIBA MQ01ABD100
Serial Number: Y44MT611T
LU WWN Device Id: 5 000039 5e1a80e85
Firmware Version: AX1P5E
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun May 3 16:42:06 2015 ART
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 234) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1671
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 306
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 152
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 699
10 Spin_Retry_Count 0x0033 106 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 300
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 216
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 14140
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Min/Max 16/44)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 19
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 515
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 190
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Vendor (0x50) Completed without error 00% 611 -
# 2 Short offline Completed without error 00% 611 -
# 3 Short offline Completed without error 00% 597 -
# 4 Vendor (0x50) Completed without error 00% 583 -
# 5 Short offline Completed without error 00% 583 -
# 6 Vendor (0x50) Completed without error 00% 575 -
# 7 Short offline Completed without error 00% 575 -
# 8 Short offline Completed without error 00% 547 -
# 9 Extended offline Completed without error 00% 529 -
#10 Short offline Completed without error 00% 355 -
#11 Short offline Completed without error 00% 355 -
#12 Extended offline Aborted by host 70% 355 -
#13 Short offline Completed without error 00% 319 -
#14 Vendor (0x50) Completed without error 00% 13 -
#15 Short offline Completed without error 00% 13 -
#16 Short offline Completed without error 00% 12 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Kernels used have been from 3.9 to current: Linux echoes 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux
Last edited by jesu (2015-05-03 19:42:53)

Something i'd noticed both the first time i was on arch and now i've reinstalled it, was that at first i didn't have this problem. I mean, when Arch was just installed. While i was installing and setting up everything.
Now, i'm not 100% sure about this, but i think problems began when using my current user. Disk is partitioned the following way:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 1000M 0 part
├─sda2 8:2 0 260M 0 part /boot
├─sda3 8:3 0 207,7G 0 part
├─sda4 8:4 0 25G 0 part
├─sda5 8:5 0 14,8G 0 part
├─sda6 8:6 0 80,5G 0 part /
├─sda8 8:8 0 599G 0 part /home
└─sda9 8:9 0 2G 0 part [SWAP]
So, i believe problems, for some reason, are related (and were related), both before and now, to the /home partition, /dev/sda8 in this ocassion.
Because of this, i booted into systemd rescue mode, like root, rw, and unmounted /home partition. Despite root-only limitations, i used the system for a couple of hours, started lxqt, browsed the web mainly, and experienced no problem at all.
Now i booted normally, with my regular user, and these problems are experienced just like before (and almost instantly, like 3 or 5 minutes after starting system use).
dmesg this time showed a some different log, though it's not the first time i see this. I just didn't saved that kind of log before.
[ 653.821719] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6 frozen
[ 653.821726] ata1.00: failed command: READ FPDMA QUEUED
[ 653.821732] ata1.00: cmd 60/08:40:60:25:43/00:00:1b:00:00/40 tag 8 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 653.821735] ata1.00: status: { DRDY }
[ 653.821739] ata1: hard resetting link
[ 659.156760] ata1: link is slow to respond, please be patient (ready=0)
[ 663.851604] ata1: COMRESET failed (errno=-16)
[ 663.851610] ata1: hard resetting link
[ 669.186591] ata1: link is slow to respond, please be patient (ready=0)
[ 673.881456] ata1: COMRESET failed (errno=-16)
[ 673.881462] ata1: hard resetting link
[ 679.216481] ata1: link is slow to respond, please be patient (ready=0)
[ 702.743982] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 703.012578] ata1.00: configured for UDMA/100
[ 703.012584] ata1.00: device reported invalid CHS sector 0
[ 703.012599] ata1: EH complete
[ 714.097642] systemd[1]: systemd-journald.service watchdog timeout (limit 1min)!
[ 742.443488] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443494] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x2a 2a 00 28 c3 c6 40 00 00 10 00
[ 742.443497] blk_update_request: I/O error, dev sda, sector 683918912
[ 742.443503] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489866)
[ 742.443506] Buffer I/O error on device sda8, logical block 9323208
[ 742.443508] Buffer I/O error on device sda8, logical block 9323209
[ 742.443515] sd 0:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443518] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x2a 2a 00 28 c3 c6 80 00 00 10 00
[ 742.443520] blk_update_request: I/O error, dev sda, sector 683918976
[ 742.443522] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489874)
[ 742.443524] Buffer I/O error on device sda8, logical block 9323216
[ 742.443526] Buffer I/O error on device sda8, logical block 9323217
[ 742.443531] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443534] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 28 c3 c6 d0 00 00 10 00
[ 742.443536] blk_update_request: I/O error, dev sda, sector 683919056
[ 742.443538] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489884)
[ 742.443540] Buffer I/O error on device sda8, logical block 9323226
[ 742.443542] Buffer I/O error on device sda8, logical block 9323227
[ 742.443547] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06
[ 742.443549] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 28 c3 c7 10 00 00 10 00
[ 742.443551] blk_update_request: I/O error, dev sda, sector 683919120
[ 742.443553] EXT4-fs warning (device sda8): ext4_end_bio:317: I/O error -5 writing to inode 20322020 (offset 0 size 0 starting block 85489892)
[ 742.443555] Buffer I/O error on device sda8, logical block 9323234
[ 742.443557] Buffer I/O error on device sda8, logical block 9323235
[ 756.187685] systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT
[ 756.187986] systemd[1]: Unit systemd-journald.service entered failed state.
[ 756.188116] systemd[1]: systemd-journald.service failed.
[ 756.188474] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 756.189106] systemd[1]: Stopping Flush Journal to Persistent Storage...
[ 756.189143] systemd[1]: Listening on Journal Audit Socket.
[ 756.189801] systemd[1]: Starting Journal Service...
[ 757.525493] systemd-coredump[1038]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.b8610e85f9074a418534aaee0adbac56.141.1430763073000000.lz4.
[ 758.133944] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ 758.503041] systemd[1]: Started Journal Service.
[ 759.180771] systemd-journald[1050]: File /var/log/journal/f646626ba4b647f48501020bf12ca33b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 974.867721] ata1.00: exception Emask 0x0 SAct 0x3f80 SErr 0x0 action 0x6 frozen
[ 974.867732] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867742] ata1.00: cmd 61/08:38:68:d3:c5/00:00:1a:00:00/40 tag 7 ncq 4096 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867747] ata1.00: status: { DRDY }
[ 974.867751] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867759] ata1.00: cmd 61/08:40:88:d3:c5/00:00:1a:00:00/40 tag 8 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867763] ata1.00: status: { DRDY }
[ 974.867767] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867774] ata1.00: cmd 61/08:48:a0:d3:c5/00:00:1a:00:00/40 tag 9 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867778] ata1.00: status: { DRDY }
[ 974.867781] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867789] ata1.00: cmd 61/20:50:c0:d3:c5/00:00:1a:00:00/40 tag 10 ncq 16384 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867793] ata1.00: status: { DRDY }
[ 974.867796] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867803] ata1.00: cmd 61/10:58:f0:d3:c5/00:00:1a:00:00/40 tag 11 ncq 8192 out
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867807] ata1.00: status: { DRDY }
[ 974.867810] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867817] ata1.00: cmd 61/08:60:10:d4:c5/00:00:1a:00:00/40 tag 12 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867821] ata1.00: status: { DRDY }
[ 974.867824] ata1.00: failed command: WRITE FPDMA QUEUED
[ 974.867831] ata1.00: cmd 61/18:68:28:d4:c5/00:00:1a:00:00/40 tag 13 ncq 12288 out
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 974.867835] ata1.00: status: { DRDY }
[ 974.867841] ata1: hard resetting link
[ 980.202774] ata1: link is slow to respond, please be patient (ready=0)
[ 984.900902] ata1: COMRESET failed (errno=-16)
[ 984.900908] ata1: hard resetting link
[ 990.236024] ata1: link is slow to respond, please be patient (ready=0)
[ 994.930829] ata1: COMRESET failed (errno=-16)
[ 994.930836] ata1: hard resetting link
[ 996.798104] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 997.014012] ata1.00: configured for UDMA/100
[ 997.014020] ata1.00: device reported invalid CHS sector 0
[ 997.014023] ata1.00: device reported invalid CHS sector 0
[ 997.014025] ata1.00: device reported invalid CHS sector 0
[ 997.014026] ata1.00: device reported invalid CHS sector 0
[ 997.014028] ata1.00: device reported invalid CHS sector 0
[ 997.014030] ata1.00: device reported invalid CHS sector 0
[ 997.014031] ata1.00: device reported invalid CHS sector 0
[ 997.014065] ata1: EH complete
There are some sda8 (home) related messages. I also found these messages first time Arch was installed (i think also related to home partition).
root and home partitions are both ext4.

Lightroom 4 freezes due to video files

I just installed Lightroom 4 Upgrade on a Mac running Lion. Everything went well until I created a Smart Collection with a file type of video. As soon as I click "Done" on the Smart Collection setup, Lightroom froze. I have to force quit the program and within a couple of seconds of starting the program up it freezes again so I don't even have time to try to delete the Smart Collection I made for videos.
How do I fix this? If I need to uninstall LR4, how do I do that since there is no uninstaller in the downloaded .dmg file. Due to the elaborate nature of Adobe software I'm reluctant to just drag the app into the trash or use the AppCleaner app I have.
This is NOT a very good start and I'M NOT HAPPY!!!!!
UPDATE:
Now Lightroom 4 won't even fininsh starting up before it freezes.
ANOTHER UPDATE:
I couldn't wait for a response so I used AppCleaner to uninstall LR4 and all its associated files and folders; then re-installed it using the .dmg. It installed as it did originally and seems to work fine.
EXCEPT: being re-installed the Smart Collection I made for videos is gone now. However, I went to the folder, while in the Library pane, which contains my iPhone photos and videos (which are the only videos I have in my LR catalog), clicked on the folder containing the videos, and LR FROZE AGAIN. BUT, at least now, after force quiting and restarting, LR seems to work OK. Stay away from video files.
Yet Another Update:
Wrong again. I closed LR4, re-opened it and guess what? IT FROZE ON STARTUP BEFORE IT EVEN FINISHED LOADING AGAIN.
Clearly from my experience and the multitude of postings on this forum, LR4 is not ready for prime time and should still be in beta.
Still Another Update:
The problem seems to revolve around video files and conversion to the 2012 process. I reinstalled LR4 and before updating to the 2012 process and without going near any video file or folders, everything worked fine, including quiting and restarting the program. I then upgraded all my photos to the 2012 process and when I quit and restarted LR it froze again. I did the whole un-install/re-install routine but before I did I moved my video files out of the folder in the catalog and after doing everything as before, LR finally quit and restarted without freezing. So stay away from video files for the time being.

mrbofus wrote:
I can't imagine that we're alone in this; perhaps we're the only ones that care enough to post about it. =)
It's not that we don't care, it's that the root cause of how exactly our iPads fail and have error's pop up are so numerous and complex that deciphering them all (along with their causes) would be a full time job! And I'm busy enough with my real one, there's bills to be paid! lol
In response to the actual topic at hand, I did notice deleting my videos made my syncs faster, thank you very much for that suggestion. I mean, I did have to delete ALL my videos to get a noticeable effect, but still, at least now I'm not scared I'm going to burn out my Pad's core every time I add a new song. lol

Random freezes due to gnome-settings-daemon

Hello,
I've been experiencing frequent and random crashes during which the entire system freezes over a several-second period due to gnome-settings-daemon quickly consuming all available ram. During the crashes the mouse, keyboard, sound, and screen all become frozen, and I cannot trigger suspend, hibernate, shutdown, or switch virtual terminals. gnome-settings-daemon memory usage rises to 1.2GB. Nothing stands out in journalctl except for the usual general abundance of seemingly unrelated error messages, and I can't link the crash to any obvious trigger. The only way out is cutting the power. I've tried limiting /tmp size, killing the daemon, and closing applications in the brief time before total unusability, and none of these things has had any effect... According to a Google search, this was a problem with a recent version of the daemon, but it was apparently fixed. Has anybody else experienced this? Thanks.
Update: It's happening about once or twice an hour. I'll just go to move the mouse and it won't. Sound sometimes keeps functioning choppily for up to ~30 seconds.
Last edited by Aestus (2013-12-19 15:22:40)

Use lxappearance to set your gtk settings. There are some other ones too, like gtk-chtheme, gtk-theme-switch2, and gtk2_prefs. I like lxappearance, personally.
https://wiki.archlinux.org/index.php/GTK+

Itunes won't reinstall or update due to helper.exe access

My Itunes was partially wiped out due to lack of memory in computer after attempting to install a game. The memory issue was resolved by adding more. I cannot uninstall or reinstall itunes. I even attempted to update it with the newest version, however, I keep getting the error with helper.exe. It states that I need to confirm access and retry. Nothing is working and I cannot simply delete the folders from my program file either. I'd rather not dump everthing on my computer and re-install the system just for itunes. Suggestions?
emachines W3410 Windows XP

The only thing I found was the apple software update. I removed that with the cleanup but the error still occurs in the installation. I also don't have an ipods or itunes in my add/remove option, but I still have an ipod and itunes folder in my program files that the computer refuses to delete.
okay, we'd better check on disk damage around the areas of those folders. try running a chkdsk over the C drive:
How to perform disk error checking in Windows XP
does the chkdsk find/repair any damage? if so, do you have any better luck with those folders?

Satellite P100-238 freezes after an svchost.exe program error message:

PC: Satellite P100-238 from December 2006.
approx. a minute after startup i get an error message:
Danish:
svchost.exe - programfejl
Instruktionen ved "0x745f278o" refererede hukommelse ved "0x00000000". Hukommelsen kunne ikke "read".
Klik p OK for at afslutte program.
Klik p Annuller for at udfe fejlfinding i programmet.
English translation:
svchost.exe - program error
Instruction on "0x745f278o" refered memory on "0x00000000". Memory could not "read".
Click OK for ending program
Click Cansel to do error search in the program.
After the above error message the PC freezes totally and I can only turn it off by the on/off button.
What has happened with my PC?
What should i do?
How do I get access to my data to make a backup?

Hi
I goggled a little bit in the net for some help and I was surprised that many Windows users have had the same problem
So I thought there must be generally something wrong with the windows operating system.
I have investigated a little bit in the MS knowledge base and found this:
http://support.microsoft.com/kb/916089/en-us
According to the MS info this problem may occur when you have Microsoft Office installed and the Windows Update Agent tries to scan for Windows Installer updates.

IPhone 6 freezing due to wifi connection

iphone 6 here. 16gb. Freezing in the last two weeks at home due to some sort of wifi troubleshooting. I use an airport express.
COnnection to the wifi network is almost and always very good. House is small. loses wifi connection a lot Of times during the day. And sometimes it freezes with one bar of wifi signal. After that the only thing to do is hard reset on iPhone. Sometimes sfter rebooting wifi is not available anymore on the iPhone. did a full restore twice from iTunes in one week. Restore was hard to do because iTunes wasn't able to connect with the iPhone or lost communication during connection to it.
THis is not the Apple we kknow. This is clearly a software bug and the reason i kept on choosing apple was due to its software performance.
I Am frustrated to need to full restore in a week a 600€ smartphone. It is sad I get frustrated with this and with the daily hard resets.
I Believe apple is loosing its mojo, and I wish they could get back on track with problems that should have been tested during beta. Lots of people are suffering from the same freezing issues.
THis is a sad moment for Apple but their stocks are growing so I don't believe they give a flying concern about it.

Did you check the recommended settings for Wi-Fi networks?
iOS and OS X: Recommended settings for Wi-Fi routers and access points
Did you already reset the network settings in Settings/General/Reset? You will have to fill in all the passwords for other known networks again after that.

IPad iTunes Stores App Freezes due to large number of songs purchased?

The iTunes Store App on my iPad 4 freezes when I go to " purchases" on the lower right hand corner of the screen. The screen remains blank, with the twirling icon in the middle implying 'wait.' I wanted to avoid doing a "restore" to the whole iPad, as everything else on the iPad but this works fine. After several days back and forth emailing with with Apple iTunes support, the Tech concluded it was beyond his/her technical expertise, and gave me the phone # for Apple Cares. Initial diagnosis after my first call to them was that I needed to do a 'restore' to factory setting because Apple won't push through an update to their iTunes Store App. So, I backed up the iPad to my using iTunes on my my PC and to iCloud, then called back. This time I worked with a very pleasant Apple Rep who stayed with me on the phone for over an hour running diagnostic tests, trying different things like rebooting my iPad, unplugging and resetting my Wi-Fi modem (I used AT&T UVerse for Internet and had already had techs out checking that after the first call - no problem there), going to iTunes on my PC, and a number of other things. After conferring with a senior tech, the Apple Cares rep said they concluded it was due to the large amount of songs I've purchased. I don't think of myself as a large music purchaser, maybe 4 - 5 songs a week since I bought the iPad new a year ago. So, I was wondering if anyone else has had this problem? Apple Cares was not able to tell me how to move songs out of "purchases" or whatever the bucket might be called where purchases are listed to clear this out if in fact it is the large number of songs there actually causing the iTunes Stores App to freeze. This is not an essential function, but I use it when I want to find the names of recently downloaded songs to place purchases into playlists. (I know, I should be able to remember the names, artists, etc. of the music a I purchase, but alas, no!) The nearest Apple Store is about 180 miles round-trip, and I won't get there for about two weeks. Incidentally, recently added songs show normally in the iPad's Music library. If anyone else has experienced this, was it fixed? If so how?

No, the problem still exists. As far as I know, the Case Number is still open. I've just not had time to set aside a day to bring the iPad into an Apple Store yet. It's about a 3 hr round trip, plus there'd be time walking to the store (it's inside a mall), and then the time spent while the iPad is looked at and hopefully fixed. Ugh!

Imac keeps freezing due to low storage space

I have been a very iMac user since 2008 and now my iMac, iMac (24-inch, Early 2008), keeps freezing very often causing me to reboot it.
I have tried different methods, but none helps me. Does anyone have had similar experience?
Thank you for any support.
Yusuf.

The content of the computer's hard disk drive, includes storage of your created works
files you made, images or music files, and the likes of which some flakey application
such as 'cleanmymac' won't really help with. To clear the problem, you'd have to invest
in an externally enclosed hard disk drive, and move/copy those items you sought to keep
to the external drive, then trash the originals from the computer's hard disk drive.
Or upgrade the internal hard disk drive to a larger capacity, and have an expert move
the content from the old drive into the new one, if you aren't skilled to do that task.
Also, the lack of free or unused hard drive capacity can be a problem with systemwide
performance; that is because the hard drive free space is usually available to the OS X
for use as Virtual Memory on an automatic level, in cases when there is not enough
actual chip RAM installed. The slower read-write to/from the hard disk drive takes the
place of suitable memory chip capacity, at a poorer rate of return compared to real RAM.
If your computer has less than 15% unused hard drive capacity, it will have issues; this
may vary depending on what you are using the computer for, & your open applications.
Back to RAM memory chips, if your computer has less than 6GB RAM installed, it may
be able to see a slight measure of performance gain (after removing excess files to
an outside hard drive) by upgrading this by use of suitable quality RAM chips. The OS X
versions after Snow Leopard 10.6.8 prefer more than 4GB and up, to work adequately.
•iMac: How to remove or install memory - Apple Support
Maximum Memory 6.0 GB (Actual) 4.0 GB (Apple)
Memory Slots 2 - 200-pin PC2-6400 (800MHz) DDR2 SO-DIMM
{the link above suggests less than factual upgrade capacity, so to
expand that to more than 4GB, you could use one 2-GB chip and
one 4-GB chip for a total of 6GB; or choose two 4-GB and not be
able to really see a gain from the rounding up to 8GB in your Mac}
Most credible Mac user advice, says to not use Mackeeper, Cleanmymac, or those
other non-productive third-party products; they don't really help the overall issues.
And they are very hard to completely remove; their remaining bits do affect OS X
performance and do more harm than good. So there are a few advice sections
in these ASC discussions where removing those kinds of badwares are mentioned.
Information can be found about adware, malware, and performance issues on the
pages of http://thesafemac.com and note the Tech Guides; plus link to adware medic.
You may be due to have the hard disk drive in the iMac replaced, if it's an original part.
They do wear out and when that happens, your data can all be lost. So address that
by the best means available. An iFixit.com repair guide for the build model year iMac
you have is online and can be used for free. You'd need to see it, though, when or if
the computer in use is taken offline for the procedure. Or let an expert do the upgrades.
In any event...
Good luck & happy computing!

Portege M400 freezes due to overheating

I have exactly the same problem with a Portege M400.
After an hour or 2 the the fan becomes extremely noisy and the PC freezes. The base of the PC becomes too hot to touch and in fact the Tochiba/Microsoft and barcode stickers on the base have turned brown due to the heat.
The only way to fix the problem seems to be to turn the PC off for 15 minutes of so and reboot.
When this happens I am usually only running outlook, Norton and a browser!!!
This hs been happening for about 6 months. I've cleaned out the fan but this has made no difference - anyone know a fix?

Hi
If you have cleaned the cooling modules and if this didnt help, then you should get in contact with an local ASP technicians.
Possibly the notebook must be disassembled completely and should be cleaned inside.
This is very tricky procedure! Furthermore the thermal grease which I placed between the CPU and the cooling modules should be renewed.
After a long time of usage, thermal grease becomes dry and cannot channel the warmness created by CPU.
Last but not lease you should use your notebook always on a table. Do use it in bed or lying on the knees. In such case the cooling ventilator would not get enough air and this leads to a higher temperature.

Exchange 2013 /m:recoverserver constantly failing due to MSExchangeSubmission.exe

Hi all,
I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.
The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:
setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms
I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:
Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
</System>
<EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Any thoughts?
Paul

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.
I'm in that right now, i ll tell if it's working soon.
Ty!
Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)
Nombre de la aplicación con errores: MSExchangeSubmission.exe, versión: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del módulo con errores: Microsoft.Exchange.Net.ni.dll, versión: 15.0.516.27, marca de tiempo: 0x5064072e
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicación con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicación con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del módulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
ExchangeSetup.log ends with:
[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear();
start-SetupService -ServiceName MSExchangeSubmission
" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se completó la operación de instalación de Exchange Server. Puede encontrar más detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************
Any suggestion please??? idk what else can i do!

Freeze due to spoolsv.exe

Similar Messages

Maybe you are looking for