Confusing BSOD with Windows Server 2k3

[johnnyblazex3]

I was wondering if any of you guys could help me out with the following errors I see in the event logs. I have been getting random restarts bi-daily with nothing really provoking it. Ive done a check disk and it comes back fine, I've also ran a memtest and it passed without errors. Those are the typical tests ive run in the past and was able to verify the problem, but this time is different.

Type of server:

Dell PowerEdge 2950
Windows Server 2k3 Enterprise
SCSI RAID 5

When I log in after the BSOD

0x000000d1 (0x00000054, 0xd0000002, 0x00000001, 0xba0ef984)

Event Log


Source: USER32
Catagory NONE
Event ID 1076
Type Warning
The reason supplied by user *my server* for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000d1 (0x00000054, 0xd0000002, 0x00000001, 0xba0ef984)
Comment: 0x000000d1 (0x00000054, 0xd0000002, 0x00000001, 0xba0ef984)


Source System Error
Catagory (102)
Event ID: 1003
Type Error
Error code 000000d1, parameter1 00000054, parameter2 d0000002, parameter3 00000001, parameter4 ba0ef984.

Anyone ever experience the following?

Thanks in advance for any input.

 

[BugginOuT]

What version of SP are you on? What is your AV product, if any?

 

[johnnyblazex3]

Windows Server 2k3 Enterprise R2 SP 2

No AV.

 

[BugginOuT]

What changed from before to where it's being BSOD on a daily basis? Hardware/Software installation, Patches? What is this server being used for?

Can you review your dump file and locate the source?

 

[johnnyblazex3]

This is a domain controller. The dump came back with this, the server was up long enough for me to grab.

On Thu 10/20/2011 4:21:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102011-01.dmp
This was probably caused by the following module: bxnd52x.sys (bxnd52x+0x9995)
Bugcheck code: 0xD1 (0x54, 0xFFFFFFFFD0000002, 0x1, 0xFFFFFFFFBA0EF984)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\bxnd52x.sys
product: Broadcom NetXtreme II (NDIS VBD Client)
company: Broadcom Corporation
description: x86 BXND NDIS5.2 Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bxnd52x.sys (x86 BXND NDIS5.2 Driver, Broadcom Corporation).
Google query: bxnd52x.sys Broadcom Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


Anyone ever experience this? Would I just rollback this driver update?

 

[BugginOuT]

Did you recently update the Broadcom NIC and the BSOD started happening? If so, perform a rollback or do a clean install, but insure that you can access the box if you do a clean install.

 

[johnnyblazex3]

Did you recently update the Broadcom NIC and the BSOD started happening? If so, perform a rollback or do a clean install, but insure that you can access the box if you do a clean install.

The only thing I have run is a windows update on the machine. The Broadcom NIC hasnt been updated according to the system device manager. Shows most recent update was in 09.

 

[BugginOuT]

Could be an MS update that's causing a conflict with the Broadcom. I would suggest updating to a newer Broadcom driver and see if that resolves your issue.

I am assuming you have other DC's in the environment that is handling authentication?

 

[johnnyblazex3]

Thanks for the responses. I updated the driver, so far so good. Weird that a update would mess with a NIC like that. Keeping my fingers crossed.