Author Topic: Kmode Exception Win 2K  (Read 1746 times)

Anonymous

  • Guest
Kmode Exception Win 2K
« on: June 02, 2002, 10:06:54 AM »
I have been running Win2K on a 1G Athalon Tbird with 512K ram for over a year and within the last week started getting this error message:
   \" Stop 0x0000001E (0x0000005) 0xEB4232D1, 0x000000, 0x00000028  Kmode exception not handled  address EB4232D1 base EB42000, Date stamp 39fb06 class pnp.sys\"
    Of course the blue screen of death comes along also.  It will restart and work fine until it does it again anywheres from 1 to 4 hours later.  Tried restore from my ERD.  The CPU Temp at time of lock-up is 106F.  I removed 1 memory stick at a time without any improvement.  Any ideas?  MB Is Asus A7v133, Vid ATI All-in-wonder128 RAEDON, SB PCI-128.  Reseated all plugins.  Am I losing my MB or CPU or what?

Offline rdc

  • enthusiast
  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 372
  • Karma: +0/-0
    • View Profile
Kmode Exception Win 2K
« Reply #1 on: June 02, 2002, 03:51:06 PM »
Got to  the winnt folder -system32 -drivers - and  rename  pnp.sys to something like pnp.syx , If you cannot rename it move it to the root directory and restart windows .I looked into the drivers folder of my w2k pro and the pnp.sys doesn\'t exist only \"isapnp.sys\"
good luck .

Offline Tracky110XP

  • member
  • Global Moderator
  • Full Member
  • *****
  • Posts: 118
  • Karma: +0/-0
    • View Profile
Kmode Exception Win 2K
« Reply #2 on: July 11, 2002, 10:05:34 AM »
stop 0x1E error messages are very generic, but for the most part refferance drivers of software goign bad on a system.
one thing to try is to rename the %systemroot%system32drivers folder to drivers.old then do TWO fast repairs back to back without booting into the OS.

if that doesn\'t work then boot to the w2k cd and press enter to install then r to repair the install that it finds.

but all in all a clean install will fix this issue, i don\'t think that any hardware is going bad on the system.