Cheat Engine

[marcthe666]

OK VOTE IN POLL

I badly wan to know how many times this has happened to people becuase i got the blue screen of death like 30 times.

Out of the like 30 times 2 times where sever one time screwed up my mother bord other one just gave me a bunch of errors.Also if u got blue screened alot like more then 20 times u shouldnt use Kernal debugger becuase thats why it is blue screening.Also please vote if u hade got a RED SCREEN WICH IS VERY VERY BAD So please vote

HERE is a link to a pic of one typ of blue screen of death FOR WINDOWS XP LOOK YOU MIGHT HAVE HAD



THIS ONE IS FOR WINDOWS 2000




RED SCREEN OF DEATH

[nightvision_288]

No comment..

[chu_hi]

5-10 TIMES

[marcthe666]

WOW MANY PEOPLE have not ever got a blue screen or for short bsod or AKA STOP ERROR

[Renato]

My uce uses hideme and i have never gotten a blue screen
i do however get the blue screen of ban

[marcthe666]

Like normally when you are using the debugger and stuff your computer wont know hot to handel it so it stops every thing. Here is a thing from wikipidea i splled wrong i think who cares here it is.

it kind of long but here it is very informational to.

The Blue Screen of Death (sometimes only called "bluescreen", "stop error", or just abbreviated as "BSOD") is the popular name for the screen displayed by Microsoft's Windows operating system when it encounters a system error (the Microsoft term is Stop error). There are two Windows error screens that are both referred to as the blue screen of death, with one (Windows NT 4/2000/XP/Vista) being significantly more serious than the other (Windows 9x). There are several causes of the blue screen popping up. It can be a poorly-written device driver, bad memory, damaged registry or usage of incompatible versions of DLLs (see more on the "Types of blue screens" section). Physical memory dumps may occur. The blue screen of death in one form or another has been present in all Windows operating systems since Windows version 3.1. It is the successor of the less well-known black screen of death that occurs in OS/2 as well as MS-DOS[1]. In early builds of Windows Vista it was complemented with a red screen of death, used for boot loader errors.

In Windows NT, Windows 2000, Windows XP, Windows Server 2003, and Windows Vista, the blue screen of death occurs when the kernel or a driver running in kernel mode encounters an error from which it cannot recover. This is usually caused by an illegal operation being performed. The only safe action the operating system can take in this situation is to restart the computer. As a result, data may be lost, as users are not given an opportunity to save data that has not yet been saved to the hard drive.

Blue screens are known as "Stop errors" in the Windows Resource Kit documentation. They are referred to as "bug checks" in the Windows Software development kit and Driver development kit documentation.


The text on the error screen contains the code of the error as well as its symbolic name (e.g. 0x0000001E, KMODE_EXCEPTION_NOT_HANDLED) along with four error-dependent values in parentheses that are there to help software engineers with fixing the problem that occurred. Depending on the error code, it may display the address where the problem occurred, along with the driver which is loaded at that address. Under Windows NT and 2000, the second and third sections of the screen may contain information on all loaded drivers and a stack dump, respectively. The driver information is in three columns; the first lists the base address of the driver, the second lists the driver's creation date (as a Unix timestamp), and the third lists the name of the driver [2].

By default, Windows will create a memory dump file when a blue screen error occurs. Depending on the OS version, there may be several formats this can be saved in, ranging from a 64 KB "minidump" to a "complete dump" which is effectively a copy of the entire contents of physical RAM. The resulting memory dump file may be debugged later, using a kernel debugger. A debugger is necessary to obtain a stack trace, and may be required to ascertain the true cause of the problem; as the information onscreen is limited and thus possibly misleading, it may hide the true source of the error.

Microsoft Windows can also be configured to send live debugging information to a kernel debugger running on a separate computer. (Windows XP also allows for kernel debugging from the machine that is running the OS.) If a blue screen error is encountered while a live kernel debugger is attached to the system, Windows will halt execution and cause the debugger to "break in", rather than displaying the BSOD. The debugger can then be used to examine the contents of memory and determine the source of the problem.


The Windows debugger is available as a free download from Microsoft.[3]

Windows includes a feature that can be used to cause a blue screen manually. To enable it, the user must add a value to the Windows registry. After that, a BSOD will appear when the user presses the SCROLL LOCK key twice while holding the right CTRL key.[4] This feature is primarily useful for obtaining a memory dump of the computer while it is in a given state. As such, it is generally used to aid in troubleshooting system hangs.
By default, Windows XP is configured to save only a 64K minidump when it encounters a blue screen, and then to automatically reboot the computer. Because this process happens very quickly, the blue screen may be seen only for an instant or not at all. Users have sometimes noted this as a Random reboot rather than a traditional stop error, and are only aware of an issue after Windows reboots and displays a notification that it has recovered from a serious error.

A BSOD can also be caused by a critical boot loader error, where the operating system is unable to access the boot partition due to incorrect storage drivers or similar problems. The error code in this situation is STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE). In such cases, there is no memory dump saved. Since the system is unable to boot from the hard drive in this situation, correction of the problem often requires booting from the Microsoft Windows CD. After booting to the CD, it may be possible to correct the problem by performing a repair install or by using the Recovery Console (with CHKDSK).

The color blue was chosen because there was a version of Windows NT for the DEC Alpha platform and there the console colors could not be changed in an easy way. For consistency reasons blue became the color for Stop errors on all platforms (alpha/i386/mips/ppc).

LOL THERE IT IS ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


TOLD YOU IT WAS LONG AND INFORMATINAL I SPelled that wrong i am not dumb

[marcthe666]

Yea i know it stops it becuase it dosn't no how to handel it so it stops it to prevent errors by the way it seems as if ur getting all this from blue screen picture lol

[chenl520769]

i use to get bluescreen.

i think the problem was my xp system's problem.

little suggestion: XP system may uses XE instead using CE.


ALSO, DO THE RIGHT THING.

i mean, dont click the non script option

[XxOsirisxX]

LOL, just try left click the arrays of bytes, and lets see comments

[Prowsezy]

I remember that! My dad red screened on Lotus Notes xD

[marcthe666]

More people hade got blue screns now

[MrFriedRice]

I never had a BSOD.

[BRONiUS]

I have BSOD's because of nv4_disp.dll :S And also if I try to run any engine with kernel stealth mode on for second time.

[marcthe666]

SO you hade a BSOD BEFOR

[Daaamon]

OWNED