One of your drivers caused this error, not much information was given.
An attempt was made to execute non-executable memory.
Enable driver verifier, follow the instructions in the below tutorial.
Driver Verifier - Enable and Disable
This will help find the driver.
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: fffff880009e9180, Virtual address for the attempted execute.
Arg2: 80000000001a1963, PTE contents.
Arg3: fffff88006dd0920, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88006dd0920 -- (.trap 0xfffff88006dd0920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff96000370100 rbx=0000000000000000 rcx=fffff900c01ff00f
rdx=fffff900c06b1210 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880009e9180 rsp=fffff88006dd0ab8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff96000166f98
r11=fffff900c1b3d520 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff880`009e9180 801f00 sbb byte ptr [rdi],0 ds:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002943e9f to fffff800028c4f00
STACK_TEXT:
fffff880`06dd07b8 fffff800`02943e9f : 00000000`000000fc fffff880`009e9180 80000000`001a1963 fffff880`06dd0920 : nt!KeBugCheckEx
fffff880`06dd07c0 fffff800`028c2fee : 00000000`00000008 fffff900`c06b1210 00000000`00000000 fffff800`028cadda : nt! ?? ::FNODOBFM::`string'+0x42567
fffff880`06dd0920 fffff880`009e9180 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`06dd0ab8 fffffa80`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : 0xfffff880`009e9180
fffff880`06dd0ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`739c2450 : 0xfffffa80`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42567
fffff800`02943e9f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42567
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
Followup: MachineOwner
---------
Run Disk Check
How to Run Disk Check in Windows 7
Code:
Event[320]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-05-25T17:56:53.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: JEFF-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880078bd088, 0xfffff880078bc8e0, 0xfffff800026e84f5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052511-29140-01.