48 Posts

April 23rd, 2004 14:00

I seem to have fixed the problem ! 

Just now I uninstalled Sound Blaster Live! card and the modem and now the system booted without the dreaded KMODE_EXCEPTION NOT HANDLED...  ntoskrnl.exe. 

 Note that in the initial installation I simultaneously placed Sound Blaster card AND modem card on motherboard,  Maybe the moral of the story is that one should add adapter cards one by one ?

My next step is to reinstall modem, shut down, see if system boots, then repeat this process for SoundBlaster card,   

48 Posts

April 23rd, 2004 15:00

11:40 am  Nasty surprise ! I put the modem card on the motherboard and rebooted and ... got the nasty ***STOP...KMODE_EXCEPTION_NOT_HANDLED

11:50 am  Now I am retrying , this time going into SETUP on my XPST500 BIOS version A11 and specifying "No" to Advanced > Plug&PlayO/S.and specifying "Yes" to ResetConfigurationData.  This is based on idea that maybe the modem does not function as Plug&Play under Win2000 (I think it's PNP under Win98).

11:53 am   Rats !!! Got the same old "***STOP:... KMODE_EXCEPTION_NOT HANDLED .. ntoskrnl.exe.  I wish that Microsoft would give error numbers for each type of crash so that one could reference them.,

Should I conclude from this that the modem is incompatible with Win2000 ?  I note I downloaded a Win2000 driver for this modem.... but from a third party source,,,  Maybe I should go to CompUSA and pick up another modem ?  

Or should I boot in Safe Mode and remove any drivers for this modem (drivers did not show when the modem was removed).

11:57 Reviewing documentation provided by Dell concerning identity of modem supplied with my machine shows total confusion, with three different model numbers and names, as follows:

(a) Dell Packing Slip that came with my computer says "Conexant V.90/56 Telephoney". 

Online Dell documentation on original configuration of my computer is a triumph of confusion because it lists *two* modems, both with different names than on the Packing Slip: 

(b) It lists model # 037JN   Kit, Modem, V.90, Data/Fax/Voice, Dimension, Asia, Latin America, North America and 

(c) It lists model # 49XJC   Modem, V.90, Internal, DFV, Asia, Latin America, North America, Dimension, 

Someone at Dell is seriously incompetent !

12:51 pm  Rebooting in Safe Mode to look for any modem drivers to remove them. In System>Device Manager>Modem the current modem driver is listed as Conexant MDP3900V-U modem. Evidently this has to be wrong so I'm going to remove it and reboot.

12:52 pm  Time for lunch.... will report on next episode in this saga later on

 

 

 

 

48 Posts

April 23rd, 2004 15:00

11:40 am  Nasty surprise ! I put the modem card on the motherboard and rebooted and ... got the nasty ***STOP...KMODE_EXCEPTION_NOT_HANDLED

11:50 am  Now I am retrying , this time going into SETUP on my XPST500 BIOS version A11 and specifying "No" to Advanced > Plug&PlayO/S.and specifying "Yes" to ResetConfigurationData.  This is based on idea that maybe the modem does not function as Plug&Play under Win2000 (I think it's PNP under Win98).

11:53 am   Rats !!! Got the same old "***STOP:... KMODE_EXCEPTION_NOT HANDLED .. ntoskrnl.exe.  I wish that Microsoft would give error numbers for each type of crash so that one could reference them.,

Should I conclude from this that the modem is incompatible with Win2000 ?  I note I downloaded a Win2000 driver for this modem.... but from a third party source,,,  Maybe I should go to CompUSA and pick up another modem ?  

Or should I boot in Safe Mode and remove any drivers for this modem (drivers did not show when the modem was removed).

11:57 Reviewing documentation provided by Dell concerning identity of modem supplied with my machine shows total confusion, with three different model numbers and names, as follows:

(a) Dell Packing Slip that came with my computer says "Conexant V.90/56 Telephoney". 

Online Dell documentation on original configuration of my computer is a triumph of confusion because it lists *two* modems, both with different names than on the Packing Slip: 

(b) It lists model # 037JN   Kit, Modem, V.90, Data/Fax/Voice, Dimension, Asia, Latin America, North America and 

(c) It lists model # 49XJC   Modem, V.90, Internal, DFV, Asia, Latin America, North America, Dimension, 

Someone at Dell is seriously incompetent !

12:51 pm  Rebooting in Safe Mode to look for any modem drivers to remove them. In System>Device Manager>Modem the current modem driver is listed as Conexant MDP3900V-U modem. Evidently this has to be wrong so I'm going to remove it and reboot.

12:52 pm  Time for lunch.... will report on next episode in this saga later on

 

 

 

 

2 Intern

 • 

2.4K Posts

April 24th, 2004 01:00

If you have isolated the modem and nothing else as the culprit and you really need it, consider selling the one you have and buy an another one that is Win2k compatible.

2 Posts

May 18th, 2004 16:00

Hello.

I have gotten the similar problem yesterday without any additional installed driver!!  (I am a sort of beginner with maintaining W2K, FYI.)

Message were:

STOP 0x0000001E (0xC0000005, 0x8041FBB1, 0x00000000, 0x00000008) KMODE_EXCEPTION_NOT_HANDLED.

Address 8041FBB1 based at 80400000, DataStamp 4047db83 - ntoskrnl.exe

Beginning dump of physical memory

----------

 

According to some suggestions at MS website, 1) I have restarted on safe mode and tried to install Service Pack 4 which has been installed, but I cannot see on "Add/Delete Program" window on the safe mode or I cannot install it again with some error which is not clear during the installation on the safe mode.

2) I have also tried to fix it using Recovery Console (with the w2k installation disk) but in vain.

Or, 3) I have reinstalled on the recovery installation, but in vain.

Since I did not install any new driver before getting the blue screen error, I have no idea what driver conflicts.  Will you give me an advice how I can figure it out?

BTW, I have had the blue screen error message when shut off/restart 'physical momory error (due to the driver conflict, I guess) for a while.  It may be related with the error this time, but again I never knew what drivers conflicts each other.

Thank you so much for your informative suggestions.

 

48 Posts

May 19th, 2004 21:00

Hi:  I don't know enough to help you on this one.   But I do suggest you repost this message as a new message... it'll kind of get buried here..

May 21st, 2004 20:00

I am getting the exact message you posted.

I pop out my DVD/CD writer and things boot fine.  Not a solution, but a clue

2 Posts

May 21st, 2004 21:00

Hi.  I gave up fixing it and reinstalled the whole W2K today.  From now I am taking notes whenever I install any software or hardware what makes "memory dump".

Well,

Still I would like to have the solution for this if anyone could solve it.

Thanks,

sophie

 

 

 

No Events found!

Top