📎 AI Summary:
The thread discusses a Windows Blue Screen of Death (BSOD) related to a virtual hosted Exchange server, with the initial poster seeking help. A contributor analyzes the crash dump, suggesting it may be caused by outdated network drivers and advising an update. The original poster plans to consult their hosting provider, while another member notes that the issue occurs within the IIS worker process and implicates the Windows networking subsystem, possibly due to the VMware environment's network driver. The overall sentiment indicates ongoing troubleshooting, focusing on driver updates and underlying virtualization network components.
The thread discusses a Windows Blue Screen of Death (BSOD) related to a virtual hosted Exchange server, with the initial poster seeking help. A contributor analyzes the crash dump, suggesting it may be caused by outdated network drivers and advising an update. The original poster plans to consult their hosting provider, while another member notes that the issue occurs within the IIS worker process and implicates the Windows networking subsystem, possibly due to the VMware environment's network driver. The overall sentiment indicates ongoing troubleshooting, focusing on driver updates and underlying virtualization network components.
Solution
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,163
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffff8800169456b}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+132 )
Followup: MachineOwnerthis bugcheck is usually caused by drivers using improper addresses. Unfortunately no actual driver was mentioned but looking at your call stack it does look network related. I notice some of your drivers date from 2007 and if possible try updating to later versions.
- Joined
- Jul 4, 2015
- Messages
- 8,995
Yeah looks like the BSOD is occurring in an IIS worker thread (w3wp.exe) and the actual BSOD is from the Windows networking subsystem NETIO. Since this is on a VMware box it could be the underlying network driver on the ESX host.
Last edited by a moderator:
