cancel
Showing results for 
Search instead for 
Did you mean: 

DL 380 BSD

 
Jon_151
Regular Advisor

DL 380 BSD

When I try to view the integrated log the server BSD. I tried viewing the log file via another server browsing to the log file and it still BSD. The BSD is Driver_irql_not_less_or_equal STOP 0x000000D1
It has BSD on its own but I can not view the log to see what the error is. Does anyone know the name of the log file? I did a search for *iml but came back empty.

This is a DL380 server and is very very.... old

Not sure exactly what to do or w. I considered a PSP but wanted to get a second opinion. :-)

Thanks
5 REPLIES
dms_1
Trusted Contributor

Re: DL 380 BSD

Hi,

STOP 0x000000D1 that is a driver issue.
I agree, you should update to PSP 7.91 (in case OS is Windows 2003)
Especially if there is PSP 7.8 installed now - there are some known issues with this version.
If you are running Windows 2000 the newest version should be 7.6
This is a DL 380 generation?

Regards
Jon_151
Regular Advisor

Re: DL 380 BSD

DMS,

Yes it is the original DL380. Running Windows 2000. Thanks I will give that a shot.
James ~ Happy Dude
Honored Contributor

Re: DL 380 BSD

Hello Jon,

Do you have the hotfix + latest SP ?

http://support.microsoft.com/?kbid=841194

Regards.
Jon_151
Regular Advisor

Re: DL 380 BSD

Happy Dude,

My parameters are different than the one for the hotfix,
Stop 0x000000D1 (0x00114600 0x0000001c 0x00000001 0x88f6c3db)
DRIVER_IRQL_NOT_LESS_OR_EQUAL.

I can consistently make it BSD by using the integrated log viewer. I am leaning more towards a PSP, but thanks for the input. I like to have a plan B too. ;-))
Peter Turek
Frequent Advisor

Re: DL 380 BSD

I agree with DMS- there are known issues with the PSP 7.7-7.9 where the cpqteam.sys is known to cause problems. It's the teaming software. Upgrade to 7.91 or just upgrade the teaming and nic drivers to latest versions.

I had a server crash every 11 days and even with MS helping me with various debug utils, we couldn't quite find it until I looked up this doc. http://support.microsoft.com/kb/943998

It fixed my issue, may help others as well since there seem to be people reporting other issues than just what I and said doc experienced.

Good luck with your issue.