When I enter --no-sandbox to resolve chrome conflict, it says the name specified in the target box is not valid; any other option?

Try below steps to fix error code 0xc0000005:
1. Locate Google Chrome shortcut on the desktop or in the start menu.
2. Right Click on the shortcut and open Properties.
3. Now go to the Shortcut tab and you'll see a field named Target.
4. Add the following attribute at the end of the Target Field after giving a space: -no-sandbox
5. You are done. Now restart Chrome and you won't see that error message again.

GuruAid.com

You need to check out all these:
1. Check for Conflicting Software:
- Some third-party software can cause Google Chrome to crash. When this happens, you'll see the message "Whoa! Google Chrome has crashed. It's possible that you have malware that can cause Google Chrome to crash.
- Google Chrome has a hidden page that will tell you if any software on your system is known to conflict with Google Chrome. To access it, type chrome://conflicts into Chrome's address bar and press Enter.
- You can try to fix these crashes by updating, disabling, or uninstalling any conflicting third-party software listed in "about:conflicts" on your computer. Also, take a look at Google Chrome's known issues for specific solutions to resolve crashes caused by some software.
2. Scan for Malware
- This includes malware and network-related software that interferes with Google Chrome. Malware can also interfere with Google Chrome and cause it to crash.
- You can try using Malwarebytes, or other anti-virus software to scan for and remove malware or you can also try searching the web for information related to any conflicting modules listed on the chrome://conflicts page (Windows only), to see if there are other steps you can take to remove malware.
- Many crashes are caused by malware. If you're experiencing frequent crashes, try scanning your computer with antivirus software.
3. Solve Flash Crashes
- We have found that the Flash plugin Chrome includes can cause it to crash in some cases. If you are seeing regular Shockwave Flash crashes, you may want to try disabling the internal Flash plugin and using the standard Flash plugin in Google Chrome.
4. Switch to a New Profile
- Chrome crashes may be caused by a corrupted profile. You can test this by creating a new profile from Chrome's Settings screen. Open the Settings page from Chrome's menu and click Add new user under Users.
- Change to the new profile after creating it and see if the crashes continue to occur. You can sign into Chrome with your Google account to sync the data from your old profile. However, Google recommends you don't copy any files from the old profile folder by hand - they may be corrupted and causing the problem.
5. Fix System File Problems

- Google recommends running the SFC.EXE /SCANNOW program to check for - and fix - problems with protected system files on your Windows system if you are encountering crashes. To do this, locate the Command Prompt in your Start menu (press the Windows key and type Command Prompt), right-click it, and select Run as Administrator.
- Type the following command in the Command Prompt window and press Enter:
SFC.EXE /SCANNOW
- Windows will scan your computer for problems with system files and fix any problems it finds.
6. Hardware issues
- It can also cause Chrome crashes. You may want to test your computer's RAM and ensure it isn't faulty.

· If still problem not solve, maybe you should try these simple steps:
1. Try restarting your computer first. It could be that the computer has just encountered a slight glitch on your system, which is causing things to not work properly.
2. Remove and Re-install the Google Chrome application. Doing this will allow your computer to read the files a lot better and faster, and also repair any damaged or corrupt files that have been causing the issue. To remove the Google Chrome application, first insure that you have another browser, such as IE or Firefox, click "Start, Control Panel, Add / Remove Programs," locate "Google Chrome" click UNINSTALL next to it. When the application loads, select "REMOVE" (not repair). Follow the uninstall process, and restart your PC. Problems uninstalling or re-installing Chrome indicate mal- or spy-ware, which must be dealt with.
3. Remove any extensions that you have on Google Chrome. Although they are a great way to personalize your Internet browsing experience, they are not so good for speed and functionality, as many can cause the application to crash. To remove any extensions follow these steps: Open up Google Chrome. In the address bar type chrome: //extensions. Click Uninstall, or Click Disable if you think you may use the add-on in the future. Restart your browser.
4. Disable plug-ins. Chrome can get bogged down with plugins that you aren't using, also. Type about: plugins into Chrome; it will redirect to chrome://plugins. Disable any that you aren't currently using.
Hopefully your Google Chrome crash problems are gone. Hope it works. Sharing is always caring.

A few things I found with a Google search:

• Try GooglePortable.
• Run a virus check.
• I think you should open Google Chrome without Sandboxing feature. In some cases reported, this feature was found to be the main element responsible for frequent crashes.
  
  1. Right click Chrome icon.
  2. Select Properties.
  3. Click the Shortcut tab.
  4. At the end of the Target textbox, type the following command:
  " -no sandbox"
  (without quotes; of course)
  5. Click OK.
• http://chromecrashes.com/

try to check the lights on your modem if the DSL light is blinking then it means that you have a intermittent signal or a drop of signal if it is solid try to check other web browsers like firefox or IE . if you could surf other websites using other browsers then it means that the problem is Google chrome try to optimize the browser (google) then try to close then open google to see if it works. if not try to uninstall reinstall google

Found this tip on another forum:

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

Right click on the Chrome icon and select properties and add " --no-sandbox" to the end of Target

example:

"C:\Documents and Settings\DRA\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --no-sandbox

Note: there must be a space between the final apostrophy and the two dashes

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

I have no idea how this works, but it worked for me - I am now able to use Chrome again.

PS. My problem started when my PC (WinXP) was infected by Trojan.FakeAV

See: http://www.symantec.com/security_response/writeup.jsp?docid=2007-101013-3606-99&tabid=2

YES yes yes, i went to C:\Users\(your profile name here)\AppData\Local\Google\Chrome\Application and renamed the file from chrome.exe to whatever.exe, note you wonte see the .exe but the file is the application or executable file. I did the change went to my desktop launched it and Oh yea it works baby.

Tried the -no-sandbox it didn't work, plus there is a security issue.

try this one. right-click on the Google Chrome icon and click Properties. Then go to the Target box and add --no-sandbox after the target and click OK.

For example, if it shows the following in the target box:

C:\Documents and Settings\Rodietom\Local Settings\Application Data\Google\Chrome\Application\chrome.exe"

it should look like the following after adding --no-sandbox to it..

C:\Documents and Settings\Rodietom\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --no-sandbox

if the above does not work and you are using symantec endpoint, you may want to check the following: http://techie-buzz.com/tips-and-tricks/fix-for-aw-snap-error-in-google-chrome-reader-recommendation.html

let us know how it goes for you.

*rodietom

Gmail Is Up or Down

1) right click on the google chrome icon on your desktop

2) click on properties

3) click on shortcut

4) where it says target and the end put a space and then --no-sandbox

5) press apply and then ok and it should work

if this does not work i am sorry but this is what worked for me