Solved Daily BSOD - BCCode: 1000007e

[Seithes]

Hello,

I'm currently having some difficulties with my Lenovo Thinkpad x230 running Windows 7 Professional x64.

Generally when the error occurs, I am working in Android studio but I often have multiple tasks also running including a Chrome tab with YouTube playing music and Skype messenger.

I believe the most likely source is involving USBs as I have had a few issues with them stopping working occasionally (Causing me to swap ports to get functionality back)

Also related to the USB issue, I am often testing with Android mobile devices which have a tendency to disconnect and reconnect at the slightest touch. (Generally 2 devices connected)

The issue has only happened a few times but seems to be at least once per day since last week. No new hardware or updates as far as I am aware. I have found out this error tends to be associated with driver issues and I had came across a potential HotFix, but I am unsure if that applies to my issue.

Windows 7/Windows Server2008 R2 SP1 All (Global) x64 Fix367138

I attempted to gather data on the issue on Friday, If required I have available:
- SysnativeFileCollection report (Friday crash)
- Perfmon report (Friday crash)
- Memory.DMP (Today's only)
- Windows System Event Logs (Friday & Today)

I have attached the DM Logs as directed by the posting guide and the perfmon report only. Hopefully that will be sufficient to diagnose my issue, but please let me know if the other information would be useful.

Any help with this would be much appreciated, Thank you for taking the time to read my message.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80002EC12D0
BCP3: FFFFF880031E6BE8
BCP4: FFFFF880031E6440
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

 

[axe0]

Remove Avast and use Microsoft Security Essentials as alternative, see if that helps.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
[COLOR="Red"]Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code[/COLOR], but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: [COLOR="red"]ffffffff80000003, The exception code that was not handled[/COLOR]
Arg2: fffff80002e722d0, The address that the exception occurred at
Arg3: fffff880031fbbe8, Exception Record Address
Arg4: fffff880031fb440, Context Record Address


fffff880`03307198  fffff880`043c3866*** WARNING: Unable to verify timestamp for aswbidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for aswbidsdrivera.sys
 aswbidsdrivera+0x1c866
fffff880`033079e8  fffff880`03a68e75*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
 aswSP+0x2ae75

 

[Seithes]

Thanks for your reply Axe0, I have uninstalled Avast and installed MSE as you have suggested. Hopefully it works out, I'll post here again if the blue screen returns.

Any particular reason for suspecting Avast? I have been using it for several years and never had an issue with it before.

 

[axe0]

Avast drivers were flagged in all dumps.

aswSP.sys and aswbidsdrivera.sys are both Avast drivers. What I posted means that Avast is related to the BSODs, most likely the cause.

 

[Seithes]

Second day and no blue screens, since it was the Avast drivers which seem to be at fault I'll go ahead and mark this as solved now.

Thanks for your help and quick responses Axe0