Solved running Procmon need more detail

[bbxrider]

having a problem where a .asp is attempting to instantiate an installed .dll component(createobject), program blows up can't see anything
Ran procmon with default filters (see in the attachment) Got an access violation message at the point of instantiation but hoping I can get
more detail on the specifics of the access violation.
should I remove some or all of the filters? procmon is so verbose I'm hesitant on getting it more detailed. Also just not sure how much detail is available for access violation.

from the procmon log:
41:29.2 w3wp.exe 7852 RegOpenKey HKCR\MyProg.clsMyProg ACCESS DENIED
41:29.2 w3wp.exe 7852 RegOpenKey HKU\S-1-5-20_CLASSES\MyProg.clsMyProg NAME NOT FOUND
41:29.2 w3wp.exe 7852 RegOpenKey HKCR\MyProg.clsMyProg ACCESS DENIED
Attached Images

 

[LMiller7]

You are likely to get more help with this problem at the Sysinternals forum:
Sysinternals Forums

 

[bbxrider]

yah, that makes sense, didn't think to check for a specific sysinternal forum