Laptop experience issues after reinstall graphics card driver

ubuysa

The BSOD Doctor
I would absolutely recommend a reinstall in this case because you can't be certain that the new motherboard is an exact replacement. Windows configures itself at install time for the hardware platform it finds itself going on, and the drivers (chipset in particular) are specific to the motherboard. Unless PCS can guarantee that the new motherboard is exactly the same I would definitely reinstall. TBH I would reinstall anyway just to be sure. The objective is a stable system and if you have to spend a day or two to be certain of getting a stable system then it's time well spent IMO.
 

SpyderTracks

We love you Ukraine
I would absolutely recommend a reinstall in this case because you can't be certain that the new motherboard is an exact replacement. Windows configures itself at install time for the hardware platform it finds itself going on, and the drivers (chipset in particular) are specific to the motherboard. Unless PCS can guarantee that the new motherboard is exactly the same I would definitely reinstall. TBH I would reinstall anyway just to be sure. The objective is a stable system and if you have to spend a day or two to be certain of getting a stable system then it's time well spent IMO.
I would agree, it’s a very good point, could be a new revision of the motherboard
 

Arcbleast

Active member
I did ask them to wipe both of my hard drives and get rid of the partitions (as there were a lot of partitions due to how windows now setup their recover drive these days)

I was planning to do a clean install any case.
 

ubuysa

The BSOD Doctor
The 'lots of partitions' is how a UEFI Windows install is setup. There will be three partitions and may even be four. This is a fact of life and you can't change it. The three non-Windows partitions are very small in any case.
 

Arcbleast

Active member
The 'lots of partitions' is how a UEFI Windows install is setup. There will be three partitions and may even be four. This is a fact of life and you can't change it. The three non-Windows partitions are very small in any case.
The only reason I have asked them to do it is because it was messing up the overprovision as well.

I had lost complete control of the overprovision as windows jammed a recovery driver in the middle of them and I will have to spend a long time to correct that, as I am not that good with windows command prompt (I kind of miss the good old mechanical hard drive for these situations)
 

ubuysa

The BSOD Doctor
I had lost complete control of the overprovision as windows jammed a recovery driver in the middle of them and I will have to spend a long time to correct that, as I am not that good with windows command prompt (I kind of miss the good old mechanical hard drive for these situations)
Why do you care? On an SSD you have no idea where the data is stored in any case. The partition view you see is just an illusion, it bears no relationship at all with where data is on the SSD. The kinds of data management we used to have to do on HDDs is not only not needed on an SSD, it's not even possible. The wear-levelling algorithms regularly move data around to even out the use - an SSD really is just a black hole.
 

Arcbleast

Active member
Why do you care? On an SSD you have no idea where the data is stored in any case. The partition view you see is just an illusion, it bears no relationship at all with where data is on the SSD. The kinds of data management we used to have to do on HDDs is not only not needed on an SSD, it's not even possible. The wear-levelling algorithms regularly move data around to even out the use - an SSD really is just a black hole.
Because it somehow made the Overprovision over 50%, and I cannot change the overprovision without removing the partitions
 

ubuysa

The BSOD Doctor
Are you creating an overprovision partition to reserve some SSD space that cannot be used? That's quite sensible, but you still don't care (or know) what SSD blocks are in that partition.

Overprovisioning is about reducing the used space on an SSD to give the wear levelling algorithm plenty of spare blocks to work with, but you still don't care where these blocks are.

What exactly is it that you're trying to achieve?
 

Arcbleast

Active member
I was not sure how, but what happened was, I have originally setup 30% of the block as overprovision.

When I did the reinstalling, I am unsure what happened, but the recover drive jammed into the other end and caused an increase in unallocated space that after another reinstall

I can't even understand the logic of how it happened, but I assume the unallocated spaces from the recover drive that was jammed on the other end is causing an issues and somehow, making new overprovision/unallocated space. Every time I reinstall, it somehow cause more mess on the other end and creating more unnecessary partitions and overprovisions. it eventually took about 50% of the hard drive up.

And because of the gap stuck between the two overprovision, I cannot change it the easy way using disk storage management tool and will have to go into command to sort the that partition out, if PCS did not clear that for me.
 
Top