Troubleshooting Win2K Instability

[owensdj]

Win2K Pro hasn't been nearly as stable on my machine as NT 4.0 Workstation was. I ran NT 4.0 24/7 for over 8 months without a single crash on the same hardware that Kernel Stops(Blue Screen Crashes) about every 2 weeks on average. I have a Tyan Trinity 400(VIA Apollo Pro 133A chipset) mainboard with a 667MHz P3, NOT overclocked. The rest of my specs are in my system rig info. I have SP 1 for Win2K installed.

The Kernel Stops are very random, but they never occur when I leave the machine running overnight with the Distributed.net client still running. The Stops are different each time. I've seen BAD_POOL_CALLER, UNHANDLED_KMODE_EXECPTION, and others.

Any suggestions on how I would start tracking down the problem?

 

[Shudder]

An old version of BlackIce Defender crashed my kernel overnight all the time.

If you have any type of software aside from Dis.net you may want to look into it.

 

[loosbrew]

kmode_exception_not_handled is a driver issue as is the bad_pool_caller. check to see if you have the latest drivers and or via drivers.

some more info here
bad_pool_caller

kmode exception

i get these all from this invaluable site here

good luck
loosbrew

 

[kuphryn]

Bad drivers cause most system crash for Win2k Pro. Make sure you have the latest Win2k Pro driver for every hardware.

Kuphryn