[Mike8888]

For the past few weeks my Dell E1505 has been getting blue screens when going to sleep/shutting down. The error:

DRIVER_POWER_STATE_FAILURE
0x0000009F (0x00000003, 0x84686700, 0x86171030, 0x87AA8C98) or...
" " " " 0x853E3700, 0x8617A3D0, 0x87313328) and so on...

I did a WinDbg on the crash dump memory file and got this...




Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0
Debug session time: Sat Jun 16 11:41:17.446 2007 (GMT-6)
System Uptime: 0 days 3:16:08.380
Loading Kernel Symbols
................................................................................
................................................................................
...............
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 8437ab98, 862f7030, 855dd270}

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




Probably caused by : bcmwl6.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8437ab98, Physical Device Object of the stack
Arg3: 862f7030, Functional Device Object of the stack
Arg4: 855dd270, The blocked IRP

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






DRVPOWERSTATE_SUBCODE: 3

DEVICE_OBJECT: 862f7030

DRIVER_OBJECT: 86299730

IMAGE_NAME: bcmwl6.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 458843cb

MODULE_NAME: bcmwl6

FAULTING_MODULE: 88e31000 bcmwl6

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: Idle

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81c4ada0 to 81cd85c9

STACK_TEXT:
81cf1b54 81c4ada0 0000009f 00000003 8437ab98 nt!KeBugCheckEx+0x1e
81cf1bb0 81c50441 81cf1cbc 81cf1c88 00000001 nt!PopCheckIrpWatchdog+0x165
81cf1bf0 81ca99d1 81d09fc0 00000000 8af9b9a1 nt!PopCheckForIdleness+0x33f
81cf1ce8 81ca9321 00000000 00000000 000b82c9 nt!KiTimerExpiration+0x498
81cf1d50 81c912ae 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
81cf1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_bcmwl6.sys

BUCKET_ID: 0x9F_IMAGE_bcmwl6.sys

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




Does anyone know how I can fix this? I have seen things like this when I search the internet for this but never for bcmwl6.sys. I have also tried about 2 or 3 updates from microsoft.com but none of them fixed the problem

[Advertisements]

I would check to be sure that your network drivers are up to date from dell. The bcmwl6.sys file from what it appears is a broadcom wireless lan driver. If you just go to dell, choose support, driver downloads and enter your service tag when prompted it will bring you to the correct page to get the drivers, etc.

[Dave Kruger]

I would check to be sure that your network drivers are up to date from dell. The bcmwl6.sys file from what it appears is a broadcom wireless lan driver. If you just go to dell, choose support, driver downloads and enter your service tag when prompted it will bring you to the correct page to get the drivers, etc.

[Mike8888]

alright i thought that did it because it didnt do it for a couple days, but then i got the error message again last night. so thats not the problem.

???

[Dave Kruger]

Hmmm....I thought for sure that would have taken care of it. If you would turn on tracing for your wireless networking, perhaps that will give some ideas of the cause. The following link gives instructions to enable the tracing:

http://technet2.micr...spx#BKMK_Sectn7

Hopefully that will give some ideas of the cause.

If the above link does not work, you may just have to click on Section 7 link...or could try the following:

http://technet2.micr...3.mspx?mfr=true

Edited by Dave Kruger, 09 November 2007 - 11:20 AM.

[Mike8888]

i actually enabled tracing by doing this

now im just waiting for another blue screen, and ill see what i find in the log traces.??

[Dave Kruger]

Yes, hopefully any info picked up by turning on the tracing will give a solution.

[Mike8888]

alright i got another blue screen, but what should i be trying to look for? a file in C:\Windows\tracing\wireless or something in Computer Management?

[Dave Kruger]

In computer management, open reliability and performance, then reports, system, wireless diag, and the wireless trace report should be showing up under that location somewhere. Post back any information that occurred around the time of the blue screen error, hopefully something will help resolve the problem.

[Mike8888]

Whenever I go to there, under Report Status it keeps saying "Collecting data..." and It never goes to the report, I can let it sit there for hours and it will still say "Collecting data...". I have no clue why its not doing it???

[Mike8888]

alright it doesnt stop freezing there anymore, but whenever i click on the wireless trace files, they dont open. When I hover over them, they say theyre .txt files but whenever i go to them in Explorer they are .etl files, and i cant open them. I try to look at them in notepad but i get a bunch of this ... so its a little hard to look at:)

???

[Dave Kruger]

Hi, sorry for my delay, I was out of town most of the weekend. With those etl file(s), if you open computer management right click on Event Viewer, then choose open saved log, you will be able to browse to the specific etl file, when you open it there, it should allow you to view the events stored in the trace file.

[Mike8888]

Well the trace files were kind of useless because all of them were restarted once the computer shut down, so the earliest traces I could get were from right when windows started after the the blue screen. But I did some searching through the Event Viewer and the only good information I found was in Event Viewer > Windows Logs > System. This is what I got right before it shut down/blue screened....




Edid checksum error (11/12/2007 4:31:07 PM - 11/12/2007 4:34:12 PM)

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00197DBD779C. The following error occurred:
The semaphore timeout period has expired.. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. (11/12/2007 4:35:02 PM)

Edid checksum error (11/12/2007 4:35:42 PM - 11/12/2007 4:35:45 PM)

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 00197DBD779C. The following error occurred:
The wait operation timed out.. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. (11/12/2007 4:35:57 PM)

Edid checksum error (11/12/2007 4:36:22 PM - 11/12/2007 4:36:23 PM)

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 00197DBD779C. The following error occurred:
The wait operation timed out.. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. (11/12/2007 4:41:38 PM)

[Dave Kruger]

HI, if you check on the driver properties for your wlan card, does it have the option selected for the system to be able to power off the wlan device, I think it is under power management tab? To see if it makes any difference, maybe try unchecking that option. It might not help, but will not hurt anything to try it.

I will try searching more regarding those errors to see if I can find anything. I probably will not post back until tomorrow evening some time.

[Mike8888]

I dont have a Power Management tab/option for my [Dell Wireless 1390] WLAN Card, but I do have that option for my [Broadcom 440x 10/100 Integrated Control] LAN Card. Should I uncheck that for my LAN Card, or do you think the problem has to be with my WLAN Card?

[Dave Kruger]

I dont have a Power Management tab/option for my [Dell Wireless 1390] WLAN Card, but I do have that option for my [Broadcom 440x 10/100 Integrated Control] LAN Card. Should I uncheck that for my LAN Card, or do you think the problem has to be with my WLAN Card?

Sure, just to see if it makes a difference. I think the error was something regarding the broadcom card, but I had thought the wireless were broadcom as well...sorry about that misunderstanding on my part. Is your broadcom card the one that has the MAC (physical address) of 00197DBD779C? If so, I am thinking that card or its driver etc might be causing the problem with it bluescreening.

If you are not sure how to check the mac address, the easiest way I do so, is start a command prompt, then type ipconfig /all just look for the Physical Address section for the broadcom card, you could send the output to a file if desired by using a command like:

ipconfig /all > %userprofile%\desktop\ipconfig.log

Which will output a file called ipconfig.log on your desktop with the output from ipconfig. or wherever else you may want to output the file to, or name etc. If you already know the MAC, or how to check it, just ignore the previous instructions for getting the info.

If the MAC for the broadcom card is the 00197DBD779C, I would check to be certain there are no available driver updates for that card as well from dell.