[Solved]vista sleep and wakeup problom

**jaleo** · December 11, 2008

Sorry for my poor english,

I just install vista ultimate x64 (with sp1), but i have a trouble these days.

vista can sleep after 1 hour, but when i wakeup it, and few minutes later,computer will restart automatically.

here is information. and attached file is error xml

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.0.6001.2.1.0.256.1

Locale ID: 1033

Additional information about the problem:

BCCode: 4e

BCP1: 0000000000000099

BCP2: 000000000006AAAC

BCP3: 0000000000000002

BCP4: FFFFFFFFFFFFFFFF

OS Version: 6_0_6001

Service Pack: 1_0

Product: 256_1

Please help me .

Thanks in advance.

error.xml

Edited December 16, 2008 by jaleo

**Tripredacus** · December 11, 2008

Please list your hardware, also if your hardware is Vista x64 certified.

**MagicAndre1981** · December 11, 2008

please provide the dmp file, so that we can analyze the Dump

**jaleo** · December 12, 2008

Upload my dump file.

My computer:

Intel E8200

Gigabyte EP45C-DS3 (S3 enabled)

A-Data DDR2-800 2*2GB 800M 4-4-4-12

GF6600GT

ST3500320NS 500GB

ST3320620AS 320GB

Matrox 6B200M0 200GB

Intel Pro/100 Server Adapter (550EY Server)

Pioneer DVD-ROM 227P

Pioneer DVD-RW DVR-112 ATA Device

OS: vista ultimate sp1 x64

AHCI enabled

dump.zip

**cluberti** · December 12, 2008

All of these are memory_corruption/driver or high IRQL/driver bugchecks, indicating a probable driver causing the issue - if they were all memory corruption I'd blame RAM, but the 4E (PFN corrupt) dump leads me to believe it's a driver. The first three are STOP 0xD3 bugchecks, meaning a driver tried to access a memory address that was invalid or paged out to disk. The problem with minidumps are that the callstacks are usually not entirely there, especially in D3 bugchecks. However, I can see that the 3 D3 dumps are all going through win32k.sys' CallHook function before the machine crashes, meaning some driver has a global hook that win32k.sys is passing processing off to.

In looking at the one STOP 0x4E dump (PFN_LIST_CORRUPT), this is quite obviously a driver passing in a bad memory descriptor list:

0: kd> k
Child-SP		  RetAddr		   Call Site
fffffa60`0c8ab168 fffff800`01ee93db nt!KeBugCheckEx
fffffa60`0c8ab170 fffff800`01ed201d nt!MiBadShareCount+0x4b
fffffa60`0c8ab1b0 fffff800`020f0e89 nt!MmUnmapViewInSystemCache+0x3e72d
fffffa60`0c8ab480 fffff800`01e847ae nt!CcUnmapVacb+0x59
fffffa60`0c8ab4c0 fffff800`01ea585d nt!CcUnmapVacbArray+0x2be
fffffa60`0c8ab540 fffff800`01e8a4b8 nt!CcGetVacbMiss+0x3fd
fffffa60`0c8ab5d0 fffff800`020a6cc7 nt!CcGetVirtualAddress+0x348
fffffa60`0c8ab650 fffff800`01e45551 nt!CcMapDataCommon+0x5f
fffffa60`0c8ab6c0 fffff800`020dc279 nt!CcMapDataForOverwrite+0xb5
fffffa60`0c8ab740 fffffa60`012f61a7 nt!CcPreparePinWrite+0x69
fffffa60`0c8ab800 fffffa60`012d2a21 Ntfs!LfsAllocateLbcb+0x117
fffffa60`0c8ab860 fffffa60`012d2c65 Ntfs!LfsWriteLogRecordIntoLogPage+0x4f1
fffffa60`0c8ab8d0 fffffa60`012d3692 Ntfs!LfsWrite+0x135
fffffa60`0c8ab990 fffffa60`012da2b6 Ntfs!NtfsWriteLog+0x452
fffffa60`0c8abbe0 fffffa60`012dbcd0 Ntfs!NtfsChangeAttributeValue+0x286
fffffa60`0c8abd80 fffffa60`012b819e Ntfs!NtfsUpdateStandardInformation+0x26e
fffffa60`0c8abe90 fffffa60`012c4786 Ntfs!NtfsUpdateAllInformation+0x3e
fffffa60`0c8abf00 fffffa60`012e2e28 Ntfs!NtfsOpenExistingPrefixFcb+0x3d6
fffffa60`0c8abfe0 fffffa60`012de9a4 Ntfs!NtfsFindStartingNode+0x5f8
fffffa60`0c8ac0b0 fffffa60`0122510d Ntfs!NtfsCommonCreate+0x3a4
fffffa60`0c8ac2b0 fffff800`01e933b1 Ntfs!NtfsCommonCreateCallout+0x1d
fffffa60`0c8ac2e0 fffffa60`0122583a nt!KeExpandKernelStackAndCalloutEx+0x2e1
fffffa60`0c8ac370 fffffa60`012dd56d Ntfs!NtfsCommonCreateOnNewStack+0x4a
fffffa60`0c8ac3d0 fffffa60`00d5de17 Ntfs!NtfsFsdCreate+0x1ad
fffffa60`0c8ac570 fffffa60`00d7a26c fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227
fffffa60`0c8ac5e0 fffffa60`0c012608 fltmgr!FltpCreate+0x25d
fffffa60`0c8ac690 00000000`656e6f4e amon+0x4608
fffffa60`0c8ac698 00000000`00000030 0x656e6f4e
fffffa60`0c8ac6a0 fffffa80`065a7470 0x30
fffffa60`0c8ac6a8 00000000`00000000 0xfffffa80`065a7470
fffffa60`0c8ac6b0 00000020`00000040 0x0
fffffa60`0c8ac6b8 00000000`00000000 0x20`00000040
fffffa60`0c8ac6c0 fffffa80`06b67480 0x0
fffffa60`0c8ac6c8 00000000`00000000 0xfffffa80`06b67480
fffffa60`0c8ac6d0 fffffa80`067dfbc0 0x0
fffffa60`0c8ac6d8 fffffa80`065a7470 0xfffffa80`067dfbc0
fffffa60`0c8ac6e0 fffffa80`067dfc58 0xfffffa80`065a7470
fffffa60`0c8ac6e8 fffffa80`048d2b10 0xfffffa80`067dfc58
fffffa60`0c8ac6f0 00000000`00000040 0xfffffa80`048d2b10
fffffa60`0c8ac6f8 fffff800`020f9cc3 0x40
fffffa60`0c8ac700 fffff800`020f3999 nt!IopParseDevice+0x5e3
fffffa60`0c8ac8a0 fffff800`020f7884 nt!ObpLookupObjectName+0x5eb
fffffa60`0c8ac9b0 fffff800`02103e30 nt!ObOpenObjectByName+0x2f4
fffffa60`0c8aca80 fffff800`02104968 nt!IopCreateFile+0x290
fffffa60`0c8acb20 fffff800`01e71e33 nt!NtCreateFile+0x78
fffffa60`0c8acbb0 00000000`77805fca nt!KiSystemServiceCopyEnd+0x13
00000000`0007e4c8 00000000`00000000 0x77805fca
0: kd> lmvm amon
start			 end				 module name
fffffa60`0c00e000 fffffa60`0c08a000   amon	 T (no symbols)		   
	Loaded symbol image file: amon.sys
	Image path: amon.sys
	Image name: amon.sys
	Timestamp:		Fri May 11 02:23:04 2007 (46440BC8)
	CheckSum:		 0002D3DB
	ImageSize:		0007C000
	Translations:	 0000.04b0 0000.04e4 0409.04b0 0409.04e4

We can plainly see that we come out of the callback list for an NTFS IRP (doing some file I/O here) that we're passed through amon.sys, which is a part of the NOD32 antivirus product.

I might suggest uninstalling (not disabling, but UNINSTALLING) the NOD32 antivirus application and trying to reproduce the problem. If it still happens, get more dump data. While it's not uncommon to see antivirus drivers loaded during filesystem work, a quick internet search on these bugcheck codes and amon.sys does turn up other hits with people having the same problems as you when NOD32 is installed, so an educated guess (plus the above data) seems to implicate NOD32 in your crashes.

**jaleo** · December 12, 2008

Thanks for reply.

I uninstall NOD32 2.7, and test again.

computer still restart.

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.0.6001.2.1.0.256.1

Locale ID: 1033

Additional information about the problem:

BCCode: d3

BCP1: FFFFF960002D7100

BCP2: 0000000000000002

BCP3: 0000000000000000

BCP4: FFFFF80001EB5E5E

OS Version: 6_0_6001

Service Pack: 1_0

Product: 256_1

uplod new dump file.

Mini121208_02.zip

Edited December 12, 2008 by cluberti
shortening post for slow-connection users

**cluberti** · December 12, 2008

This actually looks a little different - it appears your video driver has passed in bad parameters to a window draw function, vSolidFillRect. From the loaded module list, it looks like you're running an nvidia driver:

1: kd> lmivm nvlddmkm
start			 end				 module name
fffffa60`03a08000 fffffa60`04310980   nvlddmkm   (deferred)			 
	Symbol file: nvlddmkm.sys
	Image path: nvlddmkm.sys
	Image name: nvlddmkm.sys
	Timestamp:		Tue Oct 07 17:57:15 2008 (48EBDB3B)
	CheckSum:		 0090E3AE
	ImageSize:		00908980
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0

Does it crash if you change your video driver to "Standard VGA" and uninstall the nVidia drivers?

**jaleo** · December 12, 2008

Thanks.

I install NOD32 3.0 x64 and nVidia drivers 175.21 version(this is vista recommend).

test again. restart still exist.

i try to change video driver to "Standard VGA",but vista will install latest driver automatically . can you tell me how to set to VGA mode?

**Tripredacus** · December 12, 2008

Thanks.
I install NOD32 3.0 x64 and nVidia drivers 175.21 version(this is vista recommend).
test again. restart still exist.
i try to change video driver to "Standard VGA",but vista will install latest driver automatically . can you tell me how to set to VGA mode?

Uninstall the nVidia driver package from Programs and Features. Do not restart like it wants you to. Then remove the display adapters from Device Manager. Then restart the computer. When it comes back up, your resolution may be different, but then go check Device Manager and see what name it has in Display Adapters. It should be Standard VGA.

**jaleo** · December 13, 2008

Thanks.
I install NOD32 3.0 x64 and nVidia drivers 175.21 version(this is vista recommend).
test again. restart still exist.
i try to change video driver to "Standard VGA",but vista will install latest driver automatically . can you tell me how to set to VGA mode?
Uninstall the nVidia driver package from Programs and Features. Do not restart like it wants you to. Then remove the display adapters from Device Manager. Then restart the computer. When it comes back up, your resolution may be different, but then go check Device Manager and see what name it has in Display Adapters. It should be Standard VGA.

Thanks.

I do it,but computer also restart.

At last i find many people talk about gigabyte EP45 mainboard unstable after sending to STR sleep state.

such as http://forums.tweaktown.com/f69/ga-ep45-ds...ep-state-27296/

so i try to update BIOS version, now I am testing system. hope this can solve my problom.

Sign In

[Solved]vista sleep and wakeup problom

Recommended Posts

jaleo

Link to comment

Share on other sites

Tripredacus

Link to comment

Share on other sites

MagicAndre1981

Link to comment

Share on other sites

jaleo

Link to comment

Share on other sites

cluberti

Link to comment

Share on other sites

jaleo

Link to comment

Share on other sites

cluberti

Link to comment

Share on other sites

jaleo

Link to comment

Share on other sites

Tripredacus

Link to comment

Share on other sites

jaleo

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members

Activity

Browse