Re: OT (BSOD ammusements)
Erin Drummond <[email protected]> Tue, 31 May 2011 19:47:56 +1200
| Newsgroups | gmane.org.user-groups.linux.hawkes-bay |
|---|---|
| Message-ID | <[email protected]> |
--===============0660609599== Content-Type: multipart/alternative; boundary=90e6ba5bbc6b4817af04a48d9fd1 --90e6ba5bbc6b4817af04a48d9fd1 Content-Type: text/plain; charset=ISO-8859-1 Sounds like the motherboard is faulty - its the only component left On May 31, 2011 5:09 PM, "Chris Morris" <[email protected]> wrote: > Win XPH pc turns up producing BSODs (stop errors) on top of the assorted > ransom-ware fake AV programs etc.. > Fun for all.. > > In my experience stop errors are usually caused by corrupted system > files and/or bad hard drive - also faulty ram can cause it too. > > So I do a boot from CD and repair - chkdsk /p and it finds no hard disk > errors. > > Maybe its the ransom-ware causing it, boot into safe mode and run USB > spyware scanner - halfway through scan BSOD > > Ok swap out the RAM for known good stuff - repeat above steps - BSOD > > hmmm sumbich! > > Chuck in another Hard Drive and start a winxph reinstall - halfway > through, you guessed it........BSOD > > x#$$^&=~!!! > > Ok - faulty PSU perhaps? > Change that out - still does it .... FFS! > > So we have changed out the HDD, RAM, PSU, DVDRW, and associated cables... > And we still get BSODs. > > The saga continues....... > > chris > > > > > _______________________________________________ > HBLUG mailing list > [email protected] > http://www.linux.net.nz/cgi-bin/mailman/listinfo/hblug --90e6ba5bbc6b4817af04a48d9fd1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <p>Sounds like the motherboard is faulty - its the only component left</p> <div class=3D"gmail_quote">On May 31, 2011 5:09 PM, "Chris Morris"= ; <<a href=3D"mailto:[email protected]">[email protected]<= /a>> wrote:<br type=3D"attribution">> Win XPH pc turns up producing B= SODs (stop errors) on top of the assorted <br> > ransom-ware fake AV programs etc..<br>> Fun for all..<br>> <br>&= gt; In my experience stop errors are usually caused by corrupted system <br= >> files and/or bad hard drive - also faulty ram can cause it too.<br> > <br>> So I do a boot from CD and repair - chkdsk /p and it finds no= hard disk <br>> errors.<br>> <br>> Maybe its the ransom-ware caus= ing it, boot into safe mode and run USB <br>> spyware scanner - halfway = through scan BSOD<br> > <br>> Ok swap out the RAM for known good stuff - repeat above steps= - BSOD<br>> <br>> hmmm sumbich!<br>> <br>> Chuck in another Ha= rd Drive and start a winxph reinstall - halfway <br>> through, you guess= ed it........BSOD<br> > <br>> x#$$^&=3D~!!!<br>> <br>> Ok - faulty PSU perhaps?<b= r>> Change that out - still does it .... FFS!<br>> <br>> So we hav= e changed out the HDD, RAM, PSU, DVDRW, and associated cables...<br>> An= d we still get BSODs.<br> > <br>> The saga continues.......<br>> <br>> chris<br>> <br>= > <br>> <br>> <br>> ___________________________________________= ____<br>> HBLUG mailing list<br>> <a href=3D"mailto:[email protected]= z">[email protected]</a><br> > <a href=3D"http://www.linux.net.nz/cgi-bin/mailman/listinfo/hblug">htt= p://www.linux.net.nz/cgi-bin/mailman/listinfo/hblug</a><br></div> --90e6ba5bbc6b4817af04a48d9fd1-- --===============0660609599== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ HBLUG mailing list [email protected] http://www.linux.net.nz/cgi-bin/mailman/listinfo/hblug --===============0660609599==--