I only use standby. Never been a hibernate fan.
From: Maglinger, Paul [mailto:[email protected]] Sent: Tuesday, June 09, 2009 6:34 AM To: NT System Admin Issues Subject: RE: Windows7 Stop error 0x00000124 You might check and see if you have a BIOS enabled power saving mode along with the Windows. It's been awhile, but I have seen conflicts because of this. Along with the chipset driver, you might also check for the latest BIOS upgrades, too. -Paul _____ From: Len Hammond [mailto:[email protected]] Sent: Tuesday, June 09, 2009 8:18 AM To: NT System Admin Issues Subject: Re: Windows7 Stop error 0x00000124 Yes. I stopped the hibernation (I think). Yes, chipset drivers and maybe check on the BIOS to be sure it's current. On Tue, Jun 9, 2009 at 9:03 AM, Steven M. Caesare <[email protected]> wrote: Reporting the error to MS? See if there's an updated chipset driver (either from Gateway or preferably AMD)? Don't let it hibernate ;-) -sc From: Len Hammond [mailto:[email protected]] Sent: Tuesday, June 09, 2009 8: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 -- Len Hammond CSI:Hartland ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
