Windows 7 Looking for help with mimidump file.

Solution
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: MachineOwner
...

kemical

Essential Member
Joined
Aug 28, 2007
Messages
36,176
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: MachineOwner
Hi,
this 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.
 

Solution

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,998
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.
An image from 'Looking for help with mimidump file.'. Windows network architecture showing the Winsock API, transport/service providers, and kernel components.
 

Last edited by a moderator:
Back
Top