Windows 8 and 8.1 Forums


BSOD "attempted execute of no execute memory" while idle

  1. #1


    Posts : 5
    Windows 8.1

    BSOD "attempted execute of no execute memory" while idle


    Hello and nice to meet you all!
    I found this place from searching how to solve the problem I'm experiencing and it seems to be the best bet right now.

    Problem Condition:
    I am having BSOD "Attempted execute of no execute memory" whenever I leave my computer idle for 5-10 minutes for about 2 weeks now. At 100% of its data collecting, it never restarts, and I always need to manually shut it down and re-open.
    Additional information:
    I have this laptop for about 6 months now, and this problem occurred recently, so its hard to believe that it would be a hardware problem. I tried doing a system restore to the period before this problem occurred but it does not seem to help. At the end of each system restore, it informed me that some files could not be reverted because it was protected.

    I have attached my DM log here, and if you need more information, I will be happy to cooperate.
    Thank you for your time and effort!

      My System SpecsSystem Spec

  2. #2


    Posts : 5
    Windows 8.1


    I understand that there are not many analyzers. but hope that you'll get to me soon. I'll be checking this post daily for any updates from the team.
      My System SpecsSystem Spec

  3. #3


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi zero34 & welcome to the forums ^_^,

    I am really sorry for this much delay in the response . There are not many analysts. Would you still like me to analyse the dump files? If yes, then kindly reply to this thread and I would be notified via email. I will try my best to reply within 48 hours

    I really appreciate your faith in us. Don't worry we will resolve your problem very soon


    -Pranav
      My System SpecsSystem Spec

  4. #4


    Posts : 5
    Windows 8.1


    yes, please analyze my dump files. fyi, I ran the memory diagnostic tool and have found no problems.
      My System SpecsSystem Spec

  5. #5


    Posts : 1
    Windows 8.1

    Same issue here.


    Quote Originally Posted by zero34 View Post
    Hello and nice to meet you all!
    I found this place from searching how to solve the problem I'm experiencing and it seems to be the best bet right now.

    Problem Condition:
    I am having BSOD "Attempted execute of no execute memory" whenever I leave my computer idle for 5-10 minutes for about 2 weeks now. At 100% of its data collecting, it never restarts, and I always need to manually shut it down and re-open.
    Additional information:
    I have this laptop for about 6 months now, and this problem occurred recently, so its hard to believe that it would be a hardware problem. I tried doing a system restore to the period before this problem occurred but it does not seem to help. At the end of each system restore, it informed me that some files could not be reverted because it was protected.

    I have attached my DM log here, and if you need more information, I will be happy to cooperate.
    Thank you for your time and effort!
    Hello,
    I am having the EXACT same issues as you described. Get the BSOD/non_execute crash only when machine is idle for a few mins. Will be watching this thread with interest!
      My System SpecsSystem Spec

  6. #6


    Posts : 356
    Windows 8.1 Enterprise


    Hi,
    I've marked Device/Vendor numbers with red to help identify device.
    2 out of many dumps are refered to this device.

    Dump 1:

    Code:
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0002e9e5060, Physical Device Object of the stack
    Arg3: ffffd00054b31960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0002e9d9b40, The blocked IRP
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    
    IMAGE_NAME:  pci.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53d0f1d4
    
    
    MODULE_NAME: pci
    
    
    FAULTING_MODULE: fffff800e709c000 pci
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x9F
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    DPC_STACK_BASE:  FFFFD00054B38FB0
    
    
    STACK_TEXT:  
    ffffd000`54b31928 fffff800`04082e3e : 00000000`0000009f 00000000`00000003 ffffe000`2e9e5060 ffffd000`54b31960 : nt!KeBugCheckEx
    ffffd000`54b31930 fffff800`04082d5e : ffffe000`2e9d99f8 ffffd000`54b31ae0 ffffe000`32f989f0 fffff800`03f2d515 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd000`54b31990 fffff800`03f2e428 : 00000000`00000000 ffffd000`54b31ae0 00000000`00000001 ffffd000`54b07180 : nt!PopIrpWatchdog+0x32
    ffffd000`54b319e0 fffff800`03fce4ea : ffffd000`54b07180 ffffd000`54b07180 ffffd000`54b133c0 ffffe000`334b8640 : nt!KiRetireDpcList+0x4f8
    ffffd000`54b31c60 00000000`00000000 : ffffd000`54b32000 ffffd000`54b2c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    IMAGE_VERSION:  6.3.9600.17238
    
    
    FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
    
    
    BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_acpi_image_pci.sys
    
    
    FAILURE_ID_HASH:  {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}
    
    
    Followup: MachineOwner
    ---------

    Device info:

    Code:
    6: kd> !devobj ffffe0002e9e5060
    Device object (ffffe0002e9e5060) is for:
     Cannot read info offset from nt!ObpInfoMaskToOffset
     \Driver\pci DriverObject ffffe0002e9ec8a0
    Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
    DevExt ffffe0002e9e51b0 DevObjExt ffffe0002e9e5778 DevNode ffffe0002e9d1010 
    ExtensionFlags (0000000000)  
    Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
    AttachedDevice (Upper) ffffe0002e9d3040 \Driver\ACPI
    Device queue is not busy.
    
    
    6: kd> !devnode ffffe0002e9d1010
    DevNode 0xffffe0002e9d1010 for PDO 0xffffe0002e9e5060
      Parent 0xffffe0002cc6bd30   Sibling 0xffffe0002e9d1d30   Child 0xffffe0002e9d82d0   
      InterfaceType 0x5  Bus Number 0x1
      InstancePath is "PCI\VEN_8086&DEV_0C01&SUBSYS_157D1043&REV_06\3&11583659&1&08"
      ServiceName is "pci"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[18] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[17] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[16] = DeviceNodeStarted (0x308)
      StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[13] = DeviceNodeStarted (0x308)
      StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[10] = DeviceNodeStarted (0x308)
      StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[07] = DeviceNodeStarted (0x308)
      StateHistory[06] = DeviceNodeStartPostWork (0x307)
      StateHistory[05] = DeviceNodeStartCompletion (0x306)
      StateHistory[04] = DeviceNodeStartPending (0x305)
      StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
      StateHistory[02] = DeviceNodeDriversAdded (0x303)
      StateHistory[01] = DeviceNodeInitialized (0x302)
      StateHistory[00] = DeviceNodeUninitialized (0x301)
      StateHistory[19] = Unknown State (0x0)
      Flags (0x6c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED, 
                          DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED, 
                          DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS, 
                          DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
      CapabilityFlags (0x00002002)  DeviceD2, WakeFromD3


    Dump 2: (Same device as above )

    Code:
    6: kd> !analyze -v*******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0002e9e5060, Physical Device Object of the stack
    Arg3: ffffd00054b31960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe0002e9d9b40, The blocked IRP
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    
    IMAGE_NAME:  pci.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53d0f1d4
    
    
    MODULE_NAME: pci
    
    
    FAULTING_MODULE: fffff800e709c000 pci
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x9F
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  2
    
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    DPC_STACK_BASE:  FFFFD00054B38FB0
    
    
    STACK_TEXT:  
    ffffd000`54b31928 fffff800`04082e3e : 00000000`0000009f 00000000`00000003 ffffe000`2e9e5060 ffffd000`54b31960 : nt!KeBugCheckEx
    ffffd000`54b31930 fffff800`04082d5e : ffffe000`2e9d99f8 ffffd000`54b31ae0 ffffe000`32f989f0 fffff800`03f2d515 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd000`54b31990 fffff800`03f2e428 : 00000000`00000000 ffffd000`54b31ae0 00000000`00000001 ffffd000`54b07180 : nt!PopIrpWatchdog+0x32
    ffffd000`54b319e0 fffff800`03fce4ea : ffffd000`54b07180 ffffd000`54b07180 ffffd000`54b133c0 ffffe000`334b8640 : nt!KiRetireDpcList+0x4f8
    ffffd000`54b31c60 00000000`00000000 : ffffd000`54b32000 ffffd000`54b2c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    IMAGE_VERSION:  6.3.9600.17238
    
    
    FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
    
    
    BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x9f_3_acpi_image_pci.sys
    
    
    FAILURE_ID_HASH:  {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}
    
    
    Followup: MachineOwner
    ---------

    Code:
    6: kd> lmvm pci
    start             end                 module name
    fffff800`e709c000 fffff800`e70e4000   pci        (pdb symbols)          d:\symbols\pci.pdb\8AB2DB46BB1C48778F5A8E000B9ABA642\pci.pdb
        Loaded symbol image file: pci.sys
        Mapped memory image file: d:\symbols\pci.sys\53D0F1D448000\pci.sys
        Image path: \SystemRoot\System32\drivers\pci.sys
        Image name: pci.sys
        Timestamp:        Thu Jul 24 13:45:24 2014 (53D0F1D4)
        CheckSum:         000516FC
        ImageSize:        00048000
        File version:     6.3.9600.17238
        Product version:  6.3.9600.17238
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        2.0 Dll
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     pci.sys
        OriginalFilename: pci.sys
        ProductVersion:   6.3.9600.17238
        FileVersion:      6.3.9600.17238 (winblue_gdr.140723-2018)
        FileDescription:  NT Plug and Play PCI Enumerator
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    
    
    
    6: kd> !devobj ffffe0002e9e5060
    Device object (ffffe0002e9e5060) is for:
     Cannot read info offset from nt!ObpInfoMaskToOffset
     \Driver\pci DriverObject ffffe0002e9ec8a0
    Current Irp 00000000 RefCount 0 Type 00000022 Flags 00001040
    DevExt ffffe0002e9e51b0 DevObjExt ffffe0002e9e5778 DevNode ffffe0002e9d1010 
    ExtensionFlags (0000000000)  
    Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
    AttachedDevice (Upper) ffffe0002e9d3040 \Driver\ACPI
    Device queue is not busy.
    
    
    6: kd> !devnode ffffe0002e9d1010
    DevNode 0xffffe0002e9d1010 for PDO 0xffffe0002e9e5060
      Parent 0xffffe0002cc6bd30   Sibling 0xffffe0002e9d1d30   Child 0xffffe0002e9d82d0   
      InterfaceType 0x5  Bus Number 0x1
      InstancePath is "PCI\VEN_8086&DEV_0C01&SUBSYS_157D1043&REV_06\3&11583659&1&08"
      ServiceName is "pci"
      State = DeviceNodeStarted (0x308)
      Previous State = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[18] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[17] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[16] = DeviceNodeStarted (0x308)
      StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[13] = DeviceNodeStarted (0x308)
      StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[10] = DeviceNodeStarted (0x308)
      StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
      StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
      StateHistory[07] = DeviceNodeStarted (0x308)
      StateHistory[06] = DeviceNodeStartPostWork (0x307)
      StateHistory[05] = DeviceNodeStartCompletion (0x306)
      StateHistory[04] = DeviceNodeStartPending (0x305)
      StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
      StateHistory[02] = DeviceNodeDriversAdded (0x303)
      StateHistory[01] = DeviceNodeInitialized (0x302)
      StateHistory[00] = DeviceNodeUninitialized (0x301)
      StateHistory[19] = Unknown State (0x0)
      Flags (0x6c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED, 
                          DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED, 
                          DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS, 
                          DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
      CapabilityFlags (0x00002002)  DeviceD2, WakeFromD3

    Almost all other dumps look like this one:

    Code:
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: ffffe00186bfc860, Virtual address for the attempted execute.
    Arg2: 80000000469bc963, PTE contents.
    Arg3: ffffd000cc56ae70, (reserved)
    Arg4: 0000000000000000, (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.17298 (debuggers(dbg).141024-1500) amd64fre
    
    
    TRAP_FRAME:  ffffd000cc56ae70 -- (.trap 0xffffd000cc56ae70)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000001ab000
    rdx=ffffd000cb707180 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffe00186bfc860 rsp=ffffd000cc56b000 rbp=ffffd000cf0248c9
     r8=0000000000000006  r9=7fffe001d1bf7050 r10=ffffe001d1bf7050
    r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl zr na pe nc
    ffffe001`86bfc860 0100            add     dword ptr [rax],eax ds:00000000`00000000=????????
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff803757bc5fa to fffff8037575e9a0
    
    
    STACK_TEXT:  
    ffffd000`cc56ac28 fffff803`757bc5fa : 00000000`000000fc ffffe001`86bfc860 80000000`469bc963 ffffd000`cc56ae70 : nt!KeBugCheckEx
    ffffd000`cc56ac30 fffff803`7580d50a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d74a
    ffffd000`cc56ac70 fffff803`7578944d : ffffe001`895a6080 ffffd000`cc56ad00 ffffe001`81c68900 00000000`00000000 : nt!MiRaisedIrqlFault+0x152
    ffffd000`cc56acb0 fffff803`75768c2f : 00000000`00000008 ffffe001`895a6080 00000000`80000300 fffff800`acb20000 : nt! ?? ::FNODOBFM::`string'+0x1a59d
    ffffd000`cc56ae70 ffffe001`86bfc860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
    ffffd000`cc56b000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe001`86bfc860
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4d74a
    fffff803`757bc5fa cc              int     3
    
    
    SYMBOL_STACK_INDEX:  1
    
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4d74a
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nt
    
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  54c832b2
    
    
    IMAGE_VERSION:  6.3.9600.17668
    
    
    BUCKET_ID_FUNC_OFFSET:  4d74a
    
    
    FAILURE_BUCKET_ID:  0xFC_nt!_??_::FNODOBFM::_string_
    
    
    BUCKET_ID:  0xFC_nt!_??_::FNODOBFM::_string_
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0xfc_nt!_??_::fnodobfm::_string_
    
    
    FAILURE_ID_HASH:  {a715e467-86e4-97ce-e0a9-37223e080980}
    
    
    Followup: MachineOwner
    ---------
    
    
    6: kd> .trap 0xffffd000cc56ae70
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000001ab000
    rdx=ffffd000cb707180 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffe00186bfc860 rsp=ffffd000cc56b000 rbp=ffffd000cf0248c9
     r8=0000000000000006  r9=7fffe001d1bf7050 r10=ffffe001d1bf7050
    r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl zr na pe nc
    ffffe001`86bfc860 0100            add     dword ptr [rax],eax ds:00000000`00000000=????????
    
    
    
    6: kd> !pte 80000000469bc963
                                               VA 80000000469bc963
    PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00008    PDE at FFFFF6FB400011A0    PTE at FFFFF68000234DE0
    contains 020000000482E867  contains 0210000065EAF867  contains 0000000000000000
    GetUlongFromAddress: unable to read from fffff80375971104
    pfn 482e      ---DA--UWEV  pfn 65eaf     ---DA--UWEV  not valid
    
    
    WARNING: noncanonical VA, accesses will fault !
    Write access results in fault.

    Running driver verifier should tell more:
    Where can I download Driver Verifier?

    Hopefully first 2 dumps have contributed and are telling that device vendor is Intel.
    Manufactures website does have an update for Intel devices of your laptop so first step should be to install these drivers:




    If you still encounter same problems after updating attach new dumps here.
    Additional information that could help is to run following in an elevated command prompt:


    c:
    cd \
    powercfg /energy


    And then attach HTML file found in C drive here.
    Last edited by Addictive Gamer; 03 May 2015 at 22:43.
      My System SpecsSystem Spec

  7. #7


    Posts : 5
    Windows 8.1


    Thanks alot!
    I will try your advice and inform my results maybe after a week if nothing goes wrong.

    I have tried the powercfg and here are the results.
    Attachment 61152
    I could not attach it as an HTML, since it informed me that the file was invalid, so I changed the extension to .doc. You can change it to html later I hope.
    There were several errors and warnings, but at the end, it states that there were no problems. I wasn't sure if I would need to change something here.

    As for the intel updates, I don't see any drivers that are out of date right now so will have to leave it as is. Currently I am running the Driver Verifier for all the intel drivers in my laptop.
    Last edited by zero34; 03 May 2015 at 12:30.
      My System SpecsSystem Spec

  8. #8


    Posts : 5
    Windows 8.1


    Well, after 2 weeks without this problem, I'll mark this post as solved for now.

    So what I had done just right after my last post was to update all the optional updates from my windows update.
    After then, the problem did reoccurred, but it was able to restart after collecting its info. Then, it became less frequent until it disappeared. It all happened during the first 2-3 days after I did the update.

    I guess the optional updates somehow aided windows to solve the problem and it hasn't appeared for almost 2 weeks, I'll mark this post as solved since it is somewhat related to updating the drivers to the latest versions.

    Hope this helps anyone who has a similar problem, and thanks to the members for the analysis.
      My System SpecsSystem Spec

  9. #9


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Zero34 ^_^,


    Thanks a lot for posting back what worked for you. Sorry for the delayed response
    Optional Updates solve a lot of problems. Whenever I update my Windows, I make sure to install all of the Optional Updates since they contain updates specific to the laptop components which improve their compatibility.

    Let me know in case of any further problems ^_^


    -Pranav
      My System SpecsSystem Spec

BSOD "attempted execute of no execute memory" while idle
Related Threads
I've been having this problem for a week now, i tried running memtest86 to diagnose Ram but the display does not show the test once it starts it show half the stats, the other half is hidden in mi right side screen. Only once it showed correctly and determined Errors with Tests 13 - hammering with...
It started to occur randomly, I didn't install any new software or hardware.
Hello! Another BSOD victim here. I get a "attempted execute of no execute memory" BSOD whenever I leave the computer for a few minutes and it's idle. I have looked through various "this will fix it"-threads but I haven't been successful I'm afraid. Have attached the DM log as asked. Please...
Hi eighforum, I have trouble with my laptop, This is a win 8 fresh installation(PS. I test with win 7 fresh installation, and the issue es the same) The laptop crash with bluescreen or face screen. I'd appreciate if you could look through my minidump and see if anything can be gleamed. ...
attempted execute of noexecute memory in BSOD Crashes and Debugging
So I deleted some folders in %appdata% and my computer desktop started to go black wherever I clicked. I went to reinstall windows and it wouldn't let me. So I tried re-installing windows using the recovery disk they gave me. About halfway through the process I get this error message. ATTEMPTED...
Attempted execute of no execute memory in BSOD Crashes and Debugging
Hello eightforums, I have another recurring issue, this is a fresh install of windows and I am not sure what the problem could be besides hardware. I'd appreciate if you could look through my minidump and see if anything can be gleamed.
Hey all Tearing my hair out with my 32bit W7 to W8 pro upgrade here.. :(. Setup gets to 24% and then bombs out with "Windows 8 installation has failed". The logs say.. 2012-10-27 21:01:41, Error Error while getting snapshot properties of fixed drive 2: 0x80042308...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook