All ok. PC start normally. Wonderful. So, remain only the problem with the program imazing. I don't undestand why the problem with DEP. It's very strange. If anyone have solution for this problem, the thread can be close. Thanks to all for the help.
All the Blue screen errors are now gone, good.
Then the question remains on imazing. How long have you experienced this particular problem with the program? The latest product update was last November, and that is not so very long ago. What has changed on your computer since then?
Makes me wonder what the issue is with DEP? Search Event Viewer for the error signature (Event ID), that might help identify what module is causing the User mode access violation. With this information, you could post here, or send a copy to the software vendor. Once you have more information and a better understanding, you should contact the Vendor and obtain more support from them.
Do you believe me if I tell you that I have not found anything in terms of errors in the event viewer? it seems impossible but it is so I checked in all the folders. The only things I found (I started the program a little while ago and made that error come out in order to search for it as the last event) are:
Mbamchameleon Failed to obtain file name information - C00000BE (Event ID 61703)
(which should be referred to MalwareBytes Anti-Malware but I disabled it);
The Application Compatibility Verification service is now in run mode. (Event ID 7036).
There is nothing more. It's possible? Thanks again for everything.
This was apparently a year and 2 months ago, but still, I joined just to say THANK YOU - this is why I love people who follow up with their solution if they find one! You just saved me from hours of headache doing a total reinstall of Windows on this old Vista laptop (mere days after finishing another one) due to an infinite blue screen loop, apparently caused when I disabled DEP. I thought I'd searched everywhere...it's amazing that there's almost no information about this on the internet. (Seriously, google "bcdedit" "set default nx", with the quotes... 4 entire results!)
Dumb thing is, I was this close to figuring it out before almost giving up but thankfully finding this post. I had the recovery command prompt at startup and was trying c:\Windows\system32\bcdedit /set {current} nx OptIn, based on what I was finding on other sites - but of course, that only works if you're already logged into Windows normally; I needed that elusive {default} keyword.
Anyways, THANK YOU for sharing your solution - just wanted you to know I appreciate it!!
Quote