how to get a windows 7 64 bit bios to read a samsung 4tb ssd

I have a windows 7 64 bit bios laptop that has 2 hard drives. The bootable drive is 2tb and no problems. I just installed a 4 tb ssd on the secondary drive for data only (no software either). I had it formatted, initiated as GPT. But as soon as I put files in the ssd, they get unreadable and corrupted. I have updated all the updates from the laptop manufacturers site and also replaced the 4tb ssd just in case it was defective. Note: the 4tb had to be initialized and formatted on another computer that used windows 10 since my windows 7 would not recognize the drive other than 1867~ gb. Once it was formatted I put it in my laptop and it is seen as 4tb but error happens when I transfer files into the hard drive. I also tried partitioning it into 4 separate drives at 930~gb each but still the drive is getting corrupted individually.

- Put the 4 T SSD on the second slot of your laptop.
- Is it seen by BIOS?
- Did you try to open Disk Manager, delete all partitions, create new?
- Open Disk Manager, expand all columns so we can read them and with the sniping tool take a snapshot of all page. Post it here as an attachment (Go Advanced - Manage Attachments - Browse - upload)

You say 4 tb ssd they cost £1259 Samsung 850 EVO 4 TB Solid State Drive: Amazon.co.uk: Computers & Accessories

Are you sure its right

MEGAHERTZ07, yes I already did but my laptop will not allow me to initialize it as 4 tb. I will give you pics when I get home.

That is why I initialized and formatted it on another computer. Bios does see it as 4tb. Samsung Magician also sees it as 4 tb.

Samuria- I don't know what you are asking is right. I paid $1600 U.S. DOLLARS for the samsung 4 tb ssd.

Addram- i cant format it in my pc. It wont see it as 4tb. only 2 tb

Overall requirements for a non-bootable data volume
For a system to be able to address the maximum capacity of a device that has a storage capacity of more than 2 TB, the following prerequisites apply:

• The disk must be initialized by using GPT.
• The Windows version must be one of the following (32-bit or 64-bit, unless otherwise noted, but including all SKU editions):
  
  • Windows Server 2008 R2 (only 64 bit version available)
  • Windows Server 2008
  • Windows 7
  • Windows Vista
• The latest storage drivers from your storage controller manufacturer must be installed. For example, if your system uses an Intel storage controller that is set to “RAID” mode, make sure that you have the latest applicable drivers from the Intel support site.
• Overall, you should contact your system vendor to determine whether the system supports device sizes of more than 2 TB.

https://support.microsoft.com/en-in/...rger-than-2-tb

In the other thread you had tagged on Windows 7 Won't Recognize 4TB Hard Drive I had advised you

"Hi feihung,

Make sure your system requires/uses IRST drivers. Check the existing version that is installed. You can download the latest IRST drivers from Downloads for Intel(R) Rapid Storage Technology (Intel(R) RST)- "

In case your system does not use Intel Storage controller, then your system Bios may not support drives more than 2TB. In some cases updating the BIOS to the latest available for the system helped. Check with your system manufacturer/Tech Support.

Yes I already updated intel rapid storage technology. Still no go. The manufacturer said it should work since I am not using it on the bootable drive.

I just ordered windows 7 ultimate as an upgrade. Any other suggestions?

And the microsoft statement about what needs to be done is for bootable drives. Not secondary

That is the requirement for a non-bootable data volume as the title says.. You may read the article https://support.microsoft.com/en-in/...rger-than-2-tb which gives the requirements for non-bootable data volumes and also bootable system volumes.

"The manufacturer said it should work since I am not using it on the bootable drive."

Who do you mean? Samsung or the System Manufacturer?

If updating the IRST drivers did not help, you should contact your laptop manufacturer /Tech Support and check whether a BIOS update will resolve the issue. We have had cases where a BIOS update resolved the issue.