Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


NX off on X64?

  • Please log in to reply
1 reply to this topic



    GroupPolicy Tattoo Artist

  • Member
  • PipPipPipPipPipPip
  • 1,357 posts
  • Joined 21-April 05
  • OS:none specified
  • Country: Country Flag

I disabled it quite some time ago and forgot about it. I haven't noticed any problems with it, but I vaguely remember I read somewhere it was not recommended. Is it only for memory protection purposes, or (as I think I remember) it helps with PAE or AWE or whatever address translation is called on x64 (if it exists at all)...


Sorry for not being clear, but I am very convinced I read it is strongly recommended to not turn it off, and here is my OS, working around 6 months without any problems. Any comments?


Output of bcdedit:

Windows Boot Manager


identifier {bootmgr}

device partition=C:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

resumeobject {ed361037-5239-11e1-b35a-8c185ebdf863}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader


identifier {current}

device partition=C:

path \Windows\system32\winload.exe

description Windows 7

locale en-US

inherit {bootloadersettings}

recoverysequence {ed361039-5239-11e1-b35a-8c185ebdf863}

recoveryenabled Yes

osdevice partition=C:

systemroot \Windows

resumeobject {ed361037-5239-11e1-b35a-8c185ebdf863}

nx AlwaysOff

sos Yes

useplatformclock Yes

How to remove advertisement from MSFN




  • Member
  • PipPip
  • 212 posts
  • Joined 17-August 12
  • OS:Windows 8 x64
  • Country: Country Flag

NX or DEP is from preventing the execution of malicious code that can seize the whole memory. It renders a part of the memory for data storage only and if a program tries to execute code in it it just crushes. The only problem that I am aware of is with programs that doesn't respect the DEP restrictions (usually old ones).

I always love Windows XP!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users