Thanks. I have disabled the hibernation in W7. There is no option in the BIOS to disable C1E. Seems like a pretty basic BIOS. I may have to look again.
There is supposedly a build 7200 out there as well. Were either 7127 or 7200 officially released by MS or somehow just "leaked" out? I found 7200 on the web but am not comfortable as to the d/l source indicated in the post where I found the link. On Tue, Jun 9, 2009 at 9:51 AM, Charlie Kaiser <charl...@golden-eagle.org>wrote: > You might try disabling C1E Enhanced Halt State in the BIOS. Bios updates, > for sure. You might also try a wipe and reinstall with build 7127... > But definitely disable hibernation. When bears wake up from hibernation, > they're really ornery. So is Windows. LOL... > > *********************** > Charlie Kaiser > charl...@golden-eagle.org > Kingman, AZ > *********************** > > > -----Original Message----- > > From: Len Hammond [mailto:lenhammo...@gmail.com] > > Sent: Tuesday, June 09, 2009 5:30 AM > > To: NT System Admin Issues > > Subject: Windows7 Stop error 0x00000124 > > > > I have a laptop with Windows 7 rc1 (build 7100) exhibiting a > > lockup with Stop 0x00000124. The crash is preceded with DNS > > errors and nearby is an error inplicating a failed processor. > > This is a Gateway M1626 laptop with an AMD Turion x2 @ 2.0ghz > > with 4gb RAM. It seems to have this group of errors while > > trying to come out of hibernate mode. Event logs indicate > > that it went to sleep and then into hibernation over night > > and when I hit the power switch to bring it back to life it > > comes up with mouse & keyboard frozen. I have to hard power > > down and then power it up again to get anywhere. Doing so > > brings up the DOS question about coming back from an improper > > shutdown. It comes back with the normal messages about a > > problem and wants to phone home to find a solution. If you > > let it phone home it does not find a solution. It runs fine > > for hours if you don't let it hibernate. I think I will stop > > the hibernation from happening and see if the problem goes > > away. Maybe I can isolate it to a hibernation issue. > > > > Anyone have thoughts? Something else to try, maybe? > > > > > > -- > > Len Hammond > > CSI:Hartland > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > -- Len Hammond CSI:Hartland ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
