[Ax2Grind]

Originally Posted by Windows 2000 Professional

*** STOP: 0x000000B8 (0x00000000,0x00000000,0x00000000,0x00000000)

A wait operation, attach process, or yeild was attempted from a DPC routine.

Beginning dump of physical memory

Anyone knowledgable enough about Microsoft products would help, as I've never seen this one before.

[Goofus Maximus]

I haven't found any translations, but it seems to be a common problem now with Win2K SP4 machines and various apps like Furthur, Spybod S&D, versions of Suns JRE, and some torrent apps.

A DPC stands for "Deferred Procedure Call". My knowledge is now all used up. Sorry.

[Electric_Head]

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=5782

Give that a try. The only solution I could find. It appears to be caused by virtual hardware emulators too, Daemon tools, alcohol 120%, etc, are you running any software like that?

[Ax2Grind]

Only one optical drive installed, and it's not writtable, so no Alcohol (if I remember that correctly, it's a burn program). Never heard of Furthur or Spybod (assume the latter is spyware removal), and I don't get involved at all with Kazaa or such. Could've happened from IE6, since it has - I'm assuming - the Java base or virtual console in it, but I wasn't doing anything that unusual at the time. Shame the memory dump didn't file the processes at the point of crash, but how would I go about copy/pasting a list of my current processes? The only thing I can get out of the TM is a windowshot.

Edit: oh, and there's no Clusnet key in my registry, just for future reference.

[mistawiskas]

Do you have microsoft update turned on? The updates of late are screwing with alot of machines. Several machines, all I had to do was rid them of the latest updates and all was well with the world. The first thing I do is turn that sonnovabitch off. I believe M$oft is trying to screw with XP to persuade people to make a rush on Vista when it's available....seems to be the way of microsoft to do underhanded shit anymore. i've mostly noticed that the update issues still alow one to, at least, load windows XP though, W2000 may have similar issues.

[MaesterB]

Usually physical memory dumps are a cause of bad ram in the system, partition info being corrupt, or you just need to do a clean load of Windows.

At least, in my experience, those seem to be the culprits.

[mistawiskas]

Now that maesterman mentions it, I had constant dumps on a damaged os. I reformatted and clean installed to get operation back to normal.

[Ax2Grind]

The issue hasn't occurred again, though several other crashes involving NTOSKRNL.EXE and NV4_MINI.SYS have been more frequently than before the entire issue involving my video adapter began. I don't think it's possible for Windows Update to automatically download and install anything without my knowledge when it's supposed to be set to 'request' on every turn (can't have it download anything while I'm gaming). I'll check it though, but for the mean time I'm starting another thread with the video adapter issue as a background annoyance.