Everything slow after BSODs

wongataa

agrinnall wrote: »

I have just run the Windows Memory Diagnostic Tool and it found no errors, so if that's an accurate diagnosis I presume the memory is OK.

I have had memory that passed diagnostic tests but still crashed the computer because it was faulty. Passing the test is not a guarantee it is OK.

agrinnall wrote: »

I've looked, and there are errors, but how do I know which are significant and which are irrelevant?

The system errors marked error or something equally strong are the ones to start with. You will find one that corresponds with the BSOD. Events of that type are the ones to investigate.

grumpycrab

After you've hoovered (carefully) for dust... time for a Windows10 refresh...search/Contana for "Reset this PC" and keep data/apps... (backup data first just in case).

agrinnall

Thanks to all, I'll be away for the next 2 days but when I'm back I'll try out the suggestions, making sure that my data is kept backed up just in case the SSD does give up the ghost. If anything works I'll report back in case it helps somebody else.

that

agrinnall wrote: »

I have just run the Windows Memory Diagnostic Tool and it found no errors, so if that's an accurate diagnosis I presume the memory is OK.

To be honest, think it is more a disk issue too, but in some case that 4GB memory dies, and becomes 2GB (or in my case 1G was 4+1) and it still passes the memory test .

You probably know what is in there, just make sure it is still all there,

If you have done all the other bits listed above, and still grasping at straws, then malware bytes.

debitcardmayhem

that wrote: »

To be honest, think it is more a disk issue too, but in some case that 4GB memory dies, and becomes 2GB (or in my case 1G was 4+1) and it still passes the memory test .

You probably know what is in there, just make sure it is still all there,

If you have done all the other bits listed above, and still grasping at straws, then malware bytes.

It has an SSD, he has run Malwarebytes, made sure all updates are up to date

esuhl

Sounds like it could be a driver issue to me...?


I was getting random BSODs years ago with XP. The only workaround was to uninstall the device drivers for the on-board firewall. (It was a weird motherboard!)


I'd check to see if you have the latest chipset (motherboard) drivers, BIOS, etc.

agrinnall

John_Gray wrote: »

Both the next two commands in a Command Prompt window probably "run as Administrator":

chkdsk c: /f /v /r
and allow it to reboot, when you have an hour or two (maybe!) to spare?

sfc /scannow
to see see if there are corrupt files?

I've now done both of these, neither reported any issue. I think the next thing will be to get the tiny screwdriver out and clean inside, then perhaps do the reset as grumpycrap suggests to see if that sorts things out.

debitcardmayhem

Did event viewer/blue screenview tell you what caused the BSODs? Oh and are they still occurring?

esuhl

And did you check you have the latest drivers installed? I think these are the ones to have a look at:


https://pcsupport.lenovo.com/gb/en/products/laptops-and-netbooks/yoga-series/yoga-2-pro-lenovo/downloads

agrinnall

esuhl wrote: »

And did you check you have the latest drivers installed? I think these are the ones to have a look at:


https://pcsupport.lenovo.com/gb/en/products/laptops-and-netbooks/yoga-series/yoga-2-pro-lenovo/downloads

I haven't yet, mainly because I read somewhere recently that updating the bios may cause more problems than it fixes - but I'll keep it in reserve if the other actions that don't involve replacing components don't work. Thanks for the link.