Computing.Net > Forums > Windows 2000 > KMOD_EXCEPTION_NOT_HANDLED

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

KMOD_EXCEPTION_NOT_HANDLED

Reply to Message Icon

Name: Philip Tan
Date: February 10, 2001 at 15:26:30 Pacific
Comment:

Problem: STOP: 0x0000001E KMODE_ExCEPTION_NOT_HANDLED, Address ED0232BB base at ED020000, date stamp 37fbe181 - classpnp.sys

Whilst logged in W2K Professional, system displays the blue screen and with the above message displayed and hangs.Reboot PC and repeats same action. I've a dual boot sytem,, ie WME & W2K

Installed Win 2000 Pro with SPack 1.

I've a AMD Duron 650@850 on a ASUS A7V m/board, 256Mb SDRAM, 20Gb Seagate Barracuda ATA66(7200rpm) disk, Pixel View 32Mb Geforce MX video card, Creative Soundblaster Live soundcard.
Please help, desperate!



Sponsored Link
Ads by Google

Response Number 1
Name: Kdiddy
Date: February 10, 2001 at 17:21:49 Pacific
Reply:

Had the same problem my friend with exact same board..I am going to assume that you have it on the ATA 100 controller which is what i did...well the bad news is that its going to have to come off of that controller....and go back to the ATA 66 controller...Ive tried everything, wrote asus, the whole 9....saw a couple peeps had the same prob...and this was the only solution...I moved to the ATA 66 controller and havnt had a prob since..good luck


0

Response Number 2
Name: chrisall
Date: February 13, 2001 at 02:12:54 Pacific
Reply:

I had the same problem with a flaky RAM module, changed it & problem never re-occured


0

Response Number 3
Name: PHG
Date: February 28, 2001 at 08:24:54 Pacific
Reply:

I encountered the same error when trying to do a full new install of Win2000 on an Asus P3V4X motherboard running a PIII 800. The machine had Win98 on it for a few days previously but I decided to do a full install. At the very end of the 4th start-up disk, I received the same "Stop 0x0000001e... Kmode_exception_not_handled" however my hung up on the setupdd.sys program... I tried virtually everything... I removed each board on the machine, updated the bios, took out the AGP board and substituted an old VGA board, I turned off the Bios shadowing and cache... all failed. Eventually I found a note for Microsoft Business server that mentioned that the Kmode error relating to setupdd.sys on install usually meant the hard drive was not formatted... curiously, my drive WAS formatted however I had a Maxor drive that had been formatted using fdisk & format rather than the Maxor "Maxblaster"... when I ran the Maxor program [hey, I was willing to try anything] I was surprised to get an error that said "unable to write to partition"... after rebooting and rerunning the Maxor program, the drive was reformatted to Fat32... I then installed Win98 and upgraded to Win2000 (with a conversion to NTFS]... It worked... with all of the original defaults exactly as I had started.


0

Response Number 4
Name: Poiloon
Date: April 10, 2001 at 14:33:08 Pacific
Reply:

I am having exactly same problem now with my Win2k; i.e.,
Problem: STOP: 0x0000001E KMODE_ExCEPTION_NOT_HANDLED, Address ED0232BB base at ED020000, date stamp 37fbe181 - classpnp.sys

But mine is a little weird. The BSOD with the above message happened everytime in "exactly" 60 minutes (+-1 min) after fresh reboot. Everything works fine before that. Event log is clean. I absolutely didn't install any new hardware or software, and I've never encounter any BSOD for the past 3 months with my PC (Win2k SP 1) on 24hrs/day.

I am using a PIII 1GHz on a ASUS CUV4X, 256MB RAM, WESTERN DIGITAL 30GB ATA100 on Promise Ultra100, nVidia TNT2 - 64 video.

Anybody know how to resolve this??? Please help!!!


0

Response Number 5
Name: Four-Point
Date: April 10, 2001 at 18:44:57 Pacific
Reply:

I have exactly the same problem. The system BSODs exactly 60 minutes after a re-boot.

My configuration:
ASUS P3B-F
PIII/500
Promise Ultra/100
Quantum Fireball AS 30GB ATA100
Fujitsu 6GB ATA33

Help!


0


Response Number 6
Name: Hylke Matrix
Date: April 18, 2001 at 14:30:13 Pacific
Reply:

I have the same problems as the persons above: Done everything possible but still get that stop error after 1 hour. I know this can be fix by changing it again from the ATA 100 controller to the 66 but is there not any other solutions? Microsoft is getting really annoying with there service packs that don't solve these problems....
Please help me if you know about this problem


0

Response Number 7
Name: Four-Point
Date: April 21, 2001 at 19:22:23 Pacific
Reply:

I posted response #5.

Just thought I would update all on my progress with this problem. I hope to have more time to isolate it this week.

I have called Promise tech support, they have never seen the problem before. I referred them to computing.net and the other people having the problem. They seemed interested in the problem and are looking into it. They asked me to try to isolate the problem by just installing my ATI Rage Fury video card and no other devices and re-loading Win2000. Then if that runs without error, I'll install the Ultra 100 card. They think the problem may be caused by another card, so if it runs with the Promise card, I'll install the rest of my cards one at a time.

I also called ASUS, because everyone that has had the problem so far is using an ASUS board. They seemed less willing to help me, but said they had never seen the problem before, I referred them to the posts in computing.net, but they wouldn't even look at the web site.

I'm posting my detailed configuration in hopes that there are more hardware in common than ASUS and Promise, hope this helps. Please post if you have other hardware in common with me:

ASUS P3B-F
P III / 500MHz Slot 1
192MB PC100 RAM
Rage Fury 32MB AGP card
PCI Slot 1 - Empty
PCI Slot 2 - Promise Ultra/100
Quantum 30GB Fireball AS U/100 7200RPM (Primary Master)
Fujitsu 6.4GB U/33 (Secondary Master)
PCI Slot 3 - Allied Telesyn AT-2500TX 10/100 Ethernet card
PCI Slot 4 - Creative Sound Blaster 16 PCI
PCI Slot 5 - AOpen FM56-P Modem
PCI Slot 6 - Empty
Onboard IDE
Primary - Acer 6206 - CDRW Drive (Master)
Panasonic - ZIP100 Internal (Slave)
Secondary - Acer 640a - 40X CD-ROM (Master)


0

Response Number 8
Name: gimik
Date: April 26, 2001 at 02:19:22 Pacific
Reply:

I'm running into the exact same problem as PHG (response #3):

KMODE_EXCEPTION_NOT_HANDLED
Adress BFFBBBBE at BFFA2000 DateStamp 3946cc08; setupdd.sys

i've never had a problem with my WinMe/Win2000 dual boot configuration before until just a couple days ago i rebooted my system and hit a blue screen for a fraction of a second (too quick to read) before it rebooted again automatically. booting in safe modes and last known good configuration start the same reboot loop. i attempted to boot up with a win2k bootdisk set, but sure enough right after it completed its initial load, the bsod came up and stayed (kmode_exception, etc).. i can't say for sure if this is the exact same message as when booting from the hard drive, but i'd bet it is.

i can still access the win2k fat32 partition from my windows me drive, and i've run a thorough disk surface scan on the win2k drive with no errors. still haven't come up with a solution other than to kill it and reformat.

my config:

Harddisk 0 (c) Win Millenium; 30 gig maxtor
Harddisk 1 (d) dos; 14gig ibm desktar
Harddisk 2 (e) Windows 2000; 6.4 gig maxtor
cdr/rw yamaha CRW2100e (g)

Abit BH6
P2 Celeron 300A slot1
128 mb ram
nvidia geforce agp
diamond technologies pci soundcard
336ifx modem


0

Response Number 9
Name: Poiloon
Date: May 11, 2001 at 00:13:56 Pacific
Reply:

Hi,
I've posted here earlier as I'm having these BSOD per hour problem (see above). I've found the culprit to my problem. It turns out that my Western Digital 30GB ATA100 hard drive is faulty. I just got it replaced with identical hard drive (on Promise Ultra00) and reinstall Win2k. Now, Win2k is running smoothly and no more BSOD.
Prior to replaciong the hard drive, I've connected the ATA66 socket, and no BSOD as what everyone expects. My hard drive did not exactly went dead but faulty. Win98 ran just fine. I guess Win2k is a little too sensitive to hardward glitches, thus suspending to BSOD.
Also, for your information, windows surface scan did not detect errors with my hard drive. I found that it's faulty with WD diagnostic tool.
Hope this can shed some lights on the problem. Good luck.


0

Response Number 10
Name: Kian
Date: May 20, 2001 at 01:26:48 Pacific
Reply:

I've almost similar configuration with Four-Point (Response no. 7).

ASUS P3B-F
P III / 500MHz Slot 1
256MB PC133 RAM
Creative RIVA TNT2 32MB AGP card
PCI Slot 1 - Promise Ultra/100
Maxtor 20GB U/66 7200RPM (Primary Master)
IBM 20GB U/100 (Primary Slave)
PCI Slot 2 - Empty
PCI Slot 3 - 3COM EtherLink 10/100 PCI TX NIC
PCI Slot 4 - Empty
PCI Slot 5 - Creative SoundBlaster Live
PCI Slot 6 - Empty
Last ISA Slot - US Robotics 33.6 Internal Modem
Onboard IDE
Primary Master - Creative Infra 52X

My Win2K was running fine for the past 2 months, until recently I got exactly the same error like the rest of you. The error is recurring after rebooted around an hour's time. I've just upgraded to SP2 few days ago, hoping that the problem will be solved but it turned out to be negative. I then visited the Microsoft Product Supports Site for an answer. Microsoft has confirmed that it is a problem in the Win2K but gives no solution to it. The cause to the error is
when the redirector (the OS) extends certain allocation sizes, it does not update Cache Manager with the changes which causes the computer to stop responding (hang).

Does anyone came out with new findings or solutions? Any comment about the CLASSPNP.SYS? It seems to be closly linked with the above problems.


0

Response Number 11
Name: Steven
Date: October 13, 2001 at 17:05:45 Pacific
Reply:

Had same problem - computer blue screens every hour and then reboots.

Original error message from event log was:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0xed0432d1, 0x00000000, 0x00000028). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini101201-05.dmp.

I tried everything reinstall, bios update, memory change etc etc...

I eventually ran the Western Digital diagnostic software which found an error during the quick self test. I then created a diagnostic disk using EZmaker.exe (available from www.westerndigital.com) and installed the diagnostic tools.

This fixed the problem to the following extent: the computer no longer crashed every hour. However, I now get the following error:

The description for Event ID ( 26 ) in Source ( Ultra ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: \Device\Scsi\Ultra1.

I am going to claim warranty on the hard drive and see how I go with a new drive. Will let everyone know how this goes.

Steven.


0

Response Number 12
Name: Eric
Date: February 17, 2002 at 22:36:02 Pacific
Reply:

This is what (finally) worked for me.

I too have a Maxtor HD. Used MaxBlast from their website and did a low-level format, and then partitioned and formatted it using their software also.

Then I copied the entire Windows 2000 CD to the HD. Then I booted off a WIndows 98 startup disk and entered the following to start the DOS-based setup of Windows 2000:

c:\i386\winnt

It'll ask you where you put the WIndows 2000 files, tell them and commence installing.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: KMOD_EXCEPTION_NOT_HANDLED

WIN2000 install problem www.computing.net/answers/windows-2000/win2000-install-problem/12560.html