-=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
- From: Gman <gman.pctt@xxxxxxxxx>
- To: <pctechtalk@xxxxxxxxxxxxx>
- Date: Mon, 5 Jan 2009 12:22:01 -0500
I appreciate these answers and I'm already aware that they started after SP3
was installed. That helps confirm that the fix I just sent should be the
one we need. If that fix works, my headache will have been worth it.
lol
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 12:07 PM
Subject: -=PCTechTalk=- Re: Windows XP BSOD When Attempting Wireless Network
>I did not include when these problems began. I noticed the BSOD's
>beginning
> just after installing SP3. I had BSOD when one of my memory sticks was
> bad,
> but I had replaced that long ago and had no more issues until SP3. I also
> lost the ability to standby/hibernate correctly (won't wake-up without a
> hard shut down) after installing SP3 (however, since the laptop is used so
> rarely used I shrugged my shoulders on this problem). I do notice that
> there is no listing for a hibernation sys file in the disc cleanup utility
> however.
>
> There were no hardware changes. The only software change was the
> installation of a new firewall. I changed from Kerio personal firewall to
> Comodo. I did not do any other manual settings changes (don't know about
> changes done by Windows update, Norton Live Update changes, or Comodo
> updates).
>
> I was actually not even going to try to track this problem down. I was
> just
> going to back up the few documents that I have then use the recovery disk
> and start from square one. All of the software that is installed is
> either
> freeware or I have a disk for. So, if this gives you too much of a
> headache
> (LOL) then I will just do a recovery. I even thought of uninstalling SP3,
> but heck if I do that and then reinstall it would there be any difference
> or
> would I be back to my original problem. I didn't know, so I was just
> going
> to start from scratch.
>
> Anyway, I will be awaiting your advice. Luckily, I have four days off to
> play with.
>
> Other than trying to repair the wireless network or disable the wireless
> adapter, I don't seem to have any BSOD's opening/closing programs,
> surfing,
> restarting, initial boot-up. I mentioned the hibernation/stand-by issue.
> Oh, those were manual changes I made. Since I am not able to recover from
> stand-by/hibernation, I did make power scheme changes from standby after
> x-amount of minutes to never shut off (applicable to monitor, hdd, etc).
>
> If you need more information I will do my best to answer any questions.
> ************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
> ---------------------------------------------------------------
>
---------------------------------------------------------------
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:
