Zeno~SPARTA~ Posted February 3, 2009 Share Posted February 3, 2009 Yesterday i bought 2 1.5 tb drives to add to my 2 main pcs. When I formatted them they only got to 73% then froze. I was going to take them back, but I thought I would research the problem first. Low and behold the problem is well known and the solution is to update the bios of nvidea boards, so First I updated the chipset driver, then I downloaded the latest bios which is 1801. I put the latest bios onto a cd (I couldnt make it work from a fat32 flash drive) and used the EZflash program in the bios. All went well until the restart. Now the bios doesnt even come up and I get cpu and code init messages on the little panel at the back. I have had problems with the striker before, but that was down to defective corsair ram. Vainly I swapped out the ocz hpc for some ordinary corsair ram, but the screen remains blank. to use a krambolism I cant be arsed to find a way to make this work so I will buy another ordinary non asus/nvidia board this afternoon. Grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr. Link to comment Share on other sites More sharing options...
Krambo Posted February 3, 2009 Share Posted February 3, 2009 sorry 2 hear of ur problems, best of luck Link to comment Share on other sites More sharing options...
Zeno~SPARTA~ Posted February 3, 2009 Author Share Posted February 3, 2009 I unplugged the battery, left it for a while, now the bugger has booted, it lost date and time but I get to the windows screen. I'll see what other surprises await me. Link to comment Share on other sites More sharing options...
Athlon64~SPARTA~ Posted February 3, 2009 Share Posted February 3, 2009 (edited) Sounds like something is not compatible in the bios update. Call Asus support and tell them about the problem, They can mail you a new updated bios chipp to fix it, if there is a fix. Also get on the ASUS webb sight, under support and look at your paticular board model area there might be helpfull info there as well. Edited February 3, 2009 by Athlon64~SPARTA~ Link to comment Share on other sites More sharing options...
custard~SPARTA~ Posted February 3, 2009 Share Posted February 3, 2009 Format the stick to ntfs and see if that will work, the battery removal has reset the cmos on your mobo the same thing sometimes happens to my mobo on updating bios. Link to comment Share on other sites More sharing options...
Zeno~SPARTA~ Posted February 3, 2009 Author Share Posted February 3, 2009 Viiipers using 1303 which he has sent me so I will be rolling back to that tomorrow. Link to comment Share on other sites More sharing options...
Zeno~SPARTA~ Posted February 4, 2009 Author Share Posted February 4, 2009 I tried to roll back the BIOS using EZ flash, but it wouldnt let me, I guess the software prevents it. Pain in the proverbial. However I had a brainwave and checked the ram voltage as I recall random BSODs occur if its set too low. When I reflashed it went to auto and on this board it automatically sets too low at 1.8 when it should be 2.1 min, so I set it to 2.1 we'll see how it does. Link to comment Share on other sites More sharing options...
Krambo Posted February 4, 2009 Share Posted February 4, 2009 keep us updated! Link to comment Share on other sites More sharing options...
Halli~SPARTA~ Posted February 4, 2009 Share Posted February 4, 2009 Yep Good luck and I think it's 2.01 not 2.1 if there is a difference. I decided to never change my bios as the debacle that Viiiper and I think Majestic had when they updated last year. SO the old Bios must only read 1 tera? Link to comment Share on other sites More sharing options...
NoScream~SPARTA~ Posted February 4, 2009 Share Posted February 4, 2009 That's right Halli, Maj & I still on 1303 BIOS, working and will stay till now motherboard day. Link to comment Share on other sites More sharing options...
Recommended Posts