-=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
- From: Gman <gman.pctt@xxxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Tue, 6 Jan 2009 00:06:24 -0500
Well done! I NEVER ask anyone to go through that process but it was
certainly the right thing to do in this case.
Everything in the report points right back at the wireless adapter as the
full cause of the problem.
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_WPC54Gv3+b914
At issue here is whether it's an actual hardware failure or a driver issue.
So, I'm going to suggest seeing if there's a more recent driver for this
device. If there is, download and install it to see if that clears things
up. If not, the adapter is probably beyond hope. If it's still under
warranty, return it for replacement. If it's not, ...
As always, let me know your results.
Happy Holidays,
Gman
"The only dumb questions are the ones we fail to ask"
----- Original Message -----
From: "tempting2taanzaa" <tempting2taanzaa@xxxxxxxx>
To: <pctechtalk@xxxxxxxxxxxxx>
Sent: Monday, January 05, 2009 7:18 PM
Subject: -=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
> Hi G:
>
> I just downloaded a debugging tool from MS and used the information from
> the
> dump file. I did not know whether this report would help or not:
>
>
> Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c)
> Microsoft Corporation. All rights reserved.
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini010509-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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by:
> 2600.xpsp_sp3_gdr.080814-1236 Machine Name:
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0 Debug session
> time:
> Mon Jan 5 16:21:43.236 2009 (GMT-6) System Uptime: 0 days 0:04:14.806
> Loading Kernel Symbols
> ...............................................................
> ................................................................
> ..
> Loading User Symbols
> Loading unloaded module list
> ..............
> ERROR: FindPlugIns 8007007b
> ****************************************************************************
> ***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ****************************************************************************
> ***
> Use !analyze -v to get detailed debugging information.
> BugCheck 9C, {0, 8054e0f0, a2000000, 84010400} Unable to load image
> WPC54Gv3.SYS, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for WPC54Gv3.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> WPC54Gv3.SYS Probably caused by : WPC54Gv3.SYS ( WPC54Gv3+b914 )
> Followup: MachineOwner
> ---------
> kd> !analyze -v
> ERROR: FindPlugIns 8007007b
> ****************************************************************************
> ***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ****************************************************************************
> ***
> MACHINE_CHECK_EXCEPTION (9c)
> A fatal Machine Check Exception has occurred.
> KeBugCheckEx parameters;
> x86 Processors
> If the processor has ONLY MCE feature available (For example Intel
> Pentium), the parameters are:
> 1 - Low 32 bits of P5_MC_TYPE MSR
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of P5_MC_ADDR MSR
> 4 - Low 32 bits of P5_MC_ADDR MSR
> If the processor also has MCA feature available (For example Intel
> Pentium Pro), the parameters are:
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> IA64 Processors
> 1 - Bugcheck Type
> 1 - MCA_ASSERT
> 2 - MCA_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
> processing
> MCA.
> 3 - MCA_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing MCA.
> 4 - MCA_FATAL
> FW reported a fatal MCA.
> 5 - MCA_NONFATAL
> SAL reported a recoverable MCA and we don't support
> currently
> support recovery or SAL generated an MCA and then couldn't
> produce an error record.
> 0xB - INIT_ASSERT
> 0xC - INIT_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
> processing INIT event.
> 0xD - INIT_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing INIT event.
> 0xE - INIT_FATAL
> Not used.
> 2 - Address of log
> 3 - Size of log
> 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
> AMD64 Processors
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> Arguments:
> Arg1: 00000000
> Arg2: 8054e0f0
> Arg3: a2000000
> Arg4: 84010400
> Debugging Details:
> ------------------
> NOTE: This is a hardware error. This error was reported by the CPU
> via Interrupt 18. This analysis will provide more information about
> the specific error. Please contact the manufacturer for additional
> information about this error and troubleshooting assistance.
> This error is documented in the following publication:
> - IA-32 Intel(r) Architecture Software Developer's Manual
> Volume 3: System Programming Guide
> Bit Mask:
> MA Model Specific MCA
> O ID Other Information Error Code Error Code
> VV SDP ___________|____________ _______|_______ _______|______
> AEUECRC| | | |
> LRCNVVC| | | |
> ^^^^^^^| | | |
> 6 5 4 3 2 1
> 3210987654321098765432109876543210987654321098765432109876543210
> ----------------------------------------------------------------
> 1010000111111111111111111111111110000100000000010000010000000000
>
> VAL - MCi_STATUS register is valid
> Indicates that the information contained within the IA32_MCi_STATUS
> register is valid. When this flag is set, the processor follows
> the
> rules given for the OVER flag in the IA32_MCi_STATUS register when
> overwriting previously valid entries. The processor sets the VAL
> flag and software is responsible for clearing it.
> UC - Error Uncorrected
> Indicates that the processor did not or was not able to correct the
> error condition. When clear, this flag indicates that the
> processor
> was able to correct the error condition.
> INTTIMERERR - INTERNAL TIMER ERROR
>
> Concatenated Error Code:
> --------------------------
> _VAL_UC_INTTIMERERR
> This error code can be reported back to the manufacturer.
> They may be able to provide additional information based upon
> this error. All questions regarding STOP 0x9C should be
> directed to the hardware manufacturer.
> BUGCHECK_STR: 0x9C_GenuineIntel
> CUSTOMER_CRASH_COUNT: 1
> DEFAULT_BUCKET_ID: DRIVER_FAULT
> PROCESS_NAME: System
> LAST_CONTROL_TRANSFER: from 806f1fab to 80533806
> SYMBOL_ON_RAW_STACK: 1
> STACK_ADDR_RAW_STACK_SYMBOL: ffffffff8054e17c
> STACK_COMMAND: dds 8054E17C-0x20 ; kb
> STACK_TEXT:
> 8054e15c 00000000
> 8054e160 f7ad5e00
> 8054e164 00000000
> 8054e168 f7ad5de8
> 8054e16c 00000000
> 8054e170 00200283
> 8054e174 00000000
> 8054e178 f7374914 WPC54Gv3+0xb914
> 8054e17c 00000000
> 8054e180 00000000
> 8054e184 00000000
> 8054e188 0032243a
> 8054e18c 00000000
> 8054e190 00000000
> 8054e194 00000000
> 8054e198 00000000
> 8054e19c 00000000
> 8054e1a0 00000000
> 8054e1a4 00000000
> 8054e1a8 00000000
> 8054e1ac 00000000
> 8054e1b0 00000000
> 8054e1b4 00000000
> 8054e1b8 00000000
> 8054e1bc 00000000
> 8054e1c0 00000000
> 8054e1c4 00000000
> 8054e1c8 00000000
> 8054e1cc 00000000
> 8054e1d0 00000000
> 8054e1d4 00000000
> 8054e1d8 00000000
>
> FOLLOWUP_IP:
> WPC54Gv3+b914
> f7374914 ?? ???
> SYMBOL_NAME: WPC54Gv3+b914
> FOLLOWUP_NAME: MachineOwner
> MODULE_NAME: WPC54Gv3
> IMAGE_NAME: WPC54Gv3.SYS
> DEBUG_FLR_IMAGE_TIMESTAMP: 456f795a
> FAILURE_BUCKET_ID: 0x9C_GenuineIntel_WPC54Gv3+b914
> BUCKET_ID: 0x9C_GenuineIntel_WPC54Gv3+b914
> Followup: MachineOwner
> ---------
>
>
>
>
>
> ---------------------------------------------------------------
> Please remember to trim your replies (including this sentence and
> everything below it) and adjust the subject line as necessary.
>
> To unsubscribe or change your email settings:
> //www.freelists.org/webpage/pctechtalk
>
> To access our Archives:
> http://groups.yahoo.com/group/PCTechTalk/messages/
> //www.freelists.org/archives/pctechtalk/
>
> To contact only the PCTT Mod Squad, write to:
> pctechtalk-moderators@xxxxxxxxxxxxx
>
> To join the PCTableTalk off-topic group, send a blank email to:
> pctabletalk+subscribe@xxxxxxxxxxxxxxxx
> ---------------------------------------------------------------
>
---------------------------------------------------------------
Please remember to trim your replies (including this sentence and everything
below it) and adjust the subject line as necessary.
To unsubscribe or change your email settings:
//www.freelists.org/webpage/pctechtalk
To access our Archives:
http://groups.yahoo.com/group/PCTechTalk/messages/
//www.freelists.org/archives/pctechtalk/
To contact only the PCTT Mod Squad, write to:
pctechtalk-moderators@xxxxxxxxxxxxx
To join the PCTableTalk off-topic group, send a blank email to:
pctabletalk+subscribe@xxxxxxxxxxxxxxxx
---------------------------------------------------------------
Other related posts:
