|
- ADUC MMC Crash - social. technet. microsoft. com
These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mmc exe_7ecdcef8a543e26670894ce3b261a179b69a2c1b_00000000_8898ee90 Analysis symbol: Rechecking for solution: 0 Report Id: 70d363dd-7a01-4dc5-95c4-d0099bdf0efa Report Status: 268435456 Hashed bucket: 3d5932745be69d290fc111035354d0f0 Cab Guid: 0
- Windows 8 error 0x80071a91 in the process of setting up additional . . .
2013-12-26 19:04:28, Info CBS WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6 2 9200 16384, status: 0x80071a91, failure source: Execute, start state: Installed, target state: Installed, client id: Windows Optional Component Manager
- Word 2013 Pro plus different crashes cause suspended Winword process . . .
Recently we have noticed that when, Word 2013 x86 version (15 0 4823 1000, 15 0 4805 1001) running on Windows 8 1 x64, crashes due to corrupted heap, we find suspended winword process that have no running threads the corrupte heap crashes are of the type exception c0000374 in Ntdll dll at offset 0x000e6054 We have two different situations in which we can trigger a crash that will produce the
- The system process C:\Windows\system32\lsass. exe terminated . . .
Initially we thought its related to the issue fixed by the following hotfix so we applied it but even with the hotfix it still keeps rebooting
- Restore using USMT Custom Task Sequence Fails
Trying to use a Custom Task Sequence that only Performs just the Restore using USMT from the State Migration Point This returns the following errors:
- Windows 7 for x64-based Systems (KB4022719) installation failure . . .
2017-06-18 14:31:49, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601 23833 1 6, status: 0x80004005, failure source: Execute, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
- Faulting module name: KERNELBASE. dll, version: 6. 1. 7601. 17651, time . . .
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tlc logmanager s_4d5cd055f698b9b7d9e989629dd2eb52d0be2b_1a6a145b Analysis symbol: Rechecking for solution: 0 Report Id: fefb5c84-d9b0-11e3-9578-5ef3fcdc0b9f ------------------------------------------------------------------------ Version=1 EventType=CLR20r3 EventTime=130443543988233973
- Directly Connected keyboard mouse Monitor stopped working.
I have a single monitor and mouse connected to a multipoint 2011 server - this was set to mouse and keyboard "b" and was working ok on the screen plugged into the server I have had to run the configwiz to fix a problem with a network card and now the main screen directly connected to the video card on the server is no longer associated with the mouse and keyboard plugged into the usb hub
|
|
|