ntoskrnl.exe error

[GaryCracker]

We have a Fujitsu Prinergy E200 server running Windows 2000 Server SP3 and Exchange.

Since September, we have been receiving ntoskrnl.exe blue screen errors. This randonly occurs, it could happen 3 times a day or work fine for 3 weeks then re-occur.

Working with Fujitsu we have replaced nearly every bit of hardware in the server (apart from the HDD's,Raid 5), updated service packs and drivers but still re-occurs. When we do replace some hardware or software update it does stablise the server from 1 to 3 weeks but again re-occurs. We have even tried to see if it was over-heating, so left the case off and had the air-conditiong on full power. Again it was stable for about 2 weeks but then re-occured.

Does anyone have any suggestions on what the next step could be! Is it likely to be a HDD fault, or a full software reload? Someone has suggested getting a large IDE drive, ghosting the Raid to it to eliminate if the HDD's are at fault!Would this work, or is it not likely to be the problem. I am at a wits end!

Thanks for your help in advance!

 

[MattWray]

We had the same problem. I think I have corrected it by removing a printer driver and all entries for that printer in the registry. At lease we haven't had the crash for a month and a half. The Printer driver was causing it for us I believe, but only time will tell....

Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

http://www.total-tec.com

 

[GaryCracker]

Matt,
Did the problem seem to occur everytime you printed to that specific printer or was it happening randomly without any pattern?
Thanks

 

[MattWray]

It was random, without any rhyme or reason... But once I removed that printer, everything has been running fine since, knock on wood...


Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

http://www.total-tec.com

 

[GaryCracker]

How did u know that it was a printer? Just through trial and error? Was you stripping down every piece of software to try and find the cause?

 

[MattWray]

Actually, it was blind luck. We had an old printer that was no longer on the network that kept showing up in the event logs for different reasons. So I went and removed every instance of that printer thru the registry, and all of a sudden no more BSOD's....
When it crashes, it should create a MEMORY.DMP file that can be read. If that doesn't help much, you can pay M$ to read that file and they will tell you what is going on...

Thanks,

Matt Wray
MCSE, MCSA, MCP, CCNA

http://www.sss-steel.com

http://www.total-tec.com