Solved Bsod Stop:0x7e on shutdown

[Goldstein]

I just updated my some hardware(cpu, motherboard, ram) but had to format because I'm stupid... any who, I had to update my drivers (I'm really not sure if that's the cause) I also have the latest BIOS but whenever I shutdown I get a BSOD with stop 0x7e. So those are pretty much my circumstances and now for some useful stuff...

So in the attachments are my dump files and my exact specs.

Thankyou!​

 

[koolkat77]

Welcome to SevenForums,

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Is the new hardware compatible with each other?
Have you reinstalled the operating system after installing new hardware?

If not, you should do a clean install.

Coming to what caused your BSOD. It appears that Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card seems to be the cause.

[FONT="Courier New"][SIZE="3"]STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, [B]Hardware incompatibility[/B], Faulty system service, Memory, 3rd party remote control [/SIZE][/FONT]

[FONT="Courier New"][SIZE="3"]*** 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, fffff88004c80566, fffff880009e75a8, fffff880009e6e00}

Probably caused by : bcmwl664.sys ( bcmwl664+1c566 )

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

0: 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: fffff88004c80566, The address that the exception occurred at
Arg3: fffff880009e75a8, Exception Record Address
Arg4: fffff880009e6e00, 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+1c566
fffff880`04c80566 80791d00        cmp     byte ptr [rcx+1Dh],0

EXCEPTION_RECORD:  fffff880009e75a8 -- (.exr 0xfffff880009e75a8)
ExceptionAddress: fffff88004c80566 (bcmwl664+0x000000000001c566)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000000001d
Attempt to read from address 000000000000001d

CONTEXT:  fffff880009e6e00 -- (.cxr 0xfffff880009e6e00)
rax=fffffa800857b2c0 rbx=fffffa8008108000 rcx=0000000000000000
rdx=fffff88000fb4020 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c80566 rsp=fffff880009e77e0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000004 r13=fffff88001525110
r14=fffff880015184e0 r15=0000000000000004
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
bcmwl664+0x1c566:
fffff880`04c80566 80791d00        cmp     byte ptr [rcx+1Dh],0 ds:002b:00000000`0000001d=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  000000000000001d

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eff100
GetUlongFromAddress: unable to read from fffff80002eff1c0
 000000000000001d Nonpaged pool

FOLLOWUP_IP: 
bcmwl664+1c566
fffff880`04c80566 80791d00        cmp     byte ptr [rcx+1Dh],0

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88004c80566

STACK_TEXT:  
fffff880`009e77e0 00000000`00000000 : fffff880`013e8972 fffff880`00000004 fffffa80`0717c430 00000000`00000000 : bcmwl664+0x1c566


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  bcmwl664+1c566

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME:  bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fac6851

STACK_COMMAND:  .cxr 0xfffff880009e6e00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_bcmwl664+1c566

BUCKET_ID:  X64_0x7E_bcmwl664+1c566

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

0: kd> lmvm bcmwl664
start             end                 module name
fffff880`04c64000 fffff880`051ff000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Fri May 11 07:16:01 2012 (4FAC6851)
    CheckSum:         0059DF1A
    ImageSize:        0059B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4[/SIZE][/FONT]

Try re-seating this device. Update its drivers or reinstall existing ones.

Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to "Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card" and reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.

:ar: http://www.sevenforums.com/tutorial...over-files-after-uninstalling.html#post726559

Links:

1. Driver Reference Table - bcmwl664.sys
2. Driver Reference Table - BCMWL664.SYS

See if turning on/off USB Selective Suspense helps:

• http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html

Perform a System File Check:

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Disk Check on your hard drive for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Hope this helps for now.

 

[Goldstein]

Thank you very much!

I am now able to shutdown properly. On another note, I did try all your methods and restart but I came to
just rolling back my network cards in the device manager which I think would have done the same thing but much faster. Lastly, your reply is still useful, without it I would probably never determined the problem source. So once again, thank you very much!

 

[koolkat77]

You're welcome.
Let us know how things are after a week.

 

[koolkat77]

Any BSOD-s this week?