Windows 10: Windows 10 BSOD caused by SnippingTool.exe ?!

Discus and support Windows 10 BSOD caused by SnippingTool.exe ?! in Windows 10 BSOD Crashes and Debugging to solve the problem; The Win10 Snipping Tool seems to be blue-screening several of our PCs! Any ideas why? Dump log below: Microsoft (R) Windows Debugger Version... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Matt_Parry, Feb 1, 2019.

  1. MATT_PARRY
    Matt_Parry Win User

    Windows 10 BSOD caused by SnippingTool.exe ?!


    The Win10 Snipping Tool seems to be blue-screening several of our PCs!

    Any ideas why?

    Dump log below:


    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Temp\Dump Files\TG-JRF2402\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 17134 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17134.1.amd64fre.rs4_release.180410-1804
    Machine Name:
    Kernel base = 0xfffff802`46207000 PsLoadedModuleList = 0xfffff802`465b5150
    Debug session time: Fri Feb 1 10:16:45.928 2019 (UTC + 0:00)
    System Uptime: 0 days 23:31:07.163
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000031`6f063018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ...........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A****024629e3ca}

    Probably caused by : win32kfull.sys ( win32kfull!DwmSyncCaptureSurfaceBits+112 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffffb8821df03148, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8024629e3ca, address which referenced memory

    Debugging Details:
    ------------------


    KEY_VALUES_STRING: 1


    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: HP

    SYSTEM_PRODUCT_NAME: HP 290 G1 SFF Business PC

    SYSTEM_SKU: 3ZD97EA#ABU

    BIOS_VENDOR: AMI

    BIOS_VERSION: F.01

    BIOS_DATE: 03/15/2018

    BASEBOARD_MANUFACTURER: HP

    BASEBOARD_PRODUCT: 843F

    BASEBOARD_VERSION: 00

    DUMP_TYPE: 1

    BUGCHECK_P1: ffffb8821df03148

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8024629e3ca

    READ_ADDRESS: ffffb8821df03148 Nonpaged pool

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!KiSwapThread+2ca
    fffff802`4629e3ca 488bbbc8000000 mov rdi,qword ptr [rbx+0C8h]

    CPU_COUNT: 6

    CPU_MHZ: bb8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)


    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: SnippingTool.exe

    ANALYSIS_SESSION_HOST: TH-JRF1413

    ANALYSIS_SESSION_TIME: 02-01-2019 10:27:15.0606

    ANALYSIS_VERSION: 10.0.17763.132 amd64fre

    TRAP_FRAME: ffff8987d362ac80 -- (.trap 0xffff8987d362ac80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000316f064000 rbx=0000000000000000 rcx=ffff8987d362add0
    rdx=0000000000000031 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8024629e3ca rsp=ffff8987d362ae10 rbp=0000000000000000
    r8=fffff80244d7f180 r9=0000000008000000 r10=ffffb88211e6a080
    r11=fffff80244d7f180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    nt!KiSwapThread+0x2ca:
    fffff802`4629e3ca 488bbbc8000000 mov rdi,qword ptr [rbx+0C8h] ds:00000000`000000c8=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff802463c1c69 to fffff802463b10c0

    STACK_TEXT:
    ffff8987`d362ab38 fffff802`463c1c69 : 00000000`0000000a ffffb882`1df03148 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffff****7`00000000 ffffb882`11f03080 ffffa707`d01cf2d0 00000000`00000000 : nt!KiPageFault+0x425
    ffff****7`00000000 ffff9100`a44c4100 ffffb882`11f031c0 : nt!KiCommitThreadWait+0x13b
    ffff8987`d362af80 fffff802`4629322b : ffffb882`11f036c8 00000000`00000011 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x1ff
    ffff8987`d362b060 fffff802`466e5e26 : 00000000`00000000 ffffb882`11f036c8 ffffb882`11f03080 fffff802`463b7d66 : nt!AlpcpSignalAndWait+0x17b
    ffff8987`d362b100 fffff802`466e5aa2 : ffffb882`186ff190 00000000`00000000 ffff8987`d362b420 00000000`00000000 : nt!AlpcpReceiveSynchronousReply+0x56
    ffff8987`d362b160 fffff802`4679642e : ffffb882`186ff190 00000000`00020002 ffff8987`d362b340 00000000`00000000 : nt!AlpcpProcessSynchronousRequest+0x372
    ffff8987`d362b280 fffff802`467962f9 : 00000000`00000000 ffff8987`d362b6b8 ffffb882`186ff190 ffffb882`11f03180 : nt!LpcpRequestWaitReplyPort+0x86
    ffff8987`d362b2e0 ffff****8 00000000`00000000 : win32kfull!DwmSyncCaptureSurfaceBits+0x112
    ffff8987`d362b650 ffff849a`9fa5e8ea : 00000000`ffffffff ffff84c1`8018fae0 00000000`00000000 00000000`00000000 : win32kfull!bSpDwmUpdateSurface+0x135
    ffff**** : 00000000`00003000 00000004`00001000 00000000`00000000 00000000`00000000 : win32kfull!GreStretchBltInternal+0x15c
    ffff8987`d362bd50 fffff802`463c1743 : ffffffff`ffffffff ffffb882`11f03080 00000000`00000000 00000031`6f27e4b8 : win32kfull!NtGdiStretchBlt+0x68
    ffff8987`d362bdd0 00007ffc`ab7516a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000031`6f27e728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ab7516a4


    THREAD_SHA1_HASH_MOD_FUNC: 97536b7f70c570ca2f79c4a7978521e1445c3074

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9ea354e8731979ab38a0b9bb2e7ab4818efe9931

    THREAD_SHA1_HASH_MOD: c2b2bc6e094ba248936b0a6fb3cab24808f5abf7

    FOLLOWUP_IP:
    win32kfull!DwmSyncCaptureSurfaceBits+112
    ffff849a`9fa3edd6 8bc8 mov ecx,eax

    FAULT_INSTR_CODE: 8d48c88b

    SYMBOL_STACK_INDEX: b

    SYMBOL_NAME: win32kfull!DwmSyncCaptureSurfaceBits+112

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32kfull

    IMAGE_NAME: win32kfull.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 112

    FAILURE_BUCKET_ID: AV_win32kfull!DwmSyncCaptureSurfaceBits

    BUCKET_ID: AV_win32kfull!DwmSyncCaptureSurfaceBits

    PRIMARY_PROBLEM_CLASS: AV_win32kfull!DwmSyncCaptureSurfaceBits

    TARGET_TIME: 2019-02-01T10:16:45.000Z

    OSBUILD: 17134

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2019-01-09 08:11:19

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME: 69d

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_win32kfull!dwmsynccapturesurfacebits

    FAILURE_ID_HASH: {27021fab-aa14-e3fa-b7c5-eeb9292ae3ec}

    Followup: MachineOwner
    ---------

    :)
     
    Matt_Parry, Feb 1, 2019
    #1
  2. SEBASTIAN42
    Sebastian42 Win User

    Keeping snippingtool snip ready


    Right-clicking for context menu and then selecting snippingtool and then clicking NEW, is 3 steps, instead of the one click on Snippingtool that Win7 allowed, and that I want to reproduce. In the context menu of the snippingtool icon in the open snippingtool window, there is a 'pin to desktop' option - which would satisfy me if that was pinned was the open window, but actually not even a shortcut gets pinned to the desktop - and even if it did, that is no better to me, because it would still take two clicks before capture area can be selected.
     
    Sebastian42, Feb 1, 2019
    #2
  3. AHHZZ
    Ahhzz Win User
    Windows 10 Tweaks

    Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

    Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

    • Open a new Explorer window.
    • Click View in the ribbon.
    • Click Options.
    • Under General, next to “Open File Explorer to:” choose “This PC.”
    • Click OK


    credit to Lifehacker.
     
    Ahhzz, Feb 1, 2019
    #3
  4. MANUELMOTA BOZA
    ManuelMota Boza Win User

    Windows 10 BSOD caused by SnippingTool.exe ?!

    SnippingTool

    I can not save SnippingTool capture in Windows 10 can i do to recover it?

    When I press save, it does not open the popup window to save the capture

    When pulse save as, does not open the popup window to save the capture

    To the question do you want to save the changes in cutouts? Do not keep them either
     
    ManuelMota Boza, Feb 1, 2019
    #4
Thema:

Windows 10 BSOD caused by SnippingTool.exe ?!

Loading...

  1. Windows 10 BSOD caused by SnippingTool.exe ?! - Similar Threads - BSOD caused SnippingTool

  2. RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

    in Windows 10 Gaming
    RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD: Recently I have been getting the exact same BSOD and fixes on the net doesn't seem to work. I've taken a look at the Reliability Monitor to see what was causing the same BSOD over and over again, and it seems like RAVBg64.execrashing is the main issue. I've tried disabling...

  3. RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

    in Windows 10 Software and Apps
    RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD: Recently I have been getting the exact same BSOD and fixes on the net doesn't seem to work. I've taken a look at the Reliability Monitor to see what was causing the same BSOD over and over again, and it seems like RAVBg64.execrashing is the main issue. I've tried disabling...

  4. RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

    in Windows 10 Drivers and Hardware
    RAVBg64.exe APPCRASH causing DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD: Recently I have been getting the exact same BSOD and fixes on the net doesn't seem to work. I've taken a look at the Reliability Monitor to see what was causing the same BSOD over and over again, and it seems like RAVBg64.execrashing is the main issue. I've tried disabling...

  5. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...

  6. Windows 10 1903 causes BSOD

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 1903 causes BSOD: A few months ago after upgrading to Windows 10 1903, I was getting BSOD at a very high frequency (several times a day). They would happen at any moment. I got some on the login screen, when opening the windows menu, when playing games, when browsing the internet, or when...

  7. rundll32.exe causes heavy problems

    in Windows 10 BSOD Crashes and Debugging
    rundll32.exe causes heavy problems: Hi everyone, It's simply impossible to work fluently without been stopped, because of this process. All rundll32 processes in Task Manager point to the same process in system32. Many antivirus softwares have been tried, but nothing found. System info: Lenovo yoga with i7...

  8. Windows 10 BSOD Caused by mcupdate_GenuineIntel.dll?

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 BSOD Caused by mcupdate_GenuineIntel.dll?: The last major change I did on my computer was update my graphics card drivers but that doesn't seem to be the problem. I did update my bios a while back and had BSOD problems due to the gigabyte software but I've since removed it and haven't had any issues in a while. 46085

  9. Keeping snippingtool snip ready

    in Windows 10 Software and Apps
    Keeping snippingtool snip ready: I miss the one-click snippingtool of Win7. In my attempt to reproduce that readiness-to-snip in Win10, I let a batch file launch snippingtool at Windows boot, so that when I want to use it, I just click on NEW in the open snippingtool. That works brilliantly ONCE, because,...

  10. Make SnippingTool under Windows 10 work as under Windows 7

    in Windows 10 Software and Apps
    Make SnippingTool under Windows 10 work as under Windows 7: I've been using Windows Snipping Tool since Windows 7 to quickly capture screenshots of parts of the screen. But now on Windows 10 it doesn't work the same way. Say, when I click its icon, on Windows 7 the Snipping Tool would let me select the region to make a snapshot...