-=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
- From: "tempting2taanzaa" <tempting2taanzaa@xxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Mon, 5 Jan 2009 10:48:57 -0600
Hi G:
Ok, I have looked in event viewer and here is the report (I am almost sure
this is the one after the BSOD though there are a couple more red "x's"
listed under the system area:
Type: Error Date: 1/4/2009 Time: 8:29:23 PM Source:
System Error Category: (102)
Event: 1003 User: N/A Computer: TOSHIBA
Description:
Error code 0000009c, parameter 1 00000000, parameter 2 8054e0f0, parameter 3
a2000000, parameter 4 84010400.
Data: Bytes
0000: 53 79 73 74 65 6d 20 45
System E
0008: 72 72 6f 72 20 20 45 72 rror
Er
0010: 72 6f 72 20 63 6f 64 65 ror
code
0018: 20 30 30 30 30 30 30 39
00000009
0020: 63 20 20 50 61 72 61 6d c
Param
0028: 65 74 65 72 73 20 30 30
eters
0030: 30 30 30 30 30 30 2c 20
000000,
0038: 38 30 35 34 65 30 66 30
8054e0f0
0040: 2c 20 61 32 30 30 30 30 ,
a20000
0048: 30 30 2c 20 38 34 30 31 00,
8401
0050: 30 34 30 30 0400
Data: Words
0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303020 39303030
0020: 50202063 6d617261 72657465 30302073
0030: 30303030 202c3030 34353038 30663065
0040: 3261202c 30303030 202c3030 31303438
0050: 30303430
As I said before there are other red "x's" in the system area (I'll list
them, but from the descriptions some don't seem applicable):
Type: Error Date: 1/4/2009 Time: 9:02:25 PM Source:
Service Control Manager Category: None
Event: 7000 User: N/A Computer: TOSHIBA
Description:
The mrtRate service failed to start due to the following error: The system
cannot find the file specified.
Data: None
Type: Error Date: 1/4/2009 Time: 9:02:37 PM Source:
NetBT Category: None
Event: 4321 User: N/A Computer: TOSHIBA
Description:
The name "TOSHIBA :0" could not be registered on the Interface with IP
address 192.168.15.104. The machine with the IP address 192.168.15.102* did
not allow the name to be claimed by this machine.
*had my other laptop on at this time*
Data: Bytes
0000: 00 00 00 00 04 00 56 00
......V.
0008: 00 00 00 00 e1 10 00 c0
....a..A (both "a & A" are accented)
0010: 01 01 00 00 01 00 00 c0
.......A ("A" is accented)
0018: 00 00 00 00 00 00 00 00
........
0020: 00 00 00 00 00 00 00 00
........
Data: Words
0000: 00000000 00560004 00000000 c00010e1
0010: 00000101 c0000001 00000000 00000000
0020: 00000000 00000000
Today when I booted up:
Type: Error Date: 1/5/2009 Time: 9:32:57 AM Source:
Service Control Manager Category: None
Event: 7000 User: N/A Computer: TOSHIBA
Description:
The mrtRate service failed to start due to the following error: The system
cannot find the file specified.
Data: None
Type: Error Date: 1/5/2009 Time: 9:35:45 AM Source:
Server Category: None
Event: 2505 User: N/A Computer: TOSHIBA
Description:
The server could not bind to the transport
\Device\NetBT_Tcip_{6AAB2C41-1E1B-4FF6-8B71-4FA887996EBB} because another
computer* on the network has the same name. The server could not start.
*had my other laptop on*
Data: Bytes
0000: 34 00 00 00 4...
Data: Words
0000: 00000034
Type: Error Date: 1/5/2009 Time: 9:33:54 AM Source:
NetBT Category: None
Event: 4321 User: N/A Computer: TOSHIBA
Description:
The name "TOSHIBA :0" could not be registered on the Interface with IP
address 192.168.15.104. The machine with the IP address 192.168.15.102* did
not allow the name to be claimed by this machine.
*had my other laptop on*
Data: Bytes
0000: 00 00 00 00 04 00 56 00
......V.
0008: 00 00 00 00 e1 10 00 c0
....a..A (both "a & A" are accented)
0010: 01 01 00 00 01 00 00 c0
.......A ("A" accented)
0018: 00 00 00 00 00 00 00 00
........
0020: 00 00 00 00 00 00 00 00
........
Data: Words
0000: 00000000 00560004 00000000 c00010e1
0010: 00000101 c0000001 00000000 00000000
0020: 00000000 00000000
There were no application errors or Internet Explorer errors. There was a
security "Failure Audit" however.
Type: Failure Audit Date: 1/5/2009 Time: 9:33:52 AM
Source: Security Category: Policy Change
Event: 615 User: NETWORK SERVICE Computer: TOSHIBA
Description:
IPSec Services: IPSec Services failed to get the complete list of network
interfaces on the machine. This can be a potential security hazard to the
machine since some of the network interfaces may not get the protection as
desired by the applied IPSec filters. Please run IPSec monitor snap-in to
further diagnose the problem.
Data: None
This was only listed once. All of the other audits were successful.
I opened device manager and there were no yellow triangles or errors
reported there.
Sorry this post is so long.
*********************Reply Separator********************************
Subject: -=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
Date: Mon, 5 Jan 2009 00:11:04 -0500
From: Gman <gman.pctt@xxxxxxxxx>
This helps a TON, but also brings up a bunch of questions that I may not
quite have the proper words to ask, so bear with me here. lol
The error you have here is just another way of showing the BSOD error codes.
Specifically, it translates to,
STOP: MACHINE_CHECK_EXCEPTION
(which means you have a serious hardware issue)
0x0000009C (0x00000000, 0x8054E0F), 0xA2000000, 0x84010400)
The four codes in parenthesis are not quite as important as the one outside
of it, but that's good because the second one inside should never include a
')' in it. I suspect it should have even a '0', but I hesitate to go with a
suspicion when it comes to these things.
Problems like this are often very difficult to properly diagnose, so there's
a chance we may not get very far after possibly spending a lot of time on
this. Troubleshooting hardware issues can lead us through numerous
seemingly unrelated paths (drivers, excess heat, port connections, etc.).
I'm not trying to scare you with that. I'm just preparing you for what
could be the worst possible scenario. So, let's begin by ruling out some of
the basics.
The first thing I'd like you to do is to open up the Event Viewer and see if
you can locate this same error report in there. It will probably be listed
within the System area, but that's not a definite. To open it up, go to
Start > Run, type in 'eventvwr.msc' (without the quotes) and press Enter.
Once opened, click on the word System in the left pane to see all of the
recorded events within that category. The report you seek will have a red X
before it, but I can't help you with its full title since I have no record
of this particular BSOD. To see a full error report, just double click on
one of the lines to open up another window. Start at the top and work your
way downwards opening all of the ones with a red X If you do find it, the
separate window will allow you to Copy the full report so it can be pasted
into a reply to this email. If you don't find it within the System area,
check within the Application area. I'm asking for this info just in case
the full report with the correct code will lead us to a much faster solution
than manual troubleshooting.
Next, open up Device Manager (Start > Run > devmgmt.msc) and see if there
are any hardware devices that are not being recognized properly. Let me
know what you find.
I'd also like you to describe when/how this started. Were there ANY changes
(external hardware added, software added, settings changed, etc) made to the
system just before it started?
Happy Holidays,
Gman
"The only dumb questions are the ones we fail to ask"
---------------------------------------------------------------
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: