BSOD After Shutdown/Restart, error 0x0000009F

[Garadan77]

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

 

[YoYo155]

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.

   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.

 

[Garadan77]

Okay so should I do anything in that linked Tutorial? I just created a Restore Point named it "Pre-Driver Stress Test" and am onto the next step of using the DV, just trying to cover my tracks because I read that sometimes you can actually not even get into Safe Mode and you have to resort to offline resources.

Which as you can see lol I am not the most computer savvy person when it comes to this kind of technical stuff.


EDIT: I found a tutorial on how to disable DV without loading windows SHOULD that become my only option.

I am now running DV with the settings you provided, restarted my PC, and I am back here.

 

[YoYo155]

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.

 

[Garadan77]

I notice in the tutorial it says the following:

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

So am I to continuously shut down my PC until it crashes (which shouldn't take long) or leave it on until it crashes? I have never had any sort of issue with the PC running normally, ONLY during shutdown/restart.

 

[YoYo155]

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

 

[Garadan77]

Haha I appreciate it, I already made an account and signed it to be able to read it. Alright though, I will continue this one and see how things go! Will report back as soon as a BSOD occurs.

 

[YoYo155]

We're here when and if it does.

 

[Garadan77]

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.

 

[YoYo155]

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.

fffff880`0bead498  fffff880`09c28000 [COLOR=Red]BEDaisy[/COLOR]+0x8000
fffff880`0bead7f8  fffff880`09c621c4 [COLOR=Red]BEDaisy[/COLOR]+0x421c4
fffff880`0bead828  fffff880`09c226a9 [COLOR=Red]BEDaisy[/COLOR]+0x26a9
fffff880`0bead850  fffff880`09c226a0 [COLOR=Red]BEDaisy[/COLOR]+0x26a0
fffff880`0bead858  fffff880`09c61632 [COLOR=Red]BEDaisy[/COLOR]+0x41632

[COLOR=SeaGreen]lmvm[/COLOR] [COLOR=Red]BEDaisy[/COLOR]
      
    Loaded symbol image file: BEDaisy.sys
    Image path: \??\[COLOR=Blue]C:\Program Files (x86)\Common Files\BattlEye\BEDaisy.sys[/COLOR]
    Image name: BEDaisy.sys

    Timestamp:        [COLOR=Red]Mon Nov 23 11:02:29 2015[/COLOR] (5652D625)

Please completely remove BattleEye Service.

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

• Driver Reference Table - BEDaisy.sys

Keep running DV for now.

 

[Garadan77]

I am assuming that means I have to suspend my playing of Arma 3, as Battleye is widely used by Bohemia Interactive (or maybe just Arma) way of catching cheaters/hackers that play the game. I also might add on my previous computer, Battleye did not cause this problem.

I AM going to be removing it as you have stated though, just wanted to provide that little bit of information if it's of any use.


EDIT: Do I remove only BEService.exe or the whole entire BattlEye folder?

Main reason I am asking is so that I make sure to not play Arma 3 tonight unless I am allowed to start it back up, but I THINK....it may reinstall that BattlEye driver as it is required on the servers I play on.

 

[YoYo155]

Don't just delete the software, uninstall it completely.
I recommend using the "complete" option using Revo Uninstaller.

• http://www.sevenforums.com/tutorials/106594-revo-uninstaller-freeware-uninstall-programs.html

 

[Garadan77]

Okay I watched the video, I have Revo Uninstaller downloaded however I am not seeing BattlEye anywhere to be chosen.

Update: I am assuming since it came with Arma 3 and it is in the Arma 3 folder as well, I will have to uninstall Arma 3 using Revo Uninstaller. Once that is completed may I redownload it or what shall my further instructions be?

 

[YoYo155]

Assuming you didn't disable DV and that you've removed BattleEye,
all that is left now is to see how we fair over time.

 

[Garadan77]

Nope, I still have DV enabled, and I wasn't able to find BattlEye so I just uninstalled Arma 3 all together. Will let that sit for a day or so and see what the assessment is.

Update: Restarted PC after doing all of those changes just to be safe and it BSOD again, I'm not sure what it's going to say this time. I try to open them and look I just don't have a clue what I am looking at.

New update is attached below

 

[YoYo155]

The analysis is inconclusive at this point, there was a system driver timeout
which the debugger (VRF) called a break which caused the BSOD.
I would call it a bug and and tag it as calculated risk for using Driver Verifier.

"Nothing to see here" .

P.S.
I t just so happens that I was doing my "round-back" that I noticed that you edited
your post, if something substantial happens comment using a new reply that is the
only way I'll get notified, edits don't do that.

 

[Garadan77]

Ah alright, well fingers crossed that it was just something caused by the Driver Verifier and wasn't an "Extra" problem. By the way, I was able to find more "Bohemia Interactive" and "BattlEye" things on my PC after doing the FULL uninstall of Arma 3, I guess some things weren't linked together with it.

I couldn't find an uninstall.exe for it at all, so I did the typical....delete -> recycle bin -> empty for everything else that was left over Bohemia Interactive / BattlEye related.

But I want to pick at this a little more cause I am quite curious...

BattlEye is an anti-cheat engine that comes from Arma 3 (a game I play quite often) - That gave an issue - So we remove the issue - Now are we trying to remove each/every issue until we've got them all fixed. Then slowly reinstall the things I used?

 

[YoYo155]

That is correct, the goal now is to get your system stable consistently
and for a considerable about of time.

After that is achieved, we can start poking the at beast.

 

[Garadan77]

Just out of curiosity, should I leave my PC on constantly all the time and it should eventually BSOD? Just trying to figure out what I should be doing while running Driver Verifier.

Would it be of any help to just play for 1-2 hours, restart, play for 1-2 hours, restart. Since it never BSOD unless shutdown/restart except for strangely enough that one time when running Arma 3 earlier (after enabling Driver Verifier).

Update: Tried shutting it down tonight before going to bed cause I was unsure of what to do. BSOD again, but I used to restroom so I missed the message it threw up. It MIGHT be the same "inconclusive" thing you mentioned earlier.

 

[YoYo155]

Okay this is the same as before.
I looked more closely at this dump seeing it's pretty much the same as the last
and came to the conclusion that it is similar to a 0x9f (like the ones we had before)
Wdf01000 is waiting on something locked then times out.

• Driver Reference Table - Wdf01000.sys

I was about to post a long list of actions but changed my mind because as I mentioned
before I prefer the more surgical approach.

Let's disable DV:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:ar: Update Windows avoiding Windows 10 updates(!)