Mam ten sam problem o którym kolega pisał na początku. Zrobiłem mem test i na jednej kości pokazało 12 błędów a na drugiej 6. Pożyczyłem od kolegi dwie takie same kości i na jednej są błędy a na drugiej nie ale mimo to nie działa.Najciekawsze jest to że dwum kumplom ten ram z błędami nie powoduje żadnych problemów.
Dane techniczne mojego pc:
GeForce 9600 GSO 384mb
Intel Core 2 Duo E4600
Płyta główna MSI P35 NEO2-FR
Zasilacz Chieftec cft-500a-12s
dysk seagate 500gb,32mb,sa2
pamięć - wcześniej 4gb ddr2 teraz 2gb ddr2 (taktowanie 800)
windows vista
Dodaję plik minidump ale nie wiem co z nim dalej zrobićhttp://www.sendspace...aedb941bb0db2a6
udało mi się odczytać
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini112310-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:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x82048000 PsLoadedModuleList = 0x82155930
Debug session time: Tue Nov 23 02:16:36.301 2010 (GMT+1)
System Uptime: 0 days 0:23:19.073
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, 97529710, 0, 95356}
Probably caused by dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+c3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000001f, The subtype of the bugcheck:
Arg2: 97529710
Arg3: 00000000
Arg4: 00095356
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1f
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: nba2k11.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8cfaf230 to 821036d9
STACK_TEXT:
a269d75c 8cfaf230 0000010e 0000001f 97529710 nt!KeBugCheckEx+0x1e
a269d784 8cf3a641 00000000 0000010e 0000001f watchdog!WdLogEvent5+0x130
a269d7c4 8cf3c372 00000000 97529710 a269d7ec dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0xc3
a269d90c 8cf3ce35 00000000 97529710 00000000 dxgkrnl!VIDMM_GLOBAL::DiscardAllocationInternal+0x11f
a269d920 8cf3c7b9 97529710 2e9b0bba 866cab08 dxgkrnl!VIDMM_GLOBAL::DiscardAllocation+0x1a
a269d9f0 8cf3bb67 97529710 00000000 865f7b38 dxgkrnl!VIDMM_MEMORY_SEGMENT::EvictResource+0x2e0
a269da58 8cf3a0ea a269db88 a269db28 a269db54 dxgkrnl!VIDMM_GLOBAL::ProcessDeferredCommand+0x60e
a269da70 8cf3a13d a269db4c 865f7b38 865f7b38 dxgkrnl!VidMmiProcessSystemCommand+0x20
a269da8c 8cf3094a 864d56d0 864d7008 a269dacc dxgkrnl!VidSchiSubmitSystemCommand+0x2d
a269da9c 8cf129a1 865f7b38 865f7b38 865f7c38 dxgkrnl!VidSchiSubmitQueueCommand+0x7b
a269dacc 8cf30876 864da000 a269daf0 864d7008 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
a269daf4 8cf3be74 015f7b38 86645000 86645000 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
a269db0c 8cf3bd97 864d7008 8cf3a0ca a269db4c dxgkrnl!VidSchSubmitSystemCommand+0xa6
a269db38 8cf3c02e a269db4c 97529710 866cab08 dxgkrnl!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x40
a269db70 8cf3bc6f a269db88 00000000 9c0daa98 dxgkrnl!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c
a269dbac 8cf3c3bd 00000000 00000000 a97ec1a0 dxgkrnl!VIDMM_GLOBAL::CloseOneAllocation+0x8d
a269dbcc 8cf3d154 9c0daa98 00000000 00000000 dxgkrnl!VIDMM_GLOBAL::CloseAllocation+0x37
a269dc38 8cf3d955 00000000 00000000 a5acb650 dxgkrnl!DXGDEVICE::DestroyAllocations+0x176
a269dc94 8cf3deb2 a269dcf0 00000001 2e9b0f12 dxgkrnl!DXGDEVICE::DestroyAllocation+0x28a
a269dd58 8209f9aa 30dbfee0 30dbfef0 776c9a94 dxgkrnl!DxgkDestroyAllocation+0x538
a269dd58 776c9a94 30dbfee0 30dbfef0 776c9a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
30dbfef0 00000000 00000000 00000000 00000000 0x776c9a94
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+c3
8cf3a641 8b450c mov eax,dword ptr [ebp+0Ch]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+c3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64
FAILURE_BUCKET_ID: 0x10e_1f_dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+c3
BUCKET_ID: 0x10e_1f_dxgkrnl!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+c3
Followup: MachineOwner
---------