Frequent crashes, Access Violation (0xc0000005)

[lyar]

First of all, I've been lurking around this site for a while and love the helpfulness of the community here.

So, right to the point. I've had this problem for a long time with pretty much any application.
Games would crash after 10-15 minutes and Firefox as well. Always with an access violation trying to read from or write to location 00000000.

there's, I think, the relevant part of a typical error report:

21% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [2917 MB free].
Write to location 00000000 caused an access violation.

I'll try to keep this post short but I'm not a techie so I'm not sure which parts of the crash report are relevant. Feel free to ask for any additional informations.

-----
Steps I've taken:

- ran a few scans with malwarebytes and kaspersky, returned clear.
- Fresh install of audio and graphics drivers
- I ran the build-in windows memory checker and it returned clear.
- I thought maybe some windows files were corrupted so I ran a the built-in filechecker. It found some missing (or corrupted files) and replaced them.
- I thought it might be a faulty ram so I bought a new set of 2x8gb ballistix ram and installed them instead of the old ones. (I was pretty desperate at this point, please don't judge me).
- I was under windows 7 and thought somehow my install was faulty so I installed a new windows 10 (Yes, I'm trying to nuke a cockroach at this point. But it's a very annoying cockroach).

-----

config:

- Cpu: Intel core i-7 3770 with an attached artic cpu cooler
- Gpu: Radeon R9 280x toxic
- Ram: 2x8Gb of ballistix (DDR3)
- Psu: Lepa B800M maxbron -800W

Thank you for reading this thread, and I'm eagerly waiting for any new input.

With regards,
Lyar

 

[Colif]

same errors even after a fresh install?

The error code 0xc0000005 could have been caused by a corrupt registry, malware, installed or updated software or even Windows security features.

it might be a windows update error so this page may help - https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors

can you search cortana for reliability history and choose the control panel option
its likely the errors will be showing in here as well, can you pick one and look at the link called view technical details and show us what it says there.

what motherboard is it?

 

[lyar]

Hello,

Thanks for the quick answer!

Indeed, games still crash under the new OS.

I follow the steps recommended up to the DISM (performed successfully) and sfc /scannow (returned no violations).
Still got crashes.
I'm currently updating windows again... just in case.
Next step is an in-place upgrade then a fresh install. Which I think I have covered. (I might rollback to a fresh install of windows 7 if I have to, Cortana's a bit too flirty for me)

----

Oddly enough most games (I tried 3), do not show up as errors in the reliability history, but as warnings in the event viewer.
Anyway, there's the technical details for the game that left an error message.

Please pardon windows' French.

Nom d’événement du problème : BEX64
Nom de l’application: Dauntless-Win64-Shipping.exe
Version de l’application: 4.17.2.0
Horodatage de l’application: 5b2182c8
Nom du module par défaut: StackHash_f9d8
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Décalage de l’exception: PCH_9F
Code de l’exception: c0000005
Données d’exception: 0000000000000008
Version du système: 10.0.14393.2.0.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: f9d8
Information supplémentaire n° 2: f9d82b147b6ad3097a0d9c822ca02a2a
Information supplémentaire n° 3: de0a
Information supplémentaire n° 4: de0a40479120ea8170f842d4122846d6

Informations complémentaires sur le problème
ID de compartiment : b61cf694d977d14fab51879955a3c9a7 (1968503604774160807)

(I could try to translate if you'd like but I have a feeling you already know what it is saying)

---

Motherboard is an ASRock P67 Pro3.

I can't thank you enough for your time.

 

[Colif]

its not a BSOD, right? its just a white pop up box?

Surprisingly there is a new BIOS for your motherboard though its still in beta, its likely it will never stop being a beta since there are 2 beta bios for your motherboard and one is from 2014. The newest is from May 30 2018 and would match the latest version of Intel Management Engine Interface which they haven't updated yet... curious. The changes are to correct errors in INtel CPU

Can you right click start
choose device manager
scroll down to system devices and click arrow next to it to expand tree
right click Intel Management Engine Interface and look on driver tab, can you tell me what driver number/date it shows?

Just curious if errors caused by a newer driver version sending commands bios doesn't know answer too. I could also be way off course

 

[lyar]

Pilot date: 07/07/2015
Pilot version: 11.0.0.1157

If it is indeed the source of all evil. I would've never thought of this.

edit: forgot to mention it is usually a crash to desktop with a white pop-up describing the crash. If I insist and try to immediately relaunch the program, though, the little rebellious rig will sometimes BSoD.

edit 2: Let me know if I need to add any tags for visibility to other users. I had no idea what tag(s) to add.

 

[Colif]

there is only 1 released BIOS on motherboard site, its from October 15 2015 so I am not sure my idea is correct. I expect Asrock will update the files on their site once its ready for release.

can you look in c:\windows folder
change view to show hidden files and folders
can you see how bug the MEMORY.dmp file is? That file would likely show results of BSOD in it but if its several GB in size it becomes too big to upload to a file sharing site (or even download for person who needs to read it)

If its only small, copy it to documents
upload that copy to a file sharing web site and show a link here, I will ask someone to convert it for me.

If its really big, Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here

 

[Colif]

BEX64 seems to pop up with EA games a lot, and Dauntless is still in early access so if it was only game that caused this error, the beta state would be my answer.

Are you playing it through Origin? I found one fix for FIFA

The BEX64 problem is a issue causes by the save files either your origin account or your computer has thats been loaded when starting FIFA 15.

Steps to fix:
1. Delete all save files in your users/documents folder (and perhaps libraries/documents folder).
2. Start the game launcher from origin.
3. If origin syncs save files before starting that launcher -> Repeat step 1
4. Start game
5. Play

https://answers.ea.com/t5/FIFA-15/PC-FIX-for-BEX64-error-SOLVED/td-p/3664073

Never seen it before but it gets around.

 

[lyar]

Unfortunately, I'm not playing through origin and the fresh install deleted all the save files anyway.

Firefox just crashed leaving me with the same kind of report from the reliability history.

Nom d’événement du problème : APPCRASH
Nom de l’application: firefox.exe
Version de l’application: 60.0.2.6730
Horodatage de l’application: 5b16d65f
Nom du module par défaut: ntdll.dll
Version du module par défaut: 10.0.14393.1715
Horodateur du module par défaut: 59b0d03e
Code de l’exception: c0000005
Décalage de l’exception: 00000000000495fc
Version du système: 10.0.14393.2.0.0.256.48
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 6567
Information supplémentaire n° 2: 65678298f3c65f33e28de3b01ac4aa83
Information supplémentaire n° 3: 2f44
Information supplémentaire n° 4: 2f4490b8a91dba4c21592429668f111c

Informations complémentaires sur le problème
ID de compartiment : 35774d08f9b6aff61106df3321dce3a4 (1226913359209489316)

I know it's more of the same but well. could be an unrelated .dll problem though.

Anyways, the dump is approximatly 500MB in size so I'm uploading it to dropbox.

 

[Colif]

Try doing a clean boot and see if it keeps happening, read instructions and make sure NOT to disable all Microsoft services or it won't load correctly. - https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

if that fixes it, you will need to slowly restart all other startup applications to figure out what is causing problem.

I am unsure what tags to add either

 

[lyar]

Behold my formatting prowess:
[urlExt=https://www.dropbox.com/s/yp8iu7ww7ptx628/MEMORY.DMP?dl=0
]Here's a link to the file.[/urlExt]
[urlExt=https://www.dropbox.com/sh/6tylgrm9cent5lf/AACxZiyKYbOl3-X68I-Hgmzqa?dl=0]and here's a version you can modify because I can't tech.[/urlExt]

Now I'm going to try the clean boot.

 

[lyar]

Clean boot turned out pretty easy since I've got 6 (non-microsoft) services. (3 dropbox, 1 amd's external events utility, 1 modzilla, and a VPN) none seems crucial so I'll let them off.

Once all off and every startup application (all 4 of them) deactivated, I rebooted and launched myself a sweet bloodbowl game only to have it crash after 5 minutes.

Went to check the event viewer and it immediately crashed...
This is the reliability report:

Nom d’événement du problème : APPCRASH
Nom de l’application: mmc.exe
Version de l’application: 10.0.14393.2097
Horodatage de l’application: 5a820e5d
Nom du module par défaut: KERNELBASE.dll
Version du module par défaut: 10.0.14393.2189
Horodateur du module par défaut: 5abdad60
Code de l’exception: 00000000
Décalage de l’erreur: 0000000000033c58
Version du système: 10.0.14393.2.0.0.256.48
Identificateur de paramètres régionaux: 1036

I think Terry (the old grumpy rig) doesn't want to be fixed.

 

[Colif]

You need to update windows 10, you are still on version 14393 which was released in August 2016. The current build is 17134. You are 3 versions of windows 10 behind the current version.

You might be best doing a clean install using the Windows 10 media creation tool and use it to make a win 10 installer on USB.

You can try to run the upgrade process using the USB as it may work as well. Just create USB, then navigate to USB and run install.exe from inside File explorer.

That might resolve your issues.

 

[lyar]

Colif! I've missed you.

Windows is now all up and updated. (even got a little thank you note! which made me feel a little special.)
At this point I'm running out of ideas. I'll try a new windows install tomorrow and let you know how it went but without much hope.

Anyway, you've been amazing.
So long and thanks for all the fish.

 

[Colif]

Hopefully Fresh install fixes it since update didn't seem to.

good book, good song too.

Hopefully all the dolphins are still here or we may have problems. watch out for mice too.