no-execute memory protect i thought that was an amd feature if so why is it enabled in my bios <ga-p35-ds3r> also i would like to know if it should stay enabled and if its bad for overclocking?
no-execute memory protect i thought that was an amd feature if so why is it enabled in my bios <ga-p35-ds3r> also i would like to know if it should stay enabled and if its bad for overclocking?
Intel also has feature preventing vulnerable code to be executed. This mostly prevents stack overflow.
i'm not sure about it's influence on overclocking, but guess you can try to find out this by yourself
Anyway most of the people do not clock to the bare limits, so imho impact will be marginal.
afik its actually a modification of the iopm bitmap for the thread. As such, there should be no performance impact what so ever.
Compared to the bottleneck of getting ram from the cache, it should be negligable.
throw new ArgumentException (String, String, Exception)
AMD = NX
Intel = XD
They both do the same thing - Help prevent / Stop buffer overflows.
There is no performance hit, as its simply a flag that is set in the data storage section. It only kicks in when its trying to do something it shouldn't.
This can stop some old games from working (I mean old - DOS era) like Theme Park, where writing data in that way was sometimes done.
Unless you have a specific reason to have it disabled, enable it
There are currently 1 users browsing this thread. (0 members and 1 guests)