BSOD Plus random crashs after inactivity

[Dozen]

Hi,
i got a dell xps 17 l702x
cpu i7 2720QM
gpu nvidia 555m
RAM DDR3
Main HD Crucial m4 128GB fw 309
Windows 7 x64 Professional

My PC randomly crashs without an apparent reason, one of the most annoying one happens if i leave the PC working without any input with power plan Balance, the screen is black and i can only reboot (doesn't happen with High Performance).
However sometimes i also get BSOD while working normally.
I'm also noticing how the frequency of the CPU gets really low sometimes if i remove the charger.

Everythig else is in the attachment.

Thanks.

(P.S. i just removed the mac address of the lan/wlan from the logs)

 

[zigzag3143]

this was Related to SynTP.sys Synaptics Touchpad Driver. Yours from 2011. I would re-install the newest driver available.

There are a few other things on your system that may be co-incidental causes biut lets see if you continue to crash after the driver update.

 

[Dozen]

this was Related to SynTP.sys Synaptics Touchpad Driver. Yours from 2011. I would re-install the newest driver available.

There are a few other things on your system that may be co-incidental causes biut lets see if you continue to crash after the driver update.

Thank you for the quick answer!

That looks like the latest version of the driver to me:
Drivers | Synaptics

And there is no driver on the dell website

 

[zigzag3143]

this was Related to SynTP.sys Synaptics Touchpad Driver. Yours from 2011. I would re-install the newest driver available.

There are a few other things on your system that may be co-incidental causes biut lets see if you continue to crash after the driver update.

Thank you for the quick answer!

That looks like the latest version of the driver to me:
Drivers | Synaptics

And there is no driver on the dell website

If it is the latest driver you may just want to re-install the same driver for it was clearly at fault and may have become corrupted

 

[Dozen]

more bsods

I really can't go on crashing like this. It mostly happens on system startup.

I collected plenty of dumps maybe we can find the problem now...

I also had some freezes during the last month, to fix them i updated my SSD firmware (crucial m4) to the latest available, hope it's fixed now.

P.S. i also updated my nvidia driver a few days ago

 

[writhziden]

Please provide us with the latest crash reports you collected by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

 

[Dozen]

Please provide us with the latest crash reports you collected by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

sorry! i didn't attach the files
the system didn't change from the first post.

 

[writhziden]

You haven't installed any hardware or software in over a month? You haven't removed any software in over a month?

Crashes indicate hard disk related problems and possible Windows corruption. This may be due to file system errors on the hard disk, but without the event viewer logs that are contained in the reports from the blue screen instructions, it is difficult to ascertain the likely cause. You may have a virus, bad sectors on the hard disk, simple data corruption, a memory issue, driver conflicts, Windows file corruption, or Windows registry corruption.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• For the SSD: Make sure the firmware is up to date, BIOS is up to date, chipset drivers are updated, and hard disk controller drivers are installed and updated.
  
  
• For the HDD:
  • Run the short and long tests with SeaTools.
    SeaTools for Windows
    
    SeaTools for DOS​
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• Before proceeding with the next step, see if the system is stable from doing the above steps. If you still have problems, proceed to the Verifier enabled checks.
  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:

    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      View attachment 212051
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    
    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
    
    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
    
    When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
    verifier /reset​
    -> Restart your computer.

 

[Dozen]

You haven't installed any hardware or software in over a month? You haven't removed any software in over a month?

Crashes indicate hard disk related problems and possible Windows corruption. This may be due to file system errors on the hard disk, but without the event viewer logs that are contained in the reports from the blue screen instructions, it is difficult to ascertain the likely cause. You may have a virus, bad sectors on the hard disk, simple data corruption, a memory issue, driver conflicts, Windows file corruption, or Windows registry corruption.

• If you are overclocking any hardware, please stop.
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

From newer to older:

Controllo in corso del file system su C:
Il file system è di tipo NTFS.

Il disco sarà ora controllato come pianificato.
Il disco sarà ora controllato.

Verifica dei file in corso (fase 1 di 5)...
183040 record di file elaborati. Verifica file completata.
566 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 2 record EA elaborati. 105 record reparse elaborati. Verifica degli indici in corso (fase 2 di 5)...
242938 voci di indice elaborate. Verifica indici completata.
0 file non indicizzati analizzati. 0 file non indicizzati ripristinati. Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
183040 descrittori di protezione/SID di file elaborati. Pulizia di 3 voci inutilizzate dall'indice $SII del file 0x9.
Pulizia di 3 voci inutilizzate dall'indice $SDH del file 0x9.
Pulizia dei descrittori di sicurezza inutilizzati 3.
Verifica descrittori di sicurezza completata.
29950 file di dati elaborati. CHKDSK sta verificando il journal USN...
36592744 byte USN elaborati. Verifica del journal USN completata.
Verifica dei dati dei file in corso (fase 4 di 5))...
183024 file elaborati. Verifica dei dati del file completata.
CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 5532273. Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato. (NOTHING FOUND)

124930047 KB di spazio totale su disco.
102432956 KB in 141240 file.
78440 KB in 29951 indici.
44 KB in settori danneggiati.
289515 KB in uso dal sistema.
65536 KB occupati dal file registro.
22129092 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
31232511 unità totali di allocazione su disco.
5532273 unità di allocazione disponibili su disco.

Informazioni interne:
00 cb 02 00 c0 9c 02 00 86 9e 04 00 00 00 00 00 ................
e8 02 00 00 69 00 00 00 00 00 00 00 00 00 00 00 ....i...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Controllo del disco completato.
Attendere il riavvio del computer.

Controllo in corso del file system su C:
Il file system è di tipo NTFS.

Il disco sarà ora controllato come pianificato.
Il disco sarà ora controllato.

Verifica dei file in corso (fase 1 di 5)...
183040 record di file elaborati. Verifica file completata.
570 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 2 record EA elaborati. 105 record reparse elaborati. Verifica degli indici in corso (fase 2 di 5)...
247276 voci di indice elaborate. Verifica indici completata.
0 file non indicizzati analizzati. 0 file non indicizzati ripristinati. Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
183040 descrittori di protezione/SID di file elaborati. Pulizia di 86 voci inutilizzate dall'indice $SII del file 0x9.
Pulizia di 86 voci inutilizzate dall'indice $SDH del file 0x9.
Pulizia dei descrittori di sicurezza inutilizzati 86.
Verifica descrittori di sicurezza completata.
32119 file di dati elaborati. CHKDSK sta verificando il journal USN...
35731896 byte USN elaborati. Verifica del journal USN completata.
Verifica dei dati dei file in corso (fase 4 di 5))...
Lettura non riuscita con stato 0xc0000185 a offset 0x1d0d05000 per 0x1000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x1d0d05000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 56335
di nome \Windows\winsxs\MANIFE~2\WO7700~1.MAN.
Lettura non riuscita con stato 0xc0000185 a offset 0x424b7a000 per 0x2000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x424b7a000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 67501
di nome \Windows\System32\catroot\{F750E~1\PADB45~1.CAT.
Lettura non riuscita con stato 0xc0000185 a offset 0xf7e663000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0xf7e66d000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 80417
di nome \dell\drivers\R282538\SYSTEM~1.MSI.
Lettura non riuscita con stato 0xc0000185 a offset 0xc87af9000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0xc87b05000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 90534
di nome \Users\RS\Desktop\test\DOWNLO~1\LITTLE~2.TXT.
Lettura non riuscita con stato 0xc0000185 a offset 0xd0441a000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0xd04425000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 106366
di nome \Windows\MICROS~1.NET\FRAMEW~2\V40~1.303\SQL\it\TRACKI~1.SQL.
Lettura non riuscita con stato 0xc0000185 a offset 0x19291c000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x19292b000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 108195
di nome \Windows\INSTAL~1\$PATCH~1\Managed\000041~3\14.0.4763\OARTCONV.DLL.
Lettura non riuscita con stato 0xc0000185 a offset 0x4c178f000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x4c179d000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 123708
di nome \Users\RS\Music\iTunes\ITUNES~1\MOBILE~1\SONICR~1.IPA.
Lettura non riuscita con stato 0xc0000185 a offset 0x5a3a75000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x5a3a79000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 128125
di nome \Windows\winsxs\AM788E~1.205\ieframe.dll.
Lettura non riuscita con stato 0xc0000185 a offset 0x564de7000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x564dea000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 131143
di nome \Windows\winsxs\AMD64_~2.205\ieframe.dll.
Lettura non riuscita con stato 0xc0000185 a offset 0x716e0e000 per 0x10000 byte.
Lettura non riuscita con stato 0xc0000185 a offset 0x716e16000 per 0x1000 byte.
Impossibile sostituire i cluster danneggiati nel file 158125
di nome \Windows\INSTAL~1\$PATCH~1\Managed\000041~3\14.0.4763\ACEWDAT.DLL.
183024 file elaborati. Verifica dei dati del file completata.
CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 5423157. Verifica dello spazio disponibile completata.
Aggiunta di 10 cluster danneggiati al file dei cluster danneggiati
(Added 10 damaged cluster to the damaged cluster file)
Correzione errori nella mappa di bit del volume.
Correzioni apportate al file system.

124930047 KB di spazio totale su disco.
102869688 KB in 144780 file.
78684 KB in 32120 indici.
44 KB in settori danneggiati.
289003 KB in uso dal sistema.
65536 KB occupati dal file registro.
21692628 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
31232511 unità totali di allocazione su disco.
5423157 unità di allocazione disponibili su disco.

Informazioni interne:
00 cb 02 00 0d b3 02 00 c7 b4 04 00 00 00 00 00 ................
e8 02 00 00 69 00 00 00 00 00 00 00 00 00 00 00 ....i...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Controllo del disco completato.
Attendere il riavvio del computer.

CHKDSK eseguito in modalità lettura/scrittura.

Controllo in corso del file system su D:
L'etichetta del volume è RECOVERY.

Verifica dei file in corso (fase 1 di 5)...
10240 record di file elaborati. Verifica file completata.
4 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 0 record EA elaborati. 0 record reparse elaborati. Verifica degli indici in corso (fase 2 di 5)...
10330 voci di indice elaborate. Verifica indici completata.


Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
10240 descrittori di protezione/SID di file elaborati. Verifica descrittori di sicurezza completata.
45 file di dati elaborati. Verifica dei dati dei file in corso (fase 4 di 5))...
10224 file elaborati. Verifica dei dati del file completata.
CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 1771414. Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato. (Nothing Found)

15359999 KB di spazio totale su disco.
8197608 KB in 155 file.
64 KB in 47 indici.
76671 KB in uso dal sistema.
65536 KB occupati dal file registro.
7085656 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
3839999 unità totali di allocazione su disco.
1771414 unità di allocazione disponibili su disco.

CHKDSK eseguito in modalità sola lettura in un'istantanea di volume.

Controllo in corso del file system su F:
L'etichetta del volume è OS.

Verifica dei file in corso (fase 1 di 5)...
818432 record di file elaborati. Verifica file completata.
1963 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 0 record EA elaborati. 71 record reparse elaborati. Verifica degli indici in corso (fase 2 di 5)...
937892 voci di indice elaborate. Verifica indici completata.


Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
818432 descrittori di protezione/SID di file elaborati. Verifica descrittori di sicurezza completata.
59731 file di dati elaborati. CHKDSK sta verificando il journal USN...
35709624 byte USN elaborati. Verifica del journal USN completata.
CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 13291850. Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato. (Nothing Found)

434142228 KB di spazio totale su disco.
379785236 KB in 635303 file.
253072 KB in 59732 indici.
936520 KB in uso dal sistema.
65536 KB occupati dal file registro.
53167400 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
108535557 unità totali di allocazione su disco.
13291850 unità di allocazione disponibili su disco.

CHKDSK eseguito in modalità lettura/scrittura.

Controllo in corso del file system su F:
Volume smontato. Tutti gli handle del volume aperti non sono più validi.
L'etichetta del volume è OS.

Verifica dei file in corso (fase 1 di 3)...
818432 record di file elaborati. Verifica file completata.
1963 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 0 record EA elaborati. 71 record reparse elaborati. Verifica degli indici in corso (fase 2 di 3)...
937892 voci di indice elaborate. Verifica indici completata.


Verifica dei descrittori di sicurezza in corso (fase 3 di 3)...
818432 descrittori di protezione/SID di file elaborati. Verifica descrittori di sicurezza completata.
59731 file di dati elaborati. CHKDSK sta verificando il journal USN...
35709192 byte USN elaborati. Verifica del journal USN completata.
Verifica del file system effettuata. Nessun problema rilevato. (Nothing Found)

434142228 KB di spazio totale su disco.
376999952 KB in 635301 file.
253072 KB in 59732 indici.
936520 KB in uso dal sistema.
65536 KB occupati dal file registro.
55952684 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
108535557 unità totali di allocazione su disco.
13988171 unità di allocazione disponibili su disco.

CHKDSK eseguito in modalità lettura/scrittura.

Controllo in corso del file system su F:
Volume smontato. Tutti gli handle del volume aperti non sono più validi.
L'etichetta del volume è OS.

Verifica dei file in corso (fase 1 di 3)...
818432 record di file elaborati. Verifica file completata.
1963 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 0 record EA elaborati. 71 record reparse elaborati. Verifica degli indici in corso (fase 2 di 3)...
937892 voci di indice elaborate. Verifica indici completata.


Verifica dei descrittori di sicurezza in corso (fase 3 di 3)...
818432 descrittori di protezione/SID di file elaborati. Pulizia di 10 voci inutilizzate dall'indice $SII del file 0x9.
Pulizia di 10 voci inutilizzate dall'indice $SDH del file 0x9.
Pulizia dei descrittori di sicurezza inutilizzati 10.
Verifica descrittori di sicurezza completata.
59731 file di dati elaborati. CHKDSK sta verificando il journal USN...
35708680 byte USN elaborati. Verifica del journal USN completata.
CHKDSK ha individuato spazio libero su disco contrassegnato come
allocato nella bitmap della Tabella file master (MFT).
CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap
CHKDSK ha individuato spazio libero su disco contrassegnato come
allocato nella mappa di bit del volume.
Correzioni apportate al file system.

434142228 KB di spazio totale su disco.
376999948 KB in 635300 file.
253072 KB in 59732 indici.
936520 KB in uso dal sistema.
65536 KB occupati dal file registro.
55952688 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
108535557 unità totali di allocazione su disco.
13988172 unità di allocazione disponibili su disco.

CHKDSK eseguito in modalità lettura/scrittura.

Controllo in corso del file system su D:
L'etichetta del volume è RECOVERY.

Verifica dei file in corso (fase 1 di 5)...
10240 record di file elaborati. Verifica file completata.
4 record di file di grandi dimensioni elaborati. 0 record file non validi elaborati. 0 record EA elaborati. 0 record reparse elaborati. Verifica degli indici in corso (fase 2 di 5)...
10328 voci di indice elaborate. Verifica indici completata.


Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
10240 descrittori di protezione/SID di file elaborati. Pulizia di 36 voci inutilizzate dall'indice $SII del file 0x9.
Pulizia di 36 voci inutilizzate dall'indice $SDH del file 0x9.
Pulizia dei descrittori di sicurezza inutilizzati 36.
Verifica descrittori di sicurezza completata.
44 file di dati elaborati. Verifica dei dati dei file in corso (fase 4 di 5))...
10224 file elaborati. Verifica dei dati del file completata.
CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 1771414. Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato. (Nothing Found)

15359999 KB di spazio totale su disco.
8197604 KB in 154 file.
64 KB in 46 indici.
76671 KB in uso dal sistema.
65536 KB occupati dal file registro.
7085660 KB disponibili su disco.

4096 byte in ogni unità di allocazione.
3839999 unità totali di allocazione su disco.
1771415 unità di allocazione disponibili su disco.

 

[Dozen]

• For the SSD: Make sure the firmware is up to date, BIOS is up to date, chipset drivers are updated, and hard disk controller drivers are installed and updated.

Everything is uptodate according to the website (video card and synaptic's driver are newer then the website)
While i updated the SSD firmware a few days ago.

• For the HDD:
  • Run the short and long tests with SeaTools.
    SeaTools for Windows
    
    SeaTools for DOS​

the tool couldn't find any drive!

Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

C:\Windows\system32>sfc /scannow

Avvio in corso dell'analisi del sistema. Attendere. L'operazione richiederà alcu
ni minuti.

Avvio in corso della fase di verifica dell'analisi del sistema.
100% della verifica completato.

Protezione risorse di Windows: nessuna violazione di integrità trovata. (Everything Ok)

C:\Windows\system32>

 

[writhziden]

Translated:

You have not installed any hardware or software in over a month? You have not removed any software in over a month?

Specified hard drive Crashes related problems and possible corruption Windows. This may be two-to-file system errors on the hard disk, but without the event viewer logs That are contained in the reports from the blue-screen instructions, it is apologetic Likely to ascertain the causes. You may have a virus, bad sectors on the hard disk, simple data corruption in memory issues, driver conflicts, files corruption, corruption or the Windows registry.

• If you are overclocking any hardware, please stop.
• Run Disk Check With Both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post your logs for the checks back after finding Them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html .
  For any drives That do not give the message:
  Windows has checked the file system and found no problems
  run check disk again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

From older to newer:

Control over the file system on C:
The file system is NTFS.

A disk check has been scheduled.
The disk check.

CHKDSK is verifying files (stage 1 of 5) ...
183040 file records processed. File verification completed.
566 large file records processed. 0 invalid file records processed. 2 EA records processed. 105 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5) ...
242938 index entries processed. Index verification completed.
0 files indexed analyzed. 0 files restored to non-indexed. Verifying security descriptors (stage 3 of 5) ...
183040 security descriptors / SID files processed. Cleaning of 3 unused entries from index $ SII of file 0x9.
Cleaning of 3 unused index entries from index $ SDH of file 0x9.
Cleaning the 3 unused security descriptors.
Security descriptor verification completed.
29950 data files processed. CHKDSK is verifying USN journal ...
36592744 USN bytes processed. Check the USN journal is complete.
Verification of file data (stage 4 of 5)) ...
183024 files processed. Check the data file is complete.
CHKDSK is verifying free space (stage 5 of 5) ...
Free clusters processed: 5532273. Free space verification is complete.
File system check performed. No issues were found. (NOTHING FOUND)

124930047 KB total disk space.
102432956 KB in 141240 files.
78440 KB in 29951 indexes.
44 KB in bad sectors.
289515 KB in use by the system.
65536 KB occupied by the log file.
22129092 KB available on disk.

4096 bytes in each allocation unit.
31232511 total allocation units on disk.
5532273 allocation units available on disk.

Inside Information:
00 cb 02 00 c0 9c 02 00 86 9e 04 00 00 00 00 00 ................
e8 02 00 00 69 00 00 00 00 00 00 00 00 00 00 00 .... i ...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Finished checking your disk.
Wait until you restart your computer.

Control over the file system on C:
The file system is NTFS.

A disk check has been scheduled.
The disk check.

CHKDSK is verifying files (stage 1 of 5) ...
183040 file records processed. File verification completed.
570 large file records processed. 0 invalid file records processed. 2 EA records processed. 105 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5) ...
247276 index entries processed. Index verification completed.
0 files indexed analyzed. 0 files restored to non-indexed. Verifying security descriptors (stage 3 of 5) ...
183040 security descriptors / SID files processed. Cleaning of 86 unused entries from index $ SII of file 0x9.
Cleaning of 86 unused index entries from index $ SDH of file 0x9.
Cleaning the 86 unused security descriptors.
Security descriptor verification completed.
32119 data files processed. CHKDSK is verifying USN journal ...
35731896 USN bytes processed. Check the USN journal is complete.
Verification of file data (stage 4 of 5)) ...
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x1d0d05000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x1d0d05000.
Can not replace bad clusters in file 56335
named \ Windows \ winsxs \ manifest ~ 2 \ ~ WO7700 1.MAN.
The read failed with status 0xC0000185 at offset 0x2000 bytes for 0x424b7a000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x424b7a000.
Can not replace bad clusters in file 67501
named \ Windows \ System32 \ CatRoot \ {F750E ~ 1 \ ~ PADB45 1.CAT.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0xf7e663000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0xf7e66d000.
Can not replace bad clusters in file 80417
the name \ of \ drivers \ R282538 \ SYSTEM ~ 1.MSI.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0xc87af9000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0xc87b05000.
Can not replace bad clusters in file 90534
named \ Users \ RS \ Desktop \ test \ DOWNLO ~ 1 \ LITTLE ~ 2.txt.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0xd0441a000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0xd04425000.
Can not replace bad clusters in file 106366
named \ Windows \ MICROS ~ 1.NET \ FRAMEW ~ 2 \ V40 ~ 1,303 \ SQL \ en \ ~ TRACKI 1.SQL.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0x19291c000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x19292b000.
Can not replace bad clusters in file 108195
named \ Windows \ INSTAL ~ 1 \ PATCH $ ~ 1 \ Managed \ 000041 ~ 3 \ 14.0.4763 \ OARTCONV.DLL.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0x4c178f000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x4c179d000.
Can not replace bad clusters in file 123708
named \ Users \ RS \ Music \ iTunes \ ITUNES ~ 1 \ MOBILE ~ 1 \ ~ SONICR 1.IPA.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0x5a3a75000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x5a3a79000.
Can not replace bad clusters in file 128125
named \ Windows \ winsxs \ AM788E 1,205 ~ \ ieframe.dll.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0x564de7000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x564dea000.
Can not replace bad clusters in file 131143
named \ Windows \ winsxs \ AMD64_ 2,205 ~ \ ieframe.dll.
The read failed with status 0xC0000185 for 0x10000 bytes at offset 0x716e0e000.
The read failed with status 0xC0000185 at offset 0x1000 bytes for 0x716e16000.
Can not replace bad clusters in file 158125
named \ Windows \ INSTAL ~ 1 \ PATCH $ ~ 1 \ Managed \ 000041 ~ 3 \ 14.0.4763 \ ACEWDAT.DLL.
183024 files processed. Check the data file is complete.
CHKDSK is verifying free space (stage 5 of 5) ...
Free clusters processed: 5423157. Free space verification is complete.
Adding 10 bad clusters to the Bad Clusters File
(Added 10 damaged cluster to cluster the damaged file)
Correcting errors in the bit map of the volume.
Corrections made to the file system.

124930047 KB total disk space.
102869688 KB in 144780 files.
78684 KB in 32120 indexes.
44 KB in bad sectors.
289003 KB in use by the system.
65536 KB occupied by the log file.
21692628 KB available on disk.

4096 bytes in each allocation unit.
31232511 total allocation units on disk.
5423157 allocation units available on disk.

Inside Information:
Cb 00 02 00 02 00 0d b3 b4 c7 04 00 00 00 00 00 ................
e8 02 00 00 69 00 00 00 00 00 00 00 00 00 00 00 .... i ...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Finished checking your disk.
Wait until you restart your computer.

Run CHKDSK in read / write.

Control over the file system on D:
The volume label is RECOVERY.

CHKDSK is verifying files (stage 1 of 5) ...
10240 file records processed. File verification completed.
4 records of large files processed. 0 invalid file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5) ...
10330 index entries processed. Index verification completed.


Verifying security descriptors (stage 3 of 5) ...
10240 security descriptors / SID files processed. Security descriptor verification completed.
45 data files processed. Verification of file data (stage 4 of 5)) ...
10224 files processed. Check the data file is complete.
CHKDSK is verifying free space (stage 5 of 5) ...
Free clusters processed: 1771414. Free space verification is complete.
File system check performed. No issues were found. (Nothing Found)

15359999 KB total disk space.
8197608 KB in 155 files.
64 KB in 47 indexes.
76671 KB in use by the system.
65536 KB occupied by the log file.
7085656 KB available on disk.

4096 bytes in each allocation unit.
3839999 total allocation units on disk.
1771414 allocation units available on disk.

Run CHKDSK in read-only mode in a volume snapshot.

Control over the file system on F:
Volume label is OS.

CHKDSK is verifying files (stage 1 of 5) ...
818432 file records processed. File verification completed.
1963 record large files processed. 0 invalid file records processed. 0 EA records processed. 71 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5) ...
937892 index entries processed. Index verification completed.


Verifying security descriptors (stage 3 of 5) ...
818432 security descriptors / SID files processed. Security descriptor verification completed.
59731 data files processed. CHKDSK is verifying USN journal ...
35709624 USN bytes processed. Check the USN journal is complete.
CHKDSK is verifying free space (stage 5 of 5) ...
Free clusters processed: 13291850. Free space verification is complete.
File system check performed. No issues were found. (Nothing Found)

434142228 KB total disk space.
379785236 KB in 635303 files.
253072 KB in 59732 indexes.
936520 KB in use by the system.
65536 KB occupied by the log file.
53167400 KB available on disk.

4096 bytes in each allocation unit.
108535557 total allocation units on disk.
13291850 allocation units available on disk.

Run CHKDSK in read / write.

Control over the file system on F:
Volume dismounted. All open handles to the volume are no longer valid.
Volume label is OS.

CHKDSK is verifying files (stage 1 of 3) ...
818432 file records processed. File verification completed.
1963 record large files processed. 0 invalid file records processed. 0 EA records processed. 71 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3) ...
937892 index entries processed. Index verification completed.


Verifying security descriptors (stage 3 of 3) ...
818432 security descriptors / SID files processed. Security descriptor verification completed.
59731 data files processed. CHKDSK is verifying USN journal ...
35709192 USN bytes processed. Check the USN journal is complete.
File system check performed. No issues were found. (Nothing Found)

434142228 KB total disk space.
376999952 KB in 635301 files.
253072 KB in 59732 indexes.
936520 KB in use by the system.
65536 KB occupied by the log file.
55952684 KB available on disk.

4096 bytes in each allocation unit.
108535557 total allocation units on disk.
13988171 allocation units available on disk.

Run CHKDSK in read / write.

Control over the file system on F:
Volume dismounted. All open handles to the volume are no longer valid.
Volume label is OS.

CHKDSK is verifying files (stage 1 of 3) ...
818432 file records processed. File verification completed.
1963 record large files processed. 0 invalid file records processed. 0 EA records processed. 71 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3) ...
937892 index entries processed. Index verification completed.


Verifying security descriptors (stage 3 of 3) ...
818432 security descriptors / SID files processed. Cleaning of 10 unused index entries from $ SII of file 0x9.
Cleaning of 10 unused index entries from index $ SDH of file 0x9.
Cleaning the 10 unused security descriptors.
Security descriptor verification completed.
59731 data files processed. CHKDSK is verifying USN journal ...
35708680 USN bytes processed. Check the USN journal is complete.
CHKDSK discovered free space marked as
allocated in the bitmap of the Master File Table (MFT).
CHKDSK Discovered Allocated free space marked as in the master file table (MFT) bitmap
CHKDSK discovered free space marked as
allocated in the bit map of the volume.
Corrections made to the file system.

434142228 KB total disk space.
376999948 KB in 635300 files.
253072 KB in 59732 indexes.
936520 KB in use by the system.
65536 KB occupied by the log file.
55952688 KB available on disk.

4096 bytes in each allocation unit.
108535557 total allocation units on disk.
13988172 allocation units available on disk.

Run CHKDSK in read / write.

Control over the file system on D:
The volume label is RECOVERY.

CHKDSK is verifying files (stage 1 of 5) ...
10240 file records processed. File verification completed.
4 records of large files processed. 0 invalid file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5) ...
10328 index entries processed. Index verification completed.


Verifying security descriptors (stage 3 of 5) ...
10240 security descriptors / SID files processed. Cleaning of 36 unused entries from index $ SII of file 0x9.
Cleaning of 36 unused index entries from index $ SDH of file 0x9.
Cleaning the 36 unused security descriptors.
Security descriptor verification completed.
44 data files processed. Verification of file data (stage 4 of 5)) ...
10224 files processed. Check the data file is complete.
CHKDSK is verifying free space (stage 5 of 5) ...
Free clusters processed: 1771414. Free space verification is complete.
File system check performed. No issues were found. (Nothing Found)

15359999 KB total disk space.
8197604 KB in 154 files.
64 KB in 46 indexes.
76671 KB in use by the system.
65536 KB occupied by the log file.
7085660 KB available on disk.

4096 bytes in each allocation unit.
3839999 total allocation units on disk.
1771415 allocation units available on disk.

Assuming the no problems occurred after fixing the problems, this looks good. One thing, though: C: had some bad sectors, so you should run disk checks on it once a week for a while and make sure you backup any important data on a very regular basis (at least once a week) in case the drive fails. Bad sectors can indicate the drive is starting to fail.

 

[Dozen]

Assuming the no problems occurred after fixing the problems, this looks good. One thing, though: C: had some bad sectors, so you should run disk checks on it once a week for a while and make sure you backup any important data on a very regular basis (at least once a week) in case the drive fails. Bad sectors can indicate the drive is starting to fail.

holy *, this disk is pretty new! no more than six months!

 

[writhziden]

Is the C: drive your SSD? I would think it would be, but your setup is a bit confusing.

 

[Dozen]

it is!

 

[writhziden]

My instructions were to run only the Automaticall fix file system errors for your SSD... I am confused why bad sectors would be found on an SSD, though. I have read that repairing bad sectors is unnecessary on SSDs and a step that will minutely shorten its lifespan (by a couple hours out of many years, so nothing to be concerned about so long as you do not do it on a regular basis). I will see if I can find some help from people who have an SSD; I do not have one, so I do not know if it is normal to find bad sectors on one.