problem

[Hi-5]

http://oca.microsoft.com/en/response.aspx?...436d9871&SID=10

 

 

i am having that problem, what happens is:

 

i turn my computer on, but after the XP loading screen a blue screen flashes briefly, then the computer reboots

 

 

 

if anyone can help....plz DO

[Stoked_07]

sometimes my computer randomly flashes a blue screen and restarts too.. idk why.

[protoman.exe]

Roll back your drivers that you recently installed?

[JoWie]

Does it happen all the time, does it happen in safe mode?

(for safe mode, press F8 before the boot screen shows up)

If not:

 

(!@#$%^&*uming service pack 2)

 

Right click "My computer", select properties

Goto the "Advanced" tab

 

Under "Start and Recovery settings" press the "Settings button" (the third button from the top)

 

Then remove the check before "Automaticly restart the computer"

 

Press "ok" and "ok" again

 

Do note that the button names may not be accurate because I am using a Dutch Windows

 

 

 

When done, note the exact error message in the and paste it here (no need for useless text)

[Hi-5]

ok this is it:

 

 

Stop: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000)

[L.C.]

lol. You aren't sopossed to be getting any kind of blue flashing screen of death. If you do, it can be either of the following (that I could think of):

 

(1) Bad drivers, or drivers that somehow corrupted / messed up Windows XP,

(2) Bad, old, faulty, or possible incompatible hardware.

(3) Anything to do with the CPU overheating or being clocked too high, or chipset damages/issues.

(4) Overvoltage streaming of power to any part/certain parts (ie. RAM, CPU, etc).

 

I think you need to reinstall Windows XP and see if it happens. Telling us your system specs (as well as how old your computer might be ) should help progress further to correct this problem.

 

If you have your CPU overclocked or anything, I might suggest setting it back to the default factory settings and see how it works. :\

[Stoked_07]

idk but same thing happens with me, started like a week or 2 ago

[Excel]

!@#$%^&*uming that you can't login, try running it in safe-mode and running a virus scan. If that doesn't work, !@#$%^&*uming you have one, use a backup disk to roll back windows to when it was working. Last suggestion is just to reinstall windows. If that doesn't work, you're !@#$%^&*ed... format C and you know what to do from there.

[Deathboy-evil]

That used to happen to me a lot, eventually my computer literally got screwed over.. I needed to re-format it.. After that I kept a Anti-Virus/Spybot/Ad-Aware program on my computer and everything started to work smoothly..

[Bankotsu]

lol i have nothing on my comp and it is like almost brand new like late september i got it and i had a problem where i had to re-enstall my xp disc... but it was custom made and i dint have the key so we called the xp ppl and they gave me a new key i know this has nothing to do with the blue screen but should just let you know kuzz it was FREE u just need to have to disk to install it if you get a new comp and say u lost ur key and u have the program and u need a new one its awsome

[JoWie]

http://support.microsoft.com/kb/137539/en-us

SYMPTOMS

You may receive the following error message while running Windows:

STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)

 

CAUSE

This error message can occur if either of the following conditions exists: • Your computer has hardware or software problems (hardware failure is the most common cause).

• You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).

 

The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:• Low-level hardware corruption, such as corrupt memory (RAM)

• Mismatched memory modules

• A malfunctioning motherboard

 

To determine an approximate cause, examine the parameters at the top of the STOP screen:

**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)

UNEXPECTED_KERNEL_MODE_TRAP

The most important parameter is the first one (0x0000000X) which may have several different values. The cause of this trap can vary, depending on the value of this parameter. All traps that cause a STOP 0x7F can be found in any Intel x86 microprocessor reference manual as they are specific to the x86 platform. Here are some of the most common ones:

Values Meaning

---------- --------------------

0x00000000 Divide by Zero Error

0x00000004 Overflow

0x00000005 Bounds Check Fault

0x00000006 Invalid Opcode

0x00000008 Double Fault Back to the top

 

Divide by zero error

A divide by zero is caused when a DIV instruction is executed and the divisor is 0. Memory corruption (or other hardware problems) or software failures can cause this.

 

Overflow

The overflow instruction occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.

 

Bounds check fault

This fault is generated when the processor, while executing a BOUND instruction, finds the operand exceeds the specified limits. A BOUND instruction is used to ensure that a signed array index is within a certain range.

 

Invalid opcode

This fault is generated when the processor attempts to execute an invalid instruction. This is generally caused when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this is hardware memory corruption.

 

Double fault

A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers

.

RESOLUTION

To resolve this issue, use the appropriate method: • If either software or hardware can cause a particular trap, a debug is required to determine which is the cause. If you suspect a hardware problem, try the following hardware troubleshooting steps: 1. Test the RAM in the computer by running the diagnostic software that is provided by the computer manufacturer. Replace any RAM that is reported as bad. Also, make sure that all the RAM in the computer is the same speed.

2. Try removing or swapping out controllers, cards, or other peripherals.

3. Try a different motherboard on the computer.

 

• If you are over clocking the speed of your processor, set it back to the speed at which it is designed to run.

• Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.

 

For more information on processor faults, consult an Intel processor reference manual.

 

In other words:

 

- if you overclock, dont

- it can be a hardware issue, your RAM / CPU may be damaged

- if you have norton try unstalling it, there is a bug in norton which causes this error. but only do this if the bug does not appear in safe mode

 

The mose likely cause is Hardware not software, but you cant rule software out

[Bankotsu]

*clap*clap*clap* a round of a plause for jowie and his search for the answer im having trouble putting up my pic on the computer i use kodak camera and software yall cant see my red hair and freckles