none
Windows shut down unexpectedly RRS feed

  • Question

  • Windows stopped working
    Description
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffbf8c1c9c5640, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fe835104-de19-4066-bb60-24eb74b33495.
    which is followed by
    Shut down unexpectedly
    Problem signature
    Problem Event Name: BlueScreen
    Code: ef
    Parameter 1: ffffbf8c1c9c5640
    Parameter 2: 0
    Parameter 3: 0
    Parameter 4: 0
    OS version: 10_0_15063
    Service Pack: 0_0
    Product: 768_1
    OS Version: 10.0.15063.2.0.0.768.101
    Locale ID: 16393
    and
    windows moduler installer worker stopped working
    Description
    Faulting Application Path: C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.15063.410_none_9e914f9d2d85dacb\TiWorker.exe
    Problem signature
    Problem Event Name: APPCRASH
    Application Name: TiWorker.exe
    Application Version: 10.0.15063.0
    Application Timestamp: 38cb1f7b
    Fault Module Name: StackHash_4df5
    Fault Module Version: 10.0.15063.0
    Fault Module Timestamp: b79b6ddb
    Exception Code: c0000374
    Exception Offset: PCH_59_FROM_ntdll+0x00000000000A5F04
    OS Version: 10.0.15063.2.0.0.768.101
    Locale ID: 16393
    Additional Information 1: 4df5
    Additional Information 2: 4df5ba479d56fcb136b811bbef0a316d
    Additional Information 3: 3208
    Additional Information 4: 3208e598dac3d5b7aeed8c19f48af1f9
    Extra information about the problem
    Bucket ID: dbef0d80f21aba61d24d1e68c754c67e (120731279307)
    I had run troubleshooter but it could not identify any error
    -------------------------------------------------------------------------------
    It has been starting since yesterday after installing Utorrent & Microsoft update assistant program.
    Uninstallation done, there is a problem in resetting the PC it shows while trying to do the same
    ----------------------------------------------------------------------------------
    SFC scan show
    "Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios."
    -----------------------------------------------------------------------------------------
    Run win crash ,here is the report
    On Thu 29-Jun-17 8:45:46 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062917-26296-01.dmp
    This was probably caused by the following module: win32kfull.sys (win32kfull+0x1FBD7)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF7518C01FBD7, 0xFFFFB1805398D140, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\win32kfull.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Full/Desktop Win32k Kernel Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Thu 29-Jun-17 8:45:46 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: win32kfull.sys (win32kfull!NtGdiBitBlt+0x8A7)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF7518C01FBD7, 0xFFFFB1805398D140, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\win32kfull.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Full/Desktop Win32k Kernel Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
    On Thu 29-Jun-17 12:18:35 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062917-41062-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803CCE83A75, 0xFFFFCD8037CF6CF0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    On Wed 28-Jun-17 6:09:25 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\062817-27281-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
    Bugcheck code: 0xEF (0xFFFFBF8C1C9C5640, 0x0, 0x0, 0x0)
    Error: CRITICAL_PROCESS_DIED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a critical system process died.
    There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Saturday, July 1, 2017 6:04 AM