1. #1

    volsnap.sys Black Screen of Death

    Good afternoon, my english is not that good but will try to explain everything i can.

    Windows 7 Ultimate x64 SP1
    4gb ram
    MSI H61M-P31(G3) last bios version installed 2.7

    After being affected by malware i lost the control of my pc, ran many programs to fix this.

    Adwcleaner till no infections detected
    Malwarebytes till no infections detected
    SuperAntispyware till no infections detected
    Uninstall my antivirus (panda free antivirus) because it was not working well (run always in desactivate mode)

    after I uninstall the antivirus I reboot the pc and then came this problem:

    volsnap.sys with a black window, hit the enter button and pc reset and again happen the same thing, so next time I try F8 option to run pc in safe mode, and volsnap.sys error again, try Good Last Known Configuration option and same thing, so bring my Win 7 installation dvd and enter in the automatic repair mode, did nothing, try to restore and there were none copies stored this was rare because i remembered some restore points being made.


    so the next step was command line,
    chkdsk /r
    and everything is fine
    i ran sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
    some corruptions came up but i couldn't see them for obvious reasons.
    restart and the error was still there, so my next step was asking a friend with a same OS Win 7 Ultimate x64 to take from his %windir%\system32\drivers\volsnap.sys the file i needed, i did and then rename the one in my path as "volsnap.bad" and introduce this "good" volsnap.sys, restart and then the glory my windows works and i was able to going desktop,
    update win 7 with windows update till no remaining updates were shown
    run SFC and still errors, create a sfcdetails.txt in my desktop out of cbs.log with the command:
    findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
    and still were corruptions, try dism but error 193 came up
    try SfcFix 3.0 but was not able to repair any of the problems and still one of the problems was the volsnap.sys (so it was not repaired like i thought? i dont know)
    computers works well but still sometimes freezes out the blue with no warnings, and sometimes when i switch on my pc the volsnap.sys error appears sometimes dont and my only wildcard when appear is to use F8 and use the last known good configuration to be able to use it till it freeze again.
    Investigate about volsnap.sys...something related to shadow volume copies so in the meantime i switched off the system restore option just in case it was the culprit of my freezes..will add all files i think you will need, if you need anything else please ask. Thank you in advance for helping me.

    zip containing:
    cbs.log
    sfcdetails.txt
    dism.log
    SFCFix.txt
    volsnap.bad
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Hello and welcome!

    SFCFix Script

    Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



    1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
    2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
    3. Save any open documents and close all open windows.
    4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
    5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
    6. SFCFix will now process the script.
    7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
    8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.






    SFC Scan



    1. Click on the Start button and in the search box, type Command Prompt
    2. When you see Command Prompt on the list, right-click on it and select Run as administrator
    3. When command prompt opens, copy and paste the following commands into it, press enter after each

      sfc /scannow

      Wait for this to finish before you continue

      copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
    4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
    Attached Files Attached Files
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  3. #3

    Re: volsnap.sys Black Screen of Death

    Hello softwaremaniac thanks for helping me, i follow the instructions and these are the results:
    SFCFix version 3.0.0.0 by niemiro.Start time: 2018-09-15 08:47:05.787
    Microsoft Windows 7 Service Pack 1 - amd64
    Using .zip script file at C:\Users\Zero01\Desktop\SFCFix.zip [0]








    PowerCopy::
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-wsd-challengecomponent_31bf3856ad364e35_6.1.7601.17514_none_829daeb2b9f491ba\wsdchngr.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-sx-shared_31bf3856ad364e35_6.1.7600.16385_none_9498b282333b64ec\sxshared.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-storprop_31bf3856ad364e35_6.1.7600.16385_none_8247a61e4a9abc04\Storprop.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-pnpui_31bf3856ad364e35_6.1.7600.16385_none_bacc830144fa7791\dinotify.exe
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\Photo.gmmp
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-f..-tolerant-heap-core_31bf3856ad364e35_6.1.7600.16385_none_9b4769d327134efe\fthsvc.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragsvc.dll


    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf to C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-wsd-challengecomponent_31bf3856ad364e35_6.1.7601.17514_none_829daeb2b9f491ba\wsdchngr.dll to C:\windows\winsxs\amd64_microsoft-windows-wsd-challengecomponent_31bf3856ad364e35_6.1.7601.17514_none_829daeb2b9f491ba\wsdchngr.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-sx-shared_31bf3856ad364e35_6.1.7600.16385_none_9498b282333b64ec\sxshared.dll to C:\windows\winsxs\amd64_microsoft-windows-sx-shared_31bf3856ad364e35_6.1.7600.16385_none_9498b282333b64ec\sxshared.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-storprop_31bf3856ad364e35_6.1.7600.16385_none_8247a61e4a9abc04\Storprop.dll to C:\windows\winsxs\amd64_microsoft-windows-storprop_31bf3856ad364e35_6.1.7600.16385_none_8247a61e4a9abc04\Storprop.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll to C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-pnpui_31bf3856ad364e35_6.1.7600.16385_none_bacc830144fa7791\dinotify.exe to C:\windows\winsxs\amd64_microsoft-windows-pnpui_31bf3856ad364e35_6.1.7600.16385_none_bacc830144fa7791\dinotify.exe.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\Photo.gmmp to C:\windows\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\Photo.gmmp.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-f..-tolerant-heap-core_31bf3856ad364e35_6.1.7600.16385_none_9b4769d327134efe\fthsvc.dll to C:\windows\winsxs\amd64_microsoft-windows-f..-tolerant-heap-core_31bf3856ad364e35_6.1.7600.16385_none_9b4769d327134efe\fthsvc.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll to C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragsvc.dll to C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragsvc.dll.


    Successfully restored ownership for C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully restored permissions on C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-wsd-challengecomponent_31bf3856ad364e35_6.1.7601.17514_none_829daeb2b9f491ba\wsdchngr.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-wsd-challengecomponent_31bf3856ad364e35_6.1.7601.17514_none_829daeb2b9f491ba\wsdchngr.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-sx-shared_31bf3856ad364e35_6.1.7600.16385_none_9498b282333b64ec\sxshared.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-sx-shared_31bf3856ad364e35_6.1.7600.16385_none_9498b282333b64ec\sxshared.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-storprop_31bf3856ad364e35_6.1.7600.16385_none_8247a61e4a9abc04\Storprop.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-storprop_31bf3856ad364e35_6.1.7600.16385_none_8247a61e4a9abc04\Storprop.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-pnpui_31bf3856ad364e35_6.1.7600.16385_none_bacc830144fa7791\dinotify.exe
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-pnpui_31bf3856ad364e35_6.1.7600.16385_none_bacc830144fa7791\dinotify.exe
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\Photo.gmmp
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\Photo.gmmp
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-f..-tolerant-heap-core_31bf3856ad364e35_6.1.7600.16385_none_9b4769d327134efe\fthsvc.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-f..-tolerant-heap-core_31bf3856ad364e35_6.1.7600.16385_none_9b4769d327134efe\fthsvc.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragsvc.dll
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragsvc.dll
    PowerCopy:: directive completed successfully.








    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 12 datablocks.
    Finish time: 2018-09-15 08:47:07.597
    Script hash: NDqCXJ6ccRSrZDI3nCYcwBqqyuQtwLnB7SaLXM0lOGU=
    ----------------------EOF-----------------------
    and the cbs.log still shows corruptions, here is the log:
    Dropbox - cbs.log

    if you need anything else please ask.

  4. #4
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Is this a Spanish system?
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  5. #5

    Re: volsnap.sys Black Screen of Death

    Yes, it's spanish but not spain it's spanish mexico(just in case)

  6. #6
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Oh, I see. This will take a while, because I have to create a custom VM. Please be patient.
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  7. #7

    Re: volsnap.sys Black Screen of Death

    dont worry, take your time and thank you again for helping me.

  8. #8
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    SFCFix Script

    Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.




    1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
    2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
    3. Save any open documents and close all open windows.
    4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
    5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
    6. SFCFix will now process the script.
    7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
    8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put tags around the log to break up the text.







    SFC Scan




    1. Click on the Start button and in the search box, type Command Prompt
    2. When you see Command Prompt on the list, right-click on it and select Run as administrator
    3. When command prompt opens, copy and paste the following commands into it, press enter after each

      sfc /scannow

      Wait for this to finish before you continue

      copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
    4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
    Attached Files Attached Files
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  9. #9

    Re: volsnap.sys Black Screen of Death

    Ok here are the logs:
    SFCFix version 3.0.0.0 by niemiro.Start time: 2018-09-17 13:17:33.626
    Microsoft Windows 7 Service Pack 1 - amd64
    Using .zip script file at C:\Users\Zero01\Desktop\SFCFix.zip [0]








    PowerCopy::
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volsnap.sys
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-s..p-service.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ae4cba00bf654c47\snmptrap.exe.mui
    Successfully took permissions for file or folder C:\windows\winsxs\amd64_microsoft-windows-p..oler-core.resources_31bf3856ad364e35_6.1.7600.16385_es-es_8397ae911b4db071\spoolsv.exe.mui


    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volsnap.sys to C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volsnap.sys.
    WARNING: File C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf was not backed up as that would replace the current backup.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf to C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-s..p-service.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ae4cba00bf654c47\snmptrap.exe.mui to C:\windows\winsxs\amd64_microsoft-windows-s..p-service.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ae4cba00bf654c47\snmptrap.exe.mui.
    Successfully copied file C:\Users\Zero01\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-p..oler-core.resources_31bf3856ad364e35_6.1.7600.16385_es-es_8397ae911b4db071\spoolsv.exe.mui to C:\windows\winsxs\amd64_microsoft-windows-p..oler-core.resources_31bf3856ad364e35_6.1.7600.16385_es-es_8397ae911b4db071\spoolsv.exe.mui.


    Successfully restored ownership for C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volsnap.sys
    Successfully restored permissions on C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volsnap.sys
    Successfully restored ownership for C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully restored permissions on C:\windows\winsxs\amd64_volume.inf_31bf3856ad364e35_6.1.7601.17514_none_73dcbcf012b4850e\volume.inf
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-s..p-service.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ae4cba00bf654c47\snmptrap.exe.mui
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-s..p-service.resources_31bf3856ad364e35_6.1.7600.16385_es-es_ae4cba00bf654c47\snmptrap.exe.mui
    Successfully restored ownership for C:\windows\winsxs\amd64_microsoft-windows-p..oler-core.resources_31bf3856ad364e35_6.1.7600.16385_es-es_8397ae911b4db071\spoolsv.exe.mui
    Successfully restored permissions on C:\windows\winsxs\amd64_microsoft-windows-p..oler-core.resources_31bf3856ad364e35_6.1.7600.16385_es-es_8397ae911b4db071\spoolsv.exe.mui
    PowerCopy:: directive completed successfully.








    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 15 datablocks.
    Finish time: 2018-09-17 13:17:34.296
    Script hash: Z2FweJjOHKznqBU8yBH5XK7Tx9dVyK83ZUNrg9Vp8rg=
    ----------------------EOF-----------------------
    still sfc shows corruptions that were not repaired, here is the log
    Dropbox - cbs.log

    Edit. could not found any phrase with "Cannot" in all the cbs.log but the message after sfc /scannow finish was the classic "found missing or corrupt files but couldn't repair them" that's why I said "still sfc shows corruptions..."

  10. #10
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Are KB3121461 and KB2952664 installed on the system?
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  11. #11

    Re: volsnap.sys Black Screen of Death

    Yes, both are installed
    volsnap.sys Black Screen of Death-kb2952664-jpgvolsnap.sys Black Screen of Death-kb3121461-jpg

  12. #12
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Please try uninstalling them, but make sure you uninstall KB3121461 first. If required to reboot, please do so.
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  13. #13

    Re: volsnap.sys Black Screen of Death

    Uninstall the first KB(KB3121461) and reboot, and the volsnap error(black screen of death) came up after the presentation window of the motherboard(MSI), need to use F8 to select "Last Good Known Configuration" to be able to boot windows and desktop shows, uninstall the second KB(KB2952664), now both are uninstall, what's the next step?
    volsnap.sys Black Screen of Death-volsnap-error-jpg

  14. #14
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Install any important updates that are offered.
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  15. #15

    Re: volsnap.sys Black Screen of Death

    what KB's updates should i avoid? (KB3121461, KBKB2952664) any other that shouldn't be in my pc?

  16. #16
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    KB2952664 is needed only if you want to upgrade to Win10.
    Hrimpursar says thanks for this.


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

  17. #17

    Re: volsnap.sys Black Screen of Death

    Ok, sorry for not answering or give you feedback in a while, i desist of any attempt of repairing, I will format the hdd and begin from scratch.

    the problem was after every update volsnap.sys error with black screen of death came too often between reboots of win update, and sometimes need to replace the file(volsnap.sys) from another pc to be able to boot again and continue updating windows, it was hell, you can closed the thread and mark it as solved.

    Thank you for your help.

  18. #18
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,282
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1803 x64

    Re: volsnap.sys Black Screen of Death

    Thanks for letting me know! Take care!


    If I haven't replied to your thread within 48 hours, please send me a Personal Message.

Similar Threads

  1. Replies: 3
    Last Post: 09-25-2017, 12:28 AM
  2. Replies: 4
    Last Post: 08-04-2015, 08:32 PM
  3. Replies: 78
    Last Post: 06-26-2015, 08:51 AM
  4. Black screen of death?
    By r4kolb in forum Windows 7 | Windows Vista
    Replies: 128
    Last Post: 03-15-2014, 06:56 AM

Log in

Log in