Problema bsod

[bardahl]

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...
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



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

[ezio]

I bsod su quel file dxgmms1.sys rappresentano un problema noto con alcune release dei Catalyst (a me è successo ad esempio con gli 11.6, risolto con gli utlimi hotfix).
La soluzione da te proposta è quella giusta insomma, cambia driver video (non per forza usando i più recenti) ;)

[bardahl]

e mi sapresti indicare quello che hai usato tu visto che io ieri sera ho installato proprio i 11.6 ieri notte nel tentativo di risolvere XD
Edit:
mentre non c'ero di nuovo bsod
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: 1a
BCP1: 0000000000061940
BCP2: 000000001B570000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\072011-25552-01.dmp
C:\Users\Gennaro\AppData\Local\Temp\WER-40092-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

e analizzando con windbg

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


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

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`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Wed Jul 20 11:48:00.273 2011 (UTC + 2:00)
System Uptime: 0 days 0:14:06.647
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61940, 1b570000, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1fda3 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061940, A PDE has been unexpectedly invalidated.
Arg2: 000000001b570000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_61940

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: CCC.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002a6de99 to fffff80002abff00

STACK_TEXT:
fffff880`08bec7b8 fffff800`02a6de99 : 00000000`0000001a 00000000`00061940 00000000`1b570000 00000000`00000000 : nt!KeBugCheckEx
fffff880`08bec7c0 fffff800`02adb9b2 : 00000000`00000899 00000000`76d42001 fffff700`01080000 fffffa80`059c1c68 : nt! ?? ::FNODOBFM::`string'+0x1fda3
fffff880`08bec820 fffff800`02ae69cd : 00000000`00001ebf 00000000`00000000 00000000`00000000 0000000f`ffffffff : nt!MiUpdateWsle+0xd2
fffff880`08bec880 fffff800`02ae6353 : 6bf00001`1b429025 00000001`1b429121 00000000`225ef560 fffffa80`0595aec8 : nt!MiCompleteProtoPteFault+0x2cd
fffff880`08bec910 fffff800`02adbd9e : 00000000`00000000 00000000`76d42e80 fffff680`003b6a10 fffffa80`0595aec8 : nt!MiResolveProtoPteFault+0x1d3
fffff880`08bec9b0 fffff800`02ad9f23 : 00000000`00000000 00000000`76d42e80 00000fb5`00000080 fffff880`00000000 : nt!MiDispatchFault+0x1de
fffff880`08becac0 fffff800`02abdfee : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x343
fffff880`08becc20 00000000`76d42e80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`225ee668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d42e80


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1fda3
fffff800`02a6de99 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1fda3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x1a_61940_nt!_??_::FNODOBFM::_string_+1fda3

BUCKET_ID: X64_0x1a_61940_nt!_??_::FNODOBFM::_string_+1fda3

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

se sto iniziando a capirci qualcosa il problema e sempre relativo ai catalyst giusto?
Edit2:

ho provato a disinstallare i catalyst e ora installo gli hotfix 11.5b speriamo bene

[ezio]

Esatto, stavolta è stato il Control Center.
Io ho risolto con l'ultimo hotfix degli 11.6 (11.6 hotfix B), ma potresti provare direttamente con gli 11.5.

[bardahl]

niente da fare questa schermata mi viene pure in sonno ormai...
ieri tutto il giorno il pc e andato benissimo oggi dinuovo bluescreen
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: 50
BCP1: FFFFDD03C1B6D80F
BCP2: 0000000000000001
BCP3: FFFFF960000DF882
BCP4: 0000000000000007
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\072111-25006-01.dmp
C:\Users\Gennaro\AppData\Local\Temp\WER-34632-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


e windbg

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


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

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.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50
Debug session time: Thu Jul 21 12:00:06.711 2011 (UTC + 2:00)
System Uptime: 0 days 1:16:14.100
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffdd03c1b6d80f, 1, fffff960000df882, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffdd03c1b6d80f, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960000df882, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ca80e0
ffffdd03c1b6d80f

FAULTING_IP:
win32k!GrePatBltLockedDC+2e2
fffff960`000df882 184c8bcf sbb byte ptr [rbx+rcx*4-31h],cl

MM_INTERNAL_CODE: 7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: Skype.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880039cb6f0 -- (.trap 0xfffff880039cb6f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c06a4010 rbx=0000000000000000 rcx=fffff900c06a4610
rdx=fffff900c0000de0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000df882 rsp=fffff880039cb880 rbp=0000000000e1dad8
r8=0000000000e1dad8 r9=fffff900c0000de0 r10=fffff960000f50d8
r11=fffff900c06a4010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!GrePatBltLockedDC+0x2e2:
fffff960`000df882 184c8bcf sbb byte ptr [rbx+rcx*4-31h],cl ds:e480:ffffe403`01a9180f=??
Resetting default scope

MISALIGNED_IP:
win32k!GrePatBltLockedDC+2e2
fffff960`000df882 184c8bcf sbb byte ptr [rbx+rcx*4-31h],cl

LAST_CONTROL_TRANSFER: from fffff80002aef959 to fffff80002a70700

STACK_TEXT:
fffff880`039cb588 fffff800`02aef959 : 00000000`00000050 ffffdd03`c1b6d80f 00000000`00000001 fffff880`039cb6f0 : nt!KeBugCheckEx
fffff880`039cb590 fffff800`02a6e7ee : 00000000`00000001 fffff900`c00dc000 00000000`00000000 00000000`000001f2 : nt! ?? ::FNODOBFM::`string'+0x40dcb
fffff880`039cb6f0 fffff960`000df882 : fffff900`00e1dad8 fffff880`00000000 00000000`00000000 fffff900`c0000de0 : nt!KiPageFault+0x16e
fffff880`039cb880 fffff960`000df480 : 00000000`00000000 fffff880`039cbca0 fffff880`039cbb10 fffff900`0000f0f0 : win32k!GrePatBltLockedDC+0x2e2
fffff880`039cb930 fffff960`002b5c98 : fffff880`039cbb10 fffff960`002e44c4 00000000`0008ebb0 00000000`00000000 : win32k!GrePolyPatBltInternal+0x2ec
fffff880`039cba80 fffff800`02a6f953 : 00000000`0008e2f8 fffff800`00f00021 00000000`0008ebb0 00000000`00000001 : win32k!NtGdiPolyPatBlt+0x308
fffff880`039cbbb0 00000000`74ff04ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74ff04ca


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
22 errors : !win32k (fffff960000df8c1-fffff960000df9b9)
fffff960000df8c0 90 *76 90 90 90 90 90 90 48 *ff 5c 24 08 48 89 74 .v......H.\$.H.t
fffff960000df8d0 24 *0e 57 48 83 ec 50 4c 8b *ff 48 8b f9 bb 01 00 $.WH..PL..H.....
fffff960000df8e0 00 *74 4c 3b 15 07 84 2b 00 *00 1a 41 39 5a 54 0f .tL;...+...A9ZT.
fffff960000df8f0 84 *00 01 00 00 be a0 00 00 *ff 33 d2 41 39 72 50 ..........3.A9rP
fffff960000df900 e9 *00 01 00 00 be a0 00 00 *33 44 3b cb 74 06 41 .........3D;.t.A
fffff960000df910 83 *00 02 75 7c 48 8b 0a 39 *00 50 75 3b 4d 8b 18 ...u|H..9.Pu;M..
fffff960000df920 41 *00 43 58 39 41 58 7f 2f *2e 8b 43 60 39 41 60 A.CX9AX./..C`9A`
fffff960000df930 7c *ff 41 8b 43 5c 39 41 5c *98 1d 41 8b 43 64 39 |.A.C\9A\..A.Cd9
...
fffff960000df980 39 *00 64 7c 0c 44 3b cb 4c *00 44 c2 49 8b d0 eb 9.d|.D;.L.D.I...
fffff960000df990 ba *00 3b cb 0f 85 e4 00 00 00 48 8b 02 39 70 50 ..;.......H..9pP
fffff960000df9a0 0f *00 d8 00 00 00 49 8b 08 *00 71 50 0f 85 cc 00 ......I...qP....
fffff960000df9b0 00 00 f3 0f 6f 40 58 f3 0f *00 49 58 f3 0f 7f 44 ....o@X...IX...D

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------


anche se questa mi preoccupa piu delle altre bsod...
e uscita mentre giocavo ad uno sparatutto

Edit:
stasera tornando a casa ho acceso il pc e mi ha dato subito blue screen... prima dell'accensione.. poi il pc non voleva piu accendersi.
lo ho aperto ed ho notato che la spia della ram lampeggiava (per la mia scheda madre e come se mancasse) allora le ho staccate e ho cambiato gli slot... e il pc si e riacceso ma la prima schermata (quella con il nome del produttore della scheda madre per intenderci)e durata piu del solito... ma nella cartella minidump non c'e il file da analizzare... saranno le ram? ... sarà la scheda madre ... io non ho molto tempo di garanzia... vi prego aiutatemi Q_Q

[bardahl]

ho testato le ram con memtest86+ in dos e dopo 30 min piu o meno e finito e mi ha dato 0 errori.
ah ho aggiornato il bios oggi giusto per!

[Eress]

Penso tu abbia dei problemi alle ram, prova a scollegarne una alla volta

[bardahl]

ma il memtest non mi da errori... e poi ho aggiornato il bios, cambiato di posizione le ram e scollegato la webcam XD( pagata 4 euro autoistallante che mi dava qualche problemino) e non e piu successo fino ad ora XD(poco piu di 24 ore)