BSOD After Shutdown/Restart, error 0x0000009F

I am unfortunately back here sooner than I had hoped, the PC turned off correct I believe 2-3 times without any hangups until tonight. I am going to bed right now as it is 1:00am but I wanted to add the post.

This post does include the previous 2 minidumps as I wasn't sure if I should delete those from the Minidump folder or keep them in there so you'll see those as well. Again if you would like for me to upload it, I can upload or give you a link directly to my MEMORY.dmp file. It is ~600mb

Just in case since it takes quite a while to upload it as an attachment, this is a link to my MS One Drive where the MEMORY.dmp is able to be viewed. If you don't need it that's okay as well.

Link: Microsoft services

The new dump again points to the same driver albeit, now, a different version.
Lets attack it from a different angle, let's call upon Driver Verifier.

Arc said:

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Please enable driver verifier following this TUTORIAL | But using these settings:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

OK good thanks for the update.
Now run the PC as normal and hopefully the faulty driver will be caught with verbose information.
You can even manually try and induce a bugcheck by purposely suttingdown and restarting your pc.

Some more info:

0x9F which is DRIVER POWER STATE FAILURE that happens in
transitions between power states most commonly S0 (ON state) > S3 (Sleep state)
or vice-verse. You can read more HERE | Apparently the link needs a login now,
you can read something similar HERE.

The most common cause is a device driver but sometimes it's the hardware itself
that is at fault.

(I edited and added a link above)
No, just run your PC as you normally would.

We're here when and if it does.

Great news haha, it just gave me a BSOD but it did NOT say DRIVER_POWER_STATE_FAILURE instead it stated "IRQL_NOT_LESS_OR_EQUAL" shall I keep DV running or turn it back off?

The BSOD was triggered after starting up a game "Arma 3" (which btw it has never done before)


Edit: Uploading the files you requested, I tried to upload the additional .xml file that was listed on the "Show problem details" portion of the "Windows has recovered from an unexpected shutdown" window that popped up upon restarting my PC.

Great! in a way .

Now this is better, I did see this driver in the unloaded modules list in one of your previous
dumps I did suspect it, but I was aiming for a more surgical approach.

Code:

fffff880`0bead498  fffff880`09c28000 BEDaisy+0x8000
fffff880`0bead7f8  fffff880`09c621c4 BEDaisy+0x421c4
fffff880`0bead828  fffff880`09c226a9 BEDaisy+0x26a9
fffff880`0bead850  fffff880`09c226a0 BEDaisy+0x26a0
fffff880`0bead858  fffff880`09c61632 BEDaisy+0x41632

Code:

lmvm BEDaisy
      
    Loaded symbol image file: BEDaisy.sys
    Image path: \??\C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys
    Image name: BEDaisy.sys

    Timestamp:        Mon Nov 23 11:02:29 2015 (5652D625)

Please completely remove BattleEye Service.

Code:

BattlEye Service    BEService    "c:\program files (x86)\common files\battleye\beservice.exe"

• Driver Reference Table - BEDaisy.sys

Keep running DV for now.