"Disk read error" during boot when pc has been turned off for a while

I tried that one already but Option One did not work for me. When I just installed Windows 7 directly to my drive without any previous Windows version on it and manually entered my product key it said that that product key was to be used only as an upgrade install etc. and wouldn't accept it. The second option did work since that's just the normal way to upgrade from e.g. Windows XP to Windows 7 with the upgrade disc. Luckily you don't actually need to install the whole XP. Problem with my Windows XP license is that it won't accept it anymore for some reason. And if I choose to skip licensing it during install it won't go to the next step. So actually all I need to do is install Windows XP, untill it asks for a product key. Then reboot my pc with the Windows 7 upgrade disc and use the method described in Option Two and voilà, it accepts my upgrade license.
I could also ask if I could trade it in for a better model, like a 7200 RPM, SATA3, 64MB cache but this one only costed me €60,- and drives like that go for at least double nowadays. I'm not paying €65,- extra for 500GB more and some barely noticeable performance boosters. But that's just me I guess.

Well a little update. The store wanted me to use the Samsung diagnostic tool version and they told me about Ultimate BootCD. That did have the ES-Tool. Used it and ofcourse it didn't find any problems. Hope they'll take it back, just sent them an e-mail again.
I'd say you were right about it being a malfunction in the drive itself. Seems to me that it loads some Windows bootup related part of the drive slower than the rest of the drive. It seems that the problem fixes itself if I just let it reboot itself a few times while choosing the Start Windows normally option every time. Eventually it will loads Windows normally.
Another reason why I think there has to be something wrong with the new drive is because I get a black screen after BIOS (so not even the "Starting Windows..." screen) if there are any secondary boot options enabled, when the pc has been off for a while and normally the freeze problem would occur.
It will only get to the Windows screen directly after the first boot attempt if I apply these settings in BIOS:
Boot Option Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: Disabled
Hard Drive BBS Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: Disabled

If I apply any of the following settings it will just give a black screen after BIOS:
Boot Option Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: TSSTcorp CDDVDW SH-222AL
Hard Drive BBS Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: Disabled

or

Boot Option Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: Disabled
Hard Drive BBS Priorities:
Boot Option 1: Samsung HD154UI
Boot Option 2: Samsung HD501LJ

My thoughts are that the mobo might already figure out that there's something wrong with the Windows drive, so it also looks at the other boot options. Since the other boot options don't have an OS installed it won't load anything. But if I give it no other options it will do it's best to force a Windows load out of the new drive, but will fail at the first attempts.

Does that even make any sense? I mean it should not be a problem that there are secondary boot option enabled as long as the first one is the Windows drive, since that would be it's first choice and should already boot from it, not even looking at the other options.
When I only had my old drive installed with Windows I believe I also had other boot options enabled (DVD drives) and it never had any problems finding the correct one (as long as my old drive was the first option and not a DVD drive).
The "Disc read error" seems to appear randomly sometimes. Another thing is that sometimes when it does start Windows it won't give a signal to my main screen. Eventhough it did receive a signal when the BIOS loaded. I have two screens setup so I know that it does bootup normally because my secondary screen shows me my extended desktop. Also this "error" seems to occur randomly and is always fixed by rebooting again.
Waiting for their response now. Hope the have a new drive for me and that the new one will work. Otherwise it might be some sort of compatibility issue. Then I would probably need to look for a different model.

Well both times the OS was installed in AHCI mode and it's still in AHCI mode. I also tested switching it to IDE mode but ofcourse that didn't work.

It's definitely not fixed by using a different SATA cable or port, tried both without success.

Well I'm sure the boot files for OS are on the drive (ofcourse) and I'm pretty sure that they're not corrupted. If they were it wouldn't boot after a few tries I'd think. Plus I had the same problem with my old OS install that I copied from my old drive.

Only thing I can try is test it with a different power cable/connector. I believe my PSU has at least two cable for SATA and so far I've just used one since it has just enough connectors to hook them all up on one. Will test this in a few hours when I'm at home. Hope it will fix it. That would probably mean that the connector it's hooked up to doesn't work properly, since all the other devices connected to the cable are fine. Since the new drive is connected to the 3rd connector and the old drive to the 4th (which it was connected to even before I got the new drive) I think the cable itself is fine.

I wonder if your HDD doesn't take too long to spin up and that creates problems, in other words your HDD is not up to full speed and can't properly read data, that's why you get no disc or errors on the first bootup and then everything seem to work on reboot. There should be something in BIOS to delay boot up and see if that fixes it, or simply hit reset during BIOS to delay HHD reading. If that's the case the second question would be if that is normal for this particular drive or is it defect.

Just tested with my other power cord, but still the same problem.

About the drive maybe taking to long to spin up fully:
I'm not sure if this could be the problem. That would mean that the pc would boot normally if I would enter BIOS settings and just wait a few seconds and then continue the boot process by exiting BIOS. This however is for as far as I know not the situation. For as far as I can remember. Plus that wouldn't explain why it sometimes takes the drive only two attempts and sometimes more. Ofcourse I will test this some more after this post, just to be sure.
Also if I understand it correctly, according to Samsung it should take approximately 13 seconds to get the drive spinning at full power (13 sec Drive Ready Timer (Typical) according to the Samsung specs). So if it takes more than 26 seconds to start up I would say there's something wrong with it.

Please correct me if my conclusions are wrong, sadly I'm no expert.

EDIT: Is there any program or other way to measure the drives start up ready time? Also I checked the BIOS and the MB manual but I couldn't find any option to slow down the boot process. Although if this turns out to be the problem, I'd rather use my old drive for Windows, since it seems I would have to slow it down quite a lot.