adsko utworzono 23 listopada 2014 utworzono 23 listopada 2014 Ostatnio grywam w grę przeglądarkową i zaczeły mi wyskakiwać blue screeny. Nie jestem pewien czy to na pewno od tego, dlatego daje info z WinDbg. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\112314-29889-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0xfffff800`03657000 PsLoadedModuleList = 0xfffff800`0389a890 Debug session time: Sun Nov 23 00:30:48.722 2014 (GMT+1) System Uptime: 0 days 21:54:54.612 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\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 ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ................ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 0, fffff800036d2e52} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.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 *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : ntoskrnl.exe ( nt+7be52 ) 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: 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: fffff800036d2e52, 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 *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* 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: nt FAULTING_MODULE: fffff80003657000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000000000000 CURRENT_IRQL: 0 FAULTING_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt+0x75bc0 fffff880`095a0780 00000000`0000000a : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`036d2e52 : nt+0x75169 fffff880`095a0788 00000000`00000000 : 00000000`00000002 00000000`00000000 fffff800`036d2e52 fffffa80`07c4cb10 : 0xa STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] SYMBOL_NAME: nt+7be52 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- WARNING: Whitespace at end of path element 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: 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: fffff800036d2e52, 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 *** *** *** ************************************************************************* 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: nt FAULTING_MODULE: fffff80003657000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 0 FAULTING_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt+0x75bc0 fffff880`095a0780 00000000`0000000a : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`036d2e52 : nt+0x75169 fffff880`095a0788 00000000`00000000 : 00000000`00000002 00000000`00000000 fffff800`036d2e52 fffffa80`07c4cb10 : 0xa STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] SYMBOL_NAME: nt+7be52 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- WARNING: Whitespace at end of path element 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: 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: fffff800036d2e52, 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 *** *** *** ************************************************************************* 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: nt FAULTING_MODULE: fffff80003657000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 0 FAULTING_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt+0x75bc0 fffff880`095a0780 00000000`0000000a : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`036d2e52 : nt+0x75169 fffff880`095a0788 00000000`00000000 : 00000000`00000002 00000000`00000000 fffff800`036d2e52 fffffa80`07c4cb10 : 0xa STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt+7be52 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] SYMBOL_NAME: nt+7be52 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
Youki komentarz 23 listopada 2014 komentarz 23 listopada 2014 Wszystko fajnie tylko: * Kernel symbols are WRONG. Please fix symbols to do analysis. Oznacza to, że musimy pobrać symbole do swojego systemu dzięki którym odczytamy w całości plik minidump - na tym etapie jest on niekompletny i może wskazywać nie ten plik co trzeba.Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy File -> Symbol File Path -> wpisujemy:SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
adsko komentarz 23 listopada 2014 Autor komentarz 23 listopada 2014 WARNING: Whitespace at end of path element Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\112314-29889-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0xfffff800`03657000 PsLoadedModuleList = 0xfffff800`0389a890 Debug session time: Sun Nov 23 00:30:48.722 2014 (GMT+1) System Uptime: 0 days 21:54:54.612 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, fffff800036d2e52} Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f ) 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: 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: fffff800036d2e52, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003904100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880095a08c0 -- (.trap 0xfffff880095a08c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009ed180 rdx=fffffa800ae61230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d2e52 rsp=fffff880095a0a50 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8009de8c40 r10=fffffa8009de8c40 r11=fffff880095a0ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] ds:7dc0:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`095a0780 fffff800`036cade0 : fffff8a0`17a0b990 00000000`00000040 fffff8a0`18f77ec8 fffffa80`0ae61238 : nt!KiBugCheckDispatch+0x69 fffff880`095a08c0 fffff800`036d2e52 : fffffa80`0ae611c0 fffffa80`09afa410 00000000`00000000 fffffa80`07794ad0 : nt!KiPageFault+0x260 fffff880`095a0a50 fffff800`036d1256 : 00000000`00000000 fffff880`0fdc51d8 00000000`00000000 fffffa80`09afa410 : nt!KiSignalSynchronizationObject+0x42 fffff880`095a0aa0 fffff880`0fdd547f : fffffa80`00000000 00000000`00000000 fffffa80`07d61a00 fffff880`095a0b60 : nt!KeSetEvent+0x106 fffff880`095a0b10 fffff880`0fdf32e9 : fffffa80`00000000 fffffa80`09afa410 00000000`0000000f fffff880`0fdf5085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`095a0b60 fffff880`0fdf2574 : fffff880`02fdc040 fffffa80`0cb12010 00000000`00000000 fffffa80`09afa410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`095a0b90 fffff880`0fdf2012 : 00000000`0001663d fffffa80`0cb12010 00000000`00000080 fffffa80`09afa410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`095a0bc0 fffff800`0396873a : 00000000`03179c6a fffffa80`0984bb50 fffffa80`07037ae0 fffffa80`0984bb50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`095a0c00 fffff800`036bd8e6 : fffff880`02fd7180 fffffa80`0984bb50 fffff880`02fe20c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`095a0c40 00000000`00000000 : fffff880`095a1000 fffff880`0959b000 fffff880`095a0540 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`0fdd547f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f 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: 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: fffff800036d2e52, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880095a08c0 -- (.trap 0xfffff880095a08c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009ed180 rdx=fffffa800ae61230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d2e52 rsp=fffff880095a0a50 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8009de8c40 r10=fffffa8009de8c40 r11=fffff880095a0ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] ds:7dc0:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`095a0780 fffff800`036cade0 : fffff8a0`17a0b990 00000000`00000040 fffff8a0`18f77ec8 fffffa80`0ae61238 : nt!KiBugCheckDispatch+0x69 fffff880`095a08c0 fffff800`036d2e52 : fffffa80`0ae611c0 fffffa80`09afa410 00000000`00000000 fffffa80`07794ad0 : nt!KiPageFault+0x260 fffff880`095a0a50 fffff800`036d1256 : 00000000`00000000 fffff880`0fdc51d8 00000000`00000000 fffffa80`09afa410 : nt!KiSignalSynchronizationObject+0x42 fffff880`095a0aa0 fffff880`0fdd547f : fffffa80`00000000 00000000`00000000 fffffa80`07d61a00 fffff880`095a0b60 : nt!KeSetEvent+0x106 fffff880`095a0b10 fffff880`0fdf32e9 : fffffa80`00000000 fffffa80`09afa410 00000000`0000000f fffff880`0fdf5085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`095a0b60 fffff880`0fdf2574 : fffff880`02fdc040 fffffa80`0cb12010 00000000`00000000 fffffa80`09afa410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`095a0b90 fffff880`0fdf2012 : 00000000`0001663d fffffa80`0cb12010 00000000`00000080 fffffa80`09afa410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`095a0bc0 fffff800`0396873a : 00000000`03179c6a fffffa80`0984bb50 fffffa80`07037ae0 fffffa80`0984bb50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`095a0c00 fffff800`036bd8e6 : fffff880`02fd7180 fffffa80`0984bb50 fffff880`02fe20c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`095a0c40 00000000`00000000 : fffff880`095a1000 fffff880`0959b000 fffff880`095a0540 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`0fdd547f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f 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: 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: fffff800036d2e52, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880095a08c0 -- (.trap 0xfffff880095a08c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009ed180 rdx=fffffa800ae61230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d2e52 rsp=fffff880095a0a50 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8009de8c40 r10=fffffa8009de8c40 r11=fffff880095a0ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] ds:7dc0:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`095a0780 fffff800`036cade0 : fffff8a0`17a0b990 00000000`00000040 fffff8a0`18f77ec8 fffffa80`0ae61238 : nt!KiBugCheckDispatch+0x69 fffff880`095a08c0 fffff800`036d2e52 : fffffa80`0ae611c0 fffffa80`09afa410 00000000`00000000 fffffa80`07794ad0 : nt!KiPageFault+0x260 fffff880`095a0a50 fffff800`036d1256 : 00000000`00000000 fffff880`0fdc51d8 00000000`00000000 fffffa80`09afa410 : nt!KiSignalSynchronizationObject+0x42 fffff880`095a0aa0 fffff880`0fdd547f : fffffa80`00000000 00000000`00000000 fffffa80`07d61a00 fffff880`095a0b60 : nt!KeSetEvent+0x106 fffff880`095a0b10 fffff880`0fdf32e9 : fffffa80`00000000 fffffa80`09afa410 00000000`0000000f fffff880`0fdf5085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`095a0b60 fffff880`0fdf2574 : fffff880`02fdc040 fffffa80`0cb12010 00000000`00000000 fffffa80`09afa410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`095a0b90 fffff880`0fdf2012 : 00000000`0001663d fffffa80`0cb12010 00000000`00000080 fffffa80`09afa410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`095a0bc0 fffff800`0396873a : 00000000`03179c6a fffffa80`0984bb50 fffffa80`07037ae0 fffffa80`0984bb50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`095a0c00 fffff800`036bd8e6 : fffff880`02fd7180 fffffa80`0984bb50 fffff880`02fe20c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`095a0c40 00000000`00000000 : fffff880`095a1000 fffff880`0959b000 fffff880`095a0540 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`0fdd547f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f 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: 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: fffff800036d2e52, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880095a08c0 -- (.trap 0xfffff880095a08c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009ed180 rdx=fffffa800ae61230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d2e52 rsp=fffff880095a0a50 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8009de8c40 r10=fffffa8009de8c40 r11=fffff880095a0ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] ds:7dc0:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`095a0780 fffff800`036cade0 : fffff8a0`17a0b990 00000000`00000040 fffff8a0`18f77ec8 fffffa80`0ae61238 : nt!KiBugCheckDispatch+0x69 fffff880`095a08c0 fffff800`036d2e52 : fffffa80`0ae611c0 fffffa80`09afa410 00000000`00000000 fffffa80`07794ad0 : nt!KiPageFault+0x260 fffff880`095a0a50 fffff800`036d1256 : 00000000`00000000 fffff880`0fdc51d8 00000000`00000000 fffffa80`09afa410 : nt!KiSignalSynchronizationObject+0x42 fffff880`095a0aa0 fffff880`0fdd547f : fffffa80`00000000 00000000`00000000 fffffa80`07d61a00 fffff880`095a0b60 : nt!KeSetEvent+0x106 fffff880`095a0b10 fffff880`0fdf32e9 : fffffa80`00000000 fffffa80`09afa410 00000000`0000000f fffff880`0fdf5085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`095a0b60 fffff880`0fdf2574 : fffff880`02fdc040 fffffa80`0cb12010 00000000`00000000 fffffa80`09afa410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`095a0b90 fffff880`0fdf2012 : 00000000`0001663d fffffa80`0cb12010 00000000`00000080 fffffa80`09afa410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`095a0bc0 fffff800`0396873a : 00000000`03179c6a fffffa80`0984bb50 fffffa80`07037ae0 fffffa80`0984bb50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`095a0c00 fffff800`036bd8e6 : fffff880`02fd7180 fffffa80`0984bb50 fffff880`02fe20c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`095a0c40 00000000`00000000 : fffff880`095a1000 fffff880`0959b000 fffff880`095a0540 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`0fdd547f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f 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: 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: fffff800036d2e52, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880095a08c0 -- (.trap 0xfffff880095a08c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009ed180 rdx=fffffa800ae61230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800036d2e52 rsp=fffff880095a0a50 rbp=0000000000000000 r8=0000000000000000 r9=fffffa8009de8c40 r10=fffffa8009de8c40 r11=fffff880095a0ae0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`036d2e52 488b3f mov rdi,qword ptr [rdi] ds:7dc0:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036cc169 to fffff800036ccbc0 STACK_TEXT: fffff880`095a0778 fffff800`036cc169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`095a0780 fffff800`036cade0 : fffff8a0`17a0b990 00000000`00000040 fffff8a0`18f77ec8 fffffa80`0ae61238 : nt!KiBugCheckDispatch+0x69 fffff880`095a08c0 fffff800`036d2e52 : fffffa80`0ae611c0 fffffa80`09afa410 00000000`00000000 fffffa80`07794ad0 : nt!KiPageFault+0x260 fffff880`095a0a50 fffff800`036d1256 : 00000000`00000000 fffff880`0fdc51d8 00000000`00000000 fffffa80`09afa410 : nt!KiSignalSynchronizationObject+0x42 fffff880`095a0aa0 fffff880`0fdd547f : fffffa80`00000000 00000000`00000000 fffffa80`07d61a00 fffff880`095a0b60 : nt!KeSetEvent+0x106 fffff880`095a0b10 fffff880`0fdf32e9 : fffffa80`00000000 fffffa80`09afa410 00000000`0000000f fffff880`0fdf5085 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`095a0b60 fffff880`0fdf2574 : fffff880`02fdc040 fffffa80`0cb12010 00000000`00000000 fffffa80`09afa410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`095a0b90 fffff880`0fdf2012 : 00000000`0001663d fffffa80`0cb12010 00000000`00000080 fffffa80`09afa410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`095a0bc0 fffff800`0396873a : 00000000`03179c6a fffffa80`0984bb50 fffffa80`07037ae0 fffffa80`0984bb50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`095a0c00 fffff800`036bd8e6 : fffff880`02fd7180 fffffa80`0984bb50 fffff880`02fe20c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a fffff880`095a0c40 00000000`00000000 : fffff880`095a1000 fffff880`0959b000 fffff880`095a0540 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`0fdd547f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f Followup: MachineOwner ---------
Youki komentarz 23 listopada 2014 komentarz 23 listopada 2014 Co to dokładnie za gra i z jakiej przeglądarki korzystasz ?
adsko komentarz 23 listopada 2014 Autor komentarz 23 listopada 2014 Przeglądarka Maxthon, gra przeglądarkowa RailNation, ściągałem z battle.net gre.
Youki komentarz 23 listopada 2014 komentarz 23 listopada 2014 A sprawdzałeś, czy na innej przeglądarce tak samo jest error ?
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.