[pcductape] Re: STOP error - Blue Screen

  • From: "Lori Gebhart" <ggebhart@xxxxxxxxxx>
  • To: <pcductape@xxxxxxxxxxxxx>
  • Date: Thu, 23 Dec 2004 09:38:18 -0500

I agree, excellent troubleshooting steps!
 
Lori

-----Original Message-----
From: pcductape-bounce@xxxxxxxxxxxxx
[mailto:pcductape-bounce@xxxxxxxxxxxxx] On Behalf Of bill wingler
Sent: Thursday, December 23, 2004 4:27 AM
To: pcductape@xxxxxxxxxxxxx
Subject: [pcductape] Re: STOP error - Blue Screen


Excellent Post.....   Bill
 
 

----- Original Message ----- 
From: HYPERLINK "mailto:richard_crumlich@xxxxxxxxxxx"Richard_Crumlich 
To: HYPERLINK "mailto:pcductape@xxxxxxxxxxxxx"pcductape@xxxxxxxxxxxxx
Sent: 12/23/2004 3:01:15 AM 
Subject: [pcductape] Re: STOP error - Blue Screen


My 2 cents.... and may have nothing what so ever to do with the
discussion but... this is what I have taught over 100 computer, radar,
and electronics techs to do first rather than jumping around... so far
it has worked almost all the time...
 
Quck Fault Analysis Checklist.
 
1) Reseat all cards, memory, and processor, lightly press on Bios and
any other socketed chips to reseat them in their sockets, reset Bios to
failsafe mode (lowest performance) , reboot... 
     BOOT YES -----------------Check OS...
     BOOT NO -------------------goto 2
 
2) Remove all cards except video unless it is on board.. remove all
repeat ALL drive cables from controller, remove all repeat ALL power
cables from drives..
     SYSTEM POST NO ------  Check PS with known good PS and narrow it to
PS or Motherboard... GOTO 4
     SYSTEM POST YES ----  Goto 3
 
3) Add drives ONE AT A TIME to include power cables... if all this is a
pass... add cards ONE AT A TIME ... This should narrow the problem down.
   If any unit fails.. check against in different slots or different
positions on ribbon cables.... 
 
4) PS good system still no POST... check Memory with Known good
memory... check Processor with known good processor... or check those
components on a known good MB
 
 
Don't assume that cables.. Molex (power) connectors, PCI / ISA slots on
MB, or controllers on MB  don't go bad... narrow it down to deal with
what is the problem.
 
I have seen many a system not even start the POST because floppy drives
or other devices failed.. putting to heavy a drain on the PS... If the
power supply does not present an adequate signal on the POWER GOOD
line... the MB will not even attempt to boot. hence removing all power
cables and cards...
 
XP, 2000, ME, and newer *nix OS's  all have the capability of telling a
Card and the MB what resources to use where... hence.. remove all
peripheral units and reset BIOS.. 
 
On a MB if all other checks make it appear the MB is at fault.. remove
all external wiring.. IE power light HD activity light etc.. leave MB
main Molex and supplemental on newer processors / MB ...connected...
jump power switch pins with a paper clip etc... if it posts.. reconnect
one at a time.. most indicators are LED's they can short out... again
power drain means no power good signal... no POST no Boot ...
 
 
All this can be completed in 15 minutes.. and leaves nothing to
chance... and often step 1 Solves it all... chip creep is still alive
and kicking....
 
 
Rick
 
 
 
 
 
 
----- Original Message ----- 
From: HYPERLINK "mailto:trapper@xxxxxxx"trapper 
To: HYPERLINK "mailto:pcductape@xxxxxxxxxxxxx"pcductape@xxxxxxxxxxxxx 
Sent: Wednesday, December 22, 2004 9:43 PM
Subject: [pcductape] Re: STOP error - Blue Screen

I give up you guys!
I have explained this over and over..!


Bob Noble wrote: 

Hi Trapper, 
The part you missed, besides the part that he couldn't boot was he
couldn't use his a: drive or his cd drive. So, how could he fix
anything? 

Bob Noble 
HYPERLINK "http://www.sonic.net/bnoble"www.sonic.net/bnoble 
----- Original Message ----- From: "trapper" HYPERLINK
"mailto:trapper@xxxxxxx"";><trapper@xxxxxxx> 
To: HYPERLINK "mailto:pcductape@xxxxxxxxxxxxx";<pcductape@xxxxxxxxxxxxx> 
Sent: Wednesday, December 22, 2004 12:13 PM 
Subject: [pcductape] Re: STOP error - Blue Screen 




We are going to get Carl so confused..! 
Trust me I am not confused..I know precisely what it is I am talking 
about and his repairman and the error msg proves it..:-) 
His computer is now working because what was needed was done. 
He had two distinct problems going on..Windows was shot,and he could not




To unsubscribe from this list send an email to 
HYPERLINK
"mailto:pcductape-request@xxxxxxxxxxxxx"pcductape-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field 
OR by logging into the Web interface.  
To view the message archives simply go to: HYPERLINK
"http://www.freelists.org/archives/pcductape/"http://www.freelists.org/a
rchives/pcductape/ 
Take a look at our homepage at HYPERLINK
"http://pc-ductape.home.comcast.net/"http://pc-ductape.home.comcast.net/






   _____  




Internal Virus Database is out-of-date.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.5.3 - Release Date: 12/14/2004



---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.822 / Virus Database: 560 - Release Date: 12/22/2004





---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.822 / Virus Database: 560 - Release Date: 12/22/2004
 

Other related posts: