BSOD csrss.exe crash (sxs.dll cause)
We're having random BSOD's from our computers. Only user dump files are created. Here's a snippet of the file, I'm wondering if anyone has any ideas what might be the cause?
PROCESS_NAME: csrss.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000027be0b8
READ_ADDRESS: 00000000027be0b8
FOLLOWUP_IP:
sxs!BufferedStream::getLineBuf+1f
000007fe`fcc41b2f 410fb702 movzx eax,word ptr [r10]
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
APP: csrss.exe
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
FAULTING_THREAD: 0000000000001170
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ_STACK_POINTER_MISMATCH
DEFAULT_BUCKET_ID: INVALID_POINTER_READ_STACK_POINTER_MISMATCH
LAST_CONTROL_TRANSFER: from 000007fefcc41aea to 000007fefcc41b2f
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: sxs!BufferedStream::getLineBuf+1f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sxs
IMAGE_NAME: sxs.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7c9cc
FAILURE_BUCKET_ID: INVALID_POINTER_READ_STACK_POINTER_MISMATCH_c0000005_sxs.dll!BufferedStream::getLineBuf
BUCKET_ID: X64_APPLICATION_FAULT_INVALID_POINTER_READ_STACK_POINTER_MISMATCH_sxs!BufferedStream::getLineBuf+1f
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:invalid_pointer_read_stack_pointer_mismatch_c0000005_sxs.dll!bufferedstream::getlinebuf
FAILURE_ID_HASH: {558625b4-41c0-b4dc-930c-c09d8e328e35}
This is what I got so far and you can get the dump file from %windir%\system32\config\systemprofile\appdata\local\crashdumps
- Event Type : Stopped working (APPCRASH)
Application Name: Client Server Runtime Process
Path: C:\windows\system32\csrss.exe
Event Time : 03/20/2014 12:30:24 AM
Application Name: csrss.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc115
Fault Module Name: sxs.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c9cc
Exception Code: c0000005
Exception Offset: 0000000000011b2f
Memory dump : Not created
Similar Messages
-
Explorer.exe crashing - twinui.dll?
With some relative frequency (several times an hour) explorer.exe is faulting and restarting. I only noticed because the system tray repaints. I am not sure if this is related to the applications I have installed, or is unrelated.
Has anyone else encountered this? Any ideas as to what is going on?
Below are the event log details:
Faulting application name: explorer.exe, version: 6.2.9200.16384, time stamp: 0x50107dbc
Faulting module name: twinui.dll, version: 6.2.9200.16384, time stamp: 0x50109442
Exception code: 0xc0000005
Fault offset: 0x0000000000340849
Faulting process id: 0x1584
Faulting application start time: 0x01cd7c8733f184a6
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\System32\twinui.dll
Report Id: 50dc242a-e87b-11e1-be6f-6c626ddcca27
Faulting package full name:
Faulting package-relative application ID:
I do not have a lot of applications installed at the moment, so if it is application-related, then at least there is a short list of possible causes.
AMD Catalyst Install Manager (and Catalyst Control Center)
AuthenTec WinBio Fingerprint Software x64
EventGhost 0.4.1.r1572
LastPass x64
RealTek High Definition Audio Driver
Microsoft Visual C++ 2010 x64 Distributable 10.0.30319
SharpKeysplease download this reg file from my SkyDrive:
http://cid-128fc518635be2dc.skydrive.live.com/self.aspx/.Public/MS%20Foren/Registry/WER%5E_Explorer_full.reg
and make a double click on the file to import it. If you can't do this, run regedit.exe and import the registry file there!
When the Windows Explorer crashes, Windows Error Reporting Service [1] creates a dmp file under C:\Localdumps. Please upload the created file (cmpressed as 7z or RAR) to your public Skydrive [2] folder and post the link here. I take a look at the dump with
the Debugger, maybe I can see the cause.
André
[1] http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
[2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
"A programmer is just a tool which converts caffeine into code" -
Explorer.exe crash, twinui.dll
For a couple of weeks, everytime i login into my account, explorer.exe keeps crashing and restarting.During this loop, the system is laggy and it only shows the taskbar, without the icons i put on it.
Here is the report from event viewer:
Faulting application name: explorer.exe, version: 6.3.9600.17667, time stamp: 0x54c6f7c2
Faulting module name: twinui.dll, version: 6.3.9600.17324, time stamp: 0x53f822bf
Exception code: 0xc0000006
Fault offset: 0x00000000000e87c7
Faulting process id: 0xb20
Faulting application start time: 0x01d06eb0d68fe96f
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\system32\twinui.dll
Report Id: 19f958ba-daa4-11e4-82aa-448a5bcfcd05
Faulting package full name:
Faulting package-relative application ID:
I also downloaded autoruns from sysinternals, there are some dll's, but only from winrar and poweriso, which i deactivated.I ran sfc /scannow and chkdsk /f, no changes.The system runs fine in safe mode, without any crashes.Hello Retegan Andrei (Andrew),
As this issue doesn’t exist in the safe mode, it is caused by driver or third-party software.
Please try to perform a clean boot in Windows.
https://support.microsoft.com/en-us/kb/929135
If this issue doesn’t occur in clean boot, it is caused by third-party drivers.
If this issue occurs in clean boot too, it is cuased by drivers, please update drivers from the manufacturer website.
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Mmc.exe crash - Kernelbase.dll
Hello,
Reliability monitor reports frequet crash of mmc.exe
Faulting application name: mmc.exe, version: 6.3.9600.16384, time stamp: 0x5215ef8f
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xe0434352
Fault offset: 0x000000000000606c
Faulting process id: 0xa04
Faulting application start time: 0x01d05cbe538c385b
Faulting application path: C:\WINDOWS\system32\mmc.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 788536ea-cbab-11e4-82ae-402cf46ee7fe
Faulting package full name:
Faulting package-relative application ID:
How can I investigate further to find what causes the crash ?
Regards,
Michelif you are upgraded your OS from windows 7 or Windows 8. I suggest just run windows update and check
if you are not upgraded your OS try (SFC) & DISM as
ZigZag3143x , or simply do system restore (using restore point before this issue happen) and if still not working, in place upgrade will be another option
http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html
Yes, this is an upgrade from Windows 7. I've run the Windows update (instead of SCCM software updates) and the KB3000850 (November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 ) was missing from my computer.
This update installs an updated version of kernelbase DLL (6.3.9600.17415).I'll will wait a couple of days to check if it helps -
Thinkpad T60 Blue Screening when Idle. CSRSS.exe probable cause
Hi All,
I have a customer who leaves his computer on at work overnight and has received blue screens every night when he leaves his laptop. Once he reboots, the laptop is fine until he leaves it idle again.
The bugcheck is BugCheck F4, {3, 86b9cab8, 86b9cc2c, 805d164c} and the probable cause is csrss.exe as noted in the minidump ( I still have to load symbols for the debug).
I have updated bios and all necessary drivers and it still blue screens. Any idea why this BSOD is still occurring?
Any information is appreciated.
Thanks,
Phil -
Internet explorer 11 cause explorer.exe crashes
Hi There,
Just to let you know a little tips that can help for other about IE11 and explorer crashes fix
I don't know where posting that, so it will be here ! :)
Yesterday i decided to install Internet explorer 11 on my freshly installed Windows 7 Pro ed.
No problems during install, but after the reboot, my computer went on a strange state:
- Explorer keeps crashes itself everytime i launched a tool from the run command, or simply when i wanted to launch an explorer or other.
- Some services couldn't start (svchost, dhcp client, search, wmi etc ...)
- No launched programs in the taskbar.
- Security essentials failed to launch
- Funny thing : i could type only 4 letters into the run command, impossible to launch anythink except (hopefully) a CMD prompt :D
so after breaking my head on my desk, i decided to try something :
on a CMD i ran a SFC /scannow and it repaired some errors, not all.
I parsed the CBS.LOG file, and realized that one DLL failed to repair on the generated txt (see details below) :
this dll was : IEPROXY.DLL and i made the link between my IE11 installation and this dll.
==> method to parse the CBS.LOG file : launch CMD as admin and type the following:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
so here is the fix/workaround : simply uninstall IE11!
But ... wait, you cannot access to APPWIZ.CPL (remember: impossible to laucn the control panel without crashing explorer) so we will uninstall IE11 with a command line:
on the CMD type this :
FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*11.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /quiet /norestart"
when it's ok, simply restart the computer, IE10 will be available automatically and the issue disapeared.
Hope it helps someone.
DavidHi,
Thanks for sharing your experience to us.
For the persons who have the similar issue with the explorer.exe crashes, try this solution to fix the issue.
If you have any questions or concerns, please do not hesitate to let us know.
Thanks again. Have a nice day.
Regards,
Blair Deng
Blair Deng
TechNet Community Support -
Windows Server 2012 R2 RDS + User profile Disks + App-V = Explorer.exe crashing all of the time
I have built a new RDS farm on Windows Server 2012 R2 with two Session Hosts and a combined Connect Broker/Web Access server. I had the farm up and running with User Profile Disks and all seemed OK. However, as soon as I installed the App-V 5.0 SP2 RDS
client on the session hosts, the explorer.exe process started crashing for any user logging in via the Web Access site. The process crashes and restarts every five to ten seconds. It's the same for administrators. If they log in via Web Access explorer.exe
crashes, but if they RDP directly to one of the session hosts explorer.exe is fine. If I reboot the session hosts, then the first user to log in via Web Access has a stable desktop session (and appears to have a new profile as well). However, if that user
logs out and back in again, explorer.exe starts crashing again. The only applications I have packaged at the moment are Office 2013 and Firefox.
I tried disabling User Profile Disks, but this caused a whole bunch of other problems and I eventually lost the ability to log in at all via Web Access (errors about the user profile service). As this is a small pre-production environment I completed scrapped
all of the servers and rebuilt from scratch. Again, everything appeared fine until I installed the App-V client, then explorer.exe started crashing repeatedly for all users.
Has anyone come across this issue before? I have tried installing the App-V 5.0 SP2 Hotfix Package 2, but this didn't help. I have read in a few forums that App-V doesn't work very well with User Profile Desks, but I have not heard of this particular issue.
Similarly, SP2 seems to have a lot of problems, so I am going to try removing App-V RDp Client SP2 and installing SP1. I ahev also deleted User Profile Disks for the test users to recreate their profiles, but this didn't help either.
Any other suggestions welcome!I forgot to include the application event log entry for explorer.exe crashing:
Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xc06d007e
Fault offset: 0x0000000000005bf8
Faulting process id: 0xae8
Faulting application start time: 0x01cfab3a273787fd
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 69210d77-172d-11e4-80c6-0050560102d1
Faulting package full name: -
Windows Server Backup - wbengine.exe Crashing
Hi,
When running either a scheduled back or a once off backup, I receive the following error around 30 seconds into the backup:
"The Windows Server Backup service has stopped"
"A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The Windows server Backup service has stopped"
In event viewer the following two events were logged:
Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0x13e8
Faulting application start time: 0x01cfa9f0936b235a
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e99a55c8-15e4-11e4-9ab5-a01d48c77640
The Block Level Backup Engine Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
I have tired restarting the Block Level Backup Engine Service service, deleting the backup catalogue, removing and re adding Window Server Backup feature. None of these fixed the problem.
I used Debug Diagnostic Tool v2.0 and capturing all instances of wbengine.exe process:
Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_wbengine.exe.vbs
DumpPath set to C:\Users\administrator\Desktop\wbengineLogs
[8/20/2014 9:23:48 AM] Process created. BaseModule - C:\Windows\system32\wbengine.exe. BaseThread System ID - System ID: 7940
[8/20/2014 9:23:48 AM] C:\Windows\SYSTEM32\ntdll.dll loaded at 0x77780000
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 1912
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 7756
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 4920
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6964
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6100
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6524
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 6824
[8/20/2014 9:23:48 AM] C:\Windows\system32\kernel32.dll loaded at 0x77560000
[8/20/2014 9:23:48 AM] C:\Windows\system32\KERNELBASE.dll loaded at 0xfd5e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ADVAPI32.dll loaded at 0xfe030000
[8/20/2014 9:23:48 AM] C:\Windows\system32\msvcrt.dll loaded at 0xff5d0000
[8/20/2014 9:23:48 AM] C:\Windows\SYSTEM32\sechost.dll loaded at 0xff530000
[8/20/2014 9:23:48 AM] C:\Windows\system32\RPCRT4.dll loaded at 0xfeed0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\USER32.dll loaded at 0x77680000
[8/20/2014 9:23:48 AM] C:\Windows\system32\GDI32.dll loaded at 0xffa20000
[8/20/2014 9:23:48 AM] C:\Windows\system32\LPK.dll loaded at 0xff6c0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\USP10.dll loaded at 0xff130000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ole32.dll loaded at 0xff320000
[8/20/2014 9:23:48 AM] C:\Windows\system32\OLEAUT32.dll loaded at 0xfdf40000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VSSAPI.DLL loaded at 0xfc1e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\ATL.DLL loaded at 0xfc1c0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VssTrace.DLL loaded at 0xfc1a0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SETUPAPI.dll loaded at 0xff6d0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CFGMGR32.dll loaded at 0xfd910000
[8/20/2014 9:23:48 AM] C:\Windows\system32\DEVOBJ.dll loaded at 0xfd8f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\NETAPI32.dll loaded at 0xfa190000
[8/20/2014 9:23:48 AM] C:\Windows\system32\netutils.dll loaded at 0xfc9f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\srvcli.dll loaded at 0xfd130000
[8/20/2014 9:23:48 AM] C:\Windows\system32\wkscli.dll loaded at 0xfa170000
[8/20/2014 9:23:48 AM] C:\Windows\system32\XmlLite.dll loaded at 0xfa9e0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\bcrypt.dll loaded at 0xfcf10000
[8/20/2014 9:23:48 AM] C:\Windows\system32\VirtDisk.dll loaded at 0xf5740000
[8/20/2014 9:23:48 AM] C:\Windows\system32\FLTLIB.DLL loaded at 0xf8de0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CLUSAPI.dll loaded at 0xf9c60000
[8/20/2014 9:23:48 AM] C:\Windows\system32\cryptdll.dll loaded at 0xfd040000
[8/20/2014 9:23:48 AM] C:\Windows\system32\IMM32.DLL loaded at 0xfe110000
[8/20/2014 9:23:48 AM] C:\Windows\system32\MSCTF.dll loaded at 0xff020000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPTBASE.dll loaded at 0xfd420000
[8/20/2014 9:23:48 AM] C:\Windows\system32\bcryptprimitives.dll loaded at 0xfca00000
[8/20/2014 9:23:48 AM] C:\Windows\system32\cscapi.dll loaded at 0xf9bd0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CLBCatQ.DLL loaded at 0xfdc70000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPTSP.dll loaded at 0xfcdc0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\rsaenh.dll loaded at 0xfcac0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\RpcRtRemote.dll loaded at 0xfd510000
[8/20/2014 9:23:48 AM] C:\Windows\system32\blb_ps.dll loaded at 0xf7520000
[8/20/2014 9:23:48 AM] C:\Windows\System32\vds_ps.dll loaded at 0xf8310000
[8/20/2014 9:23:48 AM] C:\Windows\system32\WINTRUST.dll loaded at 0xfd720000
[8/20/2014 9:23:48 AM] C:\Windows\system32\CRYPT32.dll loaded at 0xfd760000
[8/20/2014 9:23:48 AM] C:\Windows\system32\MSASN1.dll loaded at 0xfd5d0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\vss_ps.dll loaded at 0xfa2f0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\taskschd.dll loaded at 0xf4b20000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SspiCli.dll loaded at 0xfd390000
[8/20/2014 9:23:48 AM] C:\Windows\system32\spp.dll loaded at 0xeec40000
[8/20/2014 9:23:48 AM] C:\Windows\system32\dsrole.dll loaded at 0xfb630000
[8/20/2014 9:23:48 AM] C:\Windows\System32\msxml3.dll loaded at 0xf89b0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SHLWAPI.dll loaded at 0xff200000
[8/20/2014 9:23:48 AM] C:\Windows\System32\ES.DLL loaded at 0xfb5b0000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SXS.DLL loaded at 0xfd430000
[8/20/2014 9:23:48 AM] C:\Windows\system32\PROPSYS.dll loaded at 0xfad60000
[8/20/2014 9:23:48 AM] C:\Windows\system32\samcli.dll loaded at 0xfa670000
[8/20/2014 9:23:48 AM] C:\Windows\system32\SAMLIB.dll loaded at 0xfa650000
[8/20/2014 9:23:48 AM] C:\Windows\System32\msxml6.dll loaded at 0xf6ab0000
[8/20/2014 9:23:48 AM] Thread created. New thread system id - System ID: 7428
[8/20/2014 9:23:48 AM] Initializing control script
[8/20/2014 9:23:48 AM] Clearing any existing breakpoints
[8/20/2014 9:23:48 AM]
[8/20/2014 9:23:48 AM] Current Breakpoint List(BL)
[8/20/2014 9:23:49 AM] Thread exited. Exiting thread system id - System ID: 7428. Exit code - 0x00000000
[8/20/2014 9:23:54 AM] Thread created. New thread system id - System ID: 5848
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll loaded at 0x73050000
[8/20/2014 9:23:55 AM] C:\Windows\system32\blbres.dll Unloaded from 0x73050000
[8/20/2014 9:23:55 AM] Thread created. New thread system id - System ID: 7188
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6160
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7640
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 8148
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5348
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 2964
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5320
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 4164
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7916
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6244
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7908
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 6200
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 5028
[8/20/2014 9:24:02 AM] Thread created. New thread system id - System ID: 7804
[8/20/2014 9:24:03 AM] First chance exception - 0XE06D7363 caused by thread with System ID: 7640. DetailID = 1
[8/20/2014 9:24:03 AM] Thread exited. Exiting thread system id - System ID: 7640. Exit code - 0x00000000
[8/20/2014 9:24:07 AM] Thread exited. Exiting thread system id - System ID: 6160. Exit code - 0x00000000
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 1108
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 992
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 7784
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 4432
[8/20/2014 9:24:08 AM] Thread created. New thread system id - System ID: 5304
[8/20/2014 9:24:09 AM] First chance exception - 0XE06D7363 caused by thread with System ID: 7784. DetailID = 2
[8/20/2014 9:24:09 AM] Thread exited. Exiting thread system id - System ID: 7784. Exit code - 0x00000000
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 2780
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 8012
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 7552
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 6812
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 5368
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 1388
[8/20/2014 9:24:13 AM] Thread exited. Exiting thread system id - System ID: 2780. Exit code - 0x00000000
[8/20/2014 9:24:13 AM] Thread created. New thread system id - System ID: 7404
[8/20/2014 9:24:14 AM] Thread exited. Exiting thread system id - System ID: 7404. Exit code - 0x00000000
[8/20/2014 9:24:14 AM] Thread created. New thread system id - System ID: 2284
[8/20/2014 9:24:47 AM] Thread exited. Exiting thread system id - System ID: 6524. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 2284. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread created. New thread system id - System ID: 6188
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 6188. Exit code - 0x00000000
[8/20/2014 9:25:12 AM] Thread created. New thread system id - System ID: 7120
[8/20/2014 9:25:12 AM] Thread exited. Exiting thread system id - System ID: 7120. Exit code - 0x00000000
[8/20/2014 9:25:13 AM] Thread created. New thread system id - System ID: 7428
[8/20/2014 9:25:20 AM] Thread exited. Exiting thread system id - System ID: 7428. Exit code - 0x00000000
[8/20/2014 9:25:20 AM] Thread created. New thread system id - System ID: 1280
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 7552. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 5368. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 1280. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] Thread created. New thread system id - System ID: 8108
[8/20/2014 9:25:21 AM] Thread exited. Exiting thread system id - System ID: 8108. Exit code - 0x00000000
[8/20/2014 9:25:21 AM] C:\Windows\system32\blbsrv.dll loaded at 0xe6240000
[8/20/2014 9:25:25 AM] First chance exception - 0X80000003 caused by thread with System ID: 992. DetailID = 3
[8/20/2014 9:25:25 AM] First chance exception - 0XC0000374 caused by thread with System ID: 992. DetailID = 4
[8/20/2014 9:25:25 AM] Second chance exception - 0XC0000374 caused by thread with System ID: 992
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5028. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4432. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 992. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7804. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7908. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4164. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 2964. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 8148. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5848. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6824. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6100. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6964. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7756. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7940. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6812. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 8012. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5304. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6200. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 6244. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7916. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5320. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 5348. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 7188. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 4920. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 1912. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Thread exited. Exiting thread system id - System ID: 1388. Exit code - 0xffffffff
[8/20/2014 9:25:25 AM] Process exited. Exit code - 0xffffffff
* EXCEPTION DETAILS *
DetailID = 1
Count: 1
Exception #: 0XE06D7363
Stack:
Call Site
KERNELBASE!RaiseException
msvcrt!CxxThrowException
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
msvcrt!srand
msvcrt!ftime64_s
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 2
Count: 1
Exception #: 0XE06D7363
Stack:
KERNELBASE!RaiseException
msvcrt!CxxThrowException
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
VSSAPI!CVssJetWriter::SetWriterFailure
msvcrt!srand
msvcrt!ftime64_s
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 3
Count: 1
Exception #: 0X80000003
Stack:
ntdll!RtlUnhandledExceptionFilter
ntdll!EtwEnumerateProcessRegGuids
ntdll!RtlQueryProcessLockInformation
ntdll!RtlLogStackBackTrace
ntdll!RtlIsDosDeviceName_U
ole32!CoTaskMemFree
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
DetailID = 4
Count: 1
Exception #: 0XC0000374
Stack:
ntdll!RtlUnhandledExceptionFilter
ntdll!EtwEnumerateProcessRegGuids
ntdll!RtlQueryProcessLockInformation
ntdll!RtlLogStackBackTrace
ntdll!RtlIsDosDeviceName_U
ole32!CoTaskMemFree
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
wbengine
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart
* EXCEPTION SUMMARY *
|--------------------|
| Count | Exception |
|--------------------|
| 2 | 0XE06D7363 |
| 1 | 0X80000003 |
| 1 | 0XC0000374 |
|--------------------|
Any help would be greatly appreciated.Hi
Similar post:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4d87c9a1-8f1b-4bb3-8b13-ee37bc3c014b/windows-server-backup-failing-to-start-error-a-fatal-error-occurred-during-a-windows-server-backup?forum=windowsbackup -
HT5925 AppleIEDAV.exe crashes everytime Windows 7 64 bit opens
AppleIEDAV.exe crashes everytime Windows 7 64 bit opens. Any ideas?
Problem signature:
Problem Event Name: APPCRASH
Application Name: AppleIEDAV.exe
Application Version: 1.2.12.0
Application Timestamp: 52867716
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000005
Exception Offset: 0002e41b
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
This just started to happen. I'm using IE 11. Of course.. Safari is dead.
Thank you!Remove or uncheck Bookmarks in your iCloud control panel. That is what is causing most of the problems. At least that is what I've been able to gleen from reading other posts here in the forum.
-
Windows 8.1 BSOD - ntoskrnl.exe
Hi, I've been experiencing BSOD's on a daily basis (only when I am away from my computer) and I'd like to know the root cause of the problems. I've attached several minidump files below. Using Windbg (x64) the only problem I can see is ntoskrnl.exe being
unable to load (either corrupted or missing). sfc/scannow has detailed several problems relating to ntoskrnl.exe as well
https://onedrive.live.com/redir?resid=6e6984aa2d967f21%212299
Thanks!
BillYou've recommended the opposite of what I was told last time: "The crashes are being caused by you
NVidia display driver. Please uninstall an "clean" reinstall the current driver version".
Last time I had BSOD problems I was using version 326.19 (at least one year old) and now I have the most recent version. As a result, I do not believe this is the cause of the BSOD's.
Also, I do not see the same thing you do when opening the minidump file, as follows:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040815-36484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`0a282000 PsLoadedModuleList = 0xfffff802`0a55b250
Debug session time: Wed Apr 8 14:02:21.387 2015 (UTC - 6:00)
System Uptime: 0 days 20:32:22.558
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0019c12a760, fffff8020c30e960, ffffe001a1f67680}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: NT!_DEVICE_OBJECT ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!TRIAGE_9F_POWER ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IO_STACK_LOCATION ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_IRP ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_DEVICE_OBJECT ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. *** -
Illustrator.exe crashes in CS6
Hi. We purchased CS6 Design Standard with 4 licenses. 3 of the installations are running without any problems. The 4th crashes a few times/day. It is always Illustrator.exe, specifically MSCVR100.dll that causes the problem. It's running on a Windows 7 x64 system with Avast AVS. After messing with security settings, scratch disks, etc I finally replaced the PC with a brand new one (same OS). We are still having the same problems. The detail from the windows event log is below. Since replacing the PC did not solve the problem I believe it must be either attached hardware, conflicting software or something the user is doing. The only things that distinguish this user from the others are:
Use of a Wacom tablet/touchpad
Use of dropbox (they often save directly to dropbox)
Any clues? I've been working on this for close to two weeks and cannot resolve. Thanks.
+
System
Provider
[ Name]
Application Error
EventID
1000
[ Qualifiers]
0
Level
2
Task
100
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2012-11-20T14:46:22.000000000Z
EventRecordID
3583
Channel
Application
Computer
Tarzlyn
Security
EventData
Illustrator.exe
16.0.0.682
4f6e45b7
MSVCR100.dll
10.0.40219.1
4d5f034a
c000041d
000000000003c9ca
64c
01cdc71efef146a9
C:\Program Files\Adobe\Adobe Illustrator CS6 (64 Bit)\Support Files\Contents\Windows\Illustrator.exe
C:\Windows\system32\MSVCR100.dll
0c9a4de6-3321-11e2-9468-e06995e36c7aThen unsinstall the old ones first using your Add or Remove Programs system control panel. Just keep trying.
Mylenium -
Hello
I'm running on a brand new system Windows 7 Home Premium 64-Bit.
I have a problem with Internet Explorer 8. When a javascript tries to open a link into a new window I get the error message: Message: Cannot open an anonymous level security token.
The solution to this is to go to dcomcnfg -> Expand Componenet Services -> Computers
Select My Computer -> right click My Computer and select Properties.
On the Default Properties tab set the Default Authentication level and Default Impersonation level.
Here is the problem: These values can not be set. There are multiple problems with the DCOMCNFG interface.
1. There are no values present in the drop down window.
2. The first time one selects properties from my computer to access the default properties tab, I get only a 2 tab page consisting only of COM Security and MSDTC. I have to select the properties option a second time to get the correct page to
pop up containing the additional 4 tabs that include the default Properties. (strange, but I have actually seen this behavior reported elsewhere on the net by a developer)
3. On the default properties tab, the "enable Distributed COM on this computer" is unchecked, even though registry values indicate DCOM is enabled.
4. The drop down windows for "Default Authetication Level" and "Default Inpersonation Level" do not populate with any options when I check the "Enable Distributed COM" box. Registry values appear to have these settings correctly set.
5. Regardless of whether I modify any entries or not on the Default Properties tab, every time I close the Default Properties tab by selecting "OK", mmc.exe crashes and an error is generated. No crash if I select "cancel." Error info below:
Problem Event Name: APPCRASH
Application Name: mmc.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc808
Fault Module Name: comuid.dll
Fault Module Version: 2001.12.8530.16385
Fault Module Timestamp: 4a5bdf82
Exception Code: c000041d
Exception Offset: 0000000000027eb4
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: c04d
Additional Information 2: c04dc172367dd59f9f2c3be375fb3e80
Additional Information 3: ab1b
Additional Information 4: ab1bd07e62aa9dd1521e9b185bfe43fc
What have I done to try to remedy the problem?
Ran fsc scannow and chkdsk with no change.
What would I like?
To eliminate the anonymous level security token error in IE8, and I assume the DCOMCNFG problem may be the cause.
Thanks, JimI have the EXACT signature of symptoms as described here, but with Windows XP:
[Quote]
Multiple problems with the DCOMCNFG interface.
1. There are no values present in the drop down window.
2. The first time one selects properties from my computer to access the default properties tab, I get only a 2 tab page consisting only of COM Security and MSDTC. I have to select the properties option a second time to get the correct page to
pop up containing the additional 4 tabs that include the default Properties. (strange, but I have actually seen this behavior reported elsewhere on the net by a developer)
3. On the default properties tab, the "enable Distributed COM on this computer" is unchecked, even though registry values indicate DCOM is enabled.
4. The drop down windows for "Default Authetication Level" and "Default Inpersonation Level" do not populate with any options when I check the "Enable Distributed COM" box. Registry values appear to have these settings correctly set.
5. Regardless of whether I modify any entries or not on the Default Properties tab, every time I close the Default Properties tab by selecting "OK", mmc.exe crashes and an error is generated. No crash if I select "cancel."
[/QUOTE]
I tried the COMFIX tool suggested by Jim Bacon - it does not complete for me however
(there is no "run as admin" option in Windows XP, just double clicked to run it.
Otherwise followed as described (no Norton Ghost)
It errors out:
In the Command Window, it says Open Service Fail 1060
Specific Service does not exist as installed service
And a Windows Script Host Window that reports error "the system cannot find the file specified" - code:80070002
Is this because it is XP?
Is there something similar I can use for XP, or do I have some other limitation?
Appreciate assistance - I was happy to find this issue reported here so pleased that at least I am not unique in that! -
8i EE Setup.exe crash - XP Pro and AMD X2 CPU
When trying to install 8i on my XP Pro (SP2) box with and AMD X2 3800+, setup.exe crashes as soon as it is run. I've tried the fix for P4s (renaming the symcjit.dll instances), but to no avail. This happens wherever the setup.exe is run from.
Has anyone encountered this problem and managed to fix it?Hope you realize that Microsoft has changed a number of the kernel APIs with XP. Oracle8i was written to older APIs and you may experience crashes, possibly at random, simply because you are trying to run things in an incompatible way.
(I see this as a bit like buying a new car chassis and putting in an old engine and transmission - there is a lot of tinkering required to get the motor mounts to match.)
In my experience, people who have made 8i work on XP Pro have generally upgraded XP from an older OS and have been lucky enough to have the old APIs still lying around.
Suggest you try moving up to a newer version of Oracle and, if necessary, use the compatibility parameter to keep compatibility. -
Sapinst.exe crashes on Windows 7 (ver. 6.1)
Hi,
I am trying to install Netweaver CE 7.11 on Windows 7 64-bit. Yes, I know it is not supported. But still, I would like to ask right about the reason sapinst.exe crashes.
So, sapinst.exe can be launched in Win 7 native mode, but it is not compliant with OS compatibility. So I am trying to launch it in Vista mode. But sapinst.exe crashes with error log like this (sorry for flood, but see below).
At the same time sapinst.exe launches in Win 7 native mode + 32-bit sapinst.exe launches in Vista mode. Only 64-bit sapinst crashes in Vista mode. I suspect this is related just to JVM and near that, and may be solved. Please, advise, if someone has more expertise than me or experience with such or similar situations.
Thank you.
Regards,
Anton
An unexpected error has been detected by SAP Java Virtual Machine:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000076def2d5, pid=2852, tid=1484
Java VM: SAP Java 64-Bit Server VM (5.1.000 Feb 13 2007 23:26:13 - 01_REL - optU - bas2:69696 (mixed mode))
Problematic frame:
C ntdll::RtlCaptureContext+0x85 (0x4f2d5)
T H R E A D -
Current thread (0x0000000000a4f3c0): JavaThread "main" [_thread_in_Java, id=1484]
siginfo: ExceptionCode=0xc0000005, reading address 0xffffffffffffffff
P R O C E S S -
Java Threads: ( => current thread )
0x00000000202dc930 JavaThread "HttpServer" [_thread_in_native, id=4028]
0x00000000202dc580 JavaThread "HttpWorker" [_thread_blocked, id=3948]
0x00000000202dc1d0 JavaThread "HttpWorker" [_thread_blocked, id=6148]
0x00000000202dba70 JavaThread "HttpWorker" [_thread_blocked, id=2116]
0x00000000202ddf50 JavaThread "AlarmClock" [_thread_blocked, id=1000]
0x00000000202db310 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=7144]
0x0000000020143230 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=5636]
0x000000001f37f8c0 JavaThread "Image Fetcher 0" daemon [_thread_blocked, id=6060]
0x000000001f37f1b0 JavaThread "AWT-Windows" daemon [_thread_in_native, id=316]
0x0000000020010bc0 JavaThread "AWT-Shutdown" [_thread_blocked, id=1020]
0x000000001f027180 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=5528]
0x000000001f026880 JavaThread "CompilerThread1" daemon [_thread_blocked, id=5116]
0x000000001f01fa70 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5336]
0x000000001f01f060 JavaThread "AdapterThread" daemon [_thread_blocked, id=6240]
0x000000001f01e2f0 JavaThread "Control Handler" daemon [_thread_blocked, id=6532]
0x000000001f01da00 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=6072]
0x000000001f018af0 JavaThread "JDWP Event Helper Thread" daemon [_thread_blocked, id=6636]
0x000000001f014d10 JavaThread "JDWP Transport Listener: dt_socket" daemon [_thread_blocked, id=4964]
0x000000001e805070 JavaThread "Finalizer" daemon [_thread_blocked, id=2964]
0x000000001e8030f0 JavaThread "Reference Handler" daemon [_thread_blocked, id=324]
=>0x0000000000a4f3c0 JavaThread "main" [_thread_in_Java, id=1484]
VM Arguments:
jvm_args: -Xmx256M -Dsun.java2d.noddraw=true -Dsap.env.var.javahome=SAPINST_JRE_HOME -agentlib:jdwp=transport=dt_socket,server=y,address=8000-8100,suspend=n
classpath: C:\Users\user1\AppData\Local\Temp\sapinst_exe.5632.1284041309\jar\instgui.jar
java_command: SDTGui instwizard host=localhost port=21201 -nolock
Launcher Type: SAP_STANDARD
Environment Variables:
PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files\ThinkPad\Bluetooth Software\;C:\Program Files\ThinkPad\Bluetooth Software\syswow64;
USERNAME=user1
OS=Windows_NT
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 37 Stepping 2, GenuineIntel
current directory: C:\Users\user1\Desktop\CE711_01_IM_WIN_X86_64_ADA
S Y S T E M -
OS: Windows Vista Build 6000
CPU:total 4 em64t ht
Memory: 4k page, physical 4050608k(1810264k free), swap 8406516k(5986780k free)
vm_info: SAP Java 64-Bit Server VM (5.1.000) for windows-amd64, built on Feb 13 2007 23:26:13 by unknown with MS VC++ 8.0
hostname: IEVN60202577AAlso, I noticed that possibly JVM crashes in ntdll.dll. Here are some libs, from the errorlog:
0x0000000000400000 - 0x0000000000415000 C:\Users\i057882\AppData\Local\Temp\sapinst_exe.5528.1284043695\jre\bin\java.exe
0x0000000076da0000 - 0x0000000076f4b000 C:\Windows\SYSTEM32\ntdll.dll
0x0000000076c80000 - 0x0000000076d9f000 C:\Windows\system32\kernel32.dll
0x000007fefcdb0000 - 0x000007fefce1b000 C:\Windows\system32\KERNELBASE.dll
0x000007fefecb0000 - 0x000007fefed8b000 C:\Windows\system32\ADVAPI32.dll
0x000007fefe980000 - 0x000007fefea1f000 C:\Windows\system32\msvcrt.dll
Exception always occurs here: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc= 0x0000000076def2d5
So I assume ntdll.dll is the place where crash happens. Am I right? And what could it mean?
Thanks.
Anton
Edited by: Anton Shabinskyi on Sep 9, 2010 5:59 PM -
Mstsc.exe crashes after connecting to server 2008
Hi at all
We got a Problem with a Windows 8.1 Client, if we connect to a windows server 2008, mstsc.exe crashes:
Name der fehlerhaften Anwendung:
mstsc.exe, Version: 6.3.9600.16384, Zeitstempel: 0x5215e2b5
Name des fehlerhaften Moduls:
DUI70.dll, Version: 6.3.9600.17031, Zeitstempel: 0x53086a1c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000277d
ID des fehlerhaften Prozesses: 0x238
Startzeit der fehlerhaften Anwendung: 0x01cfe2341b86ceba
Pfad der fehlerhaften Anwendung: C:\Windows\system32\mstsc.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\DUI70.dll
Berichtskennung: 5a1aa523-4e27-11e4-8267-2c4138a7d63a
Vollständiger Name des fehlerhaften Pakets:
Connecting to a MS Server 2003 works fine, the problem only occured while connecting a MS Server 2008
I also created a dmp-file mstsc.dmp but i cannot open it for some reason :(
(can anyone tell me which settings i have to apply to open it with windbg? i inserted SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols @ "Symbol File Path" any other parameters missing? [first time using windbg ;)])
We already tried to resolve the problem with other measures like reinstall graphics driver, deactivate sound & printer mapping in the mstsc-options, deactivate the grpahiccard etc..
Thanks for your help!Hi,
According to your description, we could try to fix that user profile for test:
Create a new user account and transfer the profile data.
Please follow the steps below to do that:
1. Open the Windows Explorer.
2. Click on View tab and Click on Options at the top right corner.
3. Click the View tab, and then click Show hidden files, folders, and drives.
4. Uncheck the box which states Hide protected operating system files.
5. Click Yes to confirm, and then click OK.
6. Locate the C:\Users\Old_Username folder, where C is the drive that Windows is installed on, and Old Username is the name of the profile you want to copy files from.
7. Select all of the files and folders in this folder, except the following files:
•Ntuser.dat
•Ntuser.dat.log
•Ntuser.ini
8. Right click and Select Copy.
9. Locate the C:\Users\New_Username folder, where C is the drive that Windows is installed on, and New Username is the name of the new user profile you created.
10. Right click inside the folder and select Paste.
11. Restart your PC and check if you are able to log in to default profile.
Karen Hu
TechNet Community Support
Maybe you are looking for
-
My ipod went to the ''connect to itunes mode'' and i want to use my itunes backup but how can i do that. also when the ''recover your ipod screen'' appeared i accidentally chose not to show it anymore. please help i just had it for half a day.
-
I have a macbook air 13inch late 2010. Does this model have an illuminated keyboard
I would like to know if my keybord is suposed to light up
-
How to put the left to right scroll bar
Hi iam new comer to sap, So pls help me. I want to display more than 17 fields from 6 different tables. At the time of display i want to put left to right scroll bar in my report screen. Because in my report screen the records are displayed with merg
-
Parameters for dynamic sequence
Hi, I would like to know how to pass parameters to a sequence that is call dynamicaly. Thanks
-
My log files are not being created. On the server I am getting this error: Waiting to read the SAS context from NDS.Error 1 creating log file "100330.log"