Troubleshoot: IRQL NTOSKRNL BSOD when gaming on a relatively new PC build, install. Zipped DMP files

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7635

    #16
    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?

    It seems like a lot of people were having BSODs when playing Arma III. https://forums.bistudio.com/topic/14...d-to-fix-mine/

    Comment

    • moman
      PCHF Member
      • Dec 2016
      • 9

      #17
      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).

      Comment

      • moman
        PCHF Member
        • Dec 2016
        • 9

        #18
        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).

        Comment

        • jmarket
          PCHF Owner
          • Jan 2015
          • 7635

          #19
          Sorry about the delay @moman . Busy week

          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?

          After answering these questions in the next reply, please run Driver Verifier by following this guide and posting the results. Driver Verifier - Windows drivers | Microsoft Learn

          Comment

          • jmarket
            PCHF Owner
            • Jan 2015
            • 7635

            #20
            Any updates for us @moman ?

            Comment

            • veeg
              PCHF Director
              • Jul 2016
              • 8978

              #21
              Closed after 3 weeks of no response .

              Comment

              Working...