Brave Crashing and Throwing STATUS_ACCESS_VIOLATION

Description of the issue:
Upon browsing various websites (seems to be a big fan of Amazon and YouTube) Brave browser either periodically crashes or throws the ‘Aw, Snap!’ screen, with Error code: STATUS_ACCESS_VIOLATION

Steps to Reproduce (add as many as necessary):

  1. Browsing various pages across Amazon and/or YouTube
  2. For some reason, this page on Amazon seems to be particularly successfuly for me personally at reproducing the issue: https://www.amazon.com/auto-deliveries/landing?ref_=nav_signin

Actual Result (gifs and screenshots are welcome!):
image

(I had more crash logs but lost them when I cleared my browser data.)
image

Crash from Tuesday, July 9, 2024 at 1:46:50 PM

Status: Uploaded
Uploaded Crash Report ID: f9212000-729b-3b0c-0000-000000000000
Upload Time: Tuesday, July 9, 2024 at 1:55:58 PM
Local Crash Context: c16ea5a1-6436-4867-a404-f9bb307dd4fa

Crash from Tuesday, July 9, 2024 at 1:42:44 PM

Status: Uploaded
Uploaded Crash Report ID: cb1c2000-729b-3b0c-0000-000000000000
Upload Time: Tuesday, July 9, 2024 at 1:51:33 PM
Local Crash Context: 20889e9b-796c-4ec1-9e97-00d8bf6d1b8c

Expected result:
Webpages to load and not crash

Reproduces how often:
Seems random, though it tends to happen within a span of hours to as quickly as 2 minutes after relaunching the browser or reloading the page.

Operating System and Brave Version(See the About Brave page in the main menu):
Windows 10, Brave version 1.67.123

Additional Information:
Here is the specs of my current device
image
Processor: Intel® Core™ i7-14700KF Processor (8X 3.40GHz + 12X 2.50GHz/33MB L3 Cache)

Motherboard: ASUS PRIME Z790-V WIFI, WiFi 5, Back Panel USB (1 Type-C, 7 Type-A)

Memory: 32GB [16GB X2] DDR5-6000MHz

I do notice that there are posts that are similar to this seem to have a commonality of utilizing DDR5 RAM.

For context, I have tried several trouble shooting options referenced from other similar posts, here is a list of what I’ve tried to no avail:

  1. Downloading Brave Nightly and testing
  2. Ensuring no flags have been altered in Brave://flags (they’re default)
  3. Disabling and/or deleting all Brave Extensions
  4. Resetting my settings
  5. Clearing browsing data from beginning of time
  6. Testing with in private
  7. Testing with Brave Shield enabled and disabled
  8. Testing on other devices (My device seems to be the only one I have encountered this issue on. I also use Brave on my work computer and it works fine; no crashing)
3 Likes

@TurtleDerby,
Amazing report — thank you so much for including all the details. I literally don’t have to ask for anything. Can’t tell you how nice that is :pray:

Passing on all this information and crash reports to our devs now for review. Will reply back when I know more.

EDIT: I lied I do have one question — when you downloaded Nightly and tested did you see the same results?

1 Like

Yes, though it didn’t give the exact same error message. Let me see if I can reproduce again and I’ll screenie.

This time it did throw the same error:
image

image

Crash from Tuesday, July 9, 2024 at 2:16:31 PM

Status: Uploaded
Uploaded Crash Report ID: 38382000-729b-3b0c-0000-000000000000
Upload Time: Tuesday, July 9, 2024 at 2:17:22 PM
Local Crash Context: 5ca238af-c8ee-4f73-935a-f6e630b06788
1 Like

Got it — thanks for the information. Have ping the devs in channel about this, hope to have more information soon.

1 Like

@TurtleDerby,
Do you have any accessibility tools enabled on the OS level at this time?

@Mattches All of my Windows accessibility features are either disabled or with stock settings from OS install.

I ended up going the nuclear option and just doing a fresh windows install since honestly there appears to have been funky things happening with more than just Brave. So far so good, but I will report back if that changes…

Edit 20240719 - @Mattches for awareness; the above was my solution for any who come after me with a similar situation. I think in my case there was something up with my install of Windows 10 – what I don’t know. I nuked it and did a fresh, brand spanky new Windows 11 install and have had no issues since. Marking this as my solution.

1 Like