is the next page for you to have a look at. Do a search on the page for the word class will probably be the quickest way to find the relevant part since it's right at the bottom of the page. I'm assuming what they say is not only applicable to IBM drives
I hate to point that out again but if Seti crashes right when it starts a new WU, the load on the CPU and memory seems to be the highest.
This means that there is a stability issue with the machine.
-Set all memory timings in BIOS to safest and run at clock speed. Does it still go BSOD on you?
-Use another and only one single stick of memory. If its OK you have a memory fault.
-Run Windows in Safe mode. If its OK there is a chance of a driver incompatibility.
Class drivers for disk, tape, CD-ROM, and changer devices make use of the classpnp.sys library, a system-supplied DLL that contains a collection of operating system-specific, device-independent routines.
Most system-supplied storage class drivers provide a set of key routines similar to routines found in the classpnp.sys library. This is done so that their miniclass drivers can call class driver routines instead of making direct calls to classpnp.sys. This shields the miniclass drivers from changes to the classpnp.sys DDI.
Windows 2000 changer miniclass drivers are an exception to this rule, because in Windows 2000 the changer class driver does not provide miniclass drivers with a facility for calling the classpnp.sys routines indirectly. Thus, in Windows 2000, changer miniclass drivers must either call the classpnp.sys routines directly or call equivalent routines in line. Miniclass drivers that call classpnp.sys routines directly must link to the classpnp.sys library statically, swelling the size of the driver. If a driver dynamically links to classpnp.sys, changes to this library in subsequent releases might cause the driver to malfunction.
In Windows XP and later operating systems, several of the most important services formerly provided by direct calls to the classpnp.sys library are provided by the changer class driver. Therefore, in Windows XP and later operating systems, it is usually unnecessary for changer miniclass drivers to call classpnp.sys library routines directly.
Classpnp.sys is so a front end to access your storage devices independantly of the OS.
It's mainly used by services as journalisation, bugtracers, etc.
In a word, I should say a driver in your setup has some weakness (Happened b.e. with some old SCSI drivers) when called by a service and the cpu is overloaded.
Of course, that won't help you a lot.
Did you try to make a clean reinstall of the OS (Ok, I know, not an easy decision neither an easy task) ?
I'd have a look at your HDs, floppies and CDROMs. Maybe the master/slave settings are not perfect ?
Good point OldFrog,
perhaps there is a mishap with certain applications that usually DO NOT run on my machine:
-"Real Time" File System protection anti viral SW.
-"Packet CD" or "InCD" type incremental CD writing SW.