Ciao a tutti sono nuovo^_^.
il mio nuovo pc mi porta qui perche ha simpaticamente deciso di darmi problemi.
premetto che lo ho assemblato io e vi dico un po le caratteristiche (ma si!XD)
scheda madre: Crosshair iv formula
Processore: amd phenom II 1090t 3.4ghz
Ram: Corsair dominator 2x2gb (ddr3 1600mhz anche se il bios mi dice che le legge a 1300)
Scheda video: Sapphire radeon hd 6750(1gb ddr5)
mi da problemi da sempre ( ieri xD)
all'inizio non voleva far partire il disco di windows 7... poi ... chiamatelo caso... scollegando la mia logitech g15 il cd e magicamente partito.
poi all'avvio durante le prime installazioni mi ha dato sempre la bsod.
ho provato a formattare di nuovo e sembrava andare tutto bene poi questa sera...
Codice:
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 10e
BCP1: 000000000000001F
BCP2: FFFFF8A008BFC690
BCP3: 0000000000000000
BCP4: 00000000000D3427
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\072011-21122-01.dmp
C:\Users\Gennaro\AppData\Local\Temp\WER-30732-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
quindi ho analizzato con windbg
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072011-21122-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a52000 PsLoadedModuleList = 0xfffff800`02c8fe50
Debug session time: Wed Jul 20 00:08:30.645 2011 (UTC + 2:00)
System Uptime: 0 days 1:15:57.673
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, fffff8a008bfc690, 0, d3427}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
Followup: MachineOwner
---------
0: 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: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a008bfc690
Arg3: 0000000000000000
Arg4: 00000000000d3427
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1f
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff880019be22f to fffff80002ac3f00
STACK_TEXT:
fffff880`021bd878 fffff880`019be22f : 00000000`0000010e 00000000`0000001f fffff8a0`08bfc690 00000000`00000000 : nt!KeBugCheckEx
fffff880`021bd880 fffff880`0436e098 : fffff8a0`08bfc690 fffff8a0`08bfc690 00000000`000d3427 00000000`00000000 : watchdog!WdLogEvent5+0x11b
fffff880`021bd8d0 fffff880`0436b8af : 00000000`00000000 fffffa80`040a9578 00000000`00000c3a fffffa80`0400d070 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
fffff880`021bd910 fffff880`0438565d : 00000000`00000000 fffff8a0`091db510 fffffa80`00000000 fffffa80`04487300 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`021bdae0 fffff880`04385398 : fffff880`0308bfc0 fffff880`04384d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`021bdcd0 fffff880`04384e96 : 00000000`00000000 fffffa80`0625d410 00000000`00000080 fffffa80`05668010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`021bdd00 fffff800`02d67166 : 00000000`02de65b2 fffffa80`05669770 fffffa80`039d2040 fffffa80`05669770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`021bdd40 fffff800`02aa2486 : fffff880`03087180 fffffa80`05669770 fffff880`03092040 fffff880`01256a90 : nt!PspSystemThreadStartup+0x5a
fffff880`021bdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`0436e098 c7442450c5f3ffff mov dword ptr [rsp+50h],0FFFFF3C5h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
Followup: MachineOwner
---------
ho pensato di aggiornare i driver video... bhe staremo a vedere XD...
voi cosa mi consigliate?
grazie in anticipo