NEW to W2Kpro...blue screens

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

stephen - 25 Nov 2003 17:37 GMT

I'm very new to Windows 2000 Pro after too many years using Win98.

Just wondering if these are 'normal' win2k behaviors:

After every software load, when the system restarts I will get a blue screen
with white text displaying some message, but the display is so brief I can't
read the complete message, but I do seem to see "memory dump" in there a
lot.
The system automatically reboots and then everything opens fine.

Sometimes this blue screen 'stick's and the system does NOT automatically
reboot.
I see "Unable to load device driver ...\system32\drivers\usbd.sys
0XC0000221.

On most occasions, the only thing I have connected to the USB port is a
Microsoft Optical Mouse which was recognized by Plug-and-Play and I never
installed from the CD as I did in
Win98.

Sometimes I will have the mouse and a portable hard drive attached to the
USB port. The manufacturer claims that this device does not require any
additional device driver installation under Win2K (it did in Win98 and I
installed from their CD).

Are the automatic reboot blue screens just part of how Win2K is supposed to
work?

Reply to this Message

Daniel Chang [MSFT] - 30 Nov 2003 02:04 GMT

Automatic reboots are not a "part of how Win2K is supposed to work" A
bugcheck (or Blue Screen of Death) indicate a problem that the operating
system couldn't recover from. This may be caused by hardware, but more
often caused by a driver.

Your particular bugcheck (0xc0000221) indicates
STATUS_IMAGE_CHECKSUM_MISMATCH. This indicates a driver or system DLL has
been corrupt.

Parameters
This bug check will display a descriptive text message. The name of the
damaged file is displayed as part of the message.

Cause
This bug check results from a serious error in a driver or other system
file. The file header checksum does not match the expected checksum.

This can also be caused by faulty hardware in the I/O path to the file (a
disk error, faulty RAM, or a corrupted page file).

Are there other log entries in your System Event Log that would indicate a
corrupt page file or disk error?

I've made some other suggestions in the other NG.

Signature

--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.

: I'm very new to Windows 2000 Pro after too many years using Win98.
:
[quoted text clipped - 23 lines]
: Are the automatic reboot blue screens just part of how Win2K is supposed to
: work?

Reply to this Message