BSOD right after restarting for windows update


  1. Posts : 4
    Windows 7
       #1

    BSOD right after restarting for windows update


    Hello,
    Right after restarting the windows for completing the windows update, BSOD happend.
    The updates were for Office 2013 and also there is an update which won't install and published yesterday "Security Update for Microsoft Office 2013 (KB2810009) 64-Bit Edition" and already there are lots of thread about it.
    Thanks for your assisting
      My Computer

  2.    #2

    For the Windows Update issue, I would start a new thread here - Windows Updates & Activation - Windows 7 Help Forums

    Code:
    BugCheck F4, {3, fffffa800ae66b30, fffffa800ae66e10, fffff8000337e0d0}
    
    ----- ETW minidump data unavailable-----
    Probably caused by : csrss.exe
    Code:
    0: kd> !process fffffa800ae66b30 3
    GetPointerFromAddress: unable to read from fffff800032af000
    PROCESS fffffa800ae66b30
        SessionId: none  Cid: 0278    Peb: 7fffffdd000  ParentCid: 024c
        DirBase: 1e5bc0000  ObjectTable: fffff8a00adae470  HandleCount: <Data Not Accessible>
        Image: csrss.exe
        VadRoot fffffa800b8b4290 Vads 145 Clone 0 Private 571. Modified 1705. Locked 0.
        DeviceMap fffff8a000008aa0
        Token                             fffff8a00adb6060
        ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    fffff78000000000: Unable to get shared data
        ElapsedTime                       00:00:00.000
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.000
        QuotaPoolUsage[PagedPool]         174264
        QuotaPoolUsage[NonPagedPool]      17408
        Working Set Sizes (now,min,max)  (1394, 50, 345) (5576KB, 200KB, 1380KB)
        PeakWorkingSetSize                8816
        VirtualSize                       50 Mb
        PeakVirtualSize                   63 Mb
        PageFaultCount                    118117
        MemoryPriority                    BACKGROUND
        BasePriority                      13
        CommitCharge                      795
    Code:
    0: kd> !dpx
    Start memory scan  : 0xfffff8800c7bc738 ($csp)
    End memory scan    : 0xfffff8800c7be000 (Stack Base)
    
                   rax : 0xfffff8800c7bc7c8 : 0xfffff80003331ec4 : nt!NtTerminateProcess+0xf4
                   rsp : 0xfffff8800c7bc738 : 0xfffff80003405d92 : nt!PspCatchCriticalBreak+0x92
                   rbp : 0xfffff8000337e0d0 :  !da ""Terminating critical process 0x%p (%s).""
                   rsi : 0xfffffa800ae66e10 :  !da "csrss.exe"
                    r9 : 0xfffffa800ae66e10 :  !da "csrss.exe"
                   r11 : 0xfffff8800c7bc848 : 0xfffff80003076e13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800c7bc738 : 0xfffff80003405d92 : nt!PspCatchCriticalBreak+0x92
    0xfffff8800c7bc758 : 0xfffffa800ae66e10 :  !da "csrss.exe"
    0xfffff8800c7bc760 : 0xfffff8000337e0d0 :  !da ""Terminating critical process 0x%p (%s).""
    0xfffff8800c7bc7c8 : 0xfffff80003331ec4 : nt!NtTerminateProcess+0xf4
    0xfffff8800c7bc848 : 0xfffff80003076e13 : nt!KiSystemServiceCopyEnd+0x13
    0xfffff8800c7bc9b8 : 0xfffff800030733d0 : nt!KiServiceLinkage
    0xfffff8800c7bcd90 : 0xfffff800031f2e00 : nt!KiInitialPCR+0x100
    0xfffff8800c7bcde8 : 0xfffff8000304e55e : nt!KiOpDecode+0xf6
    0xfffff8800c7bce78 : 0xfffff80003075d7a : nt!KiPageFault+0x23a
    0xfffff8800c7bd0c8 : 0xfffff8000310344c : nt!RtlpCopyXStateChunk+0x5c
    0xfffff8800c7bd0e8 : 0xfffff8000306acd4 : nt!RtlpCopyLegacyContextAmd64+0x144
    0xfffff8800c7bd118 : 0xfffff80003077d33 : nt!KeContextToKframes+0x83
    0xfffff8800c7bd1f8 : 0xfffff800030c4790 : nt!KiRaiseException+0x1b4
    0xfffff8800c7bd538 : 0xfffff8000304d9d2 : nt!MiCopyDataPageToImagePage+0xa66
    0xfffff8800c7bd5a8 : 0xfffff88000ccd577 : CI!CiValidateImageData+0x343
    0xfffff8800c7bd678 : 0xfffff800030a5521 : nt!MiResolveMappedFileFault+0x971
    0xfffff8800c7bd6d8 : 0xfffff80003089fd2 : nt!MiUpdateWsle+0x1b2
    Code:
    0: kd> !error 0xc0000005
    Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    A page fault was called to most likely add pages to the working set of the process, but because the amount of available pages may have been exhausted already, and no trimming took place, then the system crashed.

    Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

       Information
      My Computer

  3.    #3

    Remove:

    Code:
    Start Menu\Programs\Advanced System Optimizer 3
    Start Menu\Programs\Advanced System Optimizer 3\Backup and Recovery
    Start Menu\Programs\Advanced System Optimizer 3\Common Problem Fixers
    Start Menu\Programs\Advanced System Optimizer 3\Disk Tuneup
    Start Menu\Programs\Advanced System Optimizer 3\Registry Tuneup
    Start Menu\Programs\Advanced System Optimizer 3\Regular Maintenance	
    Start Menu\Programs\Advanced System Optimizer 3\Security and Privacy	
    Start Menu\Programs\Advanced System Optimizer 3\Windows Optimization
    Windows 7 doesn't require any programs which make changes to the operating system and registry, these programs tend to cause problems by modifying and deleting files.

    Windows is a closed source system. Developers of registry cleaners do not have the core code of Windows 7 and are not working on definitive information, but rather they are going on past knowledge and experience. Automatic cleaners will usually have to do some guesswork.

    Modifying registry keys incorrectly can cause Windows instability, or make Windows unbootable. No registry cleaner is completely safe and the potential is ever present to cause more problems than they claim to fix.

    Registry cleaners cannot distinguish between good and bad. If you run a registry cleaner, it will delete all those keys which are obsolete and sitting idle; but in reality, those keys may well be needed by some programs or windows at a later time.

    Windows 7 is much more efficient at managing the registry than previous Windows versions. If you run any other registry cleaner and do not know precisely what you are doing, you will have problems down the road. There are no gains to be had from using a registry cleaner and the risk is great.
    Remove:

    Code:
    Start Menu\Programs\Driver Identifier
    These driver update programs usually install the wrong or outdated drivers, please remove this program completely from your system, most of these programs are spyware or adware anyway. The only method for installing driver is checking the motherboard support page or the hardware vendor, and then installing via Device Manager or the vendor's own tools.

    Remove:

    Code:
    Start Menu\Programs\Kaspersky Internet Security 2013
    Kaspersky and Internet Security suites in general are known to cause problems, please remove fully with the Kaspersky Removal Tool, and then run full scans with these free and proven alternatives which best with the operating system due to their lightweight nature on system resources and compatibility.

    Install and perform full scans with:

       Information
    Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

    You can also view this thread for a complete free and lightweight security protection combination:

    Reduce the number of programs at startup, to avoid any driver or program conflicts:
      My Computer


  4. Posts : 4
    Windows 7
    Thread Starter
       #4

    BSOD Report for Verifier.exe


    Hi,

    Here is the new report for BSOD:

    I appreciate your assistance.
    Last edited by Brink; 12 Sep 2013 at 10:37. Reason: moved to original thread
      My Computer

  5.    #5

    Please unmark this thread as solved, since the issue hasn't been resolved yet.

    Code:
    BugCheck C9, {23e, fffff88008db74ac, fffff980250b8ab0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\5U877.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for 5U877.sys
    *** ERROR: Module load completed but symbols could not be loaded for 5U877.sys
    Probably caused by : 5U877.sys ( 5U877+24ac )
    Code:
    2: kd> lmvm 5U877
    start             end                 module name
    fffff880`08db5000 fffff880`08de9e80   5U877    T (no symbols)           
        Loaded symbol image file: 5U877.sys
        Image path: \SystemRoot\system32\DRIVERS\5U877.sys
        Image name: 5U877.sys
        Timestamp:        Wed Mar 28 05:16:46 2012 (4F7290AE)
        CheckSum:         0003A4A4
        ImageSize:        00034E80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your 5U877 UVC driver for Ricoh camera driver seems to be causing problems, please update the driver from your model/motherboard support page.

    The driver marked the IRP as pending, but didn't return the STATUS_PENDING flag back to the I/O Manager.

    Note: Please follow my other suggestions too.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:21.
Find Us