none
Windows 8 attempted execute of no execute memory

    Question

  • Hey guys!

    I´m having some problems with blue screen and i hope you could help me?

    The last weeks i have got a couple of diffrent bluescreens but the one i got the most times is: Windows 8 attempted execute of no execute memory, and i get it when im playing games or when im trying to install diffrent thing or reapir games like LOL!

    Hopefully u guys can help me!

    Thanks!

    Thursday, May 23, 2013 8:45 PM

Answers

  • Test your i5-3570K CPU with Prime95, because you also got a fatal hardware error:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800d6d9028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  TiWorker.exe
    
    CURRENT_IRQL:  f
    
    
    ===============================================================================
    Common Platform Error Record @ fffffa800d6d9028
    -------------------------------------------------------------------------------
    Record Id     : 01ce5415cf2b4067
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 5/23/2013 10:22:18 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d90a8
    Section       @ fffffa800d6d9180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d90f0
    Section       @ fffffa800d6d9240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : a9 06 03 00 00 08 10 00 - bf e3 9a 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa800d6d9240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d9138
    Section       @ fffffa800d6d92c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal timer (Proc 0 Bank 3)
    

    Also update the BIOS/UEFI from BIOS 1708 to BIOS 1908


    "A programmer is just a tool which converts caffeine into code"

    Friday, May 24, 2013 8:18 PM
  •  recommend me to send in the computer to the store where i bought my computer parts frome and see if they can fix the problem?
    I think this is the best. Backup all your personal data before bringing the PC to the store.

    "A programmer is just a tool which converts caffeine into code"

    Saturday, May 25, 2013 7:10 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm


    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive

    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Wanikiya & Dyami--Team Zigzag

    Thursday, May 23, 2013 8:49 PM
    Moderator
  • https://skydrive.live.com/redir?resid=632DDEB2D09B15C3!107&authkey=!ANidA-_jhTt7F-E

    Hey, and thank you for the reply!

    I dont know if did this right, but here you have the link.

    Friday, May 24, 2013 1:05 PM
  • Filipp123

    There are quite a few different appearent causes.  Before we can narrow them down you need to do a few things.

    1-Remove Symantec and use the built in Defender.

    Symantec  is a frequent cause of BSOD's.  

    I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

    2-Update the following drivers

     

    CorsairLINK_HardwareMonitor.sys    7/26/2008       
    AsUpIO.sys    8/2/2010 10:47:59 PM                        
    ICCWDT.sys    8/18/2010 4:27:45 AM                      
    e1i63x64.sys    2/29/2012 11:25:14 PM                             

    How To Find Drivers:


    Search
     Google for the name of the driver
    Compare the Google results with what's installed on your system to figure out which device/program it belongs to
    Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

    The most common drivers are listed on these pages: 
    http://www.carrona.org/dvrref.php
    http://sysnative.com/drivers/

    Driver manufacturer links are on this page: http://www.carrona.org

    If you continue to crash upload the new DMP files.


    Wanikiya & Dyami--Team Zigzag


    Friday, May 24, 2013 3:37 PM
    Moderator
  • Hey and thanks again!

    I have one more question, do you think it will work if i restore the pc to factory settings? or will the problem come back? Becuas i cant find any uptades for the driver i needed to uptade!

    Friday, May 24, 2013 6:15 PM
  • Filipp

    You can reset to factory but if you plan on re-installing the things you have now it is a waste of time for it will have the same problems as it has now.  Better idea is to fix it.(especially when you reset to factory you lose any application that you installed after and you may lose your data.)

    Be sure to backup before you do.


    Wanikiya & Dyami--Team Zigzag

    Friday, May 24, 2013 6:27 PM
    Moderator
  • Test your i5-3570K CPU with Prime95, because you also got a fatal hardware error:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800d6d9028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  TiWorker.exe
    
    CURRENT_IRQL:  f
    
    
    ===============================================================================
    Common Platform Error Record @ fffffa800d6d9028
    -------------------------------------------------------------------------------
    Record Id     : 01ce5415cf2b4067
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 5/23/2013 10:22:18 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d90a8
    Section       @ fffffa800d6d9180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d90f0
    Section       @ fffffa800d6d9240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : a9 06 03 00 00 08 10 00 - bf e3 9a 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa800d6d9240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800d6d9138
    Section       @ fffffa800d6d92c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal timer (Proc 0 Bank 3)
    

    Also update the BIOS/UEFI from BIOS 1708 to BIOS 1908


    "A programmer is just a tool which converts caffeine into code"

    Friday, May 24, 2013 8:18 PM
  • Hey!

    im not very good with computers, do u guys recommend me to send in the computer to the store where i bought my computer parts frome and see if they can fix the problem?

    Becaus i have no idea how to fix this.....

    Thanks for your help!

    Friday, May 24, 2013 10:06 PM
  •  recommend me to send in the computer to the store where i bought my computer parts frome and see if they can fix the problem?
    I think this is the best. Backup all your personal data before bringing the PC to the store.

    "A programmer is just a tool which converts caffeine into code"

    Saturday, May 25, 2013 7:10 AM
  • Hey!

    I thought i fixed the problem until now, i havent got bluescreens for a very long time but yesterday i got three of them : execute of no execute memory, page fault in nonpaged area and kmod exception not handled.

    When i tried to fix the problem after the last time i wrote here, i restored the pc to factory settings, intsalled(and bought) driver reviver and updated all my drivers, i also used the build in defender. And it worked fine till yesterday.

    So here are my minidump files again: https://skydrive.live.com/#cid=632DDEB2D09B15C3&id=632DDEB2D09B15C3%21107

     Thanks again!


    Saturday, June 15, 2013 8:53 AM
  • you have RAM issues.
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff68000000408, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff802e1791bf9, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802e19c8168
    GetUlongFromAddress: unable to read from fffff802e19c81f8
     fffff68000000408 Nonpaged pool
    
    FAULTING_IP: 
    nt!MiEmptyWorkingSetHelper+19
    fffff802`e1791bf9 488b02          mov     rax,qword ptr [rdx]
    
    MM_INTERNAL_CODE:  2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  AV
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88002d638e0 -- (.trap 0xfffff88002d638e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002d63a98 rbx=0000000000000000 rcx=fffff802e19c1700
    rdx=fffff68000000408 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802e1791bf9 rsp=fffff88002d63a70 rbp=fffff78280000000
     r8=000000000000146b  r9=fffff782800000c0 r10=fffff802e19c1700
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MiEmptyWorkingSetHelper+0x19:
    fffff802`e1791bf9 488b02          mov     rax,qword ptr [rdx] ds:fffff680`00000408=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff802e178b5bc to fffff802e16ca440
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'
    nt!MmAccessFault
    nt!KiPageFault
    nt!MiEmptyWorkingSetHelper
    nt!MiEmptyWorkingSet
    nt!MiTrimAllSystemPagableMemory
    nt!MmVerifierTrimMemory
    nt!ViKeTrimWorkerThreadRoutine
    nt!PspSystemThreadStartup
    nt!KiStartSystemThread
    
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiEmptyWorkingSetHelper+19
    fffff802`e1791bf9 488b02          mov     rax,qword ptr [rdx]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiEmptyWorkingSetHelper+19
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5165e551
    
    IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_FUNC_OFFSET:  19
    
    FAILURE_BUCKET_ID:  AV_VRF_nt!MiEmptyWorkingSetHelper
    
    BUCKET_ID:  AV_VRF_nt!MiEmptyWorkingSetHelper
    
    You also have GPU related crashes.

    "A programmer is just a tool which converts caffeine into code"

    Saturday, June 15, 2013 7:52 PM