Two problems with 7264.x64 . . .

p7ast1k said:

maybe try a clean install
i have the same motherboard, with neither of those problems

I DID do a clean install -- after having done an upgrade from 7232. I've had the same problem with both the upgrade install and, subsequently, with the clean install.

Dorfdad said:

GO to your manufactures website and get all the latest drivers THEY have not microsoft has for your motherboard.

If there are no windows 7 drivers you can try the x64 Vista drivers.

I have all the lastest drivers from all the respective manufacturers -- I updated all of them yesterday when I did the clean install.

fakeasdf said:

. . . You might also check and verify your BIOS is up to date as well. The majority of times I've seen weird issues with mouse losing connectivity it's due to the BIOS settings. . . .

I updated the bios to version F7 (the most current) back when I installed build 7229 -- ages ago. Everything worked with builds 7229 and 7232 using bios F7.

I appreciate the suggestions -- keep them coming -- however, I'm usually pretty good a trouble-shooting. I think I've tried all the obvious things. Then again, sometimes the obvious just rares up and hits you in the face.

You probably upgraded. I'm using Build 7264 and it always reconnects and my IBM Mouse works perfectly. You should do a clean install. It will probably help. Plus, Download some tool that will really check every single driver for updates. E.G. Driver Magician. I thought I had the latest updates but I didn't.

I can't help ya but I just wanted to say I'm not having any problems like that here on build 7264 64bit.

I just woke up to 7 having my computer go to sleep and going back to the log-in screen. Everything is working here.

I have a G5 mouse.

fakeasdf said:

heh, I think everyone really wants you to clean install again :) just for kicks and giggles, have you tried a different mouse and seen if the same thing occurs after you put it to sleep and wake it up?

And the problem occurs with all three of the mice I currently have available to me -- when they are connected via USB. There is no problem with the mice -- any of them -- when connected via PS/2. But that's not the point. They should work when connected to USB, too -- they did before.

I've just installed the 15-day trial version of Driver Magician. The only driver it found missing/not-updated from my system is the one for my Epson scanner. And that's because my scanner driver is a customized version as that is NOT one available for Windows 7 (it's an older scanner but it does what I need it to do). Plus it works perfectly, currently, and has with all the builds I've installed thus far.

weh said:

I'm having two problems with Win.7.7264.x64 that I have not had before:

• Upon awakening from sleep, I have no mouse until I unplug it and plug it in again. (I've tried 3 different mice: my MX518, an MX310 and a Microsoft D58-00041) Then it works normally. (Applies to USB-connected mice, only - no problem when connected to PS/2 mouse port.)
• Also, my connection to my router gets wonky and rapidly quits, meaning that I have to keep trying again and again to get web pages to load because the request keeps timing out. And, after several attempts, the time out becomes permanent. This only happens after the system has awakened from sleep. Logging out and then logging in again doesn't work. Only rebooting restores normal operation.

When I first installed 7264, I upgraded from 7232. I figured my problems might stem from having upgraded; so, I bit the bullet and have now done a clean install. Same symptoms. Everything performs perfectly UNTIL the system is allowed to sleep. Upon awakening, no mouse (until I unplug & re-plug or reboot) and wonky router connection (until I reboot). Neither of these symptoms have ever occurred before.

One other note: other USB devices appear to be unaffected. My Epson & Nikon scanners, my USB CF flash card reader and my several USB flash keys all seem to work perfectly.

This is a well known issue with the X58 chipset. Possible B3 revisions of the X58 chipset may fix this problem.

Gigabyte Latest BIOS - TweakTown Forums

Please take a look at that link and see if the 'BETA' bioses resolve the problem.

Corei7Extreme said:

This is a well known issue with the X58 chipset. Possible B3 revisions of the X58 chipset may fix this problem.

Gigabyte Latest BIOS - TweakTown Forums

Please take a look at that link and see if the 'BETA' bioses resolve the problem.

I had waking problems in all builds until I switched to a beta BIOS they had for my Asus P6T6 WS. You still need to set up each device accordingly of course. I couldn't recharge my Logitech Edge keyboard while sleeping becaude it would keep waking the kid up no matter the device setting ...

I have the most current bios for my mobo listed on Gigabyte's site. I'm willing to try the beta bios -- but I wonder why, with the bios versions I've used, it wasn't a problem before. I've used 3 different bios versions -- F5, F6 and F7 -- and not had this problem with any previous build of Win.7

Beta bios installed; no change; USB mice not alive if USB allowed to be powered down when computer sleeps. USB mice alive and well if USB NOT powered down when computer sleeps.

Same true for network/router access. If network adapters are powered down when the computer sleeps, they do not recover properly and eventually (meaning within about 10 minutes of use) lock up with a re-boot required. If they are NOT powered down when the computer sleeps, no problem.

I have also just reinstalled the drive on which I had installed build 7100.x64. The USB mice and the network adapters appear to sleep and awaken without problems. Beta bios has no effect, one way or the other. Unfortunately, I do not have any other drives with previous builds installed to test.

Conclusion: There is something different in 7264.x64 that interacts with my GA-EX58-UD5 mobo, independently of bios and/or bios settings, that is triggering a problem with USB mice and the on-board network adapters. And, whatever it is, it was NOT a problem with build 7100.x64, as I have just substituted drives and proved to myself that I did not have a problem with that build.

I'm baffled.