ndis.sys BSOD Windows 7

Question

ndis.sys BSOD Windows 7

Anonymous

Hello, I am having a problem with windows 7 starter in which it's having a BSOD problem. I did get the same error in the past and what I did to fix it is that I did System Restore in Safe because I couldn't get to "Safe Mode with networking" or "Start Windows Normally". And yes, I did use Start Up repair in the past too but it didn't fix anything. It just made things worse. When ever I did something in my netbook, like move a file to another folder and restarted the netbook, a BSOD would appear! And that's why I started to use System Restore but now I am having the same problem and it doesn't seem to fix it permanently, just temporally. I don't have any malware so that's off the list. I have my windows updated(using "windows update") so that too is off the list. I haven't tried using error-checking because it takes forever to finish and I have used it in the past and still, it looks like it just fixes the problem temporally to. I have recently installed "Oracle VM VirtualBox 4.3.10" and maybe that could be the problem? Also, you may ask if I installed all the virtual drivers of the "Oracle VM VirtualBok 4.3.10" during the installation, then the answer is yes. I also have "VMware Player" just to let you know. I really need this fix because I don't want this error forever in netbook! So hope I gave enough information to see what solution you got for me. And here is what the BSOD says when it appeared:

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the stop message, disable the driver or check with the manufacture for driver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup options, and then select Safe Mode.

Technical information:

*** STOP: 0x0000007E (0xC0000005, 0x87C9088E,0x88A9FB4C,0x88A9F730)

*** ndis.sys. - Address 87C9088E base at 87C35000, Datestamp 5034f1da

Collecting data for crash dump ...

Intitializing disk for crash dump ...

Beginning dump of physical memory.

Dumping physical memory to disk: 100

Physical memory dump complete.

Contact your system admin or technical support group for further assistance.

Edit:

Oh wow! I just got to my normal desktop without using System Restore or Startup Repair. But still, can anyone please tell me what went wrong in my windows? I don't want this to happen again and I want to learn from this mistake and also help other people who has the same problem. :)

So what I did (and hope if this is the solution, if not please comment for the right and PERMANENT solution) is that in the start up, I press on the F2 key (to go to setup) and then I went to the "Boot" section. In there, there were 6 things that were under "Boot priority order" and I think that those 6 things were what started up when the computer starts up. So here was the order and the things that were in there:

HDDO : TOSHIBA MK3259GSXP
ATAPI CDROM :
USB FDD
Network Boot : Realtek PXE BO1 D00
USB HDD :
USB CDROM :

So what I did is that I moved #4 to be at #6 place. And then I "Save and Exit" and my netbook rebooted without a problem. I also investigated what a ndis.sys is and it is a windows system file and it has something to do with networking. So I guess the "Network Boot : Realtek PXE BO1 D00" had to load last because it cause a networking startup problem in my windows but that's just my theory. So please correct me if I am wrong please.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Windows7StarterFan

Thanks! Great job uploading these btw! These were all in agreement as to what driver was implicated in these crashes.

Debug session time: Sun Apr 20 14:51:32.719 2014 (UTC - 4:00)

System Uptime: 0 days 0:00:10.360

Loading Kernel Symbols

...............................................................

.........................................................

Loading User Symbols

Unable to load image \SystemRoot\system32\DRIVERS*bcmwl6.sys, Win32 error 0n2*

*** WARNING: Unable to verify timestamp for bcmwl6.sys

*** ERROR: Module load completed but symbols could not be loaded for bcmwl6.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 87ce188e, 88aa3b4c, 88aa3730}

Probably caused by : bcmwl6.sys ( bcmwl6+11668 )

Followup: MachineOwner

---------

3: 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: c0000005, The exception code that was not handled

Arg2: 87ce188e, The address that the exception occurred at

Arg3: 88aa3b4c, Exception Record Address

Arg4: 88aa3730, 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:

ndis!NdisMSynchronizeWithInterruptEx+8

87ce188e 80b88100000001 cmp byte ptr [eax+81h],1

EXCEPTION_RECORD: 88aa3b4c -- (.exr 0xffffffff88aa3b4c)

ExceptionAddress: 87ce188e (ndis!NdisMSynchronizeWithInterruptEx+0x00000008)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 00000000

Parameter[1]: 00000081

Attempt to read from address 00000081

CONTEXT: 88aa3730 -- (.cxr 0xffffffff88aa3730)

eax=00000000 ebx=00000000 ecx=88aa3c2c edx=8aaefa00 esi=8aa27000 edi=00000000

eip=87ce188e esp=88aa3c14 ebp=88aa3c14 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

ndis!NdisMSynchronizeWithInterruptEx+0x8:

87ce188e 80b88100000001 cmp byte ptr [eax+81h],1 ds:0023:00000081=??

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: 00000000

EXCEPTION_PARAMETER2: 00000081

READ_ADDRESS: GetPointerFromAddress: unable to read from 82f6f84c

Unable to read MiSystemVaType memory at 82f4ee20

00000081

FOLLOWUP_IP:

bcmwl6+11668

8c628668 ?? ???

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 8c628668 to 87ce188e

STACK_TEXT:

88aa3c14 8c628668 00000000 00000000 8c62861c ndis!NdisMSynchronizeWithInterruptEx+0x8

WARNING: Stack unwind information not available. Following frames may be wrong.

88aa3c34 8c629bd2 8aa27000 00000000 8aa27000 bcmwl6+0x11668

88aa3c48 8c629c03 8aa27000 8aa2a008 88aa3c70 bcmwl6+0x12bd2

88aa3c58 8c65756e 8aa27000 00000000 8aa2a008 bcmwl6+0x12c03

88aa3c70 8c628536 8aa2a008 88aa3c8c 8c643be4 bcmwl6+0x4056e

88aa3c7c 8c643be4 8aa27000 e0e027d8 88aa3c9c bcmwl6+0x11536

88aa3c8c 8c655a04 8aa274b8 8aa2a008 88aa3cac bcmwl6+0x2cbe4

88aa3c9c 8c655a98 8aa2a008 8aa27000 88aa3cc4 bcmwl6+0x3ea04

88aa3cac 8c628a33 8aa2a008 8abbf128 8aa27000 bcmwl6+0x3ea98

88aa3cc4 8c63365e 8aa274b8 8abc1120 8a83b028 bcmwl6+0x11a33

88aa3cdc 87c872d6 8abbf128 8abc0068 88aa3d00 bcmwl6+0x1c65e

88aa3cec 8301a625 8a83b028 8abc0068 847924c0 ndis!ndisDispatchIoWorkItem+0xf

88aa3d00 82e8314b 8abc1120 00000000 847924c0 nt!IopProcessWorkItem+0x23

88aa3d50 8300f13d 00000000 9ed4e3de 00000000 nt!ExpWorkerThread+0x10d

88aa3d90 82eb6559 82e8303e 00000000 00000000 nt!PspSystemThreadStartup+0x9e

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: bcmwl6+11668

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bcmwl6

IMAGE_NAME: bcmwl6.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ea8c599

STACK_COMMAND: .cxr 0xffffffff88aa3730 ; kb

FAILURE_BUCKET_ID: 0x7E_bcmwl6+11668

BUCKET_ID: 0x7E_bcmwl6+11668

Followup: MachineOwner

---------

3: kd> lmvm bcmwl6

start end module name

8c617000 8ca2c000 bcmwl6 T (no symbols)

Loaded symbol image file: bcmwl6.sys

Image path: \SystemRoot\system32\DRIVERS\bcmwl6.sys

Image name: bcmwl6.sys

Timestamp: Wed Oct 26 22:44:41 2011 (4EA8C599)

CheckSum: 00420B96

ImageSize: 00415000

Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update to the newest version at your computer or motherboard manufacturer's website.

bcmwl6.sys

Driver Description: Broadcom 802.11g Network Adapter driver

http://www.broadcom.com/support/ethernet_nic/

0 comments

7 additional answers

Answer 1

Oh, so your saying that I go and update to the latest Broadcom network adapter driver so my BSOD goes away(even if I haven't seen one today)? I'm I correct? Oh, and I have a Gateway netbook with windows 7 starter just to let you know.

The crash dumps indicate that there is a problem with bcmwl6.sys, and that is your Broadcom 802.11g Network Adapter driver. the decision on what to do is entirely up to you. I just ran the dumps through the debugger.

Answer 2

Anonymous

Oh, so your saying that I go and update to the latest Broadcom network adapter driver so my BSOD goes away(even if I haven't seen one today)? I'm I correct? Oh, and I have a Gateway netbook with windows 7 starter just to let you know.

0 comments

Answer 3

Anonymous

I have no idea what I am doing but here are the minidumps:

https://onedrive.live.com/redir?resid=11FEE6842B6018B8%21116

I hope I am doing this right...

0 comments

Answer 4

Windows7StarterFan.

Please follow the instructions in the link below, to post your crash dumps for analysis.

Blue Screen of Death (BSOD) Created by****ZigZag3143 (MS - MVP

http://answers.microsoft.com/en-us/windows/wiki/windows_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

Share via

ndis.sys BSOD Windows 7

7 additional answers