Topic: P67A-GD65 (B3 ) & Windows 7 64Bit Boot Issue (Read 4363 times)

thegilpins · « **on:** 04-June-12, 13:08:21 »

Hi,

I feel the need to revisit this old forum post as I do not believe it has been fully resolved:
http://forum-en.msi.com/index.php?topic=156082.0

In summary the issue is "Most times the machine boots and performs flawlessly for hours, but often it boots with the Windows-7 “need to repair” screen and after running repair for a while Windows says: “Windows cannot repair the problem”…….but when I press the Reset button, the PC boots and runs just fine".

I only had the problem since updating from 1F beta 2 to the latest BIOS version. On the original forum thread there are some that had the view that the issue was introduced around BIOS version 1.F (full release, non-beta) and 1.G. Just to confirm this issue NEVER happened for me on 1F beta 2 or earlier BIOS releases. The original forum also has some people saying the issue did not exist on earlier BIOS versions as well.

Most people seem to have solved the issue by either resetting the CMOS or loading default BIOS settings. I tried this and it did initially solve the problem for me.

BUT when I installed new drivers (such as nvidia v301.24) or added new hardware (e.g. Bigfoot PCIe network gaming card) the problem came back.

This implies to me that there is an issue with the BIOS and that resetting the CMOS is a workaround rather than a true fix.

This leaves me with two choices:
- use an older BIOS, which is ok but limits me from the new functionality in the BIOS (including not being able to use certain hardware that the BIOS updates support)
- resetting the CMOS after loading new drivers or installing new hardware and then configure my settings (which is very tedious)

Neither option is ideal to me.

The main purpose of raising this issue is to ask whether MSI Support know of this issue and have it on their bug list to fix?

I am concerned it is not being addressed as other forum entries talk about BIOS version 1.K3 being the last version.

My system details are P67-GD65(B3), Windows 7 64bit, 16GB Gskill 2133Mhz memory, 2 SSD, 2HDD, Nvidia 570 GTX, Bigfoot network gaming card.

momosala · « **Reply #1 on:** 04-June-12, 14:51:23 »

I have the same problem, not solved by CMOS Clear.

momosala · « **Reply #2 on:** 04-June-12, 16:29:31 »

On my PC, Intel management Engine wasn't installed.
I install it. Perhaps this will correct the problem.

thegilpins · « **Reply #3 on:** 04-June-12, 18:16:39 »

Quote from: momosala on 04-June-12, 16:29:31

On my PC, Intel management Engine wasn't installed.
I install it. Perhaps this will correct the problem.

I have IME installed and it doesn't make a difference, does not solve the re-boot problem.

Froggy Gremlin · « **Reply #4 on:** 04-June-12, 20:55:28 »

Might try UEFI/BIOS version v1.H. If OC'ing, it may not be completely stable.

Quote

The main purpose of raising this issue is to ask whether MSI Support know of this issue and have it on their bug list to fix?

Unless users report to MSI Technical, the answer may be no. Also, they may also need to duplicate any problems to come up with a resolve. Please report any findings to MSI Technical;

>> How To Contact MSI <<

thegilpins · « **Reply #5 on:** 05-June-12, 11:18:44 »

I will contact MSI and post any response that I get.

Thanks

jackal12 · « **Reply #6 on:** 05-June-12, 20:52:31 »

i have this problem but only since i installed a ssd drive as boot drive ,it never happened with my hard drives , so my soltution is when it say it needs to repair i just sellect "boot windows normaly" and it loads up fine

thegilpins · « **Reply #7 on:** 06-June-12, 19:58:10 »

Hi all,

MSI support suggested trying the latest BIOS 1K3. I am on 1K2, has anyone tried 1K3 and solved this issue?

Froggy Gremlin · « **Reply #8 on:** 06-June-12, 20:07:53 »

Here's the modded version;

>> Beta Mod <<

thegilpins · « **Reply #9 on:** 09-June-12, 13:38:51 »

I updated to the latest BIOS 1K3 as suggested by MSI Support and all good for a few days.

BUT once again after do firmware update to an SSD the double Windows reboot is back.

This issue still remains for me in the latest BIOS.

momosala · « **Reply #10 on:** 09-June-12, 18:23:22 »

has anyone tried the 1.K3 modded2 firmware ?

http://forum-en.msi.com/index.php?topic=158753.0;all#lastPost
Download here : http://forum-en.msi.com/index.php?action=dlattach;topic=158753.0;attach=9669

momosala · « **Reply #11 on:** 12-June-12, 10:30:38 »

No one tried 1.K3 modded2 bios ?

thegilpins · « **Reply #12 on:** 12-June-12, 21:10:20 »

Quote from: momosala on 12-June-12, 10:30:38

No one tried 1.K3 modded2 bios ?

Not yet but may try it at the weekend

thegilpins · « **Reply #13 on:** 17-June-12, 11:56:36 »

Quote from: momosala on 12-June-12, 10:30:38

No one tried 1.K3 modded2 bios ?

Hi, have now tried the new mod. The first few boots were ok. Did a cold boot today and got the double boot problem again.

Seems the latest bios (mod and official) still have this problem.

stevetski · « **Reply #14 on:** 17-June-12, 13:45:15 »

I have the same problem on my P67A-G45 with latest bios & Patriot Pyro SE 60gb SSD boot drive.

momosala · « **Reply #15 on:** 17-June-12, 15:02:20 »

Quote from: thegilpins on 17-June-12, 11:56:36

Hi, have now tried the new mod. The first few boots were ok. Did a cold boot today and got the double boot problem again.

Seems the latest bios (mod and official) still have this problem.

Thank you The gilpins for testing 1.K3 modded2 bios.
Many users have the same problem.
I pointed to the MSI customer service. No results.
Hope that a future bios will solve the problem

Zlip · « **Reply #16 on:** 18-June-12, 12:26:10 »

I myself is victim of this weird issue. Please do solve this issue.

Mutt · « **Reply #17 on:** 19-June-12, 19:51:58 »

After updating/installing your new hardware/software and restarting after each event, did windows restart normally on every instance?
Have you tried to disable the setting for automatic restart for system failures? Control Panel>System>Advanced System Settings>(System Properties) Advanced tab> Startup and Recovery, click settings button - in system failure: uncheck "automatically restart"
Have you had any BSODs and if so, have you checked your dump files for clues?
Have you tried CCCleaner...Registry scan? If you run the registry tool take notice of what it is fixing.

thegilpins · « **Reply #18 on:** 19-June-12, 20:04:02 »

Quote from: Mutt on 19-June-12, 19:51:58

After updating/installing your new hardware/software and restarting after each event, did windows restart normally on every instance?
Have you tried to disable the setting for automatic restart for system failures? Control Panel>System>Advanced System Settings>(System Properties) Advanced tab> Startup and Recovery, click settings button - in system failure: uncheck "automatically restart"
Have you had any BSODs and if so, have you checked your dump files for clues?
Have you tried CCCleaner...Registry scan? If you run the registry tool take notice of what it is fixing.

Thanks for your suggestions. Yes Windows has failed on restart of new hardware / firmware updates. The only way I get a boot every time is to disable errors via bcdedit. Not had any bsod's so no errors to look at. I have not used a registry tool since I have used an SSD.

This periodic boot problem only occurs on the newer versions of the BIOS. Under older versisons the problem was never seen.

thegilpins · « **Reply #19 on:** 19-June-12, 20:10:23 »

Have just got a response from MSI Support as follows "we have tested the problem many days,but we are very sorry,we tested the bios 1.F/1K3 with the hard disk and the OCZ SSD,the computer boot normally,of course,we installed the NVIDIA drivers and other drivers, but we can not find the problem. We have reflect to the relevant departments, if we can copy this problem, we will fix it in future bios. Sorry for any inconvenience caused. Best Regards, MSI Technical Support Team".

Whilst I am pleased they have tried to recreate the problem there is obviously differences between my and their PC builds and so this remains unsolved. I will go back and ask what the next steps are and repoprt back what I get.

So far I have counted about a dozen people that have responded to this thread or the original one but are there others out there that also have the problem? It would be good to go back to MSI Support with a long list of people affected, so if you are cvan you please say so on this forum topic. Thanks!

Mutt · « **Reply #20 on:** 19-June-12, 21:12:27 »

If after you made your upgrades and didn't get a clean restart you could have some corrupt files which could give you the repair message.

From Microsoft website: "Disable automatic restart on system failure
Prevents Windows from automatically restarting if an error causes Windows to fail. Choose this option only if Windows is stuck in a loop where Windows fails, attempts to restart, and fails again repeatedly."

From what I've read about CCleaner, you can use it for cleaning up your system and registry, just not something you should do over and over again for an exteneded period of time. It is not advised to use any of the other options/tools.

Searching the net for a cure to my problem, seems this type problem is more widespread and not just confined to MSi products...but what do I know, just a dumb dog.

jerrywall · « **Reply #21 on:** 20-June-12, 09:49:51 »

I have had exactly this boot issue with Win7 64 and the P67A-C45 (B3) since the last two BIOS for my board. Didn't have it before. I have an Intel SSD 510 120 GB as boot disk. It started with the last but one BIOS and as the current BIOS 1.I came it became so rare that I at first thougt it had gone away. Now it shows up at perhaps only every 20 boot or so, cold or warm.
The latest thing I have changed is to disable the automatic reboot and stop forcing swap file to zero on the SSD. I now have set a 512 MB swapfile at the SSD and the rest is handled by Windows, in my case it puts the main part on a normal HDD.
I will get back if the problem seems to go away.
Am I right in thinking that this only affects SDD users?

momosala · « **Reply #22 on:** 20-June-12, 12:26:08 »

Quote from: jerrywall on 20-June-12, 09:49:51

I have had exactly this boot issue with Win7 64 and the P67A-C45 (B3) since the last two BIOS for my board. Didn't have it before. I have an Intel SSD 510 120 GB as boot disk. It started with the last but one BIOS and as the current BIOS 1.I came it became so rare that I at first thougt it had gone away. Now it shows up at perhaps only every 20 boot or so, cold or warm.
The latest thing I have changed is to disable the automatic reboot and stop forcing swap file to zero on the SSD. I now have set a 512 MB swapfile at the SSD and the rest is handled by Windows, in my case it puts the main part on a normal HDD.
I will get back if the problem seems to go away.
Am I right in thinking that this only affects SDD users?

I have the swap file and the temp directory on my SSD Vertex 3, and I have the boot issue with the last bios version.
I also think it's a bios problem with SSD.

some body · « **Reply #23 on:** 27-June-12, 04:54:17 »

Glad to see this issue revived.

I had originally posted that resetting the CMOS and manually reconfiguring appeared to work for me...

It took a while, but I've had the issue reappear again very sporadically. I haven't tried another CMOS reset, but probably will.

I'm still running that last official Sandybridge 1.J0 bios - I haven't tried the 1.K betas or Modded version (altough I'm tempted to try the 1.K3 Modded) or the newer v.4.1 Ivy BIOS (looks like a one-way street if you go that route..I'll wait to see if current issues are resolved, etc.).

I don't have an SSD drive installed and experience this problem - I'm still inclined to think it relates to USB.

Zlip · « **Reply #24 on:** 27-June-12, 16:49:21 »

I am on 1.19 aka 1.J UEFI version and still facing this issue myself also I am not on SSD rather on HDD. Please fix it with new BIOS Update.

Ex Forum Mod · « **Reply #25 on:** 28-June-12, 01:02:56 »

Quote from: Zlip on 27-June-12, 16:49:21

I am on 1.19 aka 1.J UEFI version and still facing this issue myself also I am not on SSD rather on HDD. Please fix it with new BIOS Update.

We users of this forum do not make nor have anything to do with BIOS updates. If you have a problem with the BIOS for whatever reason then notify MSI HQ and give them a good description of your problem.

>> How to contact MSI <<

Zlip · « **Reply #26 on:** 28-June-12, 08:22:43 »

Quote from: Henry on 28-June-12, 01:02:56

We users of this forum do not make nor have anything to do with BIOS updates. If you have a problem with the BIOS for whatever reason then notify MSI HQ and give them a good description of your problem.

>> How to contact MSI <<

Thanks a lot for your guidance, I posted two questions.. I am sure they will help me as much as they can. Thanks once again for your guidance.

animefan · « **Reply #27 on:** 28-June-12, 23:19:24 »

I had this problem for many months. After I replaced my mouse (Logitech MX620 Cordless Laser Mouse) and my keyboard with the Logitech Cordless Desktop MX 5500 Revolution (and upgrading the bios to 4.0 and then to 4.1 - including IME 8) the problem went away. Upgrading to bios version 4.x was probably not required to fix the problem though.

I think it was the wireless mouse that caused the random boot failures.

jerrywall · « **Reply #28 on:** 03-July-12, 18:06:59 »

I think I have found the culprit of the boot failure. Since it appears so early in the boot sequence it most likely is a low level I/O driver and I suspect the Renesas/NEC USB3 driver. I managed to find an update for the driver (2.1.36.0) released by another hardware company.
Renesas/NEC does not bother with end users and MSI does not bother with this problem as it is too complicated to pinpoint. Anyway, I installed the driver and have now booted more times than I ever did with the older driver (2.0.34.0) without boot errors.
The thing that convinced me was that I at one point had forgotten that sometimes a conflict shows up in that the same drive letter might be given to two different USB hard drives. In this case you will not see the drives in Windows until you reassign two different letters to each of the drives in the Disk Administration app. Anyways, I panicked and thought the newer driver had stopped working and I reinstalled the original MSI driver.
And, boom, right away the boot error at first reboot with the MSI USB3 driver! So back in with the newer version and no boot error. I will have to test a bit longer to be on the safe side. At first boot error now I will flash the ME8 BIOS!!

thegilpins · « **Reply #29 on:** 03-July-12, 19:47:30 »

Quote from: jerrywall on 03-July-12, 18:06:59

I think I have found the culprit of the boot failure. Since it appears so early in the boot sequence it most likely is a low level I/O driver and I suspect the Renesas/NEC USB3 driver. I managed to find an update for the driver (2.1.36.0) released by another hardware company.
Renesas/NEC does not bother with end users and MSI does not bother with this problem as it is too complicated to pinpoint. Anyway, I installed the driver and have now booted more times than I ever did with the older driver (2.0.34.0) without boot errors.
The thing that convinced me was that I at one point had forgotten that sometimes a conflict shows up in that the same drive letter might be given to two different USB hard drives. In this case you will not see the drives in Windows until you reassign two different letters to each of the drives in the Disk Administration app. Anyways, I panicked and thought the newer driver had stopped working and I reinstalled the original MSI driver.
And, boom, right away the boot error at first reboot with the MSI USB3 driver! So back in with the newer version and no boot error. I will have to test a bit longer to be on the safe side. At first boot error now I will flash the ME8 BIOS!!

jerrywall what version of the BIOS are you using?

jerrywall · « **Reply #30 on:** 03-July-12, 20:04:14 »

Quote from: thegilpins on 03-July-12, 19:47:30

jerrywall what version of the BIOS are you using?

I am still at the last ME7 BIOS for P67A-C45 (B3), 1.I. The error started two revisions back, before that I never had this problem with this board. I had other problems, like unable to overclock and with 1.H this got better. BTW loading optimized defaults and not overclocking will NOT make the boot problem go away.
Any problem now and I will flash 5.1 ME8 as some say the problem goes away with that version. Since I have a SandyBridge CPU I will try to avoid it.

thegilpins · « **Reply #31 on:** 03-July-12, 21:40:29 »

Quote from: jerrywall on 03-July-12, 20:04:14

I am still at the last ME7 BIOS for P67A-C45 (B3), 1.I. The error started two revisions back, before that I never had this problem with this board. I had other problems, like unable to overclock and with 1.H this got better. BTW loading optimized defaults and not overclocking will NOT make the boot problem go away.
Any problem now and I will flash 5.1 ME8 as some say the problem goes away with that version. Since I have a SandyBridge CPU I will try to avoid it.

Hi, I tried what you suggested with the latest USB driver and all worked ok for a few boots. I then installed Samsung Kies and the double boot is back. It seems on my system that certain dirver/firmware updates trigger the issue on the first boot after install and then it can be ok for a few days before the problem resurfaces. It may be that your re-install of the old USB driver caused the same issue as me rather than there being a problem with it. I have used new and old USB drivers on 1.F beta 2 bios without any issues, which is why I still think the root issue is a bios bug rather than a driver issue.

If you do flash to bios 4.1 and it works for you please post back to the forum.

jerrywall · « **Reply #32 on:** 04-July-12, 13:43:16 »

Quote from: thegilpins on 03-July-12, 21:40:29

......

If you do flash to bios 4.1 and it works for you please post back to the forum.

The boot error came at last so I flashed the 5.1 BIOS for my p67a-c45 using the DOS method and the board went dead. Should have used the Windows method. Installed a new board Z77A-S01 and it works like a charm! The old p67-bord is sleeping in the city dump!

Froggy Gremlin · « **Reply #33 on:** 04-July-12, 18:23:41 »

Quote

The boot error came at last so I flashed the 5.1 BIOS for my p67a-c45 using the DOS method and the board went dead. Should have used the Windows method.

Don't see how. The DOS method is more safe than Windows will ever be.

jerrywall · « **Reply #34 on:** 04-July-12, 18:56:44 »

Quote from: HU16E on 04-July-12, 18:23:41

Don't see how. The DOS method is more safe than Windows will ever be.

Well this is not true for me. I have made the earlier flashes with this mb from Windows and they all went well and this time I thought I should heed your warnings and the flash failed fatally. I spent several hours trying to bring it to life but there was no response whatever I did. I striped components and ran it in the free trying all kinds of bios revival tricks, amiboot.rom on USB stick and CD but nothing happened so I went to the shopping mall and bought me a new board instead.
Way back in the olden times there always was the simple trick to boot from floppy.
This is the first time since I got my first PC back in 1994 that a flash has gone bad on me.

Froggy Gremlin · « **Reply #35 on:** 04-July-12, 19:13:03 »

So basically, the flash failed attempting an Ivy update. It could have also possibly failed using the Windows method as well. Since this thread is about a P67A-GD65(B3), there is no point in going into details on the procedure of the failed flash for a P67A-C45. There are too many variances in the features and hardware of the two anyway. Having purchased a shiny new Z77A-S01 that is made for Ivy, your problems should be solved.

jerrywall · « **Reply #36 on:** 04-July-12, 20:48:16 »

Quote from: HU16E on 04-July-12, 19:13:03

So basically, the flash failed attempting an Ivy update. It could have also possibly failed using the Windows method as well. Since this thread is about a P67A-GD65(B3), there is no point in going into details on the procedure of the failed flash for a P67A-C45. There are too many variances in the features and hardware of the two anyway. Having purchased a shiny new Z77A-S01 that is made for Ivy, your problems should be solved.

Yes you are quite right there HU16E, it´s a bit unfair to blame the method. It's nice to have a new board, no regrets. And above all, no boot hickups!!

Boldie007 · « **Reply #37 on:** 04-July-12, 21:51:39 »

I have flashed my P67A-GD55 (B3) with 4.1 IB BIOS using the windows method and it has fixed this issue for me.

momosala · « **Reply #38 on:** 04-July-12, 22:16:07 »

Quote from: Boldie007 on 04-July-12, 21:51:39

I have flashed my P67A-GD55 (B3) with 4.1 IB BIOS using the windows method and it has fixed this issue for me.

Please Boldie007,
Have you a Sandy Bridge (P67 ...) or an Ivy Bridge chipset.
I have a i7 2600K Processor and I have the 1.I I firmware for my P67A-GD55.
I dare not do the bios update to version 4.1 because some users of Sandy Bridge P67 chipset has had serious problems with it.
Thank you for your response.

Boldie007 · « **Reply #39 on:** 04-July-12, 22:34:25 »

Sorry i5 2500K, given what I know now I wouldn't flash to IB BIOS if you want to OC a SB CPU, my system is no longer able to OC anywhere near as well as previously. If there was a way of putting it back to pre IB BIOS I would.......

momosala · « **Reply #40 on:** 05-July-12, 16:55:20 »

Quote from: Boldie007 on 04-July-12, 22:34:25

Sorry i5 2500K, given what I know now I wouldn't flash to IB BIOS if you want to OC a SB CPU, my system is no longer able to OC anywhere near as well as previously. If there was a way of putting it back to pre IB BIOS I would.......

Thank you for your response Boldie007.
However, I note that the 4.1 bios version solve the double boot problem of Win 7 64 bits.
Perhaps, MSI will use this data for future 1.X bios ?

momosala · « **Reply #41 on:** 19-September-12, 16:29:15 »

The problem of incomplete boot followed by a reboot and windows repair menu is not yet solved for the P67A-GDXX motherboard.
Is anyone has solved it ? And How ?

_Melk_ · « **Reply #42 on:** 25-September-12, 14:50:50 »

Not sure if this will help, but I myself having been a 1.14 BIOS user for 1+ year without any reboot problems, installed 1.19 a few days ago after purchasing a new Vertex 4 drive. I've been trying to figure out why I had intermittent boot/repair issues and figured it was the Intel RST drivers I had newly installed (never used them before either on Vertex 1).

So after reading tons on Intel forums & here, I'm reverting back to 1.14 BIOS and NO Intel RST... let's hope it fixes it for me... I don't mind a bit less speed vs more reliability

momosala · « **Reply #43 on:** 25-September-12, 16:19:54 »

Quote from: _Melk_ on 25-September-12, 14:50:50

Not sure if this will help, but I myself having been a 1.14 BIOS user for 1+ year without any reboot problems, installed 1.19 a few days ago after purchasing a new Vertex 4 drive. I've been trying to figure out why I had intermittent boot/repair issues and figured it was the Intel RST drivers I had newly installed (never used them before either on Vertex 1).

So after reading tons on Intel forums & here, I'm reverting back to 1.14 BIOS and NO Intel RST... let's hope it fixes it for me... I don't mind a bit less speed vs more reliability

Thank you _MELK_ for bringing us your experience.
It was already reported that this bug did not appear with older firmware versions.
It is interesting to know that version 1.14 does not have this bug.
This information should help the MSI support team to create a 1.K reliable firmware.
In my opinion, I do not think that Intel RST is the cause of this bug.

_Melk_ · « **Reply #44 on:** 04-March-13, 04:16:28 »

Quote from: momosala on 25-September-12, 16:19:54

Thank you _MELK_ for bringing us your experience.
It was already reported that this bug did not appear with older firmware versions.
It is interesting to know that version 1.14 does not have this bug.
This information should help the MSI support team to create a 1.K reliable firmware.
In my opinion, I do not think that Intel RST is the cause of this bug.

Sure thing momosala..

An update to this issue is as follow...

BIOS 1.14 fixed this issue completely. NO errors since I flashed back to it. I also reinstalled Intel RST without any issue either.

Note that I wanted 1.19 for another reason as well (fix for USB 3.0 port issues). I wound up flashing the chipset for the USB ports themselves instead

. Now the MB works as intended! :D

***
***
WARNING: use the info below with CAUTION (not simple to do, and not provided/supported by MSI afaik)
***
***

INFO on USB 3.0 firmware/drivers -- again, use CAUTION and do your research before proceeding!

Note that it took me a few hours to complete the flash since I had to research which version of the chipset I had (hardware ID helped, LOTS of reading on the subject as well to find out HOW to flash my board properly).

You can find the drivers/firmware for the "Renesa USB 3.0 Host controller" by searching google for

Driver: Renesas/Nec Usb 3.0 Version 3.0.23.0/2.1.39.0 WHQL.

I used the 2.1.39.0 drivers -- you'll find the firmware at the same place and an explanation on how to flash the chipset we have on the P67A-GD65 (which has TWO identical chips to flash). The new firmware updater doesn't work on those, so you need to download an older firmware to use the older DOS program to flash with the newer .MEM files.

momosala · « **Reply #45 on:** 04-March-13, 11:43:54 »

Thank you _Melk_
1.14 bios + flashing USB 3 ports firmware in DOS solve the problem.
This is interesting.
My USB 3 ports are already flashed with the last version.
My bios is modded 1.K5.
Do you think that If I return to 1.14 bios, the boot problem will be solved ?

_Melk_ · « **Reply #46 on:** 04-March-13, 12:14:34 »

My pleasure momosala.

Note about USB 3 flash. It was NOT related to my boot problem at all so it's not required for this thread issue.

As for 1.14, after looking at the MSI website, your board (P67A-GD55) seems to be using the same BIOS as my board (P67A-GD65) so it *might* resolve your issue indeed.

I'm not sure about 1.K5 though since after looking at the MSI website, the bios numbers went from 1.19 (1.J) to 4.x ( are those 1.K bios?). I never installed one of those since I read that they're used mostly if you have a .22m Ivy CPU (I don't).

If you are comfortable with flashing BIOS (as you seem to be), I'd certainly give it a try if this boot issue gets on your nerve... it sure did for me! Also, 1.19 didn't bring anything new to my setup that I was able to notice, so I'm perfectly happy with 1.14. Everything works and is OC (Memory XMP, CPU but only to 4.0-4.3Ghz, GPU)

Good luck friend. I really hope you get to fix this as I did. Also hope MSI reads this. I reported it once (ticket) when I realized that 1.19 caused Boot issues, but the more that report this, the better -- Specially since it seems the issue still exists for many.

_Melk_

P.S. The **only** weird issue I noticed with BIOS 1.14, a long time ago (too lazy to retry now), is that XMP NEEDS to be activated in BIOS for my memory. If it's not, sometimes I'd get boot errors -- so XMP is required for my Vengeance Memory (8GB or 16GB) -- with it activated, NO Errors in the last 2 years

edit: typos

momosala · « **Reply #47 on:** 04-March-13, 15:19:21 »

_Melk_
Thank you for your response.
1.K bios is a beta bios after official 1.J bios.

Like you, I do not use the 4.X bios because I have a sandy bridge processor. I tried it but OC didn't work well.

I'll try 1.E bios like you because the boot loop problem is always here.
I'll give the feed back in this thread.
Again, thank you.

thegilpins · « **Reply #48 on:** 05-March-13, 20:48:18 »

Quote from: _Melk_ on 04-March-13, 04:16:28

You can find the drivers/firmware for the "Renesa USB 3.0 Host controller" by searching google for

Driver: Renesas/Nec Usb 3.0 Version 3.0.23.0/2.1.39.0 WHQL.

I used the 2.1.39.0 drivers -- you'll find the firmware at the same place and an explanation on how to flash the chipset we have on the P67A-GD65 (which has TWO identical chips to flash). The new firmware updater doesn't work on those, so you need to download an older firmware to use the older DOS program to flash with the newer .MEM files.

Melk, are you able to provide detailed instructions on how to flash the USB3 chips via DOS? Thanks

xmad · « **Reply #49 on:** 05-March-13, 20:49:21 »

You can do this from windows using the batch files I included.

Look here: >>Beta BIOSes<<

Otherwise, you need to type the syntax that you see in the screen shots from dos.

Edit: Look at the bottom NEC/ Reaneses Firmware

News:

Author Topic: P67A-GD65 (B3 ) & Windows 7 64Bit Boot Issue (Read 4363 times)