Build 14251 - Chrome doesn't work

You have to reinstall from the chrome website, thereby getting the latest Chrome version. You will keep your Bookmarks automatically.

After totally uninstalling Google Chrome including all registry entries and folder containers in normal and hidden folders, and the reinstalling Chrome, Google Chrome does not open. There is an exception in the event viewer, the contents of which means the following:
Computers have limits, they cannot divide a number by zero, nor read memory that isnt there, (and lots of other things).

They use a generic mechanism called Exceptions, to signal the software that it cannot do the operation it was requested to do, and some information as to why not.

Straight out of section 3.1.9, table 3-2 of Intel Processor Instruction Manual
0 #DE—Divide Error DIV and IDIV instructions.
13 #GP—General Protection Any memory reference andother protection checks.

Peruse this excerpt from the IA-32 Intel® Architecture Software Developer's Manual, Volume 3: System Programming Guide (bear with me, it gets better)

Quote:

Exceptions are classified as faults, traps, or aborts depending on the way they are reported and whether the instruction that caused the exception can be restarted with no loss of program or task continuity. Faults A fault is an exception that can generally be corrected and that, once corrected, allows the program to be restarted with no loss of continuity. When a fault is reported, the processor restores the machine state to the state prior to the beginning of execution of the faulting instruction. The return address (saved contents of the CS and EIP registers) for the fault handler points to the faulting instruction, rather than the instruction following the faulting instruction. Traps A trap is an exception that is reported immediately following the execution of the trapping instruction. Traps allow execution of a program or task to be continued without loss of program continuity. The return address for the trap handler points to the instruction to be executed after the trapping instruction. Aborts An abort is an exception that does not always report the precise location of the instruction causing the exception and does not allow restart of the program or task that caused the exception. Aborts are used to report severe errors, such as hardware errors and inconsistent or illegal values in system tables.

a #GP is a general protection fault. That means the program tried to access memory that is 'protected', it could not, and as you read above is handed to the fault handler.

Now.. If you've been in the game since Win98, you may have seen a GP_FAULT once or twice. Same thing, only now in NT/XP we get DrWatson complaing about an ACCESS_VIOLATION. This begs the question, what did it try to access that was a violation of normal runtime?

The operating system knows that programmers make mistakes, and make a special DMZ/No mans land at address 00000000 through address 0000FFFF, so that programs who try to reference NULL (a C programming way of saying Zero or Empty) will fail, rather than corrupt themselves and die horribly after corrupting your data.

Prove it, you say?? Can do.. i fire up my trusty debugger and examine this memory

Code:

0:000> !vadump ***Note this command inspects the memory properties BaseAddress: 00000000 RegionSize: 00010000 State: 00010000 MEM_FREE Protect: 00000001 PAGE_NOACCESS BaseAddress: 00010000 RegionSize: 00001000 State: 00001000 MEM_COMMIT Protect: 00000004 PAGE_READWRITE Type: 00020000 MEM_PRIVATE ***Here is no mans land*** 0:000> dc 00000000 ***Note this command displays the contents of memory 00000000 ???????? ???????? ???????? ???????? ???????????????? 00000010 ???????? ???????? ???????? ???????? ???????????????? 00000020 ???????? ???????? ???????? ???????? ???????????????? 00000030 ???????? ???????? ???????? ???????? ???????????????? 00000040 ???????? ???????? ???????? ???????? ???????????????? ****as you can see here, the end of no mans land, and the beginning of real memory**** 0:000> dc 00010000-30 0000ffd0 ???????? ???????? ???????? ???????? ???????????????? 0000ffe0 ???????? ???????? ???????? ???????? ???????????????? 0000fff0 ???????? ???????? ???????? ???????? ???????????????? 00010000 0043003d 003d003a 003a0043 0044005c =.C.:.=.C.:.\.D. 00010010 0063006f 006d0075 006e0065 00730074 o.c.u.m.e.n.t.s. 00010020 00610020 0064006e 00530020 00740065 .a.n.d. .S.e.t. 00010030 00690074 0067006e 005c0073 006f006a t.i.n.g.s.\.j.o.

So, what is an access violation, a C0000005? This is the translated #GP code the fault handler raises, which the operating system displays as an 'Access Violation', whos numerical form is c thousand 5. Its the operating system telling you that a program has malfunctioned and tried to reference no mans land. It has nothing specific to do with any particular program, or a brand of software, this is straight from the CPU and kernel of the operating system.


NOW. On to your real question, you are probably seeing a lot of these on your machine, which made you come here in search of answers. You now need to determine which program is throwing the exception. It may be several, thats certainly possible. Use Start->Run Drwtsn32 and see whats in the exception handler log. Use the event viewer, if you prefer. Once you've identified the application that is faulting, the next time it crashes on you, note where it stuck the dump (probably \windows\minidump\3279272.dmp or in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp) and run it through the dump data analysis tool in my signature, and ill tell you why it blew up, and try to recommend what to do to fix it.