|
|
|
|
Strumenti |
03-06-2009, 10:29 | #101 |
Bannato
Iscritto dal: May 2007
Città: Bari
Messaggi: 4678
|
mi è apparsa una schermata blu 0x000000f4 su windows 7 dopo aver fatto riprendere il pc dallo stato di sospensione(quando si spegne tutto e rimane solo il led verde lampeggiante)
come risolvo?possiedo la rc di win7 a 64 bit |
03-06-2009, 10:32 | #102 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Mi è capitato anche a me. Ho risolto con l'aggiornamento del bios e smanettando nel bios stesso visto che lasciando tutto su auto con le ram che ho mi dava questo problema. Aggiorna il S.O. al massimo, fai un controllo delle ram e poi vedi come è settato il bios. In caso forniscici la tua config e se sei in O.C. spesso l'O.C. comporta queste cose strambe.
|
03-06-2009, 10:38 | #103 | |
Bannato
Iscritto dal: May 2007
Città: Bari
Messaggi: 4678
|
Quote:
|
|
03-06-2009, 11:32 | #104 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
|
03-06-2009, 12:53 | #105 | |
Bannato
Iscritto dal: May 2007
Città: Bari
Messaggi: 4678
|
Quote:
cmq non credo siano le ram il problema ,in ogni caso controllerò anche quelle |
|
03-06-2009, 13:15 | #106 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
No non perchè danno problemi (Almeno non ne sono a conoscenza) ma perchè magari c'è qualche bios che può aiutarti. Asus fa spesso degli upgrade anche per problemi di questo tipo.
|
04-06-2009, 07:33 | #107 |
Bannato
Iscritto dal: May 2007
Città: Bari
Messaggi: 4678
|
ok...per adesso nessun upgrade,magari la causa del problema non è il bios...aspetto la rtm e vedo che succede
|
04-06-2009, 10:49 | #108 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
|
04-06-2009, 20:18 | #109 |
Bannato
Iscritto dal: Sep 2007
Città: Acquacanina
Messaggi: 747
|
ragazzi, ho windows vista e non riesco ad accendere il pc, ho tentato installazioni e non mi si avvia, sono però riuscito ad aprire il DOS e ho preso dei file dmp...non è che potete dirmi qual'è il problema così lo cancello dal dos e via ?
grazie 1000 Ecco i 3 files: https://cid-d435fd2f5bc8f8d1.skydriv...aspx/Documenti Per favore ragazzi, fatemi sapere..la situazione è critica |
13-06-2009, 12:42 | #110 | |
Senior Member
Iscritto dal: Nov 2008
Città: Verona
Messaggi: 776
|
Quote:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Luca\Desktop\Mini061309-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506 Machine Name: Kernel base = 0xfffff800`02810000 PsLoadedModuleList = 0xfffff800`029d5db0 Debug session time: Sat Jun 13 12:32:24.932 2009 (GMT+2) System Uptime: 0 days 22:56:03.538 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002ae0dd5, fffffa6005e5cc40, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+105 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002ae0dd5, Address of the exception record for the exception that caused the bugcheck Arg3: fffffa6005e5cc40, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: nt!ObpWaitForMultipleObjects+105 fffff800`02ae0dd5 4b8b0408 mov rax,qword ptr [r8+r9] CONTEXT: fffffa6005e5cc40 -- (.cxr 0xfffffa6005e5cc40) rax=0000000000000001 rbx=0000000000000000 rcx=00000000000003e8 rdx=fffffa80039af601 rsi=0000000000000002 rdi=00000000000003e8 rip=fffff80002ae0dd5 rsp=fffffa6005e5d4a0 rbp=fffffa6005e5dca0 r8=0001500000000000 r9=fffff8800b3e5000 r10=0000000000000000 r11=fffffffffffffd80 r12=fffffa6005e5d9b0 r13=fffff8800c595de0 r14=0000000000000002 r15=fffffa80045be060 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 nt!ObpWaitForMultipleObjects+0x105: fffff800`02ae0dd5 4b8b0408 mov rax,qword ptr [r8+r9] ds:002b:00014880`0b3e5000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: iw3mp.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a58b06 to fffff80002ae0dd5 STACK_TEXT: fffffa60`05e5d4a0 fffff800`02a58b06 : 00000000`00000003 00000000`00000000 00000000`00000001 00000000`00000001 : nt!ObpWaitForMultipleObjects+0x105 fffffa60`05e5d960 fffff800`028640f3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!NtWaitForMultipleObjects32+0xe5 fffffa60`05e5dbb0 00000000`7561374f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`143df0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7561374f FOLLOWUP_IP: nt!ObpWaitForMultipleObjects+105 fffff800`02ae0dd5 4b8b0408 mov rax,qword ptr [r8+r9] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObpWaitForMultipleObjects+105 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 49ac93e1 STACK_COMMAND: .cxr 0xfffffa6005e5cc40 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+105 BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+105 Followup: MachineOwner ---------
__________________
CASE: Cooler Master CM690; POWER SUPPLY: Corsair TX650W; MOTHERBOARD: Asus P5Q Pro; CPU: Core 2 Quad Q6600 @ 3.0Ghz + AC Freezer 7 PRO; VGA: Sapphire HD 7850 1GB OC; HD: Seagate Barracuda 500GB; RAM: Corsair DDR2 800Mhz 2X2GB MONITOR: Samsung T200 |
|
13-06-2009, 14:56 | #111 | ||||
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26487
|
Quote:
Quote:
Quote:
Inizia a provare, in successione, le indicazioni dell'altra volta (affinità, disabilitazione speedstep e c1e, versione dei Catalyst anche meno recente se necessario, test delle ram) Quote:
Specifica se hai Vista o Vista SP1 e dacci maggiori dettagli sul problema (in che punto si blocca Windows e quale errore dà).
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
||||
13-06-2009, 15:57 | #112 | |
Senior Member
Iscritto dal: Nov 2008
Città: Verona
Messaggi: 776
|
Quote:
Ho eseguito MemTest, dato che sono uscito l'ho lasciato andare, e dalla schermata che ho trovato dovrebbe aver concluso un "ciclo di test" senza errori, e giunto al 72% del secondo. Non l'avevo mai fatto prima d'ora, è giusto quello che ho detto? Allego un'immagine della schermata. Quindi le Ram non dovrebbero avere problemi. Vedremo più avanti se il problema persiste anche con c1e e Speedstep disabilitati. Escludo la possibilità dei driver, dato che ricordo che l'errore comparse anche con altre versioni dei Catalyst installate.
__________________
CASE: Cooler Master CM690; POWER SUPPLY: Corsair TX650W; MOTHERBOARD: Asus P5Q Pro; CPU: Core 2 Quad Q6600 @ 3.0Ghz + AC Freezer 7 PRO; VGA: Sapphire HD 7850 1GB OC; HD: Seagate Barracuda 500GB; RAM: Corsair DDR2 800Mhz 2X2GB MONITOR: Samsung T200 |
|
21-06-2009, 10:38 | #113 |
Senior Member
Iscritto dal: Apr 2001
Città: Giovinazzo(BA) ...bella città, riso patat e cozz a volontà!
Messaggi: 26487
|
Farei qualche ciclo in più per avere maggiori garanzie di affidabilità del test.
Ora, con c1e e SpeedStep disabilitati, come ti sta andando? Ciao
__________________
Ezio Lacandia on DeviantArt | Slimkat mod per N4 e N5 | Trattative mercatino HWU | Driver nForce NET Framework [Guida] | BSOD individuazione cause | Guida Sintetica Strap/Divisori P45 | Fix associazioni Vista/7 Problemi Win Installer | Avviare programmi senza richiesta UAC | Problemi Font | Guida Raccolte 7 | Win 32/64bit come perchè |
28-06-2009, 13:24 | #114 |
Senior Member
Iscritto dal: Nov 2008
Città: Verona
Messaggi: 776
|
Ora tutto bene, anche perchè per l'estate ho riportato tutto @default; dopo ore di gioco nessuna schermata blu. La mia idea comunque è che il problema risieda proprio nelle funzioni di risparmio energetico con l'OC attivo.
__________________
CASE: Cooler Master CM690; POWER SUPPLY: Corsair TX650W; MOTHERBOARD: Asus P5Q Pro; CPU: Core 2 Quad Q6600 @ 3.0Ghz + AC Freezer 7 PRO; VGA: Sapphire HD 7850 1GB OC; HD: Seagate Barracuda 500GB; RAM: Corsair DDR2 800Mhz 2X2GB MONITOR: Samsung T200 |
03-08-2009, 03:22 | #115 |
Bannato
Iscritto dal: May 2005
Città: Se ho fatto qualcosa di male... rivolgersi a FroZen!!!
Messaggi: 20102
|
oc e risparmio energetico, per quel poco che so non vanno per niente d'accordo
|
06-08-2009, 10:33 | #116 |
Senior Member
Iscritto dal: May 2002
Città: Nardo' (LE)
Messaggi: 4018
|
Questo sono i miei output:
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jabberwock\Desktop\Minidump\Mini080609-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Machine Name: Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c17dd0 Debug session time: Thu Aug 6 10:55:28.442 2009 (GMT+2) System Uptime: 0 days 0:04:34.172 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 110b, f0000, fffff900c1c11010} GetPointerFromAddress: unable to read from fffff80002c7a080 Probably caused by : win32k.sys ( win32k!FreeObject+3f ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 000000000000110b, (reserved) Arg3: 00000000000f0000, Memory contents of the pool block Arg4: fffff900c1c11010, Address of the block of pool being deallocated Debugging Details: ------------------ POOL_ADDRESS: fffff900c1c11010 FREED_POOL_TAG: Gla4 BUGCHECK_STR: 0xc2_7_Gla4 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: MSASCui.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002b863a5 to fffff80002aad450 STACK_TEXT: fffffa60`0d07b5c8 fffff800`02b863a5 : 00000000`000000c2 00000000`00000007 00000000`0000110b 00000000`000f0000 : nt!KeBugCheckEx fffffa60`0d07b5d0 fffff960`0015d0bb : 00000000`00000000 00000000`020109d2 00000000`020109d2 fffffa60`0d07b6d0 : nt!ExDeferredFreePool+0x90a fffffa60`0d07b680 fffff960`00160225 : fffff900`c071b010 fffff960`00170218 fffffa60`0d07b718 fffffa80`042e2b01 : win32k!FreeObject+0x3f fffffa60`0d07b6b0 fffff960`0016071b : 00000000`00001350 00000000`00000000 00000000`020109d2 fffff900`c0002f80 : win32k!DC::vReleaseVis+0x75 fffffa60`0d07b6f0 fffff960`000fe45f : fffff900`c1c0d100 00000000`00000001 fffffa80`00000000 fffff900`c008c010 : win32k!bDeleteDCInternal+0x18f fffffa60`0d07b750 fffff960`000bc488 : fffff900`c1c0d100 00000000`00000001 00000000`00000001 fffffa80`0745e760 : win32k!DestroyCacheDC+0xff fffffa60`0d07b780 fffff960`00168be3 : fffff900`c271e560 00000000`00000008 00000000`00000000 fffff800`02ab80f2 : win32k!DelayedDestroyCacheDC+0x5c fffffa60`0d07b7b0 fffff960`0015d9a8 : fffff900`c271e560 fffff800`02cf97b8 00000000`ffffffff fffff960`001710e5 : win32k!DestroyProcessInfo+0x1af fffffa60`0d07b800 fffff960`0015da8c : fffffa80`0745e760 fffff900`c271e560 00000000`00000000 fffff800`02cf97b8 : win32k!xxxUserProcessCallout+0x170 fffffa60`0d07b850 fffff800`02d059c4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`042bb690 : win32k!W32pProcessCallout+0x50 fffffa60`0d07b880 fffff800`02cf97d5 : fffffa60`40010004 fffff800`02a1d101 fffffa80`08071bb0 fffff800`78457350 : nt!PspExitThread+0x41c fffffa60`0d07b970 fffff800`02acee51 : 00000000`00000202 fffff800`02ab35f5 fffffa80`073e3790 fffff800`02bc6680 : nt!PsExitSpecialApc+0x1d fffffa60`0d07b9a0 fffff800`02ad2785 : fffffa60`0d07bc00 fffffa60`0d07ba40 fffff800`02cf97f0 00000000`00000001 : nt!KiDeliverApc+0x441 fffffa60`0d07ba40 fffff800`02aacf9d : fffffa80`042bb690 00000000`00000000 00000000`028ff401 00000000`00000000 : nt!KiInitiateUserApc+0x75 fffffa60`0d07bb80 00000000`77736c07 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2 00000000`028ffae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77736c07 STACK_COMMAND: kb FOLLOWUP_IP: win32k!FreeObject+3f fffff960`0015d0bb eb16 jmp win32k!FreeObject+0x57 (fffff960`0015d0d3) SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: win32k!FreeObject+3f FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49edb61d FAILURE_BUCKET_ID: X64_0xc2_7_Gla4_win32k!FreeObject+3f BUCKET_ID: X64_0xc2_7_Gla4_win32k!FreeObject+3f Followup: MachineOwner --------- 2: kd> lmvm win32k start end module name fffff960`000a0000 fffff960`00351000 win32k (pdb symbols) C:\ProgramData\dbg\sym\win32k.pdb\461136AA20F147C691A0FCFF0EB91E882\win32k.pdb Loaded symbol image file: win32k.sys Mapped memory image file: C:\ProgramData\dbg\sym\win32k.sys\49EDB61D2b1000\win32k.sys Image path: \SystemRoot\System32\win32k.sys Image name: win32k.sys Timestamp: Tue Apr 21 14:03:41 2009 (49EDB61D) CheckSum: 002AB0B1 ImageSize: 002B1000 File version: 6.0.6002.18023 Product version: 6.0.6002.18023 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: win32k.sys OriginalFilename: win32k.sys ProductVersion: 6.0.6002.18023 FileVersion: 6.0.6002.18023 (vistasp2_gdr.090421-0158) FileDescription: Multi-User Win32 Driver LegalCopyright: © Microsoft Corporation. All rights reserved. Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jabberwock\Desktop\Minidump\Mini080609-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 Machine Name: Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02bdedd0 Debug session time: Thu Aug 6 11:00:56.682 2009 (GMT+2) System Uptime: 0 days 0:04:34.786 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c201917e, 0, fffff960000fd086, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!FreeObject+a ) Followup: MachineOwner --------- 0: 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: fffff900c201917e, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff960000fd086, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002c41080 fffff900c201917e FAULTING_IP: win32k!FreeObject+a fffff960`000fd086 660fba610e0f bt word ptr [rcx+0Eh],0Fh MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 TRAP_FRAME: fffffa600c8f21f0 -- (.trap 0xfffffa600c8f21f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff900c2019170 rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000 rip=fffff960000fd086 rsp=fffffa600c8f2380 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=fffffa600c8f22f0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc win32k!FreeObject+0xa: fffff960`000fd086 660fba610e0f bt word ptr [rcx+0Eh],0Fh ds:f780:fffff900`c201917e=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ad5830 to fffff80002a74450 STACK_TEXT: fffffa60`0c8f2108 fffff800`02ad5830 : 00000000`00000050 fffff900`c201917e 00000000`00000000 fffffa60`0c8f21f0 : nt!KeBugCheckEx fffffa60`0c8f2110 fffff800`02a72fd9 : 00000000`00000000 fffffa60`0c8f2340 00000000`00000000 fffff900`c071c820 : nt! ?? ::FNODOBFM::`string'+0x2d3dc fffffa60`0c8f21f0 fffff960`000fd086 : 00000000`4c0f08aa fffff960`002267e5 fffff900`c020cff0 fffff960`0010ff8e : nt!KiPageFault+0x119 fffffa60`0c8f2380 fffff960`001e3572 : fffff900`c071c820 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!FreeObject+0xa fffffa60`0c8f23b0 fffff960`001e09c3 : fffff900`c071c820 00000000`00000000 fffff900`c0087010 00000000`000100b4 : win32k!vspDestroyDwmSpriteObj+0x76 fffffa60`0c8f2400 fffff960`0017ffdf : fffff900`c0807100 fffff960`002ca3a0 00000000`00000000 fffff900`c0807100 : win32k!GreDeleteSprite+0xbb fffffa60`0c8f2440 fffff960`001068e9 : fffff900`c00e8d80 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!UnsetLayeredWindow+0xcb fffffa60`0c8f24b0 fffff960`00107736 : 00000000`00000000 fffff900`c0807100 fffff900`c07c3450 fffffa80`074d0720 : win32k!xxxFreeWindow+0x9c9 fffffa60`0c8f2560 fffff960`001079e4 : 00000000`00000000 fffff900`c0807100 fffff900`c0800b60 fffff900`c0805020 : win32k!xxxDestroyWindow+0x676 fffffa60`0c8f2610 fffff960`00107481 : fffff900`c0805020 00000000`00000000 00000000`00000002 fffff900`c07c3450 : win32k!xxxDW_DestroyOwnedWindows+0xac fffffa60`0c8f2640 fffff960`00105ef9 : 00000000`00000000 00000000`00010092 fffffa60`0c8f27a0 00000000`ffdde340 : win32k!xxxDestroyWindow+0x3c1 fffffa60`0c8f26f0 fffff800`02a73ef3 : fffffa80`07ea5a30 fffffa60`0c8f27a0 00000000`047110b0 00000000`00000000 : win32k!NtUserDestroyWindow+0x3d fffffa60`0c8f2720 00000000`7778697a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02b0f008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7778697a STACK_COMMAND: kb FOLLOWUP_IP: win32k!FreeObject+a fffff960`000fd086 660fba610e0f bt word ptr [rcx+0Eh],0Fh SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!FreeObject+a FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49edb61d FAILURE_BUCKET_ID: X64_0x50_win32k!FreeObject+a BUCKET_ID: X64_0x50_win32k!FreeObject+a Followup: MachineOwner --------- 0: kd> lmvm win32k start end module name fffff960`00040000 fffff960`002f1000 win32k (pdb symbols) C:\ProgramData\dbg\sym\win32k.pdb\461136AA20F147C691A0FCFF0EB91E882\win32k.pdb Loaded symbol image file: win32k.sys Mapped memory image file: C:\ProgramData\dbg\sym\win32k.sys\49EDB61D2b1000\win32k.sys Image path: \SystemRoot\System32\win32k.sys Image name: win32k.sys Timestamp: Tue Apr 21 14:03:41 2009 (49EDB61D) CheckSum: 002AB0B1 ImageSize: 002B1000 File version: 6.0.6002.18023 Product version: 6.0.6002.18023 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: win32k.sys OriginalFilename: win32k.sys ProductVersion: 6.0.6002.18023 FileVersion: 6.0.6002.18023 (vistasp2_gdr.090421-0158) FileDescription: Multi-User Win32 Driver LegalCopyright: © Microsoft Corporation. All rights reserved. Ho testato la RAM con Memtest86+, ma niente! Ho provato ad creare un secondo account e il problema pare non presentarsi! Modifiche fatte: Catalyst 9.7, ma anche ripristinando i 9.6 con il rispristino configurazione non cambia nulla; installato Speedfan, ma anche disinstallandolo non cambia niente! A parte questo problema, la macchina funziona perfettamente: nessun blocco/BSOD anche dopo lunghe elaborazioni! Edit: forse ho trovato il colpevole: il software di gestione dell'Ati remote wonder! Fino a pochi giorni fa andava (anche se era necessario installare i driver X10), evidentemente e' stato modificato qualcosa in VIsta64 con gli ultimi aggiornamenti e il risultato e' stato quello!
__________________
15 maggio 2008 11 marzo 2013 26 febbraio 2014 Ultima modifica di Jabberwock : 06-08-2009 alle 15:03. |
09-08-2009, 20:39 | #117 |
Senior Member
Iscritto dal: Aug 2007
Messaggi: 1670
|
ecco la mia schermata blu di oggi, seguita a raffica da altre 10, ciascuna provocava un riavvio automatico del sistema. Ho risolto con F8 e cliccando su vai all'ultima configurazione funzionante (o qualcosa del genere ora non ricordo....)
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini080909-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\Windows\Symbols Executable search path is: Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x81e1c000 PsLoadedModuleList = 0x81f33c70 Debug session time: Sun Aug 9 17:34:28.417 2009 (GMT+2) System Uptime: 0 days 0:00:39.182 Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list .... Unable to load image \SystemRoot\System32\Drivers\Mpfp.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Mpfp.sys *** ERROR: Module load completed but symbols could not be loaded for Mpfp.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 8e735a81, 9c65e050, 0} *** WARNING: Unable to verify timestamp for tdx.sys *** WARNING: Unable to verify timestamp for afd.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : Mpfp.sys ( Mpfp+7482 ) Followup: MachineOwner --------- ah, ho win vista home premium SP2. come symbol ho preso il file Windows Vista SP2 and Windows Server 2008 SP2 x86 retail symbols, all languages come indicato nella 1a pagina all'indirizzo http://www.microsoft.com/whdc/devtoo...mbolpkg.mspx#d , pero' a quanto dice il report sembra che non sia quello giusto... come faccio a sapere quale ci vuole per me? edit; ho provato anche a mettere Codice:
SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini080909-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: io ho semplicemente levato la linea che conteneva il path c:\Windows\symbols e sostituita con il codice sopra... Ultima modifica di Giulio_P : 09-08-2009 alle 20:44. |
11-08-2009, 00:20 | #118 |
Member
Iscritto dal: Sep 2006
Città: Milano
Messaggi: 121
|
Vediamo se qualcuno sa aiutarmi
Recentemente ho aggiornato il mio PC, ho montato un AMD Phenom Quad Core 9600 e una MB Gigabyte GA-MA74GM-S2H (rev 2.0).Da quando ho cambiato questi pezzi mi compaiono delle BSOD random con conseguente riavvio, tuttavia non sono sicuro che ci sia un collegamento tra l'upgrade del PC e questi BSOD, ho provato a formattare ma non è cambiato nulla. Ecco gli errori che compaiono Codice:
Firma problema: Nome evento problema: BlueScreen Versione SO: 6.0.6000.2.0.0.768.3 ID impostazioni locali: 1040 Ulteriori informazioni sul problema: BCCode: 24 BCP1: 001904AB BCP2: 883CF1EC BCP3: 883CEEE8 BCP4: 0107715D OS Version: 6_0_6000 Service Pack: 0_0 Product: 768_1 File che contribuiscono alla descrizione del problema: C:\Windows\Minidump\Mini081109-01.dmp C:\Users\Gabriele\AppData\Local\Temp\WER-162802-0.sysdata.xml C:\Users\Gabriele\AppData\Local\Temp\WER8C85.tmp.version.txt Leggere l'informativa sulla privacy: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0410 Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini081109-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Users\Gabriele*http://msdl.microsoft.com/download/symbols;C:\Windows\Symbols Executable search path is: Windows Vista Kernel Version 6000 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 6000.16830.x86fre.vista_gdr.090302-1506 Machine Name: Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10 Debug session time: Tue Aug 11 01:04:10.982 2009 (GMT+2) System Uptime: 0 days 2:08:18.318 Loading Kernel Symbols ............................................................... ................................................................ ... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904ab, 883cf1ec, 883ceee8, 107715d} Probably caused by : Ntfs.sys ( Ntfs!NtfsDefragFileInternal+bcf ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 001904ab Arg2: 883cf1ec Arg3: 883ceee8 Arg4: 0107715d Debugging Details: ------------------ EXCEPTION_RECORD: 883cf1ec -- (.exr 0xffffffff883cf1ec) ExceptionAddress: 0107715d ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 0107715d Attempt to execute non-executable address 0107715d CONTEXT: 883ceee8 -- (.cxr 0xffffffff883ceee8) eax=850bb620 ebx=848ad610 ecx=81b6a4c7 edx=00000000 esi=8539b0d8 edi=86566be8 eip=0107715d esp=883cf2b4 ebp=883cf3f8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 0107715d ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. EXCEPTION_PARAMETER1: 00000008 EXCEPTION_PARAMETER2: 0107715d WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac Unable to read MiSystemVaType memory at 81d117e0 0107715d FOLLOWUP_IP: Ntfs!NtfsDefragFileInternal+bcf 81bb08db 53 push ebx FAULTING_IP: +6572952f01acd990 0107715d ?? ??? FAILED_INSTRUCTION_ADDRESS: +6572952f01acd990 0107715d ?? ??? BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from 81bb08db to 0107715d STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 883cf2b0 81bb08db 85398e00 88bd400a 8539b0d8 0x107715d 883cf3f8 81bb0d72 848ad610 84913e28 a19cad80 Ntfs!NtfsDefragFileInternal+0xbcf 883cf460 81b90690 848ad610 84913e28 883cf4b8 Ntfs!NtfsDefragFile+0x2f4 883cf478 81b9031d 848ad610 84913e28 84913e28 Ntfs!NtfsUserFsRequest+0x171 883cf498 81b904ad 848ad610 84913e28 88bd46fa Ntfs!NtfsCommonFileSystemControl+0xe1 883cf508 81c27f9b 8539b020 84913e28 84913e28 Ntfs!NtfsFsdFileSystemControl+0x17e 883cf520 807b6a5c 854cdee8 84913e28 00000000 nt!IofCallDriver+0x63 883cf544 807c8ead 883cf564 854cdee8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x22a 883cf57c 81c27f9b 854cdee8 84913e28 84913e28 fltmgr!FltpFsControl+0xe5 883cf594 81d88f55 849a93e0 84913e28 84913fdc nt!IofCallDriver+0x63 883cf5b4 81d89f15 854cdee8 849a93e0 00000001 nt!IopSynchronousServiceTail+0x1e0 883cf650 81d8eeb9 854cdee8 84913e28 00000000 nt!IopXxxControlFile+0x6b7 883cf684 81c8caea 80001c9c 00000000 00000000 nt!NtFsControlFile+0x2a 883cf684 81c7e899 80001c9c 00000000 00000000 nt!KiFastCallEntry+0x12a 883cf724 8061624b 80001c9c 00000000 00000000 nt!ZwFsControlFile+0x11 883cf9f4 8061665b 84faf0d8 80000d34 00591456 volsnap!VspOptimizeDiffAreaFileLocation+0x363 883cfac0 8061ffc4 01f361b0 00000001 883cfae8 volsnap!VspOpenDiffAreaFile+0x38d 883cfaf0 8062967c 84760cd8 12c00000 00000000 volsnap!VspCreateInitialDiffAreaFile+0x130 883cfd14 00000000 00000000 00000000 00000000 volsnap!VspPrepareForSnapshot+0x5fa SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: Ntfs!NtfsDefragFileInternal+bcf FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4764f079 STACK_COMMAND: .cxr 0xffffffff883ceee8 ; kb FAILURE_BUCKET_ID: 0x24_BAD_IP_Ntfs!NtfsDefragFileInternal+bcf BUCKET_ID: 0x24_BAD_IP_Ntfs!NtfsDefragFileInternal+bcf Followup: MachineOwner --------- Ciò avveniva anche con Windows 7 RC e Windows Vista SP2, quindi non credo che il problema stia nella mancanza di aggiornamenti e SP (ho appena formattato). Ultima modifica di cLover : 11-08-2009 alle 01:05. |
11-08-2009, 09:58 | #119 |
Bannato
Iscritto dal: Feb 2008
Città: Roma
Messaggi: 2453
|
Quindi hai cambiato la CPU e la MOBO, giusto?
A questo punto vedrei i settaggi della ram. Ti dico questo perchè avevo delle BSOD a raffica e alla fine ho scoperto, leggendo un articolo proprio su HW, che erano le ram. (il mio problema era la velocità e il voltaggio che era superiore al limite consentito dalla mia CPU). Questo per dirti che le ram spesso sono il problema di questi BSOD. |
11-08-2009, 10:16 | #120 |
Member
Iscritto dal: Sep 2006
Città: Milano
Messaggi: 121
|
Ho pensato quasi subito alla RAM, sono due banchi Kingston DDR2 800 Mhz da 1 GB.La motherboard le aveva impostate automaticamente a 667 MHz ma io ho cambiato manualmente i settaggi a 800 Mhz.
|
Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 10:43.