IOnterpretazione BSOD
-
....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 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 --------- -
il bsod da quando leggo è scaturito da un errore nei driver
-
inizia ad aggiornare i driver grafici, presumo stessi giocando...
se in OC o a default?
-
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?
-
no è un bsod generico relativo ad i driver sicuramente della vga, spesso può accadere
-
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 --------- -
sempre questione di driver
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi