Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Mighty Mouse <"squeak!"@thecheesefactory.com> Newsgroups: aus.computers Subject: Re: Why secure boot might be a good idea on your Linux machine Date: Thu, 19 Dec 2024 18:22:03 +1100 Lines: 65 Message-ID: References: <6748e05b@news.ausics.net> <674b78d6@news.ausics.net> <6758b09e@news.ausics.net> <6762262e@news.ausics.net> <67639438@news.ausics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net ExbowdVLa32hzRyvN+Lf5gPdMYAdadHDeHtPpAQDoq59c83bzz Cancel-Lock: sha1:V/R1dzFjbFFiB2M5qMM6fTbZt/4= sha256:CmhV0CmuuZHZml9kq0XQe9zMXXlqAB5aWV6OX1rKOdc= User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19 In-Reply-To: Xref: csiph.com aus.computers:71502 Mighty Mouse wrote: > Computer Nerd Kev wrote: >> Mighty Mouse <"squeak!"@thecheesefactory.com> wrote: >>> Computer Nerd Kev wrote: >>>> Mighty Mouse <"squeak!"@thecheesefactory.com> wrote: >>>>> Computer Nerd Kev wrote: >>>>>> Mighty Mouse <"squeak!"@thecheesefactory.com> wrote: >>>>> how can I check? and if there is one how do I get rid of it? >>>> I'm not sure if that can be done reliably, but I wouldn't jump to >>>> conclusions, especially if the trouble only started after you >>>> upgraded the CPU. >>>> >>>>> if it's not a boot virus what else could be the problem? >>>> Try running Memtest86 to check the RAM didn't get damaged >>>> accidentally. Linux probably won't be using as much RAM as Win10, >>>> so it may not have reached the memory region that's faulty. >>> I forgot that I had installed brand new ram, 16Gb 2x8. I ran memtest, >>> and the computer turned off after a few minutes. so in case that ram >>> was >>> faulty I put in 8 gig (2x4) of RAM, and set up a sceen to monitor >>> memtest. it ran for 21 minutes then the computer turned off again! you >>> can see here  https://auslink.info/video/memtest.mp4 . I'm sure this is >>> not supposed to happen. >> Yes, it's supposed to keep testing forever. That's certainly a >> hardware problem. >> >>> one other thing, the power supply in this PC failed, it was emitting a >>> 'hissing' noise and burnt smell, and I replaced it with a brand new >>> one. >>> it's only since then that these problems have started. could it be that >>> the motherboard is faulty? >> Yep, though it could be just one RAM slot so you might try moving >> the RAM sticks about. > > ok the RAM was running as dual channel in A2/B2 slots. I'll put it in A1/B1 and run memtest again. btw.. memtest is now in the BIOS as a boot option, and I can't see anyway to remove it.  ? > >>   It might also be that the CPU wasn't aligned >> quite right when you replaced it. > > no, i installed it very carefully. > >> >>>>> I've tried windows repair, and it didn't fix it. >>>> Did you try Safe Mode (assuming that's still around in Win10)? >>> no, but I will. stupid M$ has made it more difficult to get into safe >>> mode. it used to be that you just pressed F8 at boot. >> With Memtest86 failing then that means the problem isn't in Windows >> anyway. >> > > you're right. I will put the old CPU back, and reinstall windows. if > the problem is still extant I'll junk this motherboard. > -- Have a nice day!.. stay sane, be happy, and enjoy living.