cluberti

jscript.dll has little to do with actual java - it is responsible for running javascript, which is a java scripting language (it's not full-blown java or a java applet - they sound similar, but are much different). Does the error crash IE, or just give a pop-up error?

Are you mapping this drive via a logon script, or running something perhaps from this server during the logon process? Failing that, I'd say that getting a userenv log would be a good start.

Hmmm - seems to indicate a problem executing a method during a file backup operation, but that could be completely irrelevant. Consider using "stepping mode" (http://archives.neohapsis.com/archives/ntbugtraq/2002-q1/0125.html) - note that the KB no longer exists, but the method should still work.

What more do you want? It's either intelppm.sys, or a bum processor.

You can delete the admin account from AD - it's not a local account (DCs don't have local account SAMs).

If you run W2K3SP1 or higher, the SYSTEM account on a DC no longer has any write access to the AD database, so it won't work. If it's RTM, however, it may be possible.

You can try booting the server in AD Restore Safe Mode, and if you can login you can create an account. However, if you truly did delete the only admin account in the AD, and can't get in to restore a backup, you're pretty well hosed.

Never heard of HP-yux? Hmm - you must be a young-un http://en.wikipedia.org/wiki/HP-UX

That's not something you can do easily (well, not really at all) with the built-in ICS software in Windows. That requires the use of RRAS or ISA (or another proxy/firewall package, if you so choose).

That's pretty warm for even an Intel CPU - perhaps you can get into the BIOS and reduce the clock speed, but you'd have to check the motherboard manual, as they're all different about that sort of thing. If you leave the system off for a few hours and turn it back on, does it run without crashing for awhile, and does the temp keep going up?

Please tell me you have a recent system state backup on that server...

It's in the contract somewhere, and someone will know - if the school has a premier support agreement, they'll have access to a TAM and a CSM that can find that out as well.

Well, maybe. You crashed after doing an EtwpGetPerfCounter from the kernel (nt!), and the next call should/would have been hal!HalGetInterruptTargetInformation - this would have been a call to the processor through the driver it uses - as such, it is possible that it's a problem with the processor hardware, but it's more likely a problem with the intelppm driver from the Intel Chipset software. I can only see what you show in the dump and what I know to be happening with the perf counters in that stack from experience, but that'd be my educated guess from your basic output.

it says: "A bona fide full version of Microsoft Windows: XP Home or Professional with Service Pack 2, WIndows Vista Home Basic, Home Premium, Business, or Ultimate. (No upgrade or multi-disc versions)." and my cd is a copy so. . . i cant tell . . . should i downld. the sp2? From whom did you get the XP Home CD?

If WMI and the spooler start up, along with csrss, it could very well be a print driver trying to query data - do you have any printers installed?

All of the default DCOM permissions are stored in HKLM\Software\Microsoft\OLE, but if you need to change permissions on a COM object specifically you have to find that COM object in the registry (usually it's GUID in HKCR\CLSID or HKCR\AppID) and make the change there. A restart of the DCOM service is required, or a reboot of the box.

Well, I think perhaps a dump is in order here. The 0x0D parameter in the 0x7F bugcheck means that the OS hit an exception not covered by some other exception handler, which means that it was likely a protection fault that pertains to access violations for applications or drivers that caused the issue. While it's still possible that it's hardware, the fact that it was a 0x0D means it's at least more likely to be poorly written driver software than an actual hardware fault. What's running on that box, btw?

In shellexview you're looking for non-Microsoft or blank items - if it's not Microsoft, disable them. Reboot and see what happens.

How quickly does it occur on a first install, and does it always start at around the same point in the build, or is it random?

Since the menu and startup options are part of the loader process binary, you'll find this very difficult to do.

If it's a VLK copy of Windows corporate, no. If it's a retail or retail OEM copy, all you need is the COA and product key.

Hmmm - perhaps you could configure the box for a complete dump, reboot, and then generate the dump while the control panel is hung. However, the control panel is just launched under explorer.exe, so it could be something that you have installed with an explorer hook (you can disable these with ShellExView from nirsoft.net).

That is true for OEM copies, but not ANY other licensed copy of windows (especially VLK). Those copies are licensed to the original purchaser, and for a VLK, the license does not and cannot transfer with the hardware. You said these came with VLK corporate copies of XP, which is not OEM, which means that hardware does not have a valid license to run Windows. It only passes the check for WGA because the key is valid - it means the key is, not your license. You need licenses.

One other thing you can try - if you've got a PS/2 (not USB) keyboard attached to that box (or it's a laptop), configure your machine for a complete memory dump via the keyboard (instructions), and then shut down and reboot. Once you're "stuck", try the keyboard sequence (hold down the RIGHT-hand CTRL key and press the SCROLL LOCK key TWICE) - if the box bugchecks, you're not hung (the kernel was running) and the dump will tell us likely who or what is holding you up. However, if you set it up correctly and the keyboard sequence does NOT bugcheck the box, you've very likely got a hardware or BIOS issue.

Is it found as a fixed, or removable, drive? If it's removable, you can't do it. You'd need to change the SCSI layer implementation to do this at the OS level.