BSOD/crashes occur when computer sleeps

bru · 23 Mar 2016

New laptop with Windows 10. After about a week I noticed system crashing. Seemed to occur after the computer had gone to sleep. Possibly related to Malwarebytes scan being run as it occurred a few times right after the scan had finished and then the computer went to sleep. Would have to restart the computer and I could see that Windows had not shut down properly/had stopped working. Problem details showed "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f etc." Happened several times over the next few days. Googling led me to believe it was a driver issue so I updated some drivers (Wi-Fi adapter, Audio) but the problem persisted. Did a complete Refresh and ran the system pretty much untouched and things were good for 3 days until today when the crash again occurred.

The DM Log Collector file is attached. I appreciate the help.

BorisTheAnimal · 24 Mar 2016

Hello Bruce.

I looked at the dump file and it points out that you have an issue with the Wi-Fi adapter. Even though you say you've tried to update I'd still like for you to head to HP support and download the drivers for your WiFi adapter, in your case it will be the Realtek RTL8188EE:
HP Notebook - 15-f337wm

Oh and by the way please update your "My System Specs" tab!

Cheers, Boris :)

bru · 24 Mar 2016

BorisTheAnimal said:

Hello Bruce.

I looked at the dump file and it points out that you have an issue with the Wi-Fi adapter.

Would the dump file/log show anything related to the Malwarebytes scan causing an issue? I believe I have isolated the problem to occurring either during or after a Malwarebytes scan is run. Today after the scan completed and probably when the computer would go to sleep the computer would not respond. Had to do a hard restart. The behavior was slightly different then before and the event log only showed "Windows was not properly shut down". Previously it also showed "Windows stopped working" and "Shut down unexpectedly".

I ran the tool again and am attaching the .zip file but I don't think a dump file was created so it may still be the one from yesterday. I have not yet updated the Wi-Fi adapter. As I mentioned in my OP I did update it from HP's site and the crashes still occurred. I then did the Refresh. I wonder if I should get it direct from Realtek?

BorisTheAnimal · 24 Mar 2016

Hello Bruce, sorry for the late reply.

Well if it was Malwarebytes that caused the crash then there should have been a driver from MB in the dump but considering that the BSOD you got was a DRIVER_POWER_STATE_FAILURE, maybe when running MB it would scan the driver of the WiFi adapter and cause this crash.

This is the closest I've come to find your driver:
RTL8188CE

Cheers, Boris :)

axe0 · 24 Mar 2016

I ran the tool again and am attaching the .zip file but I don't think a dump file was created so it may still be the one from yesterday.

There is only a sudden shutdown event logged, any bugchecks haven't been saved at all.

I wonder if I should get it direct from Realtek?

Boris and mine thoughts about that are opposite, I wouldn't recommend it.

Would the dump file/log show anything related to the Malwarebytes scan causing an issue?

Possibly, unfortunately I can't look up the dates of the drivers so I have a few straight suggestions.
1. Remove Malwarebytes and reinstall it, https://support.malwarebytes.org/cus...5311?b_id=6438
2. Update Malwarebytes manually, download from Malwarebytes | Free Anti-Malware & Internet Security Software and install overtop to see if that helps. Installing overtop normally doesn't affect the program, but a reboot after overtop installation should fix problems that have occured due to overtop installation (a reboot is always recommended after overtop installation even if you didn't notice any problems). If you experience problems after reboot a removal and installation is required.

Code:

fffff801`5dbd0000 fffff801`5dbe1000   vwifimp.sys
fffff801`5dbb0000 fffff801`5dbc1000   vwifimp.sys
fffff801`5db30000 fffff801`5db41000   vwifimp.sys
fffff801`5db10000 fffff801`5db23000   mwac.sys
fffff801`5dad0000 fffff801`5db03000   MBAMSwissArm
fffff801`5dab0000 fffff801`5dac1000   vwifimp.sys
fffff801`5da90000 fffff801`5daa3000   mwac.sys
fffff801`5da50000 fffff801`5da83000   MBAMSwissArm
fffff801`5d9d0000 fffff801`5d9e1000   vwifimp.sys
fffff801`5da30000 fffff801`5da43000   mwac.sys
fffff801`5d9f0000 fffff801`5da23000   MBAMSwissArm
fffff801`5d9b0000 fffff801`5d9c3000   mwac.sys
fffff801`5d970000 fffff801`5d9a3000   MBAMSwissArm
fffff801`5d8f0000 fffff801`5d901000   vwifimp.sys
fffff801`5d950000 fffff801`5d963000   mwac.sys
fffff801`5d910000 fffff801`5d943000   MBAMSwissArm
fffff801`5d880000 fffff801`5d893000   mwac.sys
fffff801`5d840000 fffff801`5d873000   MBAMSwissArm
fffff801`5d8a0000 fffff801`5d8b1000   vwifimp.sys
fffff801`5d7f0000 fffff801`5d801000   hidusb.sys
fffff801`5d810000 fffff801`5d81c000   MTConfig.sys
fffff801`5d820000 fffff801`5d831000   vwifimp.sys
fffff801`5d7d0000 fffff801`5d7e3000   mwac.sys
fffff801`5d750000 fffff801`5d783000   MBAMSwissArm
fffff801`5d7b0000 fffff801`5d7c1000   vwifimp.sys
fffff801`5d680000 fffff801`5d691000   hidusb.sys
fffff801`5d6a0000 fffff801`5d6ac000   MTConfig.sys
fffff801`5d790000 fffff801`5d7a3000   mwac.sys
fffff801`5d6d0000 fffff801`5d6e1000   vwifimp.sys
fffff801`5d730000 fffff801`5d743000   mwac.sys
fffff801`5d6f0000 fffff801`5d723000   MBAMSwissArm
fffff801`5d660000 fffff801`5d673000   mwac.sys
fffff801`5d620000 fffff801`5d653000   MBAMSwissArm
fffff801`5d6b0000 fffff801`5d6c1000   vwifimp.sys
fffff801`5d600000 fffff801`5d611000   vwifimp.sys
fffff801`5d5d0000 fffff801`5d5e1000   hidusb.sys
fffff801`5d5f0000 fffff801`5d5fc000   MTConfig.sys
fffff801`5d5b0000 fffff801`5d5c3000   mwac.sys
fffff801`5d570000 fffff801`5d5a3000   MBAMSwissArm
fffff801`59cd0000 fffff801`59ce1000   hidusb.sys
fffff801`59cf0000 fffff801`59cfc000   MTConfig.sys
fffff801`5d4d0000 fffff801`5d4e1000   vwifimp.sys
fffff801`5aa20000 fffff801`5aa33000   mwac.sys
fffff801`5aa40000 fffff801`5aa73000   MBAMSwissArm
fffff801`5d560000 fffff801`5d567000   ActiveHealth
fffff801`5d550000 fffff801`5d55c000   MSPQM.sys
fffff801`5a9c0000 fffff801`5a9cc000   MSPQM.sys
fffff801`5a9f0000 fffff801`5aa12000   WdNisDrv.sys
fffff801`593d0000 fffff801`593df000   dump_storpor
fffff801`58600000 fffff801`5861f000   dump_amdsata

bru · 24 Mar 2016

BorisTheAnimal said:

Hello Bruce, sorry for the late reply.

No worries. We have a seven hour time difference. I appreciate your help with this.

BorisTheAnimal said:

Well if it was Malwarebytes that caused the crash then there should have been a driver from MB in the dump but considering that the BSOD you got was a DRIVER_POWER_STATE_FAILURE, maybe when running MB it would scan the driver of the WiFi adapter and cause this crash.

This is the closest I've come to find your driver:
RTL8188CE

Cheers, Boris :)

I did some more troubleshooting and while its possible it is related to Malwarebytes I wonder if it could be related to Automatic Maintenance. Here is what I did: I ran a MBAM scan and when finished I manually put the computer to sleep and all was fine. I then ran another MBAM scan but this time let the computer sit and go to sleep on its own. As it was trying to sleep it crashed. As it has done before. Event details showed all three typical messages as I have previously seen. When I checked Security and Maintenance I noticed that Automatic Maintenance ran four minutes before Windows was not properly shutdown/stopped working/shut down unexpectedly. So the maintenance ran after the MBAM scan was finished and before the computer attempted to sleep. Perhaps this was a coincidence.

I believe there is a new Dump File related to the latest crash and I have attached the .zip file from the tool.

Since I am not reading these files I would ask when you see "DRIVER_POWER_STATE FAILURE" does that specifically refer to the Wi-Fi driver? I have seen some dump files where it looks as if the driver is identified by name (e.g. Wi-Fi, Audio etc.), perhaps you didn't mention it.

bru · 24 Mar 2016

axe0 said:

There is only a sudden shutdown event logged, any bugchecks haven't been saved at all.

Boris and mine thoughts about that are opposite, I wouldn't recommend it.

Possibly, unfortunately I can't look up the dates of the drivers so I have a few straight suggestions.
1. Remove Malwarebytes and reinstall it, https://support.malwarebytes.org/cus...5311?b_id=6438
2. Update Malwarebytes manually, download from Malwarebytes | Free Anti-Malware & Internet Security Software and install overtop to see if that helps. Installing overtop normally doesn't affect the program, but a reboot after overtop installation should fix problems that have occured due to overtop installation (a reboot is always recommended after overtop installation even if you didn't notice any problems). If you experience problems after reboot a removal and installation is required.

Thank you for your reply. I was responding to Boris when I saw it so some of my response to him may apply to your thoughts as well. In the code you posted (which I did not copy here) I see several instances of Malwarebytes, so is it your feeling that the crashes are related to the program somehow? That is what I am thinking although the Automatic Maintenance aspect I mentioned may be playing a part. I did attach a new .zip file in my reply above which I think has the latest dump file. Curious if you still see the same instances of Malwarebytes causing issues.

I do plan to uninstall and reinstall the program though I will say that after doing a Refresh where the OS was reinstalled I did have to reinstall Malwarebytes and it seemed to again cause the issue. Coincidentally or not there is a new version of MBAM available so I think I will install that version after I uninstall/clean out the current version. Its all curious to me as I have run MBAM for years on many different computers and never had an issue like this, if indeed it is causing the crashes.

My final question would be do you then not think it is related to the Wi-Fi driver? As I had mentioned I did update the driver and I still had the crash issue. This was before I Refreshed the computer. Since the Refresh I have not updated the driver yet. I appreciate your help with this.

axe0 · 24 Mar 2016

I see several instances of Malwarebytes, so is it your feeling that the crashes are related to the program somehow?

Possibly, can't say with much certainty but I believe so.

Curious if you still see the same instances of Malwarebytes causing issues.

The newest dump looks pretty much the same as the other, but less Malwarebytes drivers.

Coincidentally or not there is a new version of MBAM available so I think I will install that version after I uninstall/clean out the current version. Its all curious to me as I have run MBAM for years on many different computers and never had an issue like this, if indeed it is causing the crashes.

Many users expected a new release of MBAM for quite some time, including myself. I wouldn't call it coincidence.
Unfortunately such things can happen at anytime for no clear reason to the user, although Windows 10 is less than a year old thus still new, I don't think it is fair to compare other OS with Windows 10 due to their stability. I've had recently a BSOD, looked a bit like yours although the bugcheck was different and the why was of course also different, it blamed the network drivers but I decided to clean reinstall malwarebytes because I saw a few things about it. Since updating to the newest version I have not yet had any problems anywhere on my system.

My final question would be do you then not think it is related to the Wi-Fi driver?

I've often seen it happen that security programs are the root cause when network drivers are being marked as the cause.

bru · 24 Mar 2016

axe0 said:

Many users expected a new release of MBAM for quite some time, including myself. I wouldn't call it coincidence.
Unfortunately such things can happen at anytime for no clear reason to the user, although Windows 10 is less than a year old thus still new, I don't think it is fair to compare other OS with Windows 10 due to their stability. I've had recently a BSOD, looked a bit like yours although the bugcheck was different and the why was of course also different, it blamed the network drivers but I decided to clean reinstall malwarebytes because I saw a few things about it. Since updating to the newest version I have not yet had any problems anywhere on my system.

I've often seen it happen that security programs are the root cause when network drivers are being marked as the cause.

I was about to say this sounds promising when I realized that I am already running the new version of MBAM on this computer. Now I am really stumped. I did a Refresh of the OS and reinstalled the new version of MBAM and I still am having this issue.

axe0 · 25 Mar 2016

I then ran another MBAM scan but this time let the computer sit and go to sleep on its own.

Configure your settings to never go into sleep by itself, or don't scan your pc before it goes to sleep.

Let us know how it goes with either of them :)