Not every time but way too often this apparently happens:
 
They'll be in a sales order or purchase order and be in the line item screen to enter in parts. Sometimes, when trying to lookup the correct part number for what they want, the program will die horribly. It says access violation at 00424DDD read of address 20202020 (seems pretty fake to me!) and then access violation at 00438079 read of address 20202028. That happens twice. Then ntdll.dll goes into an infinite loop of AV's. It's great fun for the whole family.

Umm I don't remember hearing complaints about it recently. I think that it must have gotten better when we upgraded versions. I'll check though.

Quote from LeAnn Cucchiara on 09/04/07 at 08:59:02:

 
Hmm... Unfortunately the addresses don't do a lot of good to most people... Maybe not even Lynn and Alan and the gang. The fault address is a pretty nice piece of info if you've got the source code to the module that faulted. In this case it appears TAS did so we're potentially stuck scratching our heads.
 
So, I don't know what to tell you. It seems to not happen all of the time here but does sometimes.