Windows 10: attempted execute of no execute memory BSOD after waking from Suspend

Hello everyone.
I've installed Windows 10 in my computer yesterday just to find out that suspending is not working, as I wake my computer I receive this error on BSOD
attempted execute of no execute memory

Tried updating VGA/LAN/Motherboard drivers but the problem persists.

This behaviour happens when selecting "High Performance" power plan.
If I select balanced, the BSOD says "Bad Pool Header" and restarts anyway.

Here I attach the zip created with the collector tool.
I've tried to diagnose on my own but can't have kd, symbols and such working properly.
Hope you can help me, I want to thank you in advance.

:)

 

Attempted Execute of No-execute Memory BSOD error on Windows 10

Hello, and thank you for the reply.

For your question, I don't think I see any other error code beside the Attempted Execute of No-execute Memory one on my BSOD. Here is a picture taken directly from my monitor of the PC:



Now, there are times when my PC restarted, a Recovery menu shows up:


The thing is, I'm unfamiliar with the Recovery tools. Are there any I should try out?

I tried your suggestion, burning out a disc of the Windows 10 ISO (on my other laptop) downloaded from the Microsoft website, but in the article you attached, the person have access to the desktop, in this case I'm stuck with a BSOD. Also, trying to load
the disc when the PC is booting up doesn't seems to help either...

Thank you again for the help, and please let me know of any ways I can do to solve/diagnose this problem.

(Also, will installing Windows 10 from my disc in Safe Mode works?)

 

Attempted Execute of No-execute Memory BSOD error on Windows 10

I am having a similar problem. During the upgrade to Windows 10 on a Pentium G620 64-bit processor, at "SECOND_BOOT", I get the "attempt to execute noexecute memory" with error code 0XC1900101-0X40017. The upgrade process then reverts back to my old Windows
7 (SP1) system. I was doing the install from the downloaded media from the Microsoft Media Creation tool on a USB stick.

Other than changing the CPU & motherboard to a Core-I3 (or better) system, is there any way past this problem?

It seems strange that MS would make it impossible to run their new flagship OS on hardware that is only 5 years old and still quite serviceable. I KNOW the risks of old hardware, but a $500 upgrade (new CPU + motherboard + clean install of Windows) is pretty
sad. A clean install is required because of the difference in motherboards. So all my apps have to be re-installed too.

 

Please update your keyboard drivers
Driver Reference Table - CORK40.sys

Please update your bluetooth drivers
Driver Reference Table - btfilter.sys






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

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.How to fill in your system specs:

 

Keyboard driver is the latest available on website, and the bluetooth manufacturer doesn't provide a driver anymore.
Windows installed automatically the current driver

Running. No problems so far

Done


Couldn't the problem be diagnosed by the provided dumps?
I've seen other diagnoses and using kd.exe usually people here and in eightforums seems to find a solution.

 

What did you see in those diagnoses?

 

They usually diagnose the stack and detect the root of the problem.
I'm no expert, but reading those post seems to make sense the things they find on the diagnose files.
For example, http://www.eightforums.com/bsod-cras...tml#post496654

 

Write access results in fault.

Running driver verifier should tell more:[/quote]
It looks a lot like each other if you ask me and the suggestion is the same, driver verifier.
Code: ******************************************************************************** * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: ffffd00000000007, Virtual address for the attempted execute. Arg2: 80000000001a8963, PTE contents. Arg3: ffffd000210ba4c0, (reserved) Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0xFC PROCESS_NAME: System CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre TRAP_FRAME: ffffd000210ba4c0 -- (.trap 0xffffd000210ba4c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffd00000000007 rbx=0000000000000000 rcx=000000000000cff0 rdx=ffffe001ad42b001 rsi=0000000000000000 rdi=0000000000000000 rip=ffffd00000000007 rsp=ffffd000210ba658 rbp=ffffe001b08b92fe r8=ffffe001ad42b010 r9=00000000000007ff r10=ffffd0019b880c40 r11=ffffd000210ba650 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc ffffd000`00000007 ff ??? Resetting default scope LOCK_ADDRESS: fffff803e6f883e0 -- (!locks fffff803e6f883e0) Resource @ nt!PiEngineLock (0xfffff803e6f883e0) Exclusively owned Contention Count = 20 Threads: ffffe001aead8040-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0xfffff803e6f883e0 Thread Count : 1 Thread address: 0xffffe001aead8040 Thread wait : 0x2e1d LAST_CONTROL_TRANSFER: from fffff803e6e1ca0e to fffff803e6dd3760 STACK_TEXT: ffffd000`210ba218 fffff803`e6e1ca0e : 00000000`000000fc ffffd000`00000007 80000000`001a8963 ffffd000`210ba4c0 : nt!KeBugCheckEx ffffd000`210ba220 fffff803`e6cc8e09 : 00000000`00000000 ffffd000`210ba448 ffffe001`b0971800 fffff803`e6c21f25 : nt! ?? ::FNODOBFM::`string'+0x3a90e ffffd000`210ba260 fffff803`e6cca17c : 00000000`00000011 ffffe001`b08b91b0 ffffd000`210ba4c0 ffffe001`b0971a40 : nt!MiSystemFault+0x7e9 ffffd000`210ba350 fffff803`e6ddc9bc : ffffe001`ab68a300 ffffe001`ae22d290 00000000`00000000 ffffd000`210ba569 : nt!MmAccessFault+0x62c ffffd000`210ba4c0 ffffd000`00000007 : fffff800`fae09fb2 ffffe001`b08b91b0 ffffc001`7907c8fd 00000000`00000000 : nt!KiPageFault+0x13c ffffd000`210ba658 fffff800`fae09fb2 : ffffe001`b08b91b0 ffffc001`7907c8fd 00000000`00000000 ffffc001`7907c8fd : 0xffffd000`00000007 ffffd000`210ba660 fffff800`fae081ff : ffffe001`b08b91b0 ffffe001`ab68a310 ffffe001`b08b91b0 ffffe001`ad480060 : PCIIDEX!ControllerStartDevice+0x1ea ffffd000`210ba6d0 fffff803`e7044a7d : ffffe001`ad403b80 ffffd000`210ba7f0 ffffe001`b08b9060 00000000`00000000 : PCIIDEX!GenPnpFdoStartDevice+0x6f ffffd000`210ba710 fffff803`e6c94e14 : ffffe001`ad480060 00000000`00000000 ffffe001`ab68a310 00000000`00000000 : nt!PnpAsynchronousCall+0xe5 ffffd000`210ba750 fffff803`e6d85294 : 00000000`00000000 ffffe001`ad480060 fffff803`e6c94970 fffff803`e6c94970 : nt!PnpSendIrp+0x54 ffffd000`210ba7c0 fffff803`e7174c73 : ffffe001`ae511d30 ffffe001`ab68a310 00000000`00000000 00000000`00000000 : nt!PnpStartDevice+0x88 ffffd000`210ba850 fffff803`e7174b5f : ffffe001`ae511d30 ffffd000`210baa20 00000000`00000000 ffffe001`ae511d30 : nt!PnpStartDeviceNode+0xdb ffffd000`210ba8e0 fffff803`e7159927 : ffffe001`ae511d30 00000000`00000001 00000000`00000001 ffffe001`ab53dd30 : nt!PipProcessStartPhase1+0x53 ffffd000`210ba920 fffff803`e712cc95 : ffffe001`ae59e010 ffffe001`aef64b30 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x40b ffffd000`210baba0 fffff803`e6d78eb2 : 00000001`00000003 00000000`00000000 00000000`00000000 ffffe001`32706e50 : nt!PiProcessReenumeration+0xa1 ffffd000`210babf0 fffff803`e6cfbb79 : ffffe001`aead8040 fffff803`e6f86e80 fffff803`e7024340 fffff803`e7024340 : nt!PnpDeviceActionWorker+0x166 ffffd000`210bacc0 fffff803`e6c9a125 : 00000004`ad1b3ffe 00000000`00000080 ffffe001`ab41b700 ffffe001`aead8040 : nt!ExpWorkerThread+0xe9 ffffd000`210bad50 fffff803`e6dd8906 : ffffd001`a0400180 ffffe001`aead8040 fffff803`e6c9a0e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`210bada0 00000000`00000000 : ffffd000`210bb000 ffffd000`210b5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: PCIIDEX!ControllerStartDevice+1ea fffff800`fae09fb2 85ff test edi,edi SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: PCIIDEX!ControllerStartDevice+1ea FOLLOWUP_NAME: MachineOwner MODULE_NAME: PCIIDEX IMAGE_NAME: PCIIDEX.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 5632d167 IMAGE_VERSION: 10.0.10586.0 BUCKET_ID_FUNC_OFFSET: 1ea FAILURE_BUCKET_ID: 0xFC_PCIIDEX!ControllerStartDevice BUCKET_ID: 0xFC_PCIIDEX!ControllerStartDevice ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xfc_pciidex!controllerstartdevice FAILURE_ID_HASH: {18624ccb-5ca4-6ecb-90a2-dc57d16efca7} Followup: MachineOwner --------- GetPointerFromAddress: unable to read from fffff803e7010200 THREAD ffffe001aead8040 Cid 0004.0efc Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 3 Not impersonating GetUlongFromAddress: unable to read from fffff803e6f5fef8 Owning Process ffffe001ab41b700 Image: System Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 11805 Context Switch Count 3687 IdealProcessor: 2 NoStackSwap ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address nt!ExpWorkerThread (0xfffff803e6cfba90) Stack Init ffffd000210badd0 Current ffffd000210ba070 Base ffffd000210bb000 Limit ffffd000210b5000 Call 0 Priority 12 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site ffffd000`210ba218 fffff803`e6e1ca0e : 00000000`000000fc ffffd000`00000007 80000000`001a8963 ffffd000`210ba4c0 : nt!KeBugCheckEx ffffd000`210ba220 fffff803`e6cc8e09 : 00000000`00000000 ffffd000`210ba448 ffffe001`b0971800 fffff803`e6c21f25 : nt! ?? ::FNODOBFM::`string'+0x3a90e ffffd000`210ba260 fffff803`e6cca17c : 00000000`00000011 ffffe001`b08b91b0 ffffd000`210ba4c0 ffffe001`b0971a40 : nt!MiSystemFault+0x7e9 ffffd000`210ba350 fffff803`e6ddc9bc : ffffe001`ab68a300 ffffe001`ae22d290 00000000`00000000 ffffd000`210ba569 : nt!MmAccessFault+0x62c ffffd000`210ba4c0 ffffd000`00000007 : fffff800`fae09fb2 ffffe001`b08b91b0 ffffc001`7907c8fd 00000000`00000000 : nt!KiPageFault+0x13c (TrapFrame @ ffffd000`210ba4c0) ffffd000`210ba658 fffff800`fae09fb2 : ffffe001`b08b91b0 ffffc001`7907c8fd 00000000`00000000 ffffc001`7907c8fd : 0xffffd000`00000007 ffffd000`210ba660 fffff800`fae081ff : ffffe001`b08b91b0 ffffe001`ab68a310 ffffe001`b08b91b0 ffffe001`ad480060 : PCIIDEX!ControllerStartDevice+0x1ea ffffd000`210ba6d0 fffff803`e7044a7d : ffffe001`ad403b80 ffffd000`210ba7f0 ffffe001`b08b9060 00000000`00000000 : PCIIDEX!GenPnpFdoStartDevice+0x6f ffffd000`210ba710 fffff803`e6c94e14 : ffffe001`ad480060 00000000`00000000 ffffe001`ab68a310 00000000`00000000 : nt!PnpAsynchronousCall+0xe5 ffffd000`210ba750 fffff803`e6d85294 : 00000000`00000000 ffffe001`ad480060 fffff803`e6c94970 fffff803`e6c94970 : nt!PnpSendIrp+0x54 ffffd000`210ba7c0 fffff803`e7174c73 : ffffe001`ae511d30 ffffe001`ab68a310 00000000`00000000 00000000`00000000 : nt!PnpStartDevice+0x88 ffffd000`210ba850 fffff803`e7174b5f : ffffe001`ae511d30 ffffd000`210baa20 00000000`00000000 ffffe001`ae511d30 : nt!PnpStartDeviceNode+0xdb ffffd000`210ba8e0 fffff803`e7159927 : ffffe001`ae511d30 00000000`00000001 00000000`00000001 ffffe001`ab53dd30 : nt!PipProcessStartPhase1+0x53 ffffd000`210ba920 fffff803`e712cc95 : ffffe001`ae59e010 ffffe001`aef64b30 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x40b ffffd000`210baba0 fffff803`e6d78eb2 : 00000001`00000003 00000000`00000000 00000000`00000000 ffffe001`32706e50 : nt!PiProcessReenumeration+0xa1 ffffd000`210babf0 fffff803`e6cfbb79 : ffffe001`aead8040 fffff803`e6f86e80 fffff803`e7024340 fffff803`e7024340 : nt!PnpDeviceActionWorker+0x166 ffffd000`210bacc0 fffff803`e6c9a125 : 00000004`ad1b3ffe 00000000`00000080 ffffe001`ab41b700 ffffe001`aead8040 : nt!ExpWorkerThread+0xe9 ffffd000`210bad50 fffff803`e6dd8906 : ffffd001`a0400180 ffffe001`aead8040 fffff803`e6c9a0e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`210bada0 00000000`00000000 : ffffd000`210bb000 ffffd000`210b5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 Machine ID Information [From Smbios 2.4, DMIVersion 0, Size=1197] BiosVendor = Award Software International, Inc. BiosVersion = F11 BiosReleaseDate = 08/10/2010 SystemManufacturer = Gigabyte Technology Co., Ltd. SystemProductName = P55A-UD3 SystemFamily = SystemVersion = SystemSKU = BaseBoardManufacturer = Gigabyte Technology Co., Ltd. BaseBoardProduct = P55A-UD3 BaseBoardVersion = x.x CPUID: "Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz" MaxSpeed: 2670 CurrentSpeed: 2532 Bugcheck code 000000FC Arguments ffffd000`00000007 80000000`001a8963 ffffd000`210ba4c0 00000000`00000002 Debug session time: Sat Dec 26 11:17:37.755 2015 (UTC + 1:00) System Uptime: 0 days 0:03:04.468 3: kd> .trap 0xffffd000210ba4c0 NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffd00000000007 rbx=0000000000000000 rcx=000000000000cff0 rdx=ffffe001ad42b001 rsi=0000000000000000 rdi=0000000000000000 rip=ffffd00000000007 rsp=ffffd000210ba658 rbp=ffffe001b08b92fe r8=ffffe001ad42b010 r9=00000000000007ff r10=ffffd0019b880c40 r11=ffffd000210ba650 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc ffffd000`00000007 ff ??? 3: kd> !pte 80000000001a8963 VA 80000000001a8963 PXE at FFFFF6FB7DBED000 PPE at FFFFF6FB7DA00000 PDE at FFFFF6FB40000000 PTE at FFFFF68000000D40 contains 01200002150E8867 contains 0000000000000000 pfn 2150e8 ---DA--UWEV not valid WARNING: noncanonical VA, accesses will fault ![/quote]

 

They usually diagnose the stack and detect the root of the problem.
I'm no expert, but reading those post seems to make sense the things they find on the diagnose files.
For example, http://www.eightforums.com/bsod-cras...tml#post496654

Thank you mate.
I've driver verifier running but no problem at the moment.
I'll let you know.
Thank you very much.

 

Should I sleep and wake with driver verifier running in order to cause the BSOD or should I wait until driver verifier "breaks" something?

 

I'm not sure if that could work, but you could give it a try as long as the system doesn't turn off completely *Smile

 

I've forced sleep and then the BSOD occurred again.
What should I do now?
Do you want to see MEMORY.DMP?

 

Just run the dm log collector again and upload a new zip *Smile
A memory.dmp isn't useful to me, because I can't get more from it. I'm no expert but a starter with this *Smile

 

I've detected a problem with PCIIDEX.SYS

 

Here it goes the new dump