Fatal System Error 0000a
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 04:44:52 GMT by s_ac4 (squid/3.5.20)
Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only fatal system rpg Display results as threads Useful Searches Recent Posts More... WindowsBBS Forums > Security > c000021a windows 10 Malware and Virus Removal > This site uses cookies. By continuing to use this site, you are agreeing to our use error 000021a windows 10 of cookies. Learn More. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations. Cookies Registration Notice Solved Error during startup: http://answers.microsoft.com/en-us/windows/forum/all/blue-screen-error-c000021a-fatal-system-error/549075f8-f695-4047-b747-2b4e118e1ffd Stop: c000021a (Fatal System Error) Discussion in 'Malware and Virus Removal' started by jharry, 2015/02/07. Page 1 of 4 1 2 3 4 Next > 2015/02/07 jharry Well-Known Member Thread Starter Joined: 2008/12/07 Messages: 106 Likes Received: 1 Trophy Points: 108 Computer Experience: intermediate [Solved] Error during startup: Stop: c000021a (Fatal System Error) My laptop failed to startup. Following are a list of screens (messages) encountered during startup of Windows https://www.windowsbbs.com/threads/error-during-startup-stop-c000021a-fatal-system-error.108848/ 7. Screen 1: Stop: c000021a (Fatal System Error) The initial session process or system process terminated unexpectedly with a status of 0x00000000 (0xc0000001 0x000106c8). The system has been shut down. Screen 2: (after Startup Repair ran for several minutes) Startup Repair cannot repair this computer automatically Sending more information can help Microsoft create solutions. -> Send information about this problem (recommended) -> Don't send view problem details I selected the "send information" option, but probably the information was not sent, because due to the system error, there was no internet connection. Screen 3: (after selecting "view problem details") Problem signatures: Problem Event Name: StartupRepairOffline Problem Signature 01: 6.1.7600.16385 Problem Signature 02: 6.1.7600.16385 Problem Signature 03: unknown Problem Signature 04: -1 Problem Signature 05: Auto Failover Problem Signature 06: 9 Problem Signature 07: NoRootCause OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Screen 4: Windows cannot repair this computer automatically view diagnostic and repair details. view advanced options for system recovery and support. Screen 5: (after selecting "view diagnostic and repair details") Starup Repair diagnosis and repair log -------------------------------------- Last successful boot time: 2/4/2015 6:00:11 AM (GMT) Number of repair attempts: 9 Session details --------------- System Disk = \Device\Harddisk0 Windows directory = D:\Windows AutoChkRun = 0 Number of root causes =
You can http://www.ibm.com/support/docview.wss?uid=swg1LO68746 track all active APARs for this component. APAR status Closed as fixed if next. Error description Error Description nsd_W64I_ACME SERVER_2012_03_23@13_12_06.log Host Name : ACME SERVER User Name : SYSTEM Date : Fri Mar 23 13:12:06 2012 Windows Dir : C:\Windows Arguments fatal system : "P:\Program Files\IBM\Lotus\Domino\nsd.exe" -dumpandkill -termstatus 1 -panicdirect -crashpid 5796 -crashtid 4140 -runtime 600 -ini "P:\Program Files\IBM\Lotus\Domino\notes.ini" -svcreq 128 NSD Version : 8.5.23.1132 (Release 8.5.2FP3) OS Version : Windows/2008 R2 6.1 [64-bit] (Build 7601), PlatID=2, Service Pack 1 (2 Processors) Build time : fatal system error Mon Jul 11 03:52:14 2011 Latest file mod : Fri May 13 09:03:31 2011 Domino Version : Release 8.5.2FP3 (64-bit server) Keyview Version : 10.8.0.0 ############################################################ ### thread 20/70: [ nHTTP: 16a4: 102c] FATAL THREAD (Panic) ### FP=0x6de07188, PC=0x77cb135a, SP=0x6de07188 ### stkbase=0x6de10000, total stksize=4194304, used stksize=36472 ### EAX=0x00000041, EBX=0x00000000, ECX=0x6de06162, EDX=0x7FE9017D537 ### ESI=0x000927c0, EDI=0x00001f9c, CS=0x00000033, SS=0x7FE0000002B ### DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0x7FE00000000 Flags=0x00000287 ############################################################ [ 1] 0x77cb135a ntdll.ZwWaitForSingleObject+10 [ 2] 0x7FEFE1B10DC KERNELBASE.WaitForSingleObjectEx+156 @[ 3] 0x00e6535f nnotes.FRSendCommandToService+1931 @[ 4] 0x00e68b73 nnotes.OSRunExternalScript+5835 @[ 5] 0x00e624d5 nnotes.FRTerminateWindowsResources+2277 @[ 6] 0x00e6bbe2 nnotes.OSFaultCleanupExt+622 @[ 7] 0x00e6c609 nnotes.OSFaultCleanup+29 (0,0,0,0) @[ 8] 0x00e8665d nnotes.OSNTUnhandledExceptionFilter+677 @[ 9] 0x00df85ca nnotes.Panic+682 (0,6,6de0fe08,e2e156) @[10] 0x00e2cf87 nnotes.OSUnlockSem+35 @[11] 0x00e2675b nnotes.LockMemHandle+371 @[12] 0x00e27ad4 nnotes.OSMemoryLock+120 (6de0fda0,0,0,6cc33750) @[13] 0x02900cc7 nnotes.DbBktDescGet+2391 4) After a couple of passes through the Fatal
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 04:44:52 GMT by s_ac4 (squid/3.5.20)