BSOD when surfing Internet

exliko · 05 Apr 2010

I have a notebook with a brand emachine d720

At first, my notebook is installed with Windows 7 Ultimate 32bit and running normally for more than 2 months.

Calamity occurs 1 week ago, when I use my notebook to surfing the internet using wifi, it happens a BSOD. However, when I use my notebook to do ordinary tasks, such as, typing, listening to music, or play video, BSOD does not appear.

I tried to analyze Minidump and the problem is the file: ntkrnlpa.exe

I had to reinstall windows more than 5 times, but always BSOD appears when used to surf the internet.

First I thought it was caused by the Mozilla Firefox browser, but I've tried using Google Chrome / Opera and the result is the same, BSOD still appears.

Finally, I decided to reinstall my notebook with Windows 7 Ultimate 64bit, BSOD still appears but not as often as when the notebook is installed with Windows 7 Ultimate 32bit.

I tried to analyze the Minidump again, this time due to the file: ntoskrnl.exe

All my drivers are updated using the latest drivers, including the bios.
I've checked the RAM using Memtest for more than 4 hours and no errors.
I've checked the Harddrive and there is no badsector.

Please help me solve this problem
Here I attach some Minidump files when using Windows 7 Ultimate 32bit and 64bit

Thanks.

Jonathan_King · 05 Apr 2010

Welcome!

Looks like your network adapter driver bcmwl664.sys is causing the problem. I suggest going here and downloading the latest driver: eMachines Support: Drivers and Downloads

If the problems persist, look for other versions of that driver.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\040410-17752-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02861000 PsLoadedModuleList = 0xfffff800`02a9ee50
Debug session time: Sun Apr  4 11:37:35.135 2010 (GMT-4)
System Uptime: 0 days 0:12:39.056
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\bcmwl664.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl664.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl664.sys
Probably caused by : bcmwl664.sys ( bcmwl664+20531 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c908 -- (.exr 0xfffff80000b9c908)
ExceptionAddress: fffff88004624531 (bcmwl664+0x0000000000020531)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff80000b9c9b0 -- (.trap 0xfffff80000b9c9b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000001e rbx=0000000000000000 rcx=0000000000000058
rdx=00000000000006e4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004624531 rsp=fffff80000b9cb40 rbp=fffffa80017c2860
 r8=000000000000001e  r9=fffff6fd40026ba8 r10=fffffa8004d740a4
r11=fffffa8004d74788 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
bcmwl664+0x20531:
fffff880`04624531 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028cac2e to fffff800028d2ed0

STACK_TEXT:  
fffff800`00b9b9e8 fffff800`028cac2e : fffffa80`05d859c0 00000000`00000000 fffff800`00b9c160 fffff800`028ffe28 : nt!KeBugCheck
fffff800`00b9b9f0 fffff800`028f8bed : fffff800`02adfc24 fffff800`02a18a3c fffff800`02861000 fffff800`00b9c908 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9ba20 fffff800`02900250 : fffff800`02a20b5c fffff800`00b9ba98 fffff800`00b9c908 fffff800`02861000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9ba50 fffff800`0290d1b5 : fffff800`00b9c908 fffff800`00b9c160 fffff800`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff800`00b9c130 fffff800`028d2542 : fffff800`00b9c908 fffffa80`049f4000 fffff800`00b9c9b0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c7d0 fffff800`028d069f : fffff800`00b9c9b0 00000000`00000002 fffffa80`0541ff00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c9b0 fffff880`04624531 : fffffa80`049f4000 00000000`00000000 00000000`00000000 fffff800`00b9cc01 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9cb40 fffffa80`049f4000 : 00000000`00000000 00000000`00000000 fffff800`00b9cc01 00000000`00000000 : bcmwl664+0x20531
fffff800`00b9cb48 00000000`00000000 : 00000000`00000000 fffff800`00b9cc01 00000000`00000000 00000000`00000000 : 0xfffffa80`049f4000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bcmwl664+20531
fffff880`04624531 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  bcmwl664+20531

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl664

IMAGE_NAME:  bcmwl664.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49cc26b1

FAILURE_BUCKET_ID:  X64_0x1E_bcmwl664+20531

BUCKET_ID:  X64_0x1E_bcmwl664+20531

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

exliko · 05 Apr 2010

Thanks for the reply jonathan

I follow your suggestion to update the driver
But i still got the BSOD

Here the minidump file exactly after i update the driver

exliko · 06 Apr 2010

I give up

Finally, i reinstall the laptop with Vista Ultimate 32bit, and no BSOD comes out.

I still wonder, what's the problem with emachine d720 and Windows 7?

Jonathan_King · 06 Apr 2010

It's obviously a driver issue. You just need to play around with different drivers until you find one that works.

I suggest uninstalling the network driver completely in Windows 7. DO NOT download a new one, but use the default one Windows finds.

If that doesn't work, try installing the Vista drivers in compatibility mode.

exliko · 06 Apr 2010

Thank you Jonathan

I need this notebook, tomorrow. So I can check if there is a holiday or perhaps I'll check again when I've got a new notebook.

Sorry to bother you.
Thanks again.