BugCheck 0xc99cc3c6 in event viewer. Causing Blue Screen

[Sheila DeLaney]

End user can be using either Micrsoft Word, excel or
software product called Cad19. Receive this message
frequently but not always within the same application.
Causing the blue screen error. Force to reboot the
computer.

This message was found in the event viewer.

the computer has rebooted from a bugcheck. The bugcheck
was: 0x0000050 (0xc99cc3c6, 0x00000000, 0xbfd2d5af,
0x00000000). Microsoft windows 2000 {v15.2195} a dump was
saved in c:\winnt\minidump\mini101503-01.dmp.

Does anyone know why?

 

[Bryan Wilhelm]

There is no way to tell for certain from the information you've given. A
good place to start is the third parameter of the Stop 0x50 bugcheck data:
0xbfd2d5af. This is the address of the instruction that referenced invalid
memory. It was probably mentioned on the bluescreen. The next best way to
get this information is to look at the memory dump. But from experience I'm
relatively sure that its ntfs.sys.

Make sure that you at the latest service pack. Also look at what file
system filter drivers (anti-virus, quota management, open file management,
etc) you have installed. Make sure they're up-to-date. You may want to
disable them one at a time until you find which one it is.

If this doesn't locate the problem, then you can pull out the big guns. The
address looks odd, so I suspect memory corruption. Enabling special pool
(gflags from the debugger tools:
http://www.microsoft.com/whdc/ddk/debugging/default.mspx) and driver
verifier (command line: verifier /flags 9 /all) will help catch the
culprit. You can also use the kernel debugger from the debugger tools to
load the memory dump (start with "!analyze -v").

If this doesn't help, then provide more details, like the debugger
"!analyze -v" output.

Bryan