Wysyłam dwa raporty plików .dmp
Pierwszy raport:
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\100513-15802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03095e90
Debug session time: Sat Oct 5 03:01:04.713 2013 (GMT+2)
System Uptime: 0 days 0:34:34.134
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff280047bfde0, 2, 1, fffff8800169b690}
Probably caused by : tcpip.sys ( tcpip!memset+80 )
Followup: MachineOwner
---------
0: 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: fffff280047bfde0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800169b690, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031010e8
fffff280047bfde0
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!memset+80
fffff880`0169b690 488911 mov qword ptr [rcx],rdx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: League of Lege
TRAP_FRAME: fffff8800a887400 -- (.trap 0xfffff8800a887400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff280047bfde0 rbx=0000000000000000 rcx=fffff280047bfde0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800169b690 rsp=fffff8800a887598 rbp=fffffa8008e54002
r8=0000000000000030 r9=0000000000000006 r10=0000000000000000
r11=fffffa8006e39910 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
tcpip!memset+0x80:
fffff880`0169b690 488911 mov qword ptr [rcx],rdx ds:0003:fffff280`047bfde0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ecfbe9 to fffff80002ed0640
STACK_TEXT:
fffff880`0a8872b8 fffff800`02ecfbe9 : 00000000`0000000a fffff280`047bfde0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a8872c0 fffff800`02ece860 : 00000000`00000001 fffffa80`042a7d50 fffff880`0a8876b8 fffffa80`080f46c0 : nt!KiBugCheckDispatch+0x69
fffff880`0a887400 fffff880`0169b690 : fffff880`01651ff6 fffffa80`080f46c0 fffffa80`08e54002 fffffa80`08e54002 : nt!KiPageFault+0x260
fffff880`0a887598 fffff880`01651ff6 : fffffa80`080f46c0 fffffa80`08e54002 fffffa80`08e54002 00000000`00000008 : tcpip!memset+0x80
fffff880`0a8875a0 fffff880`0166cd15 : 00000000`00000000 fffff880`01780002 fffffa80`066e94d1 fffff880`0000f413 : tcpip!WfpProcessOutTransportStackIndication+0x4e6
fffff880`0a887760 fffff880`016703ae : fffffa80`066ec080 fffff880`01402f04 fffff880`0177f9a0 fffffa80`06e39910 : tcpip!IppSendDatagramsCommon+0x525
fffff880`0a887a30 fffff880`0164be38 : fffffa80`06e39910 fffffa80`042a7d50 fffffa80`042a7d50 fffffa80`066ec080 : tcpip!IpNlpSendDatagrams+0x3e
fffff880`0a887a70 fffff880`0164c08b : fffffa80`08e54080 fffff880`01744450 fffff880`0a8883c0 00000000`00000000 : tcpip!UdpSendMessagesOnPathCreation+0x688
fffff880`0a887df0 fffff880`0164c5d5 : fffff880`0a888320 fffffa80`04c5f413 00000000`00000001 00000000`00000000 : tcpip!UdpSendMessages+0x1db
fffff880`0a8881e0 fffff800`02edd078 : af40815a`4315402f 2eb83b3d`848ac819 12f41d48`93bd159e 295ee319`40378d2e : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
fffff880`0a888210 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!memset+80
fffff880`0169b690 488911 mov qword ptr [rcx],rdx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tcpip!memset+80
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79420
FAILURE_BUCKET_ID: X64_0xD1_tcpip!memset+80
BUCKET_ID: X64_0xD1_tcpip!memset+80
Followup: MachineOwner
---------
0: kd> g
^ No runnable debuggees error in 'g'
Drugi raport, po tym drugim bluescreenie mialem problem z odpaleniem kompa przez jakies 10 min. Nie łapał mi nawet monitora. Otworzyłem klape kompa, spróbowałem jeszcze raz i wystartował normalnie. No i teraz pracuje już godzine.
Kod: Zaznacz cały
Loading Dump File [C:\Windows\Minidump\100513-17191-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e0b000 PsLoadedModuleList = 0xfffff800`03050e90
Debug session time: Sat Oct 5 03:03:20.332 2013 (GMT+2)
System Uptime: 0 days 0:01:31.503
Loading Kernel Symbols
................................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a00bd032a0, fffff8a00bd032a0, fffff0a00bd032a0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
Followup: Pool_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a00bd032a0, the pool entry being checked.
Arg3: fffff8a00bd032a0, the read back flink freelist value (should be the same as 2).
Arg4: fffff0a00bd032a0, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb570f to fffff80002e8b640
STACK_TEXT:
fffff880`0b37f5d8 fffff800`02fb570f : 00000000`00000019 00000000`00000003 fffff8a0`0bd032a0 fffff8a0`0bd032a0 : nt!KeBugCheckEx
fffff880`0b37f5e0 fffff800`02fb71a1 : 00000000`00000000 fffff8a0`0bd10340 00000000`00000001 39336743`ffffffff : nt!ExDeferredFreePool+0xcbb
fffff880`0b37f670 fffff880`02d5228e : ffffffff`800060b8 00000000`00000000 00000000`39336743 00000000`000007ff : nt!ExFreePoolWithTag+0x411
fffff880`0b37f720 ffffffff`800060b8 : 00000000`00000000 00000000`39336743 00000000`000007ff fffff880`0b37f788 : 0xfffff880`02d5228e
fffff880`0b37f728 00000000`00000000 : 00000000`39336743 00000000`000007ff fffff880`0b37f788 00000000`ffffffff : 0xffffffff`800060b8
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+cbb
fffff800`02fb570f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+cbb
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+cbb
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+cbb
Followup: Pool_corruption
---------
Oba bluescreeny wyskoczyły podczas gry w LoL'a. Za pierwszym razem myslalem, ze nic, ale za drugim jak mowie zmartwiłem się.
Pozdrawiam i serdecznie proszę o pomoc, w sposobie jak temu zaradzić.
