About a month ago, I started to get random issues. First off, was Cortana and the Start Menu freezing. I reset windows which seemed to fix it.
Then, I got Blue Screens of Death, saying "critical process died". I used the DISM and system repair tools and that seemed to fix it.
Then, my computer wouldn't boot into the SSD at all, whether I put it in the normal bay or the ultrabay. It said "disk read error" on startup. It WOULD boot into the HDD in the Ultrabay OR the normal bay.
So, I bought a new SSD (Samsung EVO 860) even though Samsung Magician said the previous EVO 850 was fine and installed it. Then I reinstalled windows using a USB.
Along the way, I tested my memory, CPU, and both drives using the Lenovo diagnostics tool in my BIOS.
After all that....I am again getting "disk read error" on startup intermittently. I feel stumped.
The possibilities I see:
- My CPU is broken somehow?
- My chipset that reads SSDs is broken somehow?
- My RAM is messed up, and I need to use memtest to see it because the Lenovo tool wasn't good enough?
- ????
I would appreciate any insights or next steps I could take here.
My setup is Windows 10 home on a Lenovo T430s. Version 1803, OS build 17134.1
To summarize what I have done so far:
1. Reset Windows (complete, no programs or settings left behind)
2. Updated all Lenovo and Windows drivers and Windows updates
3. Bought a new SSD (Samsung 860 EVO vs previous 850 EVO)
4. Tried putting previous SSD in Ultrabay (didn't work)
5. Booted from backup HDD in ultrabay or normal bay (worked both times)
6. Used Samsung magician (said previous SSD was fine)
7. Run Lenovo memtest
I have an intel i5 3320m processor.
I have integrated graphics.
I have 16 gigs of DDR3 RAM.
Then, I got Blue Screens of Death, saying "critical process died". I used the DISM and system repair tools and that seemed to fix it.
Then, my computer wouldn't boot into the SSD at all, whether I put it in the normal bay or the ultrabay. It said "disk read error" on startup. It WOULD boot into the HDD in the Ultrabay OR the normal bay.
So, I bought a new SSD (Samsung EVO 860) even though Samsung Magician said the previous EVO 850 was fine and installed it. Then I reinstalled windows using a USB.
Along the way, I tested my memory, CPU, and both drives using the Lenovo diagnostics tool in my BIOS.
After all that....I am again getting "disk read error" on startup intermittently. I feel stumped.
The possibilities I see:
- My CPU is broken somehow?
- My chipset that reads SSDs is broken somehow?
- My RAM is messed up, and I need to use memtest to see it because the Lenovo tool wasn't good enough?
- ????
I would appreciate any insights or next steps I could take here.
My setup is Windows 10 home on a Lenovo T430s. Version 1803, OS build 17134.1
To summarize what I have done so far:
1. Reset Windows (complete, no programs or settings left behind)
2. Updated all Lenovo and Windows drivers and Windows updates
3. Bought a new SSD (Samsung 860 EVO vs previous 850 EVO)
4. Tried putting previous SSD in Ultrabay (didn't work)
5. Booted from backup HDD in ultrabay or normal bay (worked both times)
6. Used Samsung magician (said previous SSD was fine)
7. Run Lenovo memtest
I have an intel i5 3320m processor.
I have integrated graphics.
I have 16 gigs of DDR3 RAM.