7805u Windows 7 bug - NO restart after hibernation.

When Windows 7 is in hibernation or sleep and then when you make Windows 7 go out of hibernation or sleep... my 7805u will NOT restart. I end up with a dark blank screen... and the laptop is still on.

The only fix is to disable the firewire/1394 port in the device manager.
Or never to hibernate/sleep. But I would like the option to hibernate/sleep and to use the firewire port.

I would think everybody with Windows 7 on the 7805u has this problem.

here is how to test it:

1. Hibernate or Sleep
2. Press the power button (to get out of hibernation/sleep)
3. Log On
4. Restart
you will end up with a blank screen on the restart.

and when you do get the blank screen.... all you need to do is hold down the power button to turn off the computer. Then when you turn it back on, Windows 7 will start-up with no glitches.

Now if you disable the firewire/1394... then it will restart okay after hibernation.

 

I cant replicate this with a 6860, so it might just be with the 780x series.

But then again i had to actually find hibernation because i never use it (just as quick to power down/power up for me)

Have you checked around for a better firewire driver? Win7 still isnt official quite yet so it might just be a relatively poor driver screwing up with the hibernation/sleep event.

What do you use your firewire for? (just curious)

 

No, mine works perfectly everytime and my firewire is enabled, perhaps you have some kind of driver problem.

 

I have a Canon HD Video Camera. and the camera is NOT connected when I get this Glitch.

I just can't believe I am the only person with this glitch.

just put your 7805u in sleep mode and also try hibernate if you want.
then get out of sleep mode with the power button... then try a restart.

my 7805u has the Windows 7 Enterprise trial installed. And the 178.81 Nvidia GPU Driver.

 

what GPU driver are you using?

 

I'm using 186.81 and windows 7 RC

 

I bet if someone has the exact same version of windows and video driver I have with NO raid 0... you will have the same glitch.

 

I dont use hibernate, but I do use sleep mode quite offten, I have a 7805u with Win7, and have never had a problem getting it to wake up.

 

I never did say I had problems waking up from sleep mode...

Please wake up from sleep mode... then try restarting your 7805u
then you will see the glitch.

and if you don't see it... you can have my laptop! this is how sure I am it will happen if tested right.

 

Ill have to give it a shot tonight when I get home as I am at work right now.

 

thanks.

Windows 7 users test:
1. Hibernate or Sleep - Close the lid for a few seconds.
2. Press the power button (to get out of hibernation/sleep) - or Open the lid.
3. Log On
4. Restart

after restart post the results.

 

I'll have to try to hunt down an Enterprise Trial. But as of now with my cousins 7805 with Win7 Ultimate and the 178 driver i still cant replicate the glitch. I can sleep the computer and then restart and i can hibernate the computer and then restart.

I still think its a driver issue instead of a glitch. have you tried uninstalling and then reinstalling the Firewire driver?

 

I just did.... no luck. i just can't believe i am the only one with this glitch.

 

That is odd... is there an error report recorded? Or is your system just completely failing with it?

There are hibernation glitches in Win7 but from what i can tell reading over the threads on it, that it does actually seem random. Some people have it and some dont. But with 30+ builds that have been released its a wonder any of us have good info to go on.

7100RC is stable for me so until i get Signature Ultimate in the mail i just have stopped trying different versions

 

During the restart it shuts down okay but does not boot. it just stays on with a dark blank screen.

i hope my 7805u is not defective. Because if I am the only person with this glitch... I may jump off a bridge.

 

I haven't bothered to check specifically, but I frequently "sleep" my system by closing the lid, and in fact Win7 reboots to a black screen if I choose reboot.

 

You are Not the ONLY person with the glitch. Mine is similar. It hibernates fine and comes out fine. Sleeps fine and comes out fine. But when I try to Restart, sounds exactly like what you said. Black screen with LED's? That's me. Just when trying to restart though. Shutdown is good. Bout to try right now. Gonna shutdown. Then start up. Then restart. Then sleep. Restart. Hibernate. Restart. I'll let you know.

 

Spot on! Shutdown-Check. Power on-Check. Restart-Check. Sleep-Check. Restart-Get shutting down screen and BLACK. Nothing else. Same with Hibernate. Has to be chipset right? Only does it AFTER!!! hibernate or sleep. Too weird......

 

Ok, what is happening is the bios is not posting after a soft restart. You can blame this on PnP. When you hybernate or sleep you turn off alot of hardware. When it wakes Windows starts the hardware and assigns resources. The resources are apparently somehow different than the system initilization. When the bios goes to intialize at start it fails and there you are, stuck on a blank screen........

 

Soooooo, what's the solution? I haven't a clue.

 

disabling the 1394 firewire device will fix the glitch.

or only use Shutdown after loging in from sleep/hibernate mode.

another option is to Never sleep or hibernate.

I am just glad this happens to most 7805u's with Windows 7.

for a while there I thought my laptop was defective.

I believe this is a Glitch we can all live with... but I still would like to find a better solution.

 

If you can disable the Firewire and fix this problem i still say its a Driver issue being slightly incompatible with Win7 instead of a glitch in the OS.

But i would recommend sending the report up the food chain to Microsoft. The more issues they know about the more they can fix with patches and updates as the OS becomes official.

We still have 21 days before we're technically even supposed to be running the OS so having all of this beta test info helps them stabilize the OS even more. (but i assume when more component companies fully support Win7 alot of these issues will be fixed)

 

It isn't a glitch in the OS, that is the design. it is the hardware/driver/bios. Actually two bios's the hardware bios and windows bios. I said blame PNP meaning the capability is the root cause that started all of this.........

Edit; Maybe Gateway will issue a 9c.18.00 bios to fix this and with true quad core support for all......

 

the OS supplied the buggy 1394 firewire driver.
the driver is dated 2006 and is certified by Microsoft and works perfect with Vista but not Windows 7.

So it is a Windows 7 driver bug. right?

I think calling it a Windows 7 bug is okay, just not specific.

 

The OS specific issue works with other systems without issue but ours has one. It is much more likely a Gateway issue and not an M$ one. I have seen multiple bios/driver revisions based on similar fixes. Sorry hate to date myself here..........

And to tell me you haven't seen other WHQL drivers that haven't had one issue or another????????????

 

Hope so on the Quad. But i think it's more than just BIOS to fix that problem. It's a different Mobo. Disabling Firewire now. Who uses it anyway?

 

Yeah, I know, but I can have a dream..................

 

Same problem here with my 7811 since I've istalled win 7 ultimate 64 I've tried all kind differet thinks and drivers no luck so I went back to Vista ultimate 64
it works great f win 7!

 

I've reistalled a new copy of windows 7 x64 Build 7600 RTM and same problem
before even istalling any drivers I clicked on hybernation came out from it then clickrd on restart and ir woul not restart just hanged there I had to shut the laptop manually and restart it again.So again I went back to Vista 64.
has anyone found a solution for this S.B. of a problem yet?

 

Do what RobbyMa says. You prolly don't even use Firewire.

Worked perfectly! Thanks...

 

Disabling the 1394 firewire device will fix the glitch
Tanks pmassey31545 and tanks to RobbyMa I don't use the firewire.
It work great now!!!

 

Will finally I found the solution of this problem without disabling the 1394 firewire
Just update change the driver!! And everything works great on my P-7811
Cheers!!

http://www.microsoft.com/whdc/connect/1394_Windows7.mspx

 

Is this supposed to link to a driver? All I get is an about firewire in windows 7 and a document link

 

UPDATE TO THIS DRIVER : 1394 OHCI CompliantHostController(Legacy)

1- Start menu

2- Right click "Computer" select "manage"

3- Select "Device manager" from the left hand pane

4- Expand the "IEEE 1394 Bus Host Controllers" node in the device tree on the right hand pane

5- Right click the host controller node select "Update driver software ..."

6- select "Browse my computer for driver software"

7- select "let me pick from a list of device driver on my computer ..." and you should see:

1394 OHCI CompliantHostController(Legacy)
Update to that that’s it

 

So you really are reverting to the legacy controler. Maybe one day Gateway will update the bios so we can use the supposed enhanced features of the port, then again does anyone really care or need them?

 

Yes to your question for what I read a lot of people have been having problem with the new driver especially with some older 1394 devices
with windows 7 X64 and X86.
This solved the problem with the Sleep and Hibernation not having the computer restarting. I just hate unresolved issues

 

What I meant was does anyone really need the "Enhanced Feature Set" of the new drivers for Windows 7 that would make Gateway update their bios? I wouldn't think with our chipsets that these should be considered "Older 1394 Devices/Ports". This should also be true as the drivers load and work, other than the restart issue, just fine. At the least we don't seem to have other compatability issues with the port and Windows 7.

So it is a still an unresolved issue as far as we do not have the again "Added feature set", but the bypass resolution you have is great for those not needing the Windows 7 enhancement and can suffice with "Legacy".........

 

The only features that i can remember that the 1394 does is give a slight boost in throughput (which hard drives cant keep up with) and stabalizes the power range that the firewire port uses.

Though their might be others that i dont know about/remember.

If the legacy driver fixes this issue then i would say that its a done deal, unless people are hooking up SSD RAIDs through the port

 

Agreed, the resolution is great. When I get to my system I will definately apply it. My only stipulation, albeit one that may never matter, is Gateway/M$ should hash out a PROPER fix. Now will this ever get done as the P78xx's were not designed as a Windows 7 system.........

 

It will probably get updated pretty quickly, as alot of people will use the same 1394 port in their motherboards, so it shouldnt be too long of a wait.

We'll never get the update from gateway more than likely but the driver itself will probably apprear pretty soon.

If nothing else when gateway releases the next FX (if they ever do) Gateway has a bad habit of reusing hardware so the new FX systems driver will more than likely work on all of the 78xx systems as well

 

I am sure Gateway is not the only manufacturer using the specific port hardware. Unless it is a hardware/driver conflict we will then most likely see Gateway doing a bios update. I hadn't seen other systems with this issue so I lean towards a Gateway rather than hardware incompatability issue. I could easily be wrong here, have been so before and will definately be again..............

 

That is a distinct possibility, gateway could have had arima(unfounded, but i assume arima is the supplier of these notebooks to gateway) mod the system as to somehow make it more compatible with its wants and ended up geing less compatible with a newer OS.

Stranger things have happened in Gateway land

 

Not to revive an old thread but to date apparently no fix for this issue, at least with 9c.17.00 bios. I wonder though if the newer bios versions addess this? I haven't been able to winflash my bios and maybe would DOS FLASH if it were confirmed a newer bios solves this.

While the legacy driver isn't an issue, at least as far as I can tell, I would still rather the default driver................

 

Still no fix?

 

None I know of. It would have been nice to use the proper driver but oh well, the legacy one works out if you do not use the port. I am not sure what you loose though by using the legacy drivers.............