Windows Vista BSOD when coming out of sleep mode

I am running an AMD Athlon 64 based home built rig with Vista Home Premium that gives me a Blue Screen when I wake it from S3 sleep mode. Windows says it's a hardware issue but when I run XP Pro on the same machine via a dual boot I never get the BSOD. This problem occurs every day, sometimes more than once a day. I could not find any info on this problem doing the usual searches. Has anyone else experienced this?

 

The error code you receive will be important. Check in Event Viewer.

The term "S3" is usually related to the setting the type of "sleep" set in the BIOS/Startup configuration. Windows has it's own sleep controls and these should work with (override?) those of the BIOS.

I suggest that if you have made changes to the sleep settings in the BIOS/startup configuration, go back in and set them to disabled. Adjust any sleep mode from within Windows.

"Sleep" seems to have been modified in Vista, as compared to previous versions. Read about the sleep function in Help and Support.

Check if you have a particular program open when it goes into sleep mode.

If you, say, have a third party screensaver program running, it may be a contributing factor.

Do you have a good set of chipset drivers installed? Windows will rely on these to put it into and bring it back from sleep mode.

Sorry about the shotgun approach A lot of factors may be involved.

(You may need to do a BIOS upgrade, but leave that as a last resort.)

The "sleep" habits of my computer have changed recently (I was heading to this forum to make a thread), BUT, for me, I like the changes. [? A Windows update has changed something?]

Matt

 

Evan: Thanks for the tip. Today the machine gave up this error code:
http://support.microsoft.com/?kbid=329284

I was over-clocking my CPU 5% over it's norm. D'oh! The thing is it runs smooth as silk in XP, I guess Vista is just picky.

Mattman: yes, I changed the default sleep mode to S3 power saver mode in the BIOS, didn't think it would cause any problems since it worked fine in XP. I think my problem is being caused by over-clocking. I am going to reset the BIOS to it's default and see what happens. Thanks for the help!

 

Well, that didn't take long to disprove! Still getting the BSOD when it wakes up from Sleep Mode. Windows says it created a crash dump log but I'll be darned if I can find it. I did find the Event Viewer but I've never used it before and I am not sure what info I am looking for.

I should have just stayed with XP. Too bad I can't return Vista or sell it on eBay . I'm getting a Windows ME flashback!

 

Hello Brett,

Follow the directions on posting a dump log in this post:
http://www.windowsbbs.com/showthread.php?t=33471

In the Event Viewer look in Apps and serivices > Hardware Events first. Then look in Windows Logs > System.

 

Dump Data

Charles, thanks for the help. Here is the dump log data:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini100607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16514.x86fre.vista_gdr.070627-1500
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11db0
Debug session time: Sat Oct 6 15:09:27.000 2007 (GMT-4)
System Uptime: 0 days 3:18:47.875
Loading Kernel Symbols
........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 85592d18, b2000000, 70f0f}

Probably caused by : ntkrpamp.exe ( nt!WheaReportHwError+10c )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 85592d18, Address of WHEA_ERROR_RECORD structure
Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

Debugging Details:
------------------


WHEA_ERROR_RECORD: !errrec ffffffff85592d18
!errrec ffffffff85592d18
Error Record @ FFFFFFFF85592D18
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*** ***
*************************************************************************
Section Offset : 0x0
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Section Length : 0x0
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Revision : 0x0000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Validation Bits : 0x00
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Flags : 0x00000000
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Section Type : 52455043-0100-FFFF-FFff-010001000000
FRU ID : 00000002-02E8-0000-808d-0F6A4C08C801
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
Severity : 0x0 - WheaErrSevRecoverable
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
FRU Text : CPER

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0x124

PROCESS_NAME: System

CURRENT_IRQL: a

LAST_CONTROL_TRANSFER: from 81fa6e93 to 81cd8569

STACK_TEXT:
81ceef84 81fa6e93 00000124 00000000 85592d18 nt!KeBugCheckEx+0x1e
81ceefa0 81ccec2a 85592d18 85592270 00000001 hal!HalBugCheckSystem+0x37
81ceefc0 81fa6e52 85592270 85592388 81ceeff4 nt!WheaReportHwError+0x10c
81ceefd0 81fa6f73 00000003 85592270 00000000 hal!HalpReportMachineCheck+0x28
81ceeff4 81fa389f 80153000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3
81ceeff4 00000000 80153000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!WheaReportHwError+10c
81ccec2a eb35 jmp nt!WheaReportHwError+0x143 (81ccec61)

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 468308e9

SYMBOL_NAME: nt!WheaReportHwError+10c

FAILURE_BUCKET_ID: 0x124_nt!WheaReportHwError+10c

BUCKET_ID: 0x124_nt!WheaReportHwError+10c

Followup: MachineOwner
---------

eax=81cf483c ebx=85592d18 ecx=0000059e edx=81d293dc esi=81cf4820 edi=85592d18
eip=81cd8569 esp=81ceef68 ebp=81ceef84 iopl=0 nv up di ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000086
nt!KeBugCheckEx+0x1e:
81cd8569 8be5 mov esp,ebp
ChildEBP RetAddr Args to Child
81ceef84 81fa6e93 00000124 00000000 85592d18 nt!KeBugCheckEx+0x1e
81ceefa0 81ccec2a 85592d18 85592270 00000001 hal!HalBugCheckSystem+0x37 (FPO: [Non-Fpo])
81ceefc0 81fa6e52 85592270 85592388 81ceeff4 nt!WheaReportHwError+0x10c
81ceefd0 81fa6f73 00000003 85592270 00000000 hal!HalpReportMachineCheck+0x28 (FPO: [Non-Fpo])
81ceeff4 81fa389f 80153000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3 (FPO: [Non-Fpo])
81ceeff4 00000000 80153000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77 (FPO: TSS f10f10:0)
start end module name
80403000 8040a000 pciide pciide.sys Thu Nov 02 04:51:35 2006 (4549B197)
8040a000 80419000 volmgr volmgr.sys Thu Nov 02 04:51:44 2006 (4549B1A0)
80419000 80421000 msisadrv msisadrv.sys Thu Nov 02 04:35:08 2006 (4549ADBC)
80421000 8042a000 WMILIB WMILIB.SYS Thu Nov 02 04:54:53 2006 (4549B25D)
8042a000 8046d000 acpi acpi.sys Thu Nov 02 04:35:03 2006 (4549ADB7)
8046d000 8047a000 WDFLDR WDFLDR.SYS Thu Nov 02 04:54:05 2006 (4549B22D)
8047a000 804b5000 CLFS CLFS.SYS Thu Nov 02 04:30:52 2006 (4549ACBC)
804b5000 804bd000 BOOTVID BOOTVID.dll Thu Nov 02 05:39:29 2006 (4549BCD1)
804bd000 804c6000 PSHED PSHED.dll Thu Nov 02 05:42:51 2006 (4549BD9B)
804c6000 804ce000 kdcom kdcom.dll Thu Nov 02 05:42:20 2006 (4549BD7C)
80602000 8060f000 nvstor nvstor.sys Sat Dec 23 11:07:25 2006 (458D543D)
8060f000 80617000 atapi atapi.sys Thu Nov 02 04:51:34 2006 (4549B196)
80617000 80661000 volmgrx volmgrx.sys Thu Nov 02 04:51:54 2006 (4549B1AA)
80661000 8066f000 PCIIDEX PCIIDEX.SYS Thu Nov 02 04:51:34 2006 (4549B196)
8066f000 8067f000 mountmgr mountmgr.sys Thu Nov 02 04:51:06 2006 (4549B17A)
8067f000 806a4000 pci pci.sys Thu Nov 02 04:35:13 2006 (4549ADC1)
806a4000 8071f000 Wdf01000 Wdf01000.sys Thu Nov 02 04:54:18 2006 (4549B23A)
8071f000 80800000 CI CI.dll Thu Nov 02 05:42:45 2006 (4549BD95)
81c00000 81fa1000 nt ntkrpamp.exe Wed Jun 27 21:03:37 2007 (468308E9)
81fa1000 81fd5000 hal halmacpi.dll Thu Nov 02 04:30:18 2006 (4549AC9A)
82403000 8240c000 crcdisk crcdisk.sys Thu Nov 02 04:52:27 2006 (4549B1CB)
8240c000 8241b000 mup mup.sys Thu Nov 02 04:31:04 2006 (4549ACC8)
8241b000 8242a000 partmgr partmgr.sys Thu Nov 02 04:51:47 2006 (4549B1A3)
8242a000 82432000 spldr spldr.sys Wed Oct 25 18:40:44 2006 (453FE7EC)
82432000 8245d000 msrpc msrpc.sys Thu Nov 02 04:50:16 2006 (4549B148)
8245d000 82561000 ndis ndis.sys Thu Nov 02 04:57:33 2006 (4549B2FD)
82561000 82571000 fileinfo fileinfo.sys Thu Nov 02 04:36:47 2006 (4549AE1F)
82571000 825a2000 fltmgr fltmgr.sys Thu Nov 02 04:30:58 2006 (4549ACC2)
825a2000 825e2000 storport storport.sys Thu Nov 02 04:51:45 2006 (4549B1A1)
825e2000 82600000 ataport ataport.SYS Thu Nov 02 04:51:34 2006 (4549B196)
8260e000 8261f000 disk disk.sys Thu Nov 02 04:51:40 2006 (4549B19C)
8261f000 82655000 volsnap volsnap.sys Thu Nov 02 04:52:11 2006 (4549B1BB)
82655000 826bf000 ksecdd ksecdd.sys Thu Nov 02 04:43:45 2006 (4549AFC1)
826bf000 827c7000 Ntfs Ntfs.sys Thu Nov 02 04:31:39 2006 (4549ACEB)
827c7000 82800000 NETIO NETIO.SYS Thu Nov 02 04:58:01 2006 (4549B319)
829ba000 829db000 CLASSPNP CLASSPNP.SYS Thu Nov 02 04:51:34 2006 (4549B196)
829db000 82a00000 ecache ecache.sys Thu Nov 02 04:52:42 2006 (4549B1DA)
83218000 83219380 swenum swenum.sys Thu Nov 02 04:51:15 2006 (4549B183)
8321a000 8321bc00 lv302af lv302af.sys Wed Jul 18 20:10:59 2007 (469EAC13)
83220000 83221700 USBD USBD.SYS Thu Nov 02 04:55:00 2006 (4549B264)
83296000 8329aa00 LVPr2Mon LVPr2Mon.sys Wed Jul 18 20:08:48 2007 (469EAB90)
83326000 8332e000 NuidFltr NuidFltr.sys Mon Jan 15 20:18:28 2007 (45AC27E4)
8332e000 83336000 mouhid mouhid.sys Thu Nov 02 04:51:12 2006 (4549B180)
8338e000 83396000 RDPCDD RDPCDD.sys Thu Nov 02 05:02:01 2006 (4549B409)
83396000 8339e000 rdpencdd rdpencdd.sys Thu Nov 02 05:02:01 2006 (4549B409)
8a007000 8a00e000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 13:11:27 2006 (44D7743F)
8a031000 8a038000 parvdm parvdm.sys Thu Nov 02 04:51:23 2006 (4549B18B)
8a05b000 8a062000 Null Null.SYS Thu Nov 02 04:51:05 2006 (4549B179)
8a062000 8a069000 Beep Beep.SYS Thu Nov 02 04:51:03 2006 (4549B177)
8a069000 8a06f380 HIDPARSE HIDPARSE.SYS Thu Nov 02 04:55:00 2006 (4549B264)
8a070000 8a080000 NDProxy NDProxy.SYS Tue Jul 03 21:28:13 2007 (468AF7AD)
8a110000 8a11f280 ohci1394 ohci1394.sys Thu Nov 02 04:55:16 2006 (4549B274)
8a160000 8a170000 HIDCLASS HIDCLASS.SYS Thu Nov 02 04:55:00 2006 (4549B264)
8b006000 8b02b000 drmk drmk.sys Thu Nov 02 05:20:49 2006 (4549B871)
8b02b000 8b058000 portcls portcls.sys Thu Nov 02 04:55:02 2006 (4549B266)
8b058000 8b063000 fdc fdc.sys Thu Nov 02 04:51:33 2006 (4549B195)
8b063000 8b070080 1394BUS 1394BUS.SYS Thu Nov 02 04:55:12 2006 (4549B270)
8b071000 8b0bc000 WMP54Gv41x86 WMP54Gv41x86.sys Mon Dec 11 09:38:10 2006 (457D6D52)
8b0bc000 8b0d4000 cdrom cdrom.sys Thu Nov 02 04:51:44 2006 (4549B1A0)
8b0d4000 8b0e2000 usbehci usbehci.sys Thu Nov 02 04:55:04 2006 (4549B268)
8b0e2000 8b11f000 USBPORT USBPORT.SYS Thu Nov 02 04:55:09 2006 (4549B26D)
8b11f000 8b129000 usbohci usbohci.sys Thu Nov 02 04:55:05 2006 (4549B269)
8b129000 8b138000 amdk8 amdk8.sys Thu Nov 02 04:30:18 2006 (4549AC9A)
8b138000 8b143000 tunnel tunnel.sys Wed Jun 06 22:57:03 2007 (466773FF)
8b150000 8b15a000 dump_diskdump dump_diskdump.sys Thu Nov 02 04:51:36 2006 (4549B198)
8b15a000 8b162360 aswTdi aswTdi.SYS Fri Jul 27 17:59:55 2007 (46AA6ADB)
8b163000 8b16c000 tunmp tunmp.sys Wed Jun 06 22:56:53 2007 (466773F5)
8b175000 8b17e000 lknuhst lknuhst.sys Thu Dec 14 22:11:24 2006 (4582125C)
8b17e000 8b187000 Fs_Rec Fs_Rec.SYS Mon Apr 16 21:26:39 2007 (4624224F)
8b199000 8b1a2000 rasacd rasacd.sys Thu Nov 02 04:58:13 2006 (4549B325)
8b1a2000 8b1ab000 hidusb hidusb.sys Thu Nov 02 04:55:01 2006 (4549B265)
8b1b4000 8b1bd000 asyncmac asyncmac.sys Thu Nov 02 04:58:10 2006 (4549B322)
8b1c0000 8b1ea000 ks ks.sys Thu Nov 02 04:51:18 2006 (4549B186)
8b405000 8b4a2000 dxgkrnl dxgkrnl.sys Mon Jul 02 21:01:10 2007 (46899FD6)
8b4a2000 8b4ae000 vga vga.sys Thu Nov 02 04:53:56 2006 (4549B224)
8b4ae000 8b600000 P17 P17.sys Mon Feb 05 04:10:32 2007 (45C6F488)
8b802000 8b80c000 mssmbios mssmbios.sys Thu Nov 02 04:35:13 2006 (4549ADC1)
8b80c000 8b816000 serenum serenum.sys Thu Nov 02 04:51:25 2006 (4549B18D)
8b816000 8b830000 serial serial.sys Thu Nov 02 04:51:29 2006 (4549B191)
8b830000 8b83b000 TDI TDI.SYS Thu Nov 02 04:58:46 2006 (4549B346)
8b83b000 8b846000 ndistapi ndistapi.sys Tue Jul 03 21:28:09 2007 (468AF7A9)
8b851000 8b85c000 kbdclass kbdclass.sys Thu Nov 02 04:51:09 2006 (4549B17D)
8b85c000 8b867000 mouclass mouclass.sys Thu Nov 02 04:51:09 2006 (4549B17D)
8b867000 8b872000 Msfs Msfs.SYS Thu Nov 02 04:30:56 2006 (4549ACC0)
8b87d000 8b888000 point32k point32k.sys Wed Nov 08 02:02:38 2006 (4551810E)
8b888000 8b893000 tcpipreg tcpipreg.sys Thu Nov 02 04:57:46 2006 (4549B30A)
8b8f0000 8b8fd000 watchdog watchdog.sys Thu Nov 02 04:37:44 2006 (4549AE58)
8b8fd000 8b9ff680 nvmfdx32 nvmfdx32.sys Thu May 03 20:41:02 2007 (463A811E)
8ba04000 8ba0e000 flpydisk flpydisk.sys Thu Nov 02 04:51:32 2006 (4549B194)
8ba0e000 8ba1b000 umbus umbus.sys Thu Nov 02 04:55:24 2006 (4549B27C)
8ba1b000 8ba2e000 raspptp raspptp.sys Thu Nov 02 04:58:14 2006 (4549B326)
8ba2e000 8ba3d000 raspppoe raspppoe.sys Thu Nov 02 04:58:12 2006 (4549B324)
8ba3d000 8ba60000 ndiswan ndiswan.sys Thu Nov 02 04:58:13 2006 (4549B325)
8ba60000 8ba77000 rasl2tp rasl2tp.sys Thu Nov 02 04:58:13 2006 (4549B325)
8ba77000 8baa2000 msiscsi msiscsi.sys Thu Nov 02 04:52:40 2006 (4549B1D8)
8baa2000 8bab0000 Npfs Npfs.SYS Thu Nov 02 04:30:57 2006 (4549ACC1)
8bab0000 8bac8000 parport parport.sys Thu Nov 02 04:51:29 2006 (4549B191)
8bac8000 8c1ffdc0 nvlddmkm nvlddmkm.sys Fri Jul 06 17:05:06 2007 (468EAE82)
8c205000 8c21b000 pacer pacer.sys Tue Jul 03 21:27:33 2007 (468AF785)
8c21b000 8c22f000 smb smb.sys Thu Nov 02 04:57:10 2006 (4549B2E6)
8c22f000 8c244000 tdx tdx.sys Thu Nov 02 04:57:34 2006 (4549B2FE)
8c244000 8c25d000 fwpkclnt fwpkclnt.sys Thu Nov 02 04:57:26 2006 (4549B2F6)
8c295000 8c298b20 aswRdr aswRdr.SYS Fri Jul 27 18:00:37 2007 (46AA6B05)
8c2bd000 8c2de000 VIDEOPRT VIDEOPRT.SYS Thu Nov 02 04:54:07 2006 (4549B22F)
8c2de000 8c2ed000 lknuhub lknuhub.sys Thu Dec 14 22:11:15 2006 (45821253)
8c2ed000 8c321000 usbhub usbhub.sys Thu Nov 02 04:55:20 2006 (4549B278)
8c321000 8c32e000 crashdmp crashdmp.sys Thu Nov 02 04:51:36 2006 (4549B198)
8c32e000 8c33b000 dump_nvstor dump_nvstor.sys Sat Dec 23 11:07:25 2006 (458D543D)
8c3b0000 8c3bd000 hiber_nvstor hiber_nvstor.sys Sat Dec 23 11:07:25 2006 (458D543D)
8c3f1000 8c400000 termdd termdd.sys Thu Nov 02 05:02:00 2006 (4549B408)
8ca08000 8ca4f000 afd afd.sys Thu Nov 02 04:58:41 2006 (4549B341)
8ca4f000 8cb20000 tcpip tcpip.sys Thu Nov 02 04:58:31 2006 (4549B337)
8cb20000 8cb2e000 netbios netbios.sys Thu Nov 02 04:57:26 2006 (4549B2F6)
8cc0a000 8cc1c000 USBSTOR USBSTOR.SYS Fri Apr 27 22:39:34 2007 (4632B3E6)
8cc2c000 8cc43000 usbccgp usbccgp.sys Thu Nov 02 04:55:11 2006 (4549B26F)
8cc43000 8cc52000 monitor monitor.sys Thu Nov 02 04:54:05 2006 (4549B22D)
8cc83000 8cc8d000 Dxapi Dxapi.sys Thu Nov 02 04:38:17 2006 (4549AE79)
8cc97000 8cca1000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528)
8ccbf000 8ccc9000 ndisuio ndisuio.sys Thu Nov 02 04:57:22 2006 (4549B2F2)
8ccfb000 8cd05000 hiber_diskdump hiber_diskdump.sys Thu Nov 02 04:51:36 2006 (4549B198)
8cd5f000 8cd76000 dfsc dfsc.sys Thu Nov 02 04:31:04 2006 (4549ACC8)
8cd76000 8cd80000 nsiproxy nsiproxy.sys Thu Nov 02 04:57:30 2006 (4549B2FA)
8cd80000 8cdbb000 rdbss rdbss.sys Thu Nov 02 04:31:24 2006 (4549ACDC)
8cdbb000 8cdce000 wanarp wanarp.sys Tue Jul 03 21:28:16 2007 (468AF7B0)
8cdce000 8ce00000 netbt netbt.sys Thu Nov 02 04:57:18 2006 (4549B2EE)
90800000 909ff000 win32k win32k.sys unavailable (00000000)
90c5e000 90c6f780 usbaudio usbaudio.sys Thu Nov 02 04:55:04 2006 (4549B268)
90daf000 90db8000 kbdhid kbdhid.sys Thu Nov 02 04:51:12 2006 (4549B180)
90dc1000 90dc9900 LVUSBSta LVUSBSta.sys Wed Jul 18 20:10:33 2007 (469EABF9)
938bf000 939f5680 LV302V32 LV302V32.SYS Wed Jul 18 20:11:37 2007 (469EAC39)
939f6000 93bff700 LVMVDrv LVMVDrv.sys Fri Jul 20 03:05:24 2007 (46A05EB4)
93ffe000 941ff680 LVcKap LVcKap.sys Fri Jul 20 03:05:31 2007 (46A05EBB)
94250000 94260000 lltdio lltdio.sys Thu Nov 02 04:56:48 2006 (4549B2D0)
94447000 9445d000 aswMonFlt aswMonFlt.sys Fri Jul 27 11:14:18 2007 (46AA0BCA)
9445d000 94478000 luafv luafv.sys Thu Nov 02 04:33:07 2006 (4549AD43)
944e5000 944f8000 rspndr rspndr.sys Thu Nov 02 04:56:48 2006 (4549B2D0)
94598000 945c0000 fastfat fastfat.SYS Thu Nov 02 04:30:49 2006 (4549ACB9)
94800000 94809000 TSDDD TSDDD.dll unavailable (00000000)
94810000 9481e000 cdd cdd.dll unavailable (00000000)
95301000 95317000 cdfs cdfs.sys Thu Nov 02 04:30:50 2006 (4549ACBA)
95522000 95600000 peauth peauth.sys Mon Oct 23 04:55:32 2006 (453C8384)
96295000 962c0000 nwifi nwifi.sys Thu Nov 02 04:55:41 2006 (4549B28D)
97a3e000 97a59000 srvnet srvnet.sys Thu Nov 02 04:31:43 2006 (4549ACEF)
97a99000 97b27000 spsys spsys.sys Wed Oct 25 18:43:28 2006 (453FE890)
98201000 98225000 srv2 srv2.sys Thu Nov 02 04:31:46 2006 (4549ACF2)
98225000 98237000 mrxsmb20 mrxsmb20.sys Thu Nov 02 04:31:16 2006 (4549ACD4)
98237000 98270000 mrxsmb10 mrxsmb10.sys Thu Nov 02 04:31:25 2006 (4549ACDD)
982b0000 982ce000 mrxsmb mrxsmb.sys Thu Nov 02 04:31:20 2006 (4549ACD8)
982ce000 982ed000 mrxdav mrxdav.sys Thu Nov 02 04:31:24 2006 (4549ACDC)
982ed000 98301000 mpsdrv mpsdrv.sys Wed Jun 06 22:55:55 2007 (466773BB)
98301000 9831a000 bowser bowser.sys Thu Nov 02 04:31:11 2006 (4549ACCF)
9835a000 983c0000 HTTP HTTP.sys Thu Nov 02 04:57:06 2006 (4549B2E2)
985b4000 98600000 srv srv.sys Thu Nov 02 04:31:55 2006 (4549ACFB)

Unloaded modules:
83366000 8336e000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
8b1ea000 8b1f7000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
8b150000 8b15a000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
8b143000 8b150000 dump_nvstor.
Timestamp: unavailable (00000000)
Checksum: 00000000
8b187000 8b190000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
8320a000 8320c000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
8b17e000 8b187000 LVUSBSta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

"Your debugger is not using the correct symbols "

I expect you need to go to Start(Orb) -> Computer -> open C: -> Organize (menu), create a new folder Symbols.

This will create the C:\Symbols folder that the debugger is looking for (Edit: In the debugger, you may need to change the path for the symbols back to C:\Symbols).

Matt

 

Ya got me, mattman, I have a C:/symbols folder, Don't know how to change the path in the debugger tool.

 

Look in the File menu -> Symbol File Path. It should read SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

You need to be connected to the internet when you run the debugger.

Matt

 

Thanks mattman. I set the proper path but I still get the same results. I guess I am just not running the program properly. I followed the directions from the thread linked above and I'm always connected to the internet but when I run the debugwiz.exe I keep getting the same result. Am I supposed to do something more with the MS WinDbg program other than install it and configure the path? I'm lost. Thanks again.

 

In the lines after "Your debugger is not using the correct symbols" it talks about "public OS symbols ". I just might consider that a program is being run that Windows does have the symbols for, which may mean a "backyard" built program or maybe some type of dodgy program running in the background.

I would look through a Hijack This log, but I am somewhat of a novice reading them. Post a Hijack This log here if you like. If one of the experienced readers is following this, they may see something, otherwise I will try to highlight anything I see and you could ask for it to be checked in the Security forum [let us know if you need help with Hijack This].

Matt

 

Apart from the areas I mentioned in the last post, have you investigated an updated set of Vista drivers for the system:

"Power Control" (sleep, hibernation, turn off monitor, drives, etc) is run through the chipset drivers. After you installed Vista, did you run the drivers disk that came with the motherboard? Did the drivers disk that was supplied with the motherboard have drivers for Vista? If not, go to the manufacturer's website and look for current or specific Vista drivers.

If your motherboard is not able to utilise (cope with) what Vista tells it to do, you may need to look at why. You may need to upgrade the BIOS.

So...my checks would be to investigate if software was working correctly (no junk running in the background), if Vista specific drivers have been installed, then, look at if the motherboard's BIOS can work with how Vista wants to run the power control options (a BIOS upgrade).

Did you notice exactly when this problem started?

Matt

 

mattman: yes, I did upgrade the mobo drivers after my install. I noticed the problem soon after I first enabled S3 mode via the BIOS. It does not crash in XP, only when I boot to Vista. I enabled S3 mode because this rig is loud and I wanted to save a buck or 2 on my electric bill.

Arie: Yes, the error BugCheck 124.... is always the same.

The event logs for event 1003:
Log Name: System
Source: Microsoft-Windows-Dhcp-Client
Date: 10/8/2007 6:45:05 PM
Event ID: 1003
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Brett-PC
Description:
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 001A70A38764. The following error occurred:
The operation was canceled by the user.. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.


Event 1002:

Log Name: System
Source: Microsoft-Windows-Dhcp-Client
Date: 7/19/2007 6:13:50 PM
Event ID: 1002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Brett-PC
Description:
The IP address lease 0.0.0.0 for the Network Card with network address 001109ED7BEE has been denied by the DHCP server 0.0.0.0 (The DHCP Server sent a DHCPNACK message).

Event 1001:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 9/18/2007 7:32:14 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Brett-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x00000000, 0x85594d18, 0xb2000000, 0x00070f0f). A dump was saved in: C:\Windows\MEMORY.DMP.

 

As I said, I would not use the S3 setting, both Win XP and Vista's power controls should take control of power saving.

To me, it would appear that Win XP can work with S3 on your computer, Vista finds problems with it. I am finding Vista has changed it's sleep habits. My Vista computer (desktop) can now go into an apparent "shutdown ", but I am at exactly the same place as soon as the monitor warms up after pressing the power button.

Using S3, it seems you are trying to override Windows power controls (I expect S3 is for use with operating systems that are not able to control power saving themselves, DOS might be an example).

I let Windows control the power saving settings. You can adjust these in Control Panel -> Power Options. Vista appears to have more options (different options) than Win XP.

For me, Vista's power saving is working better than I expected.

Matt

 

Arie: Thanks for the help. I just wonder why it doesn't occur in XP?

mattman: I wanted to use S3 mode rather than S1 so it would power down the fans and HDDs. My rig is very loud when running so I wanted it to go to a quiet power saving sleep mode. All I did was to set S3 as default sleep mode in the BIOS, that was before installing Vista. I could try to un-do this and then see how Vista puts the machine to sleep. You said it works fine for you, I will give it a try. Otherwise I'm out of ideas, except that if I can't get Vista to be stable when coming out of sleep mode I am going back to XP.

Thanks for all your help! This is a great forum.

 

I see your dilemma (catch 22).

Either way, you should check if the S3 setting is the cause.

I don't know exactly why the power saving system on my Vista computer changed from "idling" (fans/LEDs running) to apparent shutdown. I did not change any settings.

Note that I have a Readyboost drive and I am wondering that if, rather than saved system settings needing to retrieved from the HDD, coming out of Sleep, they are being retrieved from the Readyboost drive.

Anyway, I hope it works for you.

Matt