Re: [PCWorks] Dreaded Blue Screen on Shut Down
- From: "Clint Hamilton-PCWorks Admin-OrpheusComputing.com & ComputersCustomBuilt.com" <PCWorks@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: <pcworks@xxxxxxxxxxxxx>
- Date: Sat, 26 Jan 2008 01:27:31 -0600
I don't remember the whole threads on this, but I was sure at
one time at least someone mentioned safe mode. Yes, if it you
don't have it in safe mode then it's not hardware causing it.
F5 puts a PC in safe mode, so that's not it. F6 is what you
press just before the install when it asks about 3rd party
drivers, usually for controllers like non-native HD controllers
(VIA, Silicon Image, Promise, etc.), or SCSI cards. A PSU has
nothing to do with drivers. So it was no doubt the HD
controller on the mobo or controller card. These however can
be changed in Windows via the Device Manager, but you of course
have to know they are the culprit.
-Clint
God Bless
Clint Hamilton, Owner
http://www.OrpheusComputing.com
http://www.ComputersCustomBuilt.com
----- Original Message -----
From: "LarryB"
Just wanted to followup on this message as Wil, the gentleman
that is
working on my problem has told me that it is fixed.
I do not understand much about what he said was wrong but it
had to do
with reinstalling the OS Windows XP Pro on the new 80g HD and
the
drivers that are installed. He said that when you bootup
something about
hitting F6 for the drivers windows thinks I need and hitting F5
which
brings up a list of the actual driver I was using. I may not
have this
right so I hope it is making sense to someone out there.
He did say that you would not get the BSOD when in Safe Mode so
that
kind of told him a driver was the problem. He also said the
driver had
to do with the power supply or something that drove the MB.
That's the best I can do without making notes when he is
telling me all
this.
Hope this helps some one else someday.
LarryB
K & L Electronics
South Carolina
Clint Hamilton-PCWorks Admin-OrpheusComputing. com &
ComputersCustomBuilt. com wrote:
You never were able to find out anything from that Debug
program? Some time back when I was having BSOD's before the
mobo went bad, the Debug program actually told me what was
causing it, and it was a .sys file in Kaspersky. They've since
fixed that in a new version.
It's best just to reformat when it starts costing you money.
It's faster in the long run, and certainly cheaper.
(The footers Larry). ;-)
-Clint
----- Original Message -----
From: "LarryB"
Well, I met my match for sure. I was unable to fix this problem
so I
took it to someone that is professionally in the business. (by
the way
our last communique, he has less hair.)I'll let you know when
it is
fixed if ever.
I have checked many resources to no avail. Most say good luck
finding
the cause.
LarryB
K & L Electronics
South Carolina
Clint Hamilton-PCWorks Admin-OrpheusComputing. com &
ComputersCustomBuilt. com wrote:
Many people do, (I always do), and there's no easy solution
to
it. It can be software, or it can be hardware causing it.
The
only thing I can suggest is to install that Debugger from M$
and see what it says.
Go to the area like you're going to the Device Manager, but
instead click the "Advanced" tab, then under "Startup and
Recovery" click "Advanced Settings". Then under "System
Failure" check the first box, then in the drop-down I'd
suggest
trying the Kernel dump first. If that takes too long or
locks
up the PC, then select the "Small memory dump". This will
write the info into a file in that Minidump folder,
hopefully.
Then you can open that Debugger and load the .dmp file and
see
if it will tell you anything. Usually you can just drag the
dmp file to the program after you open it.
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
The dmp files are not always created on BSOD's while starting
or shutting down, so it may or may not create one.
In my case, I'm pretty sure my BSOD's are caused by a bad
motherboard.
-Clint
-----1st Original Message -----
From: "LarryB"
I get the blue screen on shut down with the following info.
IRQL_not_less_or_equal.
0x0000000A
(0x000000B0,0x00000002,0x00000000,0x804EA44F)
I have visited M$ and didn't learn much that was useful to
me.
I have installed a Kodak printer but removing it does not
solve
the
problem. It is a all in one type printer.
This is my home computer using XP Home and it is a Dell
laptop.
When this happens I have to hit the power button and hold it
to
turn it
off. I can then turn it back on with no problem and nothing
seems to be
wrong otherwise. I have checked for malware with spybot, AVG,
and
Spysweeper. Nothing unusual.
M$ says it could be a driver! Good how do you find the one
that
is the
culprit?
=========================
The list's FAQ's can be seen by sending an email to
PCWorks-request@xxxxxxxxxxxxx with FAQ in the subject line.
To unsubscribe, subscribe, set Digest or Vacation to on or off, go to
//www.freelists.org/list/pcworks . You can also send an email to
PCWorks-request@xxxxxxxxxxxxx with Unsubscribe in the subject line. Your
member list settings can be found at
//www.freelists.org/cgi-bin/lsg2.cgi/l=pcworks . Once logged in, you have
access to numerous other email options.
The list archives are located at //www.freelists.org/archives/pcworks/ .
All email posted to the list will be placed there in the event anyone needs to
look for previous posts.
Other related posts:
