+- Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety • (https://windows7forum.pl)
+-- Dział: Pomoc i wsparcie, Windows 7 (/pomoc-i-wsparcie-windows-7-26-f)
+--- Dział: Software (/software-27-f)
+--- Wątek: Rozwiązany Bluescreen (/bluescreen-18510-t)
Bluescreen - Xarid - 10.09.2011 11:30
Wielokrotnie przy tych samych czynnościach dostaję bluescreena np. przy używaniu jakiegokolwiek torrent downloadera, blizzard downloadera, streamowanie za pomocą xsplita. Zaktualizowałem wszystkie sterowniki, przeczyściłem komputer sprężonym powietrzem, jednak problem wciąż występuje. Po takim błędzie otrzymuję taki komunikat:
Cytat:Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje o problemie:
BCCode: a
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002FFA33E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Pliki pomagające opisać problem:
C:\Windows\Minidump\091011-28033-01.dmp
C:\Users\Xarid\AppData\Local\Temp\WER-58983-0.sysdata.xml
Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415
Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
C:\Windows\system32\pl-PL\erofflps.txt
RE: Bluescreen - thermalfake - 10.09.2011 16:32
Poproszę o spakowane i udostępnione pliki *.dmp z folderu c:\windows\minidump
RE: Bluescreen - Xarid - 10.09.2011 18:39
Proszę:
http://www.speedyshare.com/files/30259842/091011-28033-01.dmp
RE: Bluescreen - thermalfake - 10.09.2011 21:23
Wygląda na to, że sterowniki sieci Rt64win7.sys (Realtek lan) robi takie kłopoty. Zalecam usunięcie, restart i zainstalowanie ponownie (nie ta sama wersja). Np stąd
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\091011-28033-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c54670
Debug session time: Sat Sep 10 12: 21: 32.580 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 47: 01.125
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff80002ffa33e}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+10bb8 )
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: 0000000000000008, 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: fffff80002ffa33e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe100
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalpDmaFreeMapRegisters+1a
fffff800`02ffa33e 488b5a08 mov rbx,qword ptr [rdx+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002fbd800 -- (.trap 0xfffff88002fbd800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fbd930 rbx=0000000000000000 rcx=fffffa8004390208
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ffa33e rsp=fffff88002fbd990 rbp=0000000000000c00
r8=fffff88002fbd930 r9=fffff80003024c60 r10=000000000000036c
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
hal!HalpDmaFreeMapRegisters+0x1a:
fffff800`02ffa33e 488b5a08 mov rbx,qword ptr [rdx+8] ds: 00000000`00000008=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a8b1e9 to fffff80002a8bc40
STACK_TEXT:
fffff880`02fbd6b8 fffff800`02a8b1e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fbd6c0 fffff800`02a89e60 : fffffa80`06029c40 00000000`000007ff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fbd800 fffff800`02ffa33e : fffffa80`040a8030 fffffa80`040a8030 fffffa80`054688d0 00000000`00000001 : nt!KiPageFault+0x260
fffff880`02fbd990 fffff800`02ffcb82 : fffffa80`04390190 00000000`00000000 fffffa80`04390190 00000000`000005a0 : hal!HalpDmaFreeMapRegisters+0x1a
fffff880`02fbd9c0 fffff800`02ffc825 : fffffa80`05263380 00000000`00000c90 00000000`00000000 fffffa80`04119c50 : hal!IoFreeMapRegisters+0x62
fffff880`02fbda30 fffff880`01467831 : fffffa80`04119b80 fffffa80`04119a50 fffffa80`05255120 fffffa80`040a8030 : hal!HalPutScatterGatherList+0xd5
fffff880`02fbda90 fffff880`02c7abb8 : fffff800`02c2c201 fffffa80`05255120 00000000`00000000 fffff800`02c2c201 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`02fbdad0 fffff800`02c2c201 : fffffa80`05255120 00000000`00000000 fffff800`02c2c201 00000000`00000000 : Rt64win7+0x10bb8
fffff880`02fbdad8 fffffa80`05255120 : 00000000`00000000 fffff800`02c2c201 00000000`00000000 00000000`00000000 : nt!ExpThreadSetManagerShutdownEvent+0x1
fffff880`02fbdae0 00000000`00000000 : fffff800`02c2c201 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`05255120
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+10bb8
fffff880`02c7abb8 ? ?
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Rt64win7+10bb8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49a65b0d
FAILURE_BUCKET_ID: X64_0xA_Rt64win7+10bb8
BUCKET_ID: X64_0xA_Rt64win7+10bb8
Followup: MachineOwner
---------