Password reset and notification emails are now sending correctly.
If you recently requested a password reset, please check your inbox (and spam folder just in case).
You can now reset your password and log in as normal.
Welcome back to PCHF, and thank you for your patience during our migration process!
β The PCHF Team
Welcome to PC Help Forum!
Youβre viewing our community as a guest.
That means you can browse posts, but canβt yet reply or start new topics.
Join us today β it's completely free!
As a member, you'll be able to:
β Get personalized tech support from trusted volunteers
π¦ Work one-on-one with our Malware Removal Specialists
Iβve analyzed your dump file and have come across the possible cause. A 0A bug check code signals that the IRQL was too high. The likely cause is a device driver. Have you ensured that all your drivers are up to date, particularly the R9 drivers?
Windows tells me drivers are up to date but I understand it isnβt always accurate and would be advised to check the manufacturers website. As suggested by a friend (see post #4), I updated the drivers that I was linked to. To the best of my abilities, essential drivers such as R9 appear to be the latest. For peripherals like mouse and keyboard, I was informed they are out of date by my friend but when I went to update from manufacturers website, update program said they were indeed up to date.
Said friend from post #4 also examined my full mini dump folder (provided here as well) and followed up with this:
I tested 5 of the new crash dumps you sent me. 2 had the Battleye driver in the execution stack, the others didnβt.
However, it is a general memory corruption style of crash, which means a driver is writing to kernel-mode memory outside of its allocated space. This means a driver doesnβt necessarily need to be in the execution stack of the thread which throws a bug check (and yes, that does open the door to other drivers acting outside of the stacks which the Battleye driver shows up in). The Battleye driver is still the only 3rd party driver to show up in any of the stacks (3 of 6 now), so it still has my suspicions.
Iβm not familiar with how you join Arma games, but since this crash only happens while playing the game, Iβd recommend you try joining a server which doesnβt make sure of the anti-cheat software, or doing single player or the like.
If you can last longer than the typical 30-60 minutes before crashes happen while playing the game like this (where you know the anti-cheat software isnβt running), then Iβd say that is pretty definitive evidence of what the cause is.
Of course, BattleEye is absolutely necessary to play online in order to eliminate hacking/cheating so if this were the source of the crashes, it would indicate a crucial flaw that one would think many others would be complaining about (as you pointed out, though it isnβt apparent that battle eye was the cause for that particular thread).
while playing the game, I minimized the game screen to save the user profile as a recent crash corrupted/deleted the game save progress so I got into the habit of saving this folder (located in ~/My Documents/Arma III - Other Profiles) and my pc BSOD as soon as I hit the button to save a copy. It was an βIRQLβ BSOD. The game was still running but it was minimized.
Here is a zipped copy of my minidumps folder. This specific BSOD should be one of the most recent dumps (sorted by date).
Again itβs caused by a IRQL error. Letβs narrow down a few things:
1.) Does it only happen when playing Arma III?
2.) Does it happen when doing other tasks, such as playing other games, browsing the web, etc?
3.) Have you experienced any previous BSODs before buying Arma III?
4.) Are you running an antivirus when playing Arma 3?
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment