STOP Error - nicm.sys

[Guest]

Intermittenly I recieve a STOP error on two different Windows XP Professional
machines. They both have service pack 2 (SP2) and Novell Client 4.83
installed. Does anyone know how to resolve this? The details of the blue
screen are as follows:

A problem has been detected and Windows has been shut down to prevent damage
to your computer. The problem seems to be caused by the following file:
nicm.sys

PAGE_FAULT_IN_NOPAGED_AREA

Technical Info:
STOP: 0x00000050 (0xE3269FD0, 0X00000000, 0xAA77D570, 0x00000001)
Nicm.sys - Address F7F6F570 base at F7F6E000.
Date Stamp 3C61CB82

 

[Bert Kinney]

Hi Matt,

Here's a good place to start looking.
Troubleshooting Windows STOP Messages
http://aumha.org/win5/kbestop.php#general

 

[Guest]

Bert-

Thank you for the response and the great link. I bookmarked it and will
visit this site frequently. However, the information I found was a bit
general and wasn't very helpful. I'm hoping to get an answer from someone who
has had this problem themselves or have heard about it. I researched the file
nicm.sys and it's definitely related to the Novell client. Thanks again.

-Matt

Hi Matt,

Here's a good place to start looking.
Troubleshooting Windows STOP Messages
http://aumha.org/win5/kbestop.php#general

--
Regards,
Bert Kinney [MS-MVP DTS]
http://dts-l.org/

Intermittenly I recieve a STOP error on two different
Windows XP Professional machines. They both have service
pack 2 (SP2) and Novell Client 4.83 installed. Does
anyone know how to resolve this? The details of the blue
screen are as follows:

A problem has been detected and Windows has been shut
down to prevent damage to your computer. The problem
seems to be caused by the following file: nicm.sys

PAGE_FAULT_IN_NOPAGED_AREA

Technical Info:
STOP: 0x00000050 (0xE3269FD0, 0X00000000, 0xAA77D570,
0x00000001)
Nicm.sys - Address F7F6F570 base at F7F6E000.
Date Stamp 3C61CB82

 

[Joshua Smith [MSFT]]

Hi Matt,

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft

 

[Guest]

Joshua-

Thanks for the great advice. This seems like a sure way of narrowing this
error down. Also, learning verifier will definitely help me out for future
blue screens as well. I'll do this on the problematic computers and send you
the contents of the minidump when another blue screen occurs. This problem is
fairly intermitten so it may be awhile 'til I can get back to you. Thanks for
your help.

-Matt

 

[Guest]

Here's some additional information I found from the Event Log about the same
time the blue screen occurs:

Source: System Error
Category: (102)
Event ID: 1003
Description: Error code 10000050, parameter1 e322efd0, parameter2 00000000,
parameter3 aa7a1570, parameter4 00000001.

Note: parameter3 varies each time. (Examples: aa789570, aa77d570, aa785570,
f8a19570, aa78d570, aa795570) Seems as though it's usually aa7**570

 

[Bert Kinney]

In addition to Joshua Smith's fine troubleshooting steps, here's some
information on the error reported in the Event Viewer.

EventID.Net
http://www.eventid.net/display.asp?eventid=1003&source=system+error