Go to BIOS, find option 'Data Execution Prevention', and enable it. Moreover, enable option called 'Virtualization Technology (VT)' feature, in a case; you are trying to install Windows 8 from virtualization software like oracle or VMWare.
How to enable above option
To enter in BIOS, restart computer and on very first screen find a message like this:
'DEL to enter setup'
'Press Esc to Enter Setup'
'BIOS Configuration: F2'
'F10 to Enter Setup'
Carefully find any message on your screen and press respective key to enter in BIOS.
Once you enter in BIOS setting, go to Advanced Options and select Processor then No Execute Memory Protection, if not, then Security > Options and Select Execute Disable. Change this to 'Enable' or 'On'.
Save changes and Exit Bios Setting if you perform Windows 8 installation in a new PC, otherwise move on to next step
Enable Virtualization Technology (VT) feature
Go to BIOS setting by following above-mentioned steps. Go to Performance options. Change the Virtualization feature to 'Enable' or 'On'. Save changes and Exit BIOS setup. Proceed to next step if your system supports the security feature. This is how you can solve the issue.
00 = Divide Fault
Occurs if division by zero is attempted or if the result of the operation does not fit in the destination operand.
02=NMI interrupt
Interrupt 2 is reserved for the hardware Non-Maskable-Interrupt condition. No exceptions trap through interrupt 2.
04=Overflow trap
Occurs after an INTRO instruction has executed and the OF bit is set to 1.
05=Bounds Check fault
The array Index is out of range
06=Invalid Opcode fault
This error can be caused by one of the below conditions.
07=Copressor not available fault.
This error can occur if no math coprocessor is present. This error can also occur when the math coprocessor is used and a task switch is executed.
08=Double Fault.
This error occurs when processing an exception triggers a second exception.
09(OD)=Copressor Segment Overrun.
Floating point operand is outside the segment.
10(0Ah/0A)=Invalid Task State Segment Fault
Can be caused by a number of possibilities as Task State Segment contains a number of descriptors.
11(0Bh)=Not Present Fault
The Not Present interrupt allows the operating system to implement virtual memory through the segmentation mechanism. 0B fault occurs when this segment is not available.
12(0Ch)=Stack Fault
Occurs when instruction refers to memory beyond the limit of the stack segment.
13(Odh)=General Protection Fault
Caused
by any condition that is not covered by any of the other processor
exceptions. The exception indicates that this program has been corrupted
in memory generally resulting in the immediate termination of the
program.
14(Oeh)=Page Fault
Occurs when a paging
protection rule is violated (when the retrieve fails, data retrieved is
invalid or the code that issued the fault broke the protection rule for
the processor).
16(10h)=Coprocessor error fault
Occurs when an unmasked floating-point exception has signaled a previous instruction.
17(11h)=Alignment Check Fault
Only
used on 80486 computers. Caused when code executing at ring privilege 3
attempts to access a word operand that is not divisible by four, or a
long real or temp real whose address is not divisible by eight.
Find out the reason of Fatal Error if that is due to Software related then go in safe mode and uninstall the software recently installed or udate them/patch them. or if the same is related to hardware then unplug the recently added hardware,
please vote
In many cases this error has been generated by faulty RAM memory. So if you have just upgraded your computer with some new memory and you started getting this error then would remove them and see if the error goes away. If it does then send the memory back and get a refund!
In Windows XP Service Pack 2 Microsoft introduced Data execution prevention (DEP), a set of hardware and software technologies that perform additional checks on memory to help protect against malicious code exploits. In Windows XP SP2, DEP is enforced by both hardware and software.
Some software/application behaviours are incompatible with DEP - data execution prevention.
/NOEXECUTE
This option is only available on 32-bit versions of Windows when running on processors supporting no-execute protection. It enables no-execute protection (also known as Data Execution Protection - DEP), which results in the Memory Manager marking pages containing data as no-execute so that they cannot be executed as code. This can be useful for preventing malicious code from exploiting buffer overflow bugs with unexpected program input in order to execute arbitrary code. No-execute protection is always enabled on 64-bit versions of Windows on processors that support no-execute protection.
There are several options you can specify with this switch:
/NOEXECUTE=OPTIN Enables DEP for core system images and those specified in the DEP configuration dialog.
/NOEXECUTE=OPTOUT Enables DEP for all images except those specified in the DEP configuration dialog.
/NOEXECUTE=ALWAYSON Enables DEP on all images.
/NOEXECUTE=ALWAYSOFF Disables DEP. (This setting doesn't provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor doesn't run in Physical Address Extension (PAE) mode unless the /PAE option is present in the boot.ini file.)
This error also seen when people have updated drivers for their graphics card. If this happens just roll back your drivers. Also keep an eye on the vendors website to see if they have an update/patch available or coming soon.
216 views
Usually answered in minutes!
http://answers.microsoft.com/en-us/ie/fo...
×