BSOD intermittently since going to W2K sp4

[tahoe2]

Hello.
We run MetaFrame 1.8 sp4 on a W2K SP4 server. Until April, we were running W2K SP3 with all patches applied. The server was running perfectly, so why mess with a good thing?

We then upgraded our primary industry application (StaffSuite by VCG), and the server started blue screening: KMODE errors.

The developers told me it was time and I upgraded to SP4 for W2K.

Now I get STOP 0x00000050 PAGE_FAULT errors referencing ntoskrnl.exe and I get them every day or two.
I've run memory and hardware testers, it's all fine. No drivers were updated.

Any ideas? This is a critical server and I'm starting to look bad... )

Thanks,
Corie

 

[tahoe2]

It occurred to me that I was having problems like this before. When I researched, I found an article about a bad font presenting the above mentioned error. It's in KB article 237424, but basically it states BOOKMAN OLD STYLE ITALIC (bookosi.ttf, located in WINNT\FONTS) dated 1997 or earlier will crash your server when it tries to read a certain letter.

I had replaced this file a few months back, however when I ran a search I found an old version had been added when I installed Adobe Acrobat (it was in the Acrobat folder in Program Files). Our upgraded software uses, you guessed it, Acrobat to read and print reports.

I replaced the file with a new version. We'll see what happens.

Corie

 

[tahoe2]

Well, that wasn't it. This morning, as soon as folks started to log in, it crashed again. Same error.

I checked the security logs against the system log (the one that gives that all-important message "the system shutdown at (this time) was unexpected) and I found nothing in common with anything.

Any ideas?


Thanks,
Corie

 

[Ogi]

Hi,

What is your configuration?

Plus, take a look at:-

http://support.microsoft.com/search...50&QuerySource=gsfxSearch_Query&srchExtraQry=

This is all the 0x50 errors on Microsoft's site, I'd start looking at printers!

Cheers,
Carl

 

[xs4citrix]

Like Ogi says; the 50 probably means you are running a version-2 kernel mode third party printer driver on your server.
Replace it with a version-3 user mode driver.
Preferably from your OS cdrom.
Check out

http://www.printingsupport.com/proces.htm

Stefan

http://www.printingsupport.com

 

[tahoe2]

Last year we had several printing issues, and it was at that time that I got rid of all v2 kernel drivers.

OK, here is what I did and the problem has not returned for two days... I'll declare it a success next week!

I updated the NIC drivers. We have a 3Com gigabit card (3c996b) and the drivers were dated 1999.

I had been going through the event logs and figured out that the crashes happened when two or more people were trying to log in or out at roughly the same time. That's when I checked out the drivers.

As an aside, This also corrected another problem. Part of our main software is a Query Builder. Part of this wouldn't work no matter what, and the developers were pulling their hair out. This morning they called and asked me what I had done to fix it.

Thanks for the help!

Corie