error messages in win 2k 1

[candyman72]

Hi All, I am having ramdom error messages appearing for no real reason at all, this is all the errors i am getting:
*STOP:0X0000001E(0XE0000005,0XEB4232BB,0X00000000,0X00000028)K_MODE_EXCEPTION_NOT_HANDLED

ADDRESS F20232BB BASE AT F2020000 DATESTAMP 37FBE181 CLASS PNP.SYS
BEGINNING DUMP OF PHYSICAL MEMORY
PHYSICAL MEMORY DUMP COMPLETE.CONTACT SYSTEM ADMI.OR TECH. SUPPORT GROUP

STOP:0000007B(0XEB81B84C,0XC0000034,0X00000000,0X00000000)INNACESSIBLE BOOT DEVICE

Now for my system specs:

AMD 700
asus a7v mainboard
asus nvidia riva tnt2 m64 video
creative 52x cd-rom
plextor 12-10-32
384 megs ram
generic sound card
windows 2000 home pro.
Thanks a lot for any help you can give me.

 

[SESaskDFC]

Howdy:

As per Microsoft..

During the normal operation of your computer running Microsoft Windows NT, the computer may stop responding (hang) and display one of the following error messages:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL


STOP 0x0000001E: K_MODE_EXCEPTION_NOT_HANDLED
When you run the Dumpchk.exe utility, the utility may report that the dump file is invalid.
CAUSE
The Pagefile.sys file may be damaged.
RESOLUTION
To resolve this issue:
Click Start, click Run, type CHKDSK drive: /F /R where drive: is the partition containing the Pagefile.sys file, and then click OK.
When the Chkdsk.exe utility has completed, set the paging file size to 0.
Click Start, point to Settings, click Control Panel, and then double-click System. Click the Performance tab, click Change, and then point to the partition containing the Pagefile.sys file.
In the Initial Size (MB): box, type 0.
In the Maximum Size (MB): box, type 0.
Click Set, click OK, click Close, and then click Yes when you are prompted to restart the computer.
After the computer has restarted, reset the Pagefile.sys file to the correct size.
Click Start, point to Settings, click Control Panel, and then double-click System. Click the Performance tab, click Change, and then point to the partition containing the Pagefile.sys file.
In the Initial Size (MB): box, type a value equal to the amount of random access memory (in megabytes) in your computer plus 11.
In the Maximum Size (MB): box, type a value equal to or less than the amount of disk space available (in megabytes) on the specified partition minus 1.
Click Set, click OK, click Close, and then click Yes when you are prompted to restart the computer.

Murray

 

[candyman72]

WOW, thanks alot,, not only fast,but detailed instructions on how to fix it. thanks alot again.will let you know what happens!!
p.s.: someone else told me it could be an aspi layer that is missing?? any comment?? thanks again.

 

[gargouille]

What are you doing when it happens?
Have any scsi devices onboard? (asking for boot from scsi in BIOS?)
classpnp.sys are scsi drivers (that's where the error message originates as expressed in the last of the 2nd line of the error message.

IF no joy from Murray's post:

http://support.microsoft.com/default.aspx?scid=kb;en-us;122926

 

[candyman72]

wierd, it is still doing it,kmode exception not handled,, the others arenot coming back as of yet,.thanks alot for your help, any thought of the aspi layer??

 

[candyman72]

new error,,is as follows:

STOP:0X0000001E(0XC0000005,0XEB42332D,0X00000000,0
X00000028)
anyone have any clues??thanks

 

[GeoffTCS]

This is from microsoft technet. Q195857.

Symptoms
While shutting down an application the system may stop with a STOP 0x0000001E or STOP 0x00000024 error message. In the case of the STOP 0x0000001E the first parameter will always be C0000005.

Cause
This problem occurs when an application opens a lot of handles but never closes them. This has been seen when an application continually opens a registry key but never closes it. When the application is closed the system attempts to close all of the keys but runs out of system resources while doing it.

Resolution
To resolve this problem, the application has to be modified to close the registry key when it is done with it.

HTH
Geoff

 

[AlexTG]

This is just more info for anyone else who comes along looking for an answer to this one:

I have been receiving the same STOP error with CLASSPNP.SYS lately, and I know that I have either a bad Maxtor(Promise) ATA100 controller, or the relatively new 80Gig Maxtor drive connected to it is bad.

The pagefile.sys file was on this drive at first, but after my initial problems I moved the page file to another drive. Once I did this and repaired the drive (I think there was a bad spot on the drive) with a Maxtor drive utility, the initial problem went away for a few weeks.

After this problem began the first time, I ran CHKDSK on the drive once and the problem stopped for a while, but now it's back.

My system crashes exactly 1 hour after reboot, almost on the nose - I can tell this by the time stamp on the minidump files I get when I immediately reboot after a blue screen. So, the system is checking my hard drives in some way exactly 1 hour after booting up, and it doesn't like something it finds on this drive.