BSOD On Startup and Shutdown, error 0x0000007E

DeathbyKimchi · 03 Apr 2014

Hi there. Had this computer for about a month and a half. For the past couple of weeks, I've been plagued with a BSOD every so often, mostly occurring either during startup or shutdown, as well as once while playing a game. As far as I know, all my drivers are updated. That said, I'm fairly newbish when it comes to the more technical aspects of computers, so who knows. My basic system specs are as follows:

CPU: Intel Core i7-4280K @3.70GHz
RAM: 16 GB
OS: Windows 7 Home Premium 64 bit
Harddrives: 256 GB SSD - ADATA SP900, 500 GB WD50, 3 TB Seagate external harddrive
Video Card: nVidia GeForce GTX 780
Network Adapter: ASUS PCE-AC68 802.11ac

Also attached the .zip file containing info collected via DM Log Collector. Any help to resolve the issue would be greatly appreciated. :]

Thanks

Arc · 03 Apr 2014

Hi DeathbyKimchi.

Try to update ASUS Utility\PCE-AC68 WLAN Card to version 2.0.8.4 from
ASUSTeK Computer Inc. -Support- Drivers and Download PCE-AC68

The BSODs are all pointing to it.

Let us know the results.
_____________________________________

Code:

*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880088c5661, fffff8800394d4d8, fffff8800394cd30}

Probably caused by : bcmwl664.sys ( bcmwl664+221661 )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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.
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, 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880088c5661, The address that the exception occurred at
Arg3: fffff8800394d4d8, Exception Record Address
Arg4: fffff8800394cd30, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
bcmwl664+221661
fffff880`088c5661 410fb64a10      movzx   ecx,byte ptr [r10+10h]

EXCEPTION_RECORD:  fffff8800394d4d8 -- (.exr 0xfffff8800394d4d8)
ExceptionAddress: fffff880088c5661 (bcmwl664+0x0000000000221661)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000007f8
Attempt to read from address 00000000000007f8

CONTEXT:  fffff8800394cd30 -- (.cxr 0xfffff8800394cd30;r)
rax=000000000000005e rbx=0000000000000004 rcx=000000000000002e
rdx=0000000000000000 rsi=fffffa80172e8010 rdi=0000000000000002
rip=fffff880088c5661 rsp=fffff8800394d718 rbp=0000000000000004
 r8=fffffa801758c03a  r9=0000000000000000 r10=00000000000007e8
r11=fffffa801758c03a r12=000000000000c000 r13=fffffa801758c04a
r14=0000000000000000 r15=0000000000000006
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
bcmwl664+0x221661:
fffff880`088c5661 410fb64a10      movzx   ecx,byte ptr [r10+10h] ds:002b:00000000`000007f8=??
Last set context:
rax=000000000000005e rbx=0000000000000004 rcx=000000000000002e
rdx=0000000000000000 rsi=fffffa80172e8010 rdi=0000000000000002
rip=fffff880088c5661 rsp=fffff8800394d718 rbp=0000000000000004
 r8=fffffa801758c03a  r9=0000000000000000 r10=00000000000007e8
r11=fffffa801758c03a r12=000000000000c000 r13=fffffa801758c04a
r14=0000000000000000 r15=0000000000000006
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
bcmwl664+0x221661:
fffff880`088c5661 410fb64a10      movzx   ecx,byte ptr [r10+10h] ds:002b:00000000`000007f8=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000007f8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ad100
GetUlongFromAddress: unable to read from fffff800032ad1c0
 00000000000007f8 Nonpaged pool

FOLLOWUP_IP: 
bcmwl664+221661
fffff880`088c5661 410fb64a10      movzx   ecx,byte ptr [r10+10h]

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88008710fca to fffff880088c5661

STACK_TEXT:  
fffff880`0394d718 fffff880`08710fca : 00000000`00000004 00000000`00000000 fffffa80`1758c03a fffffa80`169b7000 : bcmwl664+0x221661
fffff880`0394d720 00000000`00000004 : 00000000`00000000 fffffa80`1758c03a fffffa80`169b7000 00000006`00000004 : bcmwl664+0x6cfca
fffff880`0394d728 00000000`00000000 : fffffa80`1758c03a fffffa80`169b7000 00000006`00000004 fffff880`0394d838 : 0x4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bcmwl664+221661

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME:  bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  517b1abc

STACK_COMMAND:  .cxr 0xfffff8800394cd30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_bcmwl664+221661

BUCKET_ID:  X64_0x7E_bcmwl664+221661

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_bcmwl664+221661

FAILURE_ID_HASH:  {f1d4e58f-ad1c-c410-b8ea-417c9132ed87}

Followup: MachineOwner
---------

5: kd> lmvm bcmwl664
start             end                 module name
fffff880`086a4000 fffff880`08f4e000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Sat Apr 27 05:54:28 2013 (517B1ABC)
    CheckSum:         008A5E8B
    ImageSize:        008AA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

DeathbyKimchi · 04 Apr 2014

Alrighty, thanks for the info, Arc.

Just updated, so hopefully that'll solve the issue. Probably won't truly know until I go without a BSOD for a couple days or so. But I'll keep my fingers crossed. :] I'll most certainly keep you posted if any issues resurface. For now, thanks a lot for the help.

Cheers!

Arc · 04 Apr 2014

You are welcome. :)