|
|||||||
|
|
|
 |
|
|
Strumenti |
28-03-2011, 07:38
|
#1101 | ||
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
Quote:
Quote:
http://answers.microsoft.com/it-it/S...question=false credo che sia un problema di driver |
||
|
|
|
28-03-2011, 10:28
|
#1102 | |
|
Member
Iscritto dal: Sep 2006
Messaggi: 34
|
Quote:
Dimenticavo di dirvi che ho fatto anche test della memoria ram sia con l'applicazione contenuta in windows 7 sia con memtest, nessuno dei 2 programmi ha rilevato alcun errore nelle ram. Che stress, il pc ha un anno e mezzo appena. |
|
|
|
|
|
28-03-2011, 10:35
|
#1103 |
|
Senior Member
Iscritto dal: Feb 2003
Città: Mo<->Bo
Messaggi: 41596
|
Io è da qualche giorno che sono apparse un paio di bsod...
E non so il tempo che non ne vedevo una... Il sistema è stato controllato con tutti i tools possibili e nessun errore di nessun genere è mai apparso, tutto appare perfetto... Una è una IRQ_NOT_LESS_OR_EQUAL ed una è una SYSTEM_EXCEPT o simile, questa sera posto il dump... |
|
|
|
|
28-03-2011, 12:08
|
#1104 | |
|
Senior Member
Iscritto dal: Feb 2008
Messaggi: 9581
|
Quote:
|
|
|
|
|
|
28-03-2011, 14:06
|
#1105 | |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
Quote:
|
|
|
|
|
|
30-03-2011, 20:40
|
#1106 |
|
Junior Member
Iscritto dal: Mar 2011
Messaggi: 2
|
schermata blu
Ciao a tutti ragazzi!
Anch'io come gli altri ho un problema con una schermata blu Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\033011-13774-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:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82e41000 PsLoadedModuleList = 0x82f8b850
Debug session time: Wed Mar 30 18:36:16.762 2011 (UTC + 2:00)
System Uptime: 0 days 18:37:24.525
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image WSR_USF.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WSR_USF.sys
*** ERROR: Module load completed but symbols could not be loaded for WSR_USF.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {0, 2, 1, 82e7a7f3}
*** WARNING: Unable to verify timestamp for USBSTOR.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for tdrpm258.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm258.sys
*** WARNING: Unable to verify timestamp for partmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.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 : WSR_USF.sys ( WSR_USF+3d14 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e7a7f3, address which referenced memory
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: WSR_USF
FAULTING_MODULE: 82e41000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b150d80
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000
CURRENT_IRQL: 0
FAULTING_IP:
nt+397f3
82e7a7f3 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from c60fbd14 to 82e7a7f3
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
d997f370 c60fbd14 00000000 91846ac0 00000200 nt+0x397f3
d997f3d0 c60fcbe7 85be6e48 86ed8380 87d557b8 WSR_USF+0x3d14
d997f42c 82e78593 87d55700 85be6e48 86ed8380 WSR_USF+0x4be7
d997f444 c6105050 85be6e48 87f8b7dc 87c93740 nt+0x37593
d997f464 c61065c2 86ed8240 85be6e48 87ea03ec USBSTOR+0x2050
d997f4a8 c6106a05 86ed8240 85be6e48 85be6f93 USBSTOR+0x35c2
d997f4cc 82eb9933 86e8f718 87f8b7dc 00000000 USBSTOR+0x3a05
d997f510 c60fbe3b 82f00ccd b9e1d4a0 fffffffe nt+0x78933
d997f564 c60fcbe7 85be6e48 86ed8380 87d557b8 WSR_USF+0x3e3b
d997f5c0 82e78593 87d55700 85be6e48 86ed8380 WSR_USF+0x4be7
d997f5d8 c6105050 86ed8403 87f8b81c 87f8b70a nt+0x37593
d997f5f8 c6106c6b 86ed8240 85be6e48 87ea03ec USBSTOR+0x2050
d997f634 c6107ff6 86ed8240 85be6e48 86ed8240 USBSTOR+0x3c6b
d997f668 82e5445e 86ed8240 00be6e48 86e8f7d0 USBSTOR+0x4ff6
d997f68c c610593e 86ed8240 85be6e48 87f8b808 nt+0x1345e
d997f6b0 82e78593 86e8f718 85be6e48 87f8b730 USBSTOR+0x293e
d997f6c8 8c0045a4 87c69c28 87f8b730 d997f718 nt+0x37593
d997f6d8 8c003fe8 86e8f718 86ec1b80 8714f2e0 CLASSPNP+0x45a4
d997f718 8c004303 00000000 00c69c28 87d563a0 CLASSPNP+0x3fe8
d997f740 8c0043bf 86ec1ac8 00000000 86ec1ac8 CLASSPNP+0x4303
d997f754 82e78593 86ec1ac8 87c69c28 8c8fb568 CLASSPNP+0x43bf
d997f76c 8c9051be 8c92667c 86ec1ac8 87c69c28 nt+0x37593
d997f800 8c057117 86517ac0 87c69c28 00000000 tdrpm258+0xa1be
d997f814 8c057152 86605dd0 87c69ddc 86605d18 partmgr+0x1117
d997f828 82e78593 86605d18 87c69c28 00000000 partmgr+0x1152
d997f840 830f6919 878db1e0 878db1e0 42040000 nt+0x37593
d997f86c 830f5f40 86605d18 00000200 00000000 nt+0x2b5919
d997f898 830f56f3 86605d18 8622a604 d997f8bc nt+0x2b4f40
d997f8a8 8c06134f 86605d18 8622a600 86605de4 nt+0x2b46f3
d997f8bc 8c05fd43 86605dd0 8622a600 86f1e8a8 partmgr+0xb34f
d997f8d8 8c057842 8622a600 86f1e8a8 86f1eb08 partmgr+0x9d43
d997f8f8 8c057152 00000000 86605e08 86605d18 partmgr+0x1842
d997f90c 82e78593 86605d18 86f1e8a8 86f1eb2c partmgr+0x1152
d997f924 8c81b6f1 8c8192b8 86605d18 86f1e8a8 nt+0x37593
d997f928 8c8192b8 86605d18 86f1e8a8 86bf6348 snapman+0x1b6f1
d997f92c 86605d18 86f1e8a8 86bf6348 867617a0 snapman+0x192b8
d997f930 86f1e8a8 86bf6348 867617a0 86bf6348 0x86605d18
d997f934 86bf6348 867617a0 86bf6348 d997f9ec 0x86f1e8a8
d997f938 867617a0 86bf6348 d997f9ec 8c801080 0x86bf6348
d997f93c 86bf6348 d997f9ec 8c801080 862e4b00 0x867617a0
d997f940 d997f9ec 8c801080 862e4b00 87d4ef00 0x86bf6348
d997f944 8c801080 862e4b00 87d4ef00 8c81ba84 0xd997f9ec
d997f9ec 8c9051be 8c92667c 86fa7570 86f1e8a8 snapman+0x1080
d997fa80 82fdcb35 87e460e8 87e46030 86f1e8a8 tdrpm258+0xa1be
d997fa98 82fdc1ef 87e460e8 86f1e8a8 e29f7050 nt+0x19bb35
d997fae0 82e78593 87e46030 86f1e8a8 86f1e8a8 nt+0x19b1ef
d997faf8 8c3593e8 87a31ce8 00000000 8655dc20 nt+0x37593
d997fb24 82e78593 87a31ce8 86f1e8a8 8c8fc628 fltmgr+0x63e8
d997fb3c 8c9051be 8c92667c 87a31ce8 86f1e8a8 nt+0x37593
d997fbd0 8c3593e8 86f10ce8 00000000 87dd6b68 tdrpm258+0xa1be
d997fbfc 82e78593 86f10ce8 86f1e8a8 86f1e8a8 fltmgr+0x63e8
d997fc14 8306c99f 87dd6b68 86f1e8a8 86f1eb34 nt+0x37593
d997fc34 8306fb71 86f10ce8 87dd6b68 00000000 nt+0x22b99f
d997fcd0 830b63f4 86f10ce8 86f1e8a8 00000000 nt+0x22eb71
d997fd04 82e7f1ea 00000268 00000000 00000000 nt+0x2753f4
d997fd34 771e70b4 badb0d00 06a7ebfc 00000000 nt+0x3e1ea
d997fd38 badb0d00 06a7ebfc 00000000 00000000 0x771e70b4
d997fd3c 06a7ebfc 00000000 00000000 00000000 0xbadb0d00
d997fd40 00000000 00000000 00000000 00000000 0x6a7ebfc
STACK_COMMAND: kb
FOLLOWUP_IP:
WSR_USF+3d14
c60fbd14 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: WSR_USF+3d14
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: WSR_USF.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> lmvm WSR_USF
start end module name
c60f8000 c6102f80 WSR_USF T (no symbols)
Loaded symbol image file: WSR_USF.sys
Image path: WSR_USF.sys
Image name: WSR_USF.sys
Timestamp: Tue Dec 01 13:35:12 2009 (4B150D80)
CheckSum: 00019E08
ImageSize: 0000AF80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
può darsi a un driver/periferica usb? Mi sareste di grande aiuto? Grazie! 
|
|
|
|
|
30-03-2011, 21:11
|
#1107 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
Mi sembra un driver piuttosto sospetto se fossi in te approfondirei con delle scansioni antivirus, inizia da MalwareBytes aggiornato, in caso positivo posti nella sezione adatta
|
|
|
|
|
06-04-2011, 17:40
|
#1108 |
|
Senior Member
Iscritto dal: Apr 2011
Messaggi: 357
|
Oltre fare ciò che ha consigliato Eress, per caso hai un Wireless USB?
|
|
|
|
|
08-04-2011, 12:11
|
#1109 |
|
Senior Member
Iscritto dal: Dec 2007
Città: Palermo
Messaggi: 2155
|
raga dato che non riesco a fare il debugg analysis vi posto direttamente il file dump zippato.
http://www.mediafire.com/?8586uccttq8bnyt |
|
|
|
|
08-04-2011, 19:22
|
#1110 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
L'errore è relativo a halmacpi.dll col parametro 0x00000124, vedi qui
http://www.sevenforums.com/crash-loc...-what-try.html per iniziare dai una controllata alle temperature e alla ram |
|
|
|
|
14-04-2011, 15:56
|
#1111 |
|
Junior Member
Iscritto dal: Apr 2011
Messaggi: 4
|
Salve, da quando ho installato windows 7 ho questo problema: in media dopo 30 - 40 minuti di gioco il pc si riavvia con la dannata schermata blu...fino a qualche giorno fa mi apparivano diversi codici, ora sono un paio di giorni che si presenta sempre e solo lo 0x3b con la scritta "SYSTEM_SERVICE_EXCEPTION"
Ho caricato un archivio rar con gli ultimi 5 minidump, spero che possiate aiutarmi! http://www.mediafire.com/?qrbq9pg5w7ko6ca |
|
|
|
|
14-04-2011, 16:03
|
#1112 |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
Direi di iniziare dalla ram, controlla anche i driver della scheda video se sono aggiornati, altrimenti agigornali o comunque provane una versione diversa anche più vecchia ma stabile.
|
|
|
|
|
14-04-2011, 16:13
|
#1113 | |
|
Junior Member
Iscritto dal: Apr 2011
Messaggi: 4
|
Quote:
la scheda video la escluderei perchè i bsod mi sono capitati sia con i driver del CD (recenti, di ottobre 2010) sia con gli ultimissimi driver Catalyst...che fosse questo il problema ci avevo pensato, perchè prima che disinstallassi il Catalyst control center (che dicono sia opzionale), dopo ogni bsod mi diceva che CCC aveva smesso di funzionare...quindi ho provato a toglierlo ma niente: sempre bsod, ma senza questo avviso. Per la ram dovrei fare un memtest vero? Comunque il banchetto da 2Gb attualmente installato non ha più di 5 mesi, mi sembra strano che abbia già problemi! |
|
|
|
|
|
14-04-2011, 17:35
|
#1114 | |
|
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37003
|
Quote:
|
|
|
|
|
|
14-04-2011, 21:50
|
#1115 |
|
Junior Member
Iscritto dal: Apr 2011
Messaggi: 4
|
uff, sto pc mi sta facendo predere la testa:
faccio il benedetto memtest, lo faccio lavorare per 1 oretta buona, in modo da fare 2 test completi e non mi evidenzia nessun errore, liscio come l'olio. Se non che al successivo avvio mi appare la schermata blu ancora prima di accedere a windows, questa volta con un codice 0x7c o 7e non ricordo...lo riavvio e lo rifà altre 2 volte. Al quarto avvio niente bsod, ma arriva al logo di windows e si riavvia, questo altre 3-4 volte...finalmente accedo in modalità provvisoria, bsod 0x3b come al solito...non so perchè lo avvio un'altra volta e questa volta fila tutto liscio, quasi come se il pc fosse nuovo, bah... Questi segni cosa fanno pensare? Hard disk, scheda madre o cosa? |
|
|
|
|
15-04-2011, 06:07
|
#1116 | |
|
Senior Member
Iscritto dal: Apr 2011
Messaggi: 357
|
Il memtest immagino lo hai fatto con un livecd. Per vedere se il problema è hardware direi di fare partire un live linux e fare qualche prova, test disco, grafica, etc. Se lì va tutto bene è solamente colpa di Windows e quindi si analizzano i bsod.
Quote:
__________________
Diffidate da chi dispensa certezze: TUTTI possono sbagliare! - Tutto quello che dico è IMHO (nessuna garanzia  ) 
|
|
|
|
|
|
15-04-2011, 11:26
|
#1117 | |
|
Junior Member
Iscritto dal: Apr 2011
Messaggi: 4
|
Quote:
|
|
|
|
|
|
18-04-2011, 08:36
|
#1118 |
|
Senior Member
Iscritto dal: Nov 2007
Messaggi: 1863
|
Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041811-21875-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e90e90
Debug session time: Mon Apr 18 07:08:21.602 2011 (GMT+2)
System Uptime: 0 days 0:07:47.008
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 34, {50853, fffff88003143918, fffff88003143170, fffff80002d109a1}
Probably caused by : ntkrnlmp.exe ( nt!CcWriteBehind+1a1 )
Followup: MachineOwner
---------
Ed ecco la schermata: 
Ultima modifica di mattiuccio92 : 18-04-2011 alle 08:42. |
|
|
|
|
18-04-2011, 14:21
|
#1120 |
|
Senior Member
Iscritto dal: Nov 2007
Messaggi: 1863
|
ma esattamente che consiglio devo seguire?
il pc è stato appena formattato... i pezzi sono assemblati da una settimana.. |
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 23:51.
