Microsoft SBS 2011 VMware workstation constant crashing

Hello all, this is my frist thread on this site but I have used previous threads many times from here to troubleshoot other issues I've had.

We have a Windows 7 Host running VMware Workstation with 5 virtual machines, One Windows server, 2 Windows 7 machines and 2 Windows XP machines.

The host and non server VM's are fine, they run 100% of the time and never have problems, my SBS 2011 VM is another story. There have been nothing but crashe's over the past 6 months and they are fairly random.

I beleive the server BSOD's and then it reboots, upon rebooting it just sits at a black loading windows screen forever until you completely power it off and then back on, at which time it boots up normally.

The BSOD's happen ususaly around 12 AM when Windows server backup runs and creates a server backup on another server over the network, the backup runs 7 days a week but we only see the BSOD about twice a month.

I have run through drivers in my SBS 2011 install and all seem up to date to me.

Please if anyone can help me out on this one it would be greatly appreciated.

Thanks!

I see lots of users have viewed my post here but does no one have any idea what might be going on?
Maybe I should move this to another forum? Is this one mainly for Windows 7 and not the server stuff?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\scriptcypher\Windows_NT6_BSOD_jcgriff2\040712-39281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01a4e000 PsLoadedModuleList = 0xfffff800`01c93670
Debug session time: Fri Apr  6 23:13:24.517 2012 (UTC - 6:00)
System Uptime: 4 days 14:41:18.531
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88001756ad0, fffff88009857ac0, 0}

Probably caused by : afd.sys ( afd!AfdTlFindAndReferenceTransport+70 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88001756ad0, Address of the instruction which caused the bugcheck
Arg3: fffff88009857ac0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
afd!AfdTlFindAndReferenceTransport+70
fffff880`01756ad0 66397b1c        cmp     word ptr [rbx+1Ch],di

CONTEXT:  fffff88009857ac0 -- (.cxr 0xfffff88009857ac0)
rax=0000000000000002 rbx=019920600176b4e8 rcx=0000000000000000
rdx=fffff8800177ace0 rsi=0000000000000011 rdi=0000000000000002
rip=fffff88001756ad0 rsp=fffff880098584a0 rbp=0000000000000002
 r8=0000000000000011  r9=0000000000000011 r10=fffff8800205e780
r11=0000000000000014 r12=0000000000000000 r13=fffff88001772980
r14=0000000000000000 r15=0000000000000002
iopl=0         nv up ei pl nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010203
afd!AfdTlFindAndReferenceTransport+0x70:
fffff880`01756ad0 66397b1c        cmp     word ptr [rbx+1Ch],di ds:002b:01992060`0176b504=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88001781f3b to fffff88001756ad0

STACK_TEXT:  
fffff880`098584a0 fffff880`01781f3b : fffffa80`0cd4dae0 00000000`00000000 00000000`00000002 00000000`00000000 : afd!AfdTlFindAndReferenceTransport+0x70
fffff880`098584e0 fffff880`01782496 : fffff880`098586f0 fffffa80`0cd4dae0 fffffa80`09673e98 fffffa80`00000011 : afd!AfdAllocateEndpoint+0x5b
fffff880`09858590 fffff880`01796f1c : fffff8a0`00000042 00000000`00000005 fffffa80`09673ee0 fffff800`01ae184f : afd!AfdCreate+0x176
fffff880`098586e0 fffff800`01dc8f95 : 00000000`00000005 fffffa80`0d0bd4c8 fffffa80`0d9549c0 fffffa80`0abd3ee8 : afd!AfdDispatch+0x6c
fffff880`09858730 fffff800`01dc5838 : fffffa80`08f64e40 fffff800`00000000 fffffa80`0d0bd310 fffffa80`00000001 : nt!IopParseDevice+0x5a5
fffff880`098588c0 fffff800`01dc6a56 : 00000000`00000000 fffffa80`0d0bd310 00000000`0284f168 fffffa80`08271360 : nt!ObpLookupObjectName+0x588
fffff880`098589b0 fffff800`01dc835c : fffffa80`0e0df060 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`09858a80 fffff800`01dd2f78 : 00000000`0284e718 fffff880`c0140000 00000000`0284e750 00000000`0284e740 : nt!IopCreateFile+0x2bc
fffff880`09858b20 fffff800`01ac9ed3 : fffff880`09858ca0 fffffa80`09920f60 fffff880`09858bf8 00000000`00000000 : nt!NtCreateFile+0x78
fffff880`09858bb0 00000000`7705186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0284e668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7705186a


FOLLOWUP_IP: 
afd!AfdTlFindAndReferenceTransport+70
fffff880`01756ad0 66397b1c        cmp     word ptr [rbx+1Ch],di

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  afd!AfdTlFindAndReferenceTransport+70

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4efa9418

STACK_COMMAND:  .cxr 0xfffff88009857ac0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_afd!AfdTlFindAndReferenceTransport+70

BUCKET_ID:  X64_0x3B_afd!AfdTlFindAndReferenceTransport+70

Followup: MachineOwner
---------

Network related crashes. Try to re-install the latest drivers for your network adapters. If that does not work, check firewall settings.


To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

Support for Windows Small Business Server 2011, 2008, 2003 & 2000 may be better equipped to help.

Resources and Tools for IT Professionals | TechNet is also a good source for server based systems.

I reinstalled the NIC drivers again after downloading the latest one from Intel's website, however we still seem to be experiencing problems with the server crashing.

Thanks!

I'm afraid I am out of my element with Virtual Server setups. Hopefully someone else will see the thread and have some idea. I'll see about bringing others in to help if possible.