Benvenuto in Tech Station Forum.
+ Rispondi alla Discussione
Pagina 1 di 2 1 2 UltimaUltima
Risultati da 1 a 10 di 15
  1. #1
    Junior Member PASTA is on a distinguished road
    Data Registrazione
    Dec 2010
    Messaggi
    8

    Vari Riavvii e BSOD : c' una causa comune?

    Ragazzi da quando ho messo su questo sistema che mi capitano vari riavvii e bsod quando gioco.
    Ora vi posto l'evoluzione dei vari crash: sapreste dirmi se c' un unico problema di fondo o se si tratta sempre di cose diverse?...quindi "Fonte" e magari "Soluzione"

    SITUAZIONE 1

    Ho avuto lo stesso tipo di crash in un paio di situazioni diverse (l'iltima giocando ad arma) :

    Codice:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {1, 2, 8, 1}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000001, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000001, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330e0e0
     0000000000000001 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +6363336564653465
    00000000`00000001 ??              ???
    
    PROCESS_NAME:  ARMA2.exe
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    TRAP_FRAME:  fffff88003522580 -- (.trap 0xfffff88003522580)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000400 rbx=0000000000000000 rcx=0000000040b50000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000001 rsp=fffff88003522718 rbp=00000000009f2180
     r8=0000000006173ea8  r9=00000000fffffa80 r10=fffff80003066000
    r11=fffff88003522760 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    00000000`00000001 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030d5ca9 to fffff800030d6740
    
    FAILED_INSTRUCTION_ADDRESS: 
    +6363336564653465
    00000000`00000001 ??              ???
    
    STACK_TEXT:  
    fffff880`03522438 fffff800`030d5ca9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`03522440 fffff800`030d4920 : fffffa80`08c4b128 fffff880`035227b0 fffffa80`08c4b120 fffffa80`08c4b060 : nt!KiBugCheckDispatch+0x69
    fffff880`03522580 00000000`00000001 : fffff800`030e229e fffffa80`058af8e0 fffff880`04639f79 fffffa80`06112400 : nt!KiPageFault+0x260
    fffff880`03522718 fffff800`030e229e : fffffa80`058af8e0 fffff880`04639f79 fffffa80`06112400 00000000`00000001 : 0x1
    fffff880`03522720 fffff800`030e1dd6 : fffffa80`08c4b168 fffffa80`08c4b168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff880`03522790 fffffa80`05fd8a10 : 00000000`00000000 fffffa80`06173d20 fffffa80`06173d20 fffff880`046365c2 : nt!KiProcessExpiredTimerList+0xc6
    fffff880`03522de0 00000000`00000000 : fffffa80`06173d20 fffffa80`06173d20 fffff880`046365c2 fffff880`010cecc0 : 0xfffffa80`05fd8a10
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiPageFault+260
    fffff800`030d4920 440f20c0        mov     rax,cr8
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiPageFault+260
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
    
    BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
    
    Followup: MachineOwner
    ---------



    SITUAZIONE 2

    questo l'elenco degli eventi con i tre errori al momento del riavvio mentre ero in game, e mi sembra di aver capito che "critico" levento del crash











    poi in orine cronologico questo avviso












    poi l'ultimo l'avviso relativo al risultato del controllo errori con la segnalazione dello stesso e il salvataggio nel minidunp











    ecco il minidump (mi da solo queste cose: non' incompleto?):




    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\111410-24024-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03240e50
    Debug session time: Sun Nov 14 00:45:37.731 2010 (UTC + 1:00)
    System Uptime: 0 days 7:10:34.606
    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, fffff8000307d34b}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
    
    Followup: MachineOwner




    eccone un altro dello stesso dump con altri symnols:





    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\111410-24024-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03240e50
    Debug session time: Sun Nov 14 00:45:37.731 2010 (UTC + 1:00)
    System Uptime: 0 days 7:10:34.606
    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, fffff8000307d34b}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
    
    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: fffff8000307d34b, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ab0e0
     0000000000000024 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiTimerWaitTest+22b
    fffff800`0307d34b 418b4624        mov     eax,dword ptr [r14+24h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  arma2oa.exe
    
    TRAP_FRAME:  fffff88003122580 -- (.trap 0xfffff88003122580)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000307d34b rsp=fffff88003122718 rbp=fffffa8007e1f588
     r8=fffff880009f4301  r9=0000000000000002 r10=00000000000000f5
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiTimerWaitTest+0x22b:
    fffff800`0307d34b 418b4624        mov     eax,dword ptr [r14+24h] ds:5128:00000000`00000024=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003072ca9 to fffff80003073740
    
    STACK_TEXT:  
    fffff880`03122438 fffff800`03072ca9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03122440 fffff800`03071920 : fffffa80`0818ea10 fffffa80`07e1f588 fffffa80`0818ea10 00000000`0000001b : nt!KiBugCheckDispatch+0x69
    fffff880`03122580 fffff800`0307d34b : fffff880`01a730a1 00000000`00000021 00000000`00276b9b 00000000`00276be2 : nt!KiPageFault+0x260
    fffff880`03122718 fffff880`03163180 : fffffa80`07e1f580 00000000`00000000 fffffa80`03f96060 00000000`00000102 : nt!KiTimerWaitTest+0x22b
    fffff880`03122798 fffffa80`07e1f580 : 00000000`00000000 fffffa80`03f96060 00000000`00000102 00000000`0000000c : 0xfffff880`03163180
    fffff880`031227a0 00000000`00000000 : fffffa80`03f96060 00000000`00000102 00000000`0000000c 00000000`00000000 : 0xfffffa80`07e1f580
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiTimerWaitTest+22b
    fffff800`0307d34b 418b4624        mov     eax,dword ptr [r14+24h]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KiTimerWaitTest+22b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b
    
    BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b
    
    Followup: MachineOwner





    questo invece quello che mi dice l'utility bluscreen view:















    SITUAZIONE 3



    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\111910-19344-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: D:\Symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e50
    Debug session time: Fri Nov 19 16:10:25.002 2010 (UTC + 1:00)
    System Uptime: 0 days 3:58:07.266
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {8, 2, 1, fffff88002a0895e}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nwifi.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nwifi.sys
    *** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
    Probably caused by : hardware ( nwifi+895e )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88002a0895e, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
     0000000000000008 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nwifi+895e
    fffff880`02a0895e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  EFLC.exe
    
    TRAP_FRAME:  fffff88003122440 -- (.trap 0xfffff88003122440)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003122570
    rdx=0000000001eaafb8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002a0895e rsp=fffff880031225d0 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa80065b462e r10=466cedf76ebf7249
    r11=fffffa80065b4060 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nwifi+0x895e:
    fffff880`02a0895e 68488b97c0      push    0FFFFFFFFC0978B48h
    Resetting default scope
    
    MISALIGNED_IP: 
    nwifi+895e
    fffff880`02a0895e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    LAST_CONTROL_TRANSFER:  from fffff800030c9ca9 to fffff800030ca740
    
    STACK_TEXT:  
    fffff880`031222f8 fffff800`030c9ca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`03122300 fffff800`030c8920 : fffffa80`06111102 fffffa80`043b42f0 fffffa80`06111102 fffffa80`06111102 : nt!KiBugCheckDispatch+0x69
    fffff880`03122440 fffff880`02a0895e : fffffa80`0881e010 00000000`000005ce fffffa80`043b42f0 fffffa80`00000000 : nt!KiPageFault+0x260
    fffff880`031225d0 fffffa80`0881e010 : 00000000`000005ce fffffa80`043b42f0 fffffa80`00000000 00000000`00000000 : nwifi+0x895e
    fffff880`031225d8 00000000`000005ce : fffffa80`043b42f0 fffffa80`00000000 00000000`00000000 fffff880`04239f79 : 0xfffffa80`0881e010
    fffff880`031225e0 fffffa80`043b42f0 : fffffa80`00000000 00000000`00000000 fffff880`04239f79 00000000`c000000d : 0x5ce
    fffff880`031225e8 fffffa80`00000000 : 00000000`00000000 fffff880`04239f79 00000000`c000000d fffffa80`0892fa70 : 0xfffffa80`043b42f0
    fffff880`031225f0 00000000`00000000 : fffff880`04239f79 00000000`c000000d fffffa80`0892fa70 fffffa80`08000302 : 0xfffffa80`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nwifi+895e
    fffff880`02a0895e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nwifi+895e
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys
    
    BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys
    
    Followup: MachineOwner
    ---------


    SITUAZIONE 4


    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\120810-20389-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03450e50
    Debug session time: Wed Dec  8 22:32:49.086 2010 (UTC + 1:00)
    System Uptime: 0 days 1:55:46.351
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, 100000040, 8, 100000040}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: 0000000100000040, The address that the exception occurred at
    Arg3: 0000000000000008, Parameter 0 of the exception
    Arg4: 0000000100000040, Parameter 1 of the exception
    
    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: 
    +3764663965323138
    00000001`00000040 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000008
    
    EXCEPTION_PARAMETER2:  0000000100000040
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bb0e0
     0000000100000040 
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s.
    
    BUGCHECK_STR:  0x1E_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  arma2oa.exe
    
    CURRENT_IRQL:  0
    
    EXCEPTION_RECORD:  fffff8800a8ab248 -- (.exr 0xfffff8800a8ab248)
    ExceptionAddress: 0000000100000040
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000008
       Parameter[1]: 0000000100000040
    Attempt to execute non-executable address 0000000100000040
    
    TRAP_FRAME:  fffff8800a8ab2f0 -- (.trap 0xfffff8800a8ab2f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800811b050
    rdx=000000006fa9c000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000100000040 rsp=fffff8800a8ab480 rbp=fffff8a00b0a0db0
     r8=0000000000000800  r9=fffffa8008503000 r10=0000000000000001
    r11=0000000000008300 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    00000001`00000040 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032bda39 to fffff80003283740
    
    STACK_TEXT:  
    fffff880`0a8aaa78 fffff800`032bda39 : 00000000`0000001e ffffffff`c0000005 00000001`00000040 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0a8aaa80 fffff800`03282d82 : fffff880`0a8ab248 fffff8a0`0b8ad000 fffff880`0a8ab2f0 fffff880`0a8ab5f0 : nt!KiDispatchException+0x1b9
    fffff880`0a8ab110 fffff800`032818fa : 00000000`00000008 fffff8a0`0b8ad000 fffff880`0a8ab300 fffff880`04f95f00 : nt!KiExceptionDispatch+0xc2
    fffff880`0a8ab2f0 00000001`00000040 : fffff8a0`0b8ad000 fffff880`0a8abb30 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x23a
    fffff880`0a8ab480 fffff8a0`0b8ad000 : fffff880`0a8abb30 00000000`00000000 00000000`00000001 00000000`00000000 : 0x1`00000040
    fffff880`0a8ab488 fffff880`0a8abb30 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffff8a0`0b8ad000
    fffff880`0a8ab490 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`0a8abca0 : 0xfffff880`0a8abb30
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDispatchException+1b9
    fffff800`032bda39 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!KiDispatchException+1b9
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1b9
    
    BUCKET_ID:  X64_0x1E_c0000005_nt!KiDispatchException+1b9
    
    Followup: MachineOwner
    ---------

  2. #2
    Staff ciberbastard is on a distinguished road
    Data Registrazione
    Apr 2010
    Messaggi
    1,821
    dunque posta prima di tutto la tua configurazione hardware, gioco in utilizzo al momento, dopo quanto tempo crasha, poi aggiungi anche se usi periferiche nuove e il sistema operativo usato

  3. #3
    Junior Member PASTA is on a distinguished road
    Data Registrazione
    Dec 2010
    Messaggi
    8
    asus p6t se - i7 920 - 4gb ddr3 1600 - 4870x2 - nessuna periferica nuova - w7 64bit
    crasha spesso con arma ma anche con altri (gta lost plant2 ecc)...spesso dopo lunghe sessioni ma anche no

  4. #4
    Staff ciberbastard is on a distinguished road
    Data Registrazione
    Apr 2010
    Messaggi
    1,821
    li ho visto un errore usb, e mi dava un errore simile con i giochi quando avevo una porta usb rotta a cui erano collegate le cuffie, dopo un po di tempo bsod, innanzi tutto prova a staccare le periferiche e utilizzare solo il mouse e a cambiarlo, se non hai nulla di rotto poi testiamo i vari componenti e programmi

  5. #5
    Amministratore Deos is on a distinguished road
    Data Registrazione
    Oct 2007
    Messaggi
    2,914
    Citazione Originariamente Scritto da ciberbastard Visualizza Messaggio
    li ho visto un errore usb, e mi dava un errore simile con i giochi quando avevo una porta usb rotta a cui erano collegate le cuffie, dopo un po di tempo bsod, innanzi tutto prova a staccare le periferiche e utilizzare solo il mouse e a cambiarlo, se non hai nulla di rotto poi testiamo i vari componenti e programmi
    Direi potrebbe esser un buon punto da cui partire

    \Deos

  6. #6
    Junior Member PASTA is on a distinguished road
    Data Registrazione
    Dec 2010
    Messaggi
    8
    come usb ho il controllerxbox360, il mouse, la tastiera, e l'adattatore wifi....mi sa che posso fare a meno solo del controller...oppure ne uso 2 sulle usb frontali del case (che non sono state utilizzate nei momenti di bsod) e una soltanto dietro, magari il mouse cambiando porta nel caso si presenti....che dite?

  7. #7
    Staff ciberbastard is on a distinguished road
    Data Registrazione
    Apr 2010
    Messaggi
    1,821
    prova a usare solo il mouse per qualche prova e cambiandolo di porta ogni tanto, almeno ti assicuri che le usb funzionino.non sono fondamentali le altre periferiche per il funzionamento del pc, poi una volta accertato che non son le usb riattacchi tutto

  8. #8
    Junior Member PASTA is on a distinguished road
    Data Registrazione
    Dec 2010
    Messaggi
    8
    intanto altre 2 bsod (con mouse e tastiera collegati sul front panel del case):



    1)




    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\120910-17706-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03489e50
    Debug session time: Thu Dec  9 14:06:55.126 2010 (UTC + 1:00)
    System Uptime: 0 days 1:12:46.016
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {8, 2, 1, fffff88002e5a95e}
    
    Unable to load image \SystemRoot\system32\DRIVERS\netr7364.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for netr7364.sys
    *** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
    Probably caused by : hardware ( nwifi!Pt6RepackRecvNBL+2fa )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88002e5a95e, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f40e0
     0000000000000008
    
    CURRENT_IRQL:  2
    
    FAULTING_IP:
    nwifi!Pt6RepackRecvNBL+2fa
    fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  LP2DX9.exe
    
    TRAP_FRAME:  fffff88003322440 -- (.trap 0xfffff88003322440)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003322570
    rdx=0000000003ed5628 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002e5a95e rsp=fffff880033225d0 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa8004542ad9 r10=f5bc2f32e757d9b7
    r11=fffffa80045429f0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nwifi!Pt6RepackRecvNBL+0x2fa:
    fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h
    Resetting default scope
    
    MISALIGNED_IP:
    nwifi!Pt6RepackRecvNBL+2fa
    fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    LAST_CONTROL_TRANSFER:  from fffff800032bbca9 to fffff800032bc740
    
    STACK_TEXT:  
    fffff880`033222f8 fffff800`032bbca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`03322300 fffff800`032ba920 : 00000000`00000000 fffffa80`04356b10 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`03322440 fffff880`02e5a95e : fffffa80`0885d010 00000000`000000e9 fffffa80`04356b10 fffffa80`00000000 : nt!KiPageFault+0x260
    fffff880`033225d0 fffff880`02e5b6c8 : 00000000`00000000 00000000`00000004 fffffa80`07c101b0 fffffa80`0885d010 : nwifi!Pt6RepackRecvNBL+0x2fa
    fffff880`033226d0 fffff880`018489e9 : fffffa80`083171a0 00000000`00000000 00000000`00000001 fffffa80`07c101b0 : nwifi!Pt6Receive+0x170
    fffff880`03322730 fffff880`01848980 : fffffa80`0837f328 fffff880`01c300c7 fffff880`01c31340 fffff880`055b1cab : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
    fffff880`03322770 fffff880`01c2c9c0 : fffff880`01c33110 00000000`00000000 00000000`00000001 fffffa80`0837fd78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
    fffff880`033227b0 fffff880`018602b7 : fffffa80`07d351a0 fffffa80`0823d650 fffffa80`0823d650 00000000`00000001 : vwififlt!FilterReceiveNetBufferLists+0x158
    fffff880`03322810 fffff880`0427118f : fffffa80`0822f8c0 00000000`00000000 fffffa80`0841802e 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xccef
    fffff880`03322860 fffffa80`0822f8c0 : 00000000`00000000 fffffa80`0841802e 00000000`00000000 fffffa80`00000002 : netr7364+0x518f
    fffff880`03322868 00000000`00000000 : fffffa80`0841802e 00000000`00000000 fffffa80`00000002 fffffa80`08202878 : 0xfffffa80`0822f8c0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP:
    nwifi!Pt6RepackRecvNBL+2fa
    fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+2fa
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys
    
    BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys
    
    Followup: MachineOwner
    ---------






    2)



    Codice:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\120910-19468-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`0343ee50
    Debug session time: Thu Dec  9 16:15:21.449 2010 (UTC + 1:00)
    System Uptime: 0 days 2:06:56.713
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8005ee1028, be000000, 800400}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8005ee1028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  LP2DX9.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT: 
    fffff800`04b92a98 fffff800`037ef903 : 00000000`00000124 00000000`00000000 fffffa80`05ee1028 00000000`be000000 : nt!KeBugCheckEx
    fffff800`04b92aa0 fffff800`03387593 : 00000000`00000001 fffffa80`058fbcb0 00000000`00000000 fffffa80`058fbd00 : hal!HalBugCheckSystem+0x1e3
    fffff800`04b92ae0 fffff800`037ef5c8 : 00000000`00000728 fffffa80`058fbcb0 fffff800`04b92e70 fffff800`04b92e00 : nt!WheaReportHwError+0x263
    fffff800`04b92b40 fffff800`037eef1a : fffffa80`058fbcb0 fffff800`04b92e70 fffffa80`058fbcb0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`04b92c90 fffff800`037eedd5 : 00000000`00000004 00000000`00000001 fffff800`04b92ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`04b92cd0 fffff800`037e2e88 : 00000000`058cdcdc 00000000`ffffffff 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`04b92d00 fffff800`0326ffec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`04b92d30 fffff800`0326fe53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`04b92e70 00000000`004481e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0018bcbc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4481e5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner
    ---------







  9. #9
    Staff ciberbastard is on a distinguished road
    Data Registrazione
    Apr 2010
    Messaggi
    1,821
    allora dubito che siano le usb, hai provato a monitorare le temperature mentre giochi?

  10. #10
    Junior Member PASTA is on a distinguished road
    Data Registrazione
    Dec 2010
    Messaggi
    8
    tutte buone sotto liquido


 

Members who have read this thread : 0

You do not have permission to view the list of names.

Tag per Questa Discussione

Permessi di Scrittura

  • Tu non puoi inviare nuove discussioni
  • Tu non puoi inviare risposte
  • Tu non puoi inviare allegati
  • Tu non puoi modificare i tuoi messaggi