Problem with Clean Install of Win7 on SSD

Well, I got my computer (ASUS G53SW-XN1) a few days ago and I have it up and running with all the programs and data in my 64GB SSD and 500GB HDD, respectively.

I've noticed that whenever I turn it off, and try to turn it back on that it will NOT load windows, no matter what. After the POST screen with the ASUS splash logo, it will just have a black screen with nothing going on. The only way for me to load up windows is to enter BIOS when i press the power button, and save and exit (don't change any settings or anything). Then it will re-POST and windows will load up.

It's really annoying, especially when I bought a SSD to improve boot times only to find out I have to enter BIOS and save and exit each time just to load up Windows...Please help me, I will probably have to reinstall win7 as this is not acceptable.

Some random notes about my laptop:

• Win7 was installed from the downloadable links found here
• The CD key was apparently not valid when I entered it, so it says "2 days till automatic activation"...All I did was enter the CD key found at the bottom of my laptop. Will do the telephone automated thing tomorrow.
• Boot drive sequence is set to #1 - Crucial M4 SSD and I've tried setting both #2 to my DVD Drive or even disabling it, it doesn't do anything.
• Crucial M4 is on latest firmware
• I've installed Intel Rapid Storage Drivers v10.6.0.1022 a few days ago if that matters.
• I've changed the page filing from 6GB to 2GB
• I've disable Hibernation via DOS prompt
• My windows system restore is set to 1% (around 600mb)

Nothing else that really catches my eye, I hope any of you could help me solve this irritating issue!

 

sounds like your machine is not compatible with M4. In this case, you may have better luck and try to see if ASUS has a newer firmware/BIOS or whatever it is called.

The alternative is unfortunately, get another SSD.

 

if it's not compatible why would it load up once i open BIOS and close it (it has to be with "save changes and exit, not just "exit")?

That's a weird situation, rather unfortunate as well.

 

incompatible doesn't mean not working but that the POST sequence doesn't work smoothly and why I said a newer BIOS may solve the problem.

While I like to joke about OCZ and SF, they did have a point that in many cases of their drive failure, it really were about compatibility(and in some of their cases, an upgrade BIOS solved the prolem).

 

ah jeez i wish i knew that before i bought the crucial SSD, i guess im going to try contact asus/crucial to see if i can fix any of these issues as i really like the speeds/the drive itself and it would be a pain to once again reinstall win7 onto my HDD while i wait for the new SSD (vertex 3 would be my alternate) to come, then uninstall win7 and reinstall back to the vertex.

 

search OCZ forum to see if vertex 3 is compatible with your machine before you buy.

 

samething happened to me, still is and I havent seen anyone around with the same sympton (until you show up). However my temporary fix for this is when you see the black screen after the asus logo, just press the power button to turn it off. Then turn it on again and press F2 to go into bios setting, dont change anything there, scrol to the last tab and save and exit, this time it will boot into windows.

Hope this temporarily helps you and maybe someone can come up with an actual solution.

 

yep, ive compiled a thread in the ASUS main sub forum which has some links with other users experiencing the problem...hopefully we can get enough people who have the problem for Crucial to recognize it and provide us with a firmware 0003 update!

 

luckily i didn't buy the OCZ someone else recommended, Crucial updated the firmware to improve compatibility and now it works. close thread.

 

Some have found that turning off fastboot helps in this case.

I had this problem with a Corsair Force 120. I had BSODs resuming from sleep/hibernate, but it was fine when I rebooted.

The problem was solved by uninstalling the AMD southbridge drivers and using the Microsoft MSAHCI drivers. AMD finally updated the drivers and the problem no longer exists starting Catalyst 10.9.