Windows 10: BSOD. Attempted execute of noexecute memory

Discus and support BSOD. Attempted execute of noexecute memory in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I built a desktop and it was BSODing non stop with the error message, "attempted execute of noexecute memory". I then stripped out the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by natbatter, Dec 19, 2015.

  1. natbatter Win User

    BSOD. Attempted execute of noexecute memory


    Hi,
    I built a desktop and it was BSODing non stop with the error message, "attempted execute of noexecute memory".

    I then stripped out the components till finally only these are in the system and re- installed windows.

    Asus Z170 Pro
    Core i5 6600k
    Gskill Ripjaws 16 GB, DDR4, 2400, CL15
    Samsung 850 evo.


    The memory earlier was Corsair and I swapped it for the GSkill kit, and while the BSODs have reduced, I still get them, with the same Message.

    I'm attaching the dump file.

    Help will be greatly appreciated,

    Thank you.

    :)
     
    natbatter, Dec 19, 2015
    #1
  2. Hollyecho Win User

    BSOD after starting to install AMD drivers to get win 10 to see my other 3 monitors

    That method ONLY works if windows will come up. Windows will NOT START.

    1. BSOD "ATTEMPTED EXECUTE OF NOEXECUTE MEMORY"

    2. It shuts down, then goes to:

    3. Prepairing automatic repair - THEN another BSOD

    "WDF_VIOLATION"

    4. It shuts down, then goes to:

    5. (it attempts restart-then goes to)

    6. BSOD "ATTEMPTED EXECUTE OF NOEXECUTE MEMORY"

    7. It shuts down, then goes to:

    8. Prepairing automatic repair - THEN another BSOD

    "WDF_VIOLATION"

    9. (it attempts restart-then goes to)

    10. BSOD "ATTEMPTED EXECUTE OF NOEXECUTE MEMORY"

    11. It shuts down, then goes to:

    12. Prepairing automatic repair - THEN another BSOD

    "WDF_VIOLATION"

    THIS IS A FOREVER LOOP. WINDOWS WILL NOT START - F8 or SHIFT F8 will not --- repeat WILL NOT start safe mode.

    Every solution you have given me so far NEEDS WINDOWS TO START! WINDOWS WILL NOT START.
     
    Hollyecho, Dec 19, 2015
    #2
  3. Attempted Execute of Noexecute Memory BSOD?

    Driver verified and Related to cmudaxp.sys Audio WDM Driver from C-Media Inc

    Completely remove the current driver (or software) and install the newest driver available. For instructions on how to do that Read all about updating drivers here Updating a driver.
     
    ZigZag3143 (MS -MVP), Dec 19, 2015
    #3
  4. axe0 New Member

    BSOD. Attempted execute of noexecute memory

    Hi natbatter,

    Have you tried some tests for the hardware?
     
  5. natbatter Win User
    I've replaced the RAM. Also ran prime 95. At the moment there's nothing else to test. All other components are removed temporarily.

    I'm of the impression that it's a bad BIOS or some motherboard driver is bad.

    Really do not think it's a bad CPU or SSD.

    If there is any specific test I should run, please let me know.

    Cheers.
     
    natbatter, Dec 20, 2015
    #5
  6. axe0 New Member
    It's a bit difficult, the usual cause for this error, 0xFC(ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY), is drivers.

    Please try running the IntelBurnTest: Download IntelBurnTest - MajorGeeks

    Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling system and other stuff you have for your system. The PSU, cooling system and other stuff aren't mentioned in the tool.How to fill in your system specs:

    BSOD. Attempted execute of noexecute memory [​IMG]


    BSOD. Attempted execute of noexecute memory [​IMG]
     
  7. natbatter Win User
    Thanks for the prompt follow up,

    I've updated the system specs as asked and included a snap of the IBT.

    Ran prime yesterday, Small FFTS and it was ok,

    Issues aren't indicating stability issues under load, rather just arbitrary crashes. Sometimes on start up, and some times out of no where.

    If i can get clued in to what the issue is, great. Otherwise I'm of a mind to change the motherboard.

    Like mentioned earlier, it's extremely stripped down as of now, so not many drivers to conflict.

    Cheers.
     
    natbatter, Dec 20, 2015
    #7
  8. natbatter Win User

    BSOD. Attempted execute of noexecute memory

    Issue solved.

    Was a bad CPU.

    Replaced it, and all's good.
     
    natbatter, Apr 5, 2018
    #8
Thema:

BSOD. Attempted execute of noexecute memory

Loading...
  1. BSOD. Attempted execute of noexecute memory - Similar Threads - BSOD Attempted execute

  2. BSOD Attempted execute of noexecute memory

    in Windows 10 Gaming
    BSOD Attempted execute of noexecute memory: So my windows 10 blue screened today could not find a mini dump sadly but i have "MEMORY.DMP" zipped and uploaded on mega here is the link:LinkThanks in advance....
  3. BSOD Attempted execute of noexecute memory

    in Windows 10 Software and Apps
    BSOD Attempted execute of noexecute memory: So my windows 10 blue screened today could not find a mini dump sadly but i have "MEMORY.DMP" zipped and uploaded on mega here is the link:LinkThanks in advance....
  4. BSOD Attempted execute of noexecute memory

    in Windows 10 BSOD Crashes and Debugging
    BSOD Attempted execute of noexecute memory: So my windows 10 blue screened today could not find a mini dump sadly but i have "MEMORY.DMP" zipped and uploaded on mega here is the link:LinkThanks in advance....
  5. Attempted Execute of noexecute memory

    in Windows 10 BSOD Crashes and Debugging
    Attempted Execute of noexecute memory: Hi, I'm having trouble booting up my PC, after 10-15 seconds when the desktop shows a blue screen error occurs saying "Attempted Execute of noexecute memory" and the problem was "imfilter failed". I tried updating my drivers that has yellow exclamation on them but they all...
  6. BSOD caused by ntoskrnl.exe, attempted execute of noexecute memory

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by ntoskrnl.exe, attempted execute of noexecute memory: CPU: i9 9900KF 5GHz GPU: RTX 3080 FE RAM: 32GB 3200MHz https://answers.microsoft.com/en-us/windows/forum/all/bsod-caused-by-ntoskrnlexe-attempted-execute-of/6d6454fd-52ab-44d6-b919-fbfd8ab1d3bd
  7. ATTEMPTED EXECUTE OF NOEXECUTE MEMORY

    in Windows 10 BSOD Crashes and Debugging
    ATTEMPTED EXECUTE OF NOEXECUTE MEMORY: I am stuck in a nefarious blue screen loop and i cant seem to get a straight answer. I performed a computer “refresh” (HP Pavilion 510-a010 running Windows 10 Home). Upon restarting I got the stop code: ATTEMPTED EXECUTE OF NOEXECUTE MEMORY. And it just continuously keeps...
  8. BSOD attempted execute of noexecute memory

    in Windows 10 BSOD Crashes and Debugging
    BSOD attempted execute of noexecute memory: So first off. I have had this error several times today. This all started after I installed a large recent update (the creators update) from windows. At first I thought it was a youtube issue as two of the crashes happened in the middle of youtube videos. But the videos were...
  9. My new PC frequently get BSOD : Attempted execute of noexecute memory

    in Windows 10 BSOD Crashes and Debugging
    My new PC frequently get BSOD : Attempted execute of noexecute memory: I have done everything i could, updated latest window 10 updates, updated bios and all drivers by Msi driver update manager (with drivers auto-detection features), running Memory diagnostic tools and IntelBurnTest ( all results shown normal). Other than this type of issue...
  10. Attempted execute of noexecute memory - after Dell BIOS update

    in Windows 10 BSOD Crashes and Debugging
    Attempted execute of noexecute memory - after Dell BIOS update: Using a Dell Laptop running Windows 10. Never had any BSOD before ever. A few hours ago I clicked on the Dell's automatic updater which was to update the Dell BIOS version. Everything installed fine and the Dell BIOS checker checked the updated Bios installation saying all...