The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80001c770c5, 0xfffff8800a8ef6b0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 062212-24117-01. I have tested the hard drives, tested the memory, all come up as being okay. Any ideas?

Hi Allen, Please refer to the following link for the same issue. http://social.technet.microsoft.com/Forums/uk/winservergen/thread/2399aa31-363a-492c-a1b0-0ac522be23ee Thanks and Regards, Mukesh. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Please VOTE as HELPFUL if the post helps you and remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I have no repair my computer option... maybe since it's a DC? Also, I have run memory tests several times and it passes. Not running any 1394 devices. Here is a link to the bugcheck file if it helps: https://dl.dropbox.com/u/35830153/MEMORY.DMP Also this: Created by using BlueScreenView Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size 062212-24117-01.dmp 6/22/2012 4:57:43 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`01c770c5 fffff880`0a8ef6b0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7f1c0 NT Kernel & System Microsoft Windows Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\062212-24117-01.dmp 4 15 7601 288,464 061512-41355-01.dmp 6/15/2012 4:43:04 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000 tcpip.sys tcpip.sys+631f7 x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\061512-41355-01.dmp 4 15 7601 284,344 061512-27970-01.dmp 6/15/2012 3:21:23 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`010f43f6 fffff880`025e67b8 fffff880`025e6010 cdrom.sys cdrom.sys+f370 x64 Wdf01000.sys+623f6 C:\Windows\Minidump\061512-27970-01.dmp 4 15 7601 290,744 061412-34632-01.dmp 6/14/2012 9:07:38 PM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0bb87b68 fffff880`0bb873c0 fffff880`01a948f9 Ntfs.sys Ntfs.sys+948f9 x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\061412-34632-01.dmp 4 15 7601 285,720 061312-28080-01.dmp 6/13/2012 4:46:08 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 afd.sys afd.sys+53925 x64 ntoskrnl.exe+7f190 C:\Windows\Minidump\061312-28080-01.dmp 4 15 7601 283,032 061112-123568-01.dmp 6/11/2012 3:35:22 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`01f85998 fffff880`0c497040 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7f1c0 NT Kernel & System Microsoft Windows Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\061112-123568-01.dmp 4 15 7601 283,416 061112-33290-01.dmp 6/11/2012 6:13:25 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0ae3c6d8 fffff880`0ae3bf30 fffff880`01a31310 Ntfs.sys Ntfs.sys+f310 x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\061112-33290-01.dmp 4 15 7601 284,760 061012-30014-01.dmp 6/10/2012 5:31:48 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`095750d8 fffff880`09574930 fffff800`01cae87a Ntfs.sys Ntfs.sys+5a88 x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\061012-30014-01.dmp 4 15 7601 284,568 060812-29671-01.dmp 6/8/2012 4:07:51 PM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`09783198 fffff880`097829f0 fffff880`01ad6aa2 Ntfs.sys Ntfs.sys+b7aa2 x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\060812-29671-01.dmp 4 15 7601 284,184 060812-57330-01.dmp 6/8/2012 6:16:15 AM REFERENCE_BY_POINTER 0x00000018 fffffa80`06701080 fffffa80`0e807b40 00000000`00000003 00000000`00000001 ntoskrnl.exe ntoskrnl.exe+7f1c0 NT Kernel & System Microsoft Windows Operating System Microsoft Corporation 6.1.7601.17835 (win7sp1_gdr.120503-2030) x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\060812-57330-01.dmp 4 15 7601 290,528

Hello Allen, The below info is for your reference. Analyze the dump files and try to find the file, which is cause of this server shutdown. Based on the files you can go for new HW drivers update and new hot fixes. Below links are for your reference while analyzing dump file: for dump file analysis download windebuger SW and analyze the *.dmp file to know the cause of server shutdown.Links for the software: https://skydrive.live.com/#cid=63D5AB5243DB43E7&id=63D5AB5243DB43E7%21120 or http://www.windbg.org/ Another link for the steps to analyse a dmp file: http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888 Regards, Ravikumar P

Another useful link for bugcheck codes :http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspxRegards, Ravikumar P

Output of windebugger: http://pastebin.com/JQjwbDc9

Output of windebugger: http://pastebin.com/JQjwbDc9 As per above post I've found that IMAGE_NAME: sbapifs.sys is the cause of server shutdown. Seems it is AV/security SW issue.I suggest you update your Anti-Virus SW. I would like know are you using application with the name of "Sunbelt Software"? Check your installed programs once.Regards, Ravikumar P

Thank you for your help. I will contact GFI/Sunbelt. Regards, Allen