Windows Forum

Ask something
Discussion Locked

kmode_exception_not_handled

0 helpful
7 replies

by weitz

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

One of our machines blue screens with this message. It also references win32k.sys. The machine uses an accelECLIPSE AGP card with the latest driver. It is running an Adaptec 2940, Acer AW320 PCI sound, a PII 450, 256 MB PC100 RAM, and a 3com 905 10/100 PCI NIC on an Acer AX6BC MB. We have another machine that is almost identical with the only difference being that it has a Cheetah, and the trouble machine has an Ultrastar. We are running NT4SP5, and have updated all drivers. The primary application is ProENGINEER, but it will blue screen in any app. We have switched from a ps/2 to a serial mouse with no improvement. We have turned off proxy, but that doesn't help either.
Any thoughts?

7 replies

by jeremy

This breaks all troubleshooting rules of only doing one thing at time but...I have found that those 3com cards work best in PCI slot 1, so maybe you could swop it over. If you do not need the sound card try taking it out as well. Check the BIOS andmake sure that the PnP aware os is switched to No. If we are going to take the back of we might as well swap the RAM just to make sure.
Best of luck
jeremy

by andy_p

Can you publish the stop codes that can been seen in the Blue screen when the system crashes.

Without these the scope of the problem is too large to troubleshoot.

by liorz

is it an upgrade from 3.51 to 4.0 with PcAnywhere?
do you use PcAnywhere or "remotely possible"?
do you use SMP (2 processors)?

work arround:
there's a reskit utility calls "pstat.exe"
it lists all process and their memory adress.
the stop message is followed by a 8 digits numbers.the scecond 8dig number is the address of the failed process.
what you have to do is to find which process exist in the range of the stop number and this probabely the problem.
it can be antivirus, pcanywhere or alike and so.
if this not solve the problem then it maybe a hardware problem - failed memory or interface IRQ conflict (3com NIC's are very good whit "black magic" problems.

This discussion is closed to new replies.