pasta

mi sapreste consigliare qualche mouse con queste caratteristiche? - molto "ergonomico" (tipo il mamba) - con un "buon sensore" ? - (in via secondaria) "solido" (che non dia l'impressione di una fragile cineseria)

a me interessa spendere il meno possibile ma vedo che anche le poste si parla di 30-40€....ho non ho capito?

dovrei spedire un mouse in germania o in belgio: sapreste consigliarmi un metodo di spedizione?

quindi con 8 thread a disposizione ne potrei dare 4 alla macchina impostando 4 core?

dici che se imposto 2 core gli attribuirà 4 thread e non 2?

ho 4gb di ram...per il discorso processori, le voci nelle impostazioni sono 2 : n° processori e n° core

quindi "equiparare" le risorse fra macchina Host e virtuale? p.s. numero di processori indica l'effettico numero di cpu montate sulla MB o cosa?

Sto utilizzando VMware Workstation e vorrei capire come ottimizzare al meglio le risorse da attribuire alla macchina virtuale: - L'utilizzo della macchina è esclusivo (quindi quando viene utilizzata, il sistema operativo che la ospita non viene utilizzato per altro) - La macchina gira su Windows 7 64bit - L'hardware è: I7 920@4GH (HT OFF) - 4GB DDR3 1600 Come vanno attribuiti RAM numero di processori e numero di core? (che sono le 3 voci che mi interessano all'interno della configurazione della macchina)

mmmH, vorrei sapere almeno sulla base di cosa, altrimenti dopo il format potrei riavere lo stesso problema :cheazz:

nenahce tramite questo si capisce?

mi sapresti dire quale driver ha causato il crash?....almeno inizio agendo su quello (come ho fatto per il precedente crash in cui ho aggiornato i drivers del wifi...almeno come prova)

ok grazie, è la prima cosa che farò.....in serata però ho avuto anche questo: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:WindowsMinidump102911-16832-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0361d000 PsLoadedModuleList = 0xfffff800`03862670 Debug session time: Sat Oct 29 21:44:50.697 2011 (UTC + 1:00) System Uptime: 0 days 0:40:26.541 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {1, 2, 0, fffff800036a5b28} Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1c8 ) 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: 0000000000000001, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff800036a5b28, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038cc100 0000000000000001 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+1c8 fffff800`036a5b28 488b4500 mov rax,qword ptr [rbp] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffff80003836f70 rdx=fffffa8009a60268 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036a5b28 rsp=fffff80000b9c560 rbp=0000000000000001 r8=fffffa8009bf5530 r9=000000000000009b r10=fffff8000380fe80 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!KiInsertTimerTable+0x1c8: fffff800`036a5b28 488b4500 mov rax,qword ptr [rbp] ss:0018:00000000`00000001=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036991e9 to fffff80003699c40 STACK_TEXT: fffff800`00b9c288 fffff800`036991e9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9c290 fffff800`03697e60 : 00000000`40a00088 00000000`0003b3f1 fffffa80`04cb2d30 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c3d0 fffff800`036a5b28 : ffffffff`fffe7960 fffff800`036a55fc fffff800`0380fe80 00000000`00000000 : nt!KiPageFault+0x260 fffff800`00b9c560 00000000`00000000 : fffff800`00b9c608 00000000`00000002 00000000`00025f9a fffff800`036a543d : nt!KiInsertTimerTable+0x1c8 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInsertTimerTable+1c8 fffff800`036a5b28 488b4500 mov rax,qword ptr [rbp] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiInsertTimerTable+1c8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+1c8 BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+1c8 Followup: MachineOwner ---------

Praticamente il PC non stava facendo nulla di rilevante: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:WindowsMinidump102911-36613-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:Windowssymbols*[url]http://msdl.microsoft.com/download/symbols[/url] Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`03890670 Debug session time: Sat Oct 29 19:33:50.858 2011 (UTC + 2:00) System Uptime: 0 days 8:34:07.075 Loading Kernel Symbols ............................................................... ................................................................ ........................................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {24, 2, 0, fffff800036d06cb} Probably caused by : nwifi.sys ( nwifi!ExtSTAReceivePacket+a9e ) Followup: MachineOwner --------- 1: 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: 0000000000000024, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff800036d06cb, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fa100 0000000000000024 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTimerWaitTest+22b fffff800`036d06cb 418b4624 mov eax,dword ptr [r14+24h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff8800371b350 -- (.trap 0xfffff8800371b350) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800a76f700 rbx=0000000000000000 rcx=fffffa800aaa4960 rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d06cb rsp=fffff8800371b4e8 rbp=fffffa800a961c28 r8=fffff880009f4301 r9=0000000000000004 r10=0000000000000013 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiTimerWaitTest+0x22b: fffff800`036d06cb 418b4624 mov eax,dword ptr [r14+24h] ds:00000000`00000024=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036c71e9 to fffff800036c7c40 STACK_TEXT: fffff880`0371b208 fffff800`036c71e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0371b210 fffff800`036c5e60 : fffffa80`0c7af4f0 fffff880`01d170eb fffffa80`09fed8d0 fffffa80`0a961c28 : nt!KiBugCheckDispatch+0x69 fffff880`0371b350 fffff800`036d06cb : fffffa80`04cd3a70 00000000`00000041 00000000`00000000 1100d3dc`e1bc7170 : nt!KiPageFault+0x260 fffff880`0371b4e8 fffffa80`0a93c854 : fffffa80`0a961c20 fffff880`009f2180 00000000`00000001 00000000`00000102 : nt!KiTimerWaitTest+0x22b fffff880`0371b568 fffffa80`0a961c20 : fffff880`009f2180 00000000`00000001 00000000`00000102 fffff880`0314fc46 : 0xfffffa80`0a93c854 fffff880`0371b570 fffff880`009f2180 : 00000000`00000001 00000000`00000102 fffff880`0314fc46 00000000`00000000 : 0xfffffa80`0a961c20 fffff880`0371b578 00000000`00000001 : 00000000`00000102 fffff880`0314fc46 00000000`00000000 fffffa80`09fe8010 : 0xfffff880`009f2180 fffff880`0371b580 00000000`00000102 : fffff880`0314fc46 00000000`00000000 fffffa80`09fe8010 fffffa80`0a93c850 : 0x1 fffff880`0371b588 fffff880`0314fc46 : 00000000`00000000 fffffa80`09fe8010 fffffa80`0a93c850 fffffa80`0a93c850 : 0x102 fffff880`0371b590 fffff880`0314f3f2 : 00000000`00000103 00000000`00000001 fffffa80`09fe8010 fffff880`0371b8a8 : nwifi!ExtSTAReceivePacket+0xa9e fffff880`0371b670 fffff880`0312f053 : fffffa80`0c7af4f0 00000000`00000000 00000000`0000ff02 00000000`00000000 : nwifi!ExtSTAReceivePacket+0x24a fffff880`0371b6c0 fffff880`0312f808 : fffffa80`08185010 fffffa80`0b776770 fffffa80`0b776770 fffffa80`0b776770 : nwifi!Pt6RepackRecvNBL+0x9ef fffff880`0371b910 fffff880`01c62900 : fffff880`0371b960 00000000`00000000 00000000`00000000 fffff880`01d1736f : nwifi!Pt6Receive+0x2b0 fffff880`0371b970 fffff800`036056e5 : fffffa80`07ebb000 00000000`00000d00 00000000`00000000 00000000`00000000 : ndis!NdisFIndicateReceiveNetBufferLists+0x80 fffff880`0371b9b0 fffff880`03f42301 : 00000000`00000000 fffff880`04cbad40 fffff880`04cbb5b8 fffffa80`079c9000 : hal!HalpDmaReturnToScatterPool+0x4d fffff880`0371ba00 00000000`00000000 : fffff880`04cbad40 fffff880`04cbb5b8 fffffa80`079c9000 00000000`00000000 : 0xfffff880`03f42301 STACK_COMMAND: kb FOLLOWUP_IP: nwifi!ExtSTAReceivePacket+a9e fffff880`0314fc46 4881c4a0000000 add rsp,0A0h SYMBOL_STACK_INDEX: 9 SYMBOL_NAME: nwifi!ExtSTAReceivePacket+a9e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nwifi IMAGE_NAME: nwifi.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b FAILURE_BUCKET_ID: X64_0xA_nwifi!ExtSTAReceivePacket+a9e BUCKET_ID: X64_0xA_nwifi!ExtSTAReceivePacket+a9e Followup: MachineOwner ---------

mi sta capitando una cosa col razer mahba: in pratica al riavvio del pc non si muove il cursore ma il tasto destro invece apre il menu...fa cosi fino a che non premo i tasti dei dpi...ad un altro riavvio addirittura è stato necessario scollegare e ricollegare l'usb (tutto cio in modalità wired)....sapete di cosa si tratta e come si puo risolvere?

si è riverificato ma in un altro gioco Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:WindowsMinidump102011-23197-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03665000 PsLoadedModuleList = 0xfffff800`038aa670 Debug session time: Thu Oct 20 00:43:13.616 2011 (UTC + 2:00) System Uptime: 0 days 3:05:25.833 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 0, fffff800036eda17} Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+b7 ) 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: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff800036eda17, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003914100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+b7 fffff800`036eda17 488b4500 mov rax,qword ptr [rbp] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8009cea610 rdx=fffffa8009a51f18 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036eda17 rsp=fffff80000b9c560 rbp=0000000000000000 r8=fffffa8004801610 r9=00000000000000e6 r10=fffff80003857e80 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiInsertTimerTable+0xb7: fffff800`036eda17 488b4500 mov rax,qword ptr [rbp] ss:0018:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036e11e9 to fffff800036e1c40 STACK_TEXT: fffff800`00b9c288 fffff800`036e11e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9c290 fffff800`036dfe60 : fffff800`00b9cc58 00000000`00000000 fffffa80`09a51f02 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c3d0 fffff800`036eda17 : ffffffff`fffe7960 fffff800`036ed5fc 00000000`00000000 fffffa80`00000000 : nt!KiPageFault+0x260 fffff800`00b9c560 00000000`00000000 : fffff800`00b9c608 00000000`00000002 00000000`000ae1e5 fffff800`036ed43d : nt!KiInsertTimerTable+0xb7 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInsertTimerTable+b7 fffff800`036eda17 488b4500 mov rax,qword ptr [rbp] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiInsertTimerTable+b7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+b7 BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+b7 Followup: MachineOwner ---------

ok grazie, credo di poter essere soddisfatto....per l'access time a 15 si puo fare qualcosa?

Aggiorno la situazione sulle prestazioni di questo Raid0: in pratica ho aggiornato i drivers Intel Storage ecc ecc all'ultima versione ed ora ho questi risultati Dici che ho risolto l'anomalia del punteggio basso e del grafico "non" duscendente? Adesso rientra piu o meno nella norma o sono comunque basso?

i drivers li ho aggiornati proprio 2 giorni fa (con gli ultimi) e sono in oc, stabile e da un bel po di tempo, nessun problema in altri giochi e nemmeno in questo dopo lunghe sessioni...non si sa precisamente la fonte?

....si tratta di questa: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:WindowsMinidump100711-17628-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03608000 PsLoadedModuleList = 0xfffff800`0384d670 Debug session time: Fri Oct 7 01:11:25.683 2011 (UTC + 2:00) System Uptime: 0 days 3:32:56.526 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FC, {fffff880035d3180, 80000000a8ffa963, fffff80000ba2600, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4433c ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc) An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff880035d3180, Virtual address for the attempted execute. Arg2: 80000000a8ffa963, PTE contents. Arg3: fffff80000ba2600, (reserved) Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFC PROCESS_NAME: witcher2.exe CURRENT_IRQL: 2 TRAP_FRAME: fffff80000ba2600 -- (.trap 0xfffff80000ba2600) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007c3dee8 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8007c3dea8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880035d3180 rsp=fffff80000ba2798 rbp=0000000000000001 r8=fffff800037fd001 r9=0000000000000002 r10=000000000000003a r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe nc fffff880`035d3180 801f00 sbb byte ptr [rdi],0 ds:e810:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000362efc0 to fffff80003684c40 STACK_TEXT: fffff800`00ba2498 fffff800`0362efc0 : 00000000`000000fc fffff880`035d3180 80000000`a8ffa963 fffff800`00ba2600 : nt!KeBugCheckEx fffff800`00ba24a0 fffff800`03682d6e : fffff800`00ba2e88 00000000`00000000 fffffa80`0978e902 fffffa80`07c3dea8 : nt! ?? ::FNODOBFM::`string'+0x4433c fffff800`00ba2600 fffff880`035d3180 : fffffa80`07c3dea8 fffff800`037fae80 00000000`00000000 00000003`40380000 : nt!KiPageFault+0x16e fffff800`00ba2798 fffffa80`07c3dea8 : fffff800`037fae80 00000000`00000000 00000003`40380000 00000000`0000000e : 0xfffff880`035d3180 fffff800`00ba27a0 fffff800`037fae80 : 00000000`00000000 00000003`40380000 00000000`0000000e 00000000`00000000 : 0xfffffa80`07c3dea8 fffff800`00ba27a8 00000000`00000000 : 00000003`40380000 00000000`0000000e 00000000`00000000 00000000`0000000f : nt!KiInitialPCR+0x180 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4433c fffff800`0362efc0 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4433c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+4433c BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+4433c Followup: MachineOwner ---------

si ho inserito allegati.... secondo voi, se prescindiamo dall'oggetto con la sua dicitura spam, guardando solo il contenuto, potrebbe essere anche il messaggio di risposta (che viene generato in automatico, come mi sta capitando con altri enti) che mi dice dell'avvenuta ricezione della mia candidatura, e che questo messaggio è stato rilevato come spam da libero e me la segnalato come tale (o meglio come sospetto visto che non me l'ha messo nella cartella spam)? non so leggendo il contenuto sembra proprio quel tipo di messaggi :cheazz:

si l'oggetto della mail che ho ricevuto è proprio quello e il contenuto è questo: Your message To: EDPS Stage Subject: [sPAM SUSPECTED] candidature Sent: Sat, 1 Oct 2011 13:02:50 +0200 was read on Mon, 3 Oct 2011 18:44:45 +0200? Final-Recipient: RFC822; Stage@edps.europa.eu Disposition: automatic-action/MDN-sent-automatically; displayed X-MSExch-Correlation-Key: 3grJ+py2OkaHR3g5/sJ9Cg== Original-Message-ID: (mica c'è qualche info "compromettente"? :cheazz: sse no lo cancello) (p.s. credo cdi aver messo anche l'avviso di lettura)

ragazzi mi è arrivato un messaggio email, in risposta ad una mia mail di candidatura ad una cosa, ed ha questa forma(in particolare l'oggetto): "Read: [spam Suspected] candidature" (la mail inviata aveva come oggetto "candidature") ...vi chiedo se questa è una forma di avviso di thunderbirds o del mio account di mail (libero) oppure è una sorta di messaggio di risposta da parte loro (l'ente al quale mi sono candidato) che sospettano sia la mia mail uno spam?

a me interessano i Fps minimi, in quanto per i massimi (almeno fino ad ora) non ho problemi...in particolare con un titolo nel quale in media i fps sono buoni, ma alcuni picchi minimi provocano un po di stattering in alcune situazioni ed ho letto che la sezione disco influisce sui fps min.....confermato (o ferse qualcuno si è illuso) da testimonianze di miglioramenti in quel gioco utilizzando ssd

quindi dite che in termini pratici upgrade ad un disco di ultima generazione o ad un raid 0 di questi non porta evidenti miglioramenti nei giochi o cambierebbe in maniera rilevante la situazione fps? (risultati invece ottenibili solo con un passaggio a ssd) p.s. ho 2 seagate barracuda sata 2 7200.10

Il Mio Disco: Ragazzi vorrei saere un po, da chi ha piu esperienza di me in materia di benchmark e prestazioni dei dischi, come puo essere valutato il mio disco, facendo un paragone in "assoluto" e non sulla base di stessi modelli o categorie di dischi, quindi in generale paragonando le sue prestazioni (e i risultati del benchmark) con quelle di altre situazioni, ovvero: - un "buon" SataII (7200giri) di ultima generazione - un Raid0 dei precedenti oppure in alternativa un disco piu veloce (tipo10/15k) ...quindi, paragonato ad ognuna di queste situazioni, come va il mio disco in generale e sopratutto in particolare X situazioni Videogiochi, e quindi un upgrade ad ognunoa delle tre situazioni prospettate che guadagno "effettivo" di prestazioni in game porterebbe.