but there aren't options that allow me to change device settings...
I can chage :
CPU options, boot priority, fan control, wake up on LAN and an other thing of the hard disk
Since you just updated your BIOS, without making a not of what hte settings were before, you'll most likely have to play around to figure out how ot fix the enumeration issue, if it does indeed exist in the BIOS.
My rule of thumb: Never upgrade/flash/mess with the BIOS at all unless it's for a specific reason. I.E. Raid control, timings, UMA, etc. I just had to do a "hot flash" with my wifes computer on my bios chip as a result of the "newest and greatest Bios" from foxconn.
I disagree - I have yet to see a mobo OEM publish *every change made to the BIOS and how those changes affect *every user* on *every OS*.
Of course, I have my computer plugged into an APC BackupUPS rated at 1500VA, allowing me a good amount of time in case the power fails to finish the upgrade, but still - sometimes a BIOS upgrade will fix things that even the developers did not know about - thus they cannot / do not publish the 'fix' and you're left out.
Generally speaking, if they put out a revision, more often than not it will fix things - and if it does not / if it makes something break, you can always flash back.
You could flash down to the previous BIOS version.
That would be an option as well, and one you might want to pursue....
i can't understand why all people try to avoid problem resolving... i know that if i do a clean istallation i won't have problem!! but what do i learn doing a new istallation or flashing down the bios?
i posted here to learn something new and hoping that someone better than me could help me to resolve my problem...
i know that doing a clean istallation will help me, even without post my problem here....
I can't understand why you are giving us as little information as you are - If the problems occurred after updating your BIOS, the first thing you should have done is revert to the older BIOS and see if that 'fixes' the problem. If it doesn't, then it could very well be that a setting got changed to a default value that disagrees with the installation that you are currently using (for example, changing from
Advanced Host Controller Interface - Wikipedia, the free encyclopedia disabled to enabled rendered XP and Vista unbootable, and forced you to reinstall. With Win7, it may be trapping those routines and instead of rendering you inoperable is merely making things an annoyance. Other functions (other than enumeration that is) are the timers used (HPET versus AHCI, I think) and even things like enabling / disabling legacy USB support could have an effect.
I personally would be able to help you a lot ore if I had any experience with your mobo, but I don't - and since I have been using Win7 eVGA has not released a new BIOS for my mobo, so I don't even have the experience of flashing to a new BIOS the entire time I have been using Win7, so I am making suggestions to you based only upon speculation.
Finally, If you know a clean install will fix the problem, then my original supposition and subsequent discussion seems to be true - the BIOS upgrade changed something that is now at odds with your current install and you'll have to figure out *what* that change was.
Have you considered that you may not be able to do anything else about it? If there is a conflict between your software and hardware, you may not have many options.
Can you do a fresh install on a spare hard drive / partition to see if the problem is still there??
The problem can be resolved, because sometime everything work fine, btw for Antony : i have already istalled my powerfull xp on an other partition, but it's really hard to see what windows 7 do at the system start up, i'm not an operative system expert
If sometimes every thing works and sometimes it does not, then there is obviously some sort of conflict occurring - you'll have to do some extensive testing to figure out when it is happening and when it is not- for all you know it could be a bad cord in one of your USB wired devices that only occasionally acts up, or it could be related to a particular application that is running in the background, it could be related to a particular piece of hardware that you only occasionally use (not in that the hardware is bad but in that the device driver for said hardware may be instigating a conflict on the hardware level within the OS).
There are just too many variables here for us to troubleshoot it remotely as we are, and we are trying to help as much as possible, but you are the only one sitting at the machine, and you'll have to perform the troubleshooting yourself - we can only suggest, as we have been doing thus far.
