New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 593685 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crashes after start: The thread tried to read from or write to a virtual address of which it does not have the appropriate access

Reported by corkoome...@gmail.com, Mar 10 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. Install any version of W10 on an HP Elitepad 1000 G2
2. Optional: install Windows updates and drivers (we tried without this too)
3. Install and run Chrome
4. It crashes and shuts down (Windows says: "chrome has stopped working ...")

What is the expected behavior?

What went wrong?
Chrome worked when an update from W8.1 to W10 was done, but after a clean install it just doesn't work. We have tried using the drivers for Windows 8.1 as well as those for W10.

Crashed report ID: dump file is attached (because Chrome didn't start)

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

We have tried literally everything. This Dutch topic on the Chrome Forum is huge:
https://productforums.google.com/forum/#!topic/chrome-nl/1Wyl4vcgDXw
Beta, Canary and a portable version of Chrome don't work either.
Chrome only stays opened Windows Safe Mode, but the user also has an issue that the wifi driver does not work in this mode.
Can you please look into the dump file please?
I'm going to try to read it too and I already fount:

The thread tried to read from or write to a virtual address of which it does not have the appropriate access
 
2300808a-e7e2-499f-9287-87cf4667d1ef.dmp
1.2 MB Download
bump
It is been said that the Chrome forum will close very soon, April 4th. The topic I referred to (1Wyl4vcgDXw, see URL above) will be removed at April 29th by Google.

So please help us before then.
Original topic has been moved to the English Chrome forum:
https://productforums.google.com/forum/#!topic/chrome/2wB9mB0jcHo
bump

Comment 5 by ajha@chromium.org, Apr 26 2016

Cc: ajha@chromium.org
Labels: Needs-Feedback
Do you see any crash id listed under chrome://crashes. If yes, please attach the latest crash id when you encounter such crashes.
No, there are no IDs, hence the dumps.
Cc: rnimmagadda@chromium.org
@corkoomen.91 & vanantwerpenjeroen: Could you please update your Google Chrome to Latest Stable Version - 50.0.2661.102 and let us know your observations.

Also, re-test the same on a clean profile [chrome://settings -> Add Person] and provide us the Crash ID [chrome://crashes] if it is still crashing.

Thank you.
@rnimmagadda@chromium.org Thanks for your reply. The topic was already closed, but we managed to post a message to the OP. I hope he'll reply here.
This is the link to the reply in the topic:
https://productforums.google.com/d/msg/chrome/2wB9mB0jcHo/bnyZVsI7CwAJ
Project Member

Comment 9 by sheriffbot@chromium.org, May 21 2016

Labels: -Needs-Feedback Needs-Review
Owner: ajha@chromium.org
Thank you for providing more feedback. Adding requester "ajha@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by ajha@chromium.org, May 23 2016

Labels: -Needs-Review Needs-Feedback
Owner: ----
Waiting for the confirmation as per C#8.
I'm really sorry, but we didn't get a reply from the user anymore. I think he's not able to find his topic anymore because the Dutch forum was closed and the topic is moved to the English forum.

Anyway, you may close this issue.

Comment 12 by ajha@chromium.org, Jun 6 2016

Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
I am closing this for now.

Feel free to file a new issue if such issues are seen on the latest chrome versions.

Sign in to add a comment