Specyfikacja kompa:
Procesor: Intel® Core™ i5 520M
(2,40 GHz / L2 cache 3 MB)
Pamięć Pamięć systemu 4 GB (2 GB + 2 GB) / max. 8 GB DDR3
Matryca
Wyświetlacz 15,6" LED HD (1366x768) 16:9 błyszcząca
Grafika Chipset nVIDIA GeForce GT 330M
Pamięć 1 024 MB
Multimedia Dźwięk Tak (HD)
Nośniki danych Dysk twardy 500 GB (SATA, 5 400 rpm)
System operacyjny : Windows 7 Ultimate x64
Dołączam dzis kolejny BSOD:
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\112810-18517-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
Debug session time: Sun Nov 28 17: 56: 01.080 2010 (UTC + 1: 00)
System Uptime: 0 days 2: 58: 59.642
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {3c, 2, 1, fffff8800610a6fe}
Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+b46fe )
Followup: MachineOwner
---------
2: 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: 000000000000003c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800610a6fe, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b20e0
000000000000003c
CURRENT_IRQL: 2
FAULTING_IP:
RTKVHD64+b46fe
fffff880`0610a6fe f30f115438fc movss dword ptr [rax+rdi-4],xmm2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88008624570 -- (.trap 0xfffff88008624570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=0000000000000020
rdx=0000000000000060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800610a6fe rsp=fffff88008624700 rbp=0000000000000000
r8=0000000000000040 r9=0000000000000010 r10=fffff8800619b040
r11=ffffffffffffffe0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
RTKVHD64+0xb46fe:
fffff880`0610a6fe f30f115438fc movss dword ptr [rax+rdi-4],xmm2 ds: 00ff: 00000000`0000001c=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000307b469 to fffff8000307bf00
STACK_TEXT:
fffff880`08624428 fffff800`0307b469 : 00000000`0000000a 00000000`0000003c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`08624430 fffff800`0307a0e0 : 00000000`00000000 fffffa80`07747000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`08624570 fffff880`0610a6fe : fffff880`0619b730 fffff880`0619b330 00000000`00000000 fffffa80`07747000 : nt!KiPageFault+0x260
fffff880`08624700 fffff880`0619b730 : fffff880`0619b330 00000000`00000000 fffffa80`07747000 fffffa80`07719040 : RTKVHD64+0xb46fe
fffff880`08624708 fffff880`0619b330 : 00000000`00000000 fffffa80`07747000 fffffa80`07719040 00000000`00000009 : RTKVHD64+0x145730
fffff880`08624710 00000000`00000000 : fffffa80`07747000 fffffa80`07719040 00000000`00000009 fffffa80`07710040 : RTKVHD64+0x145330
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+b46fe
fffff880`0610a6fe f30f115438fc movss dword ptr [rax+rdi-4],xmm2
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RTKVHD64+b46fe
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RTKVHD64
IMAGE_NAME: RTKVHD64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b260be7
FAILURE_BUCKET_ID: X64_0xD1_RTKVHD64+b46fe
BUCKET_ID: X64_0xD1_RTKVHD64+b46fe
Followup: MachineOwner
---------
2: kd> lmvm RTKVHD64
start end module name
fffff880`06056000 fffff880`06273900 RTKVHD64 T (no symbols)
Loaded symbol image file: RTKVHD64.sys
Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
Image name: RTKVHD64.sys
Timestamp: Mon Dec 14 10: 56: 55 2009 (4B260BE7)
CheckSum: 0022191A
ImageSize: 0021D900
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
EDIT: DODAJE KOLEJNY!
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\112910-21216-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 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`0301f000 PsLoadedModuleList = 0xfffff800`0325ce50
Debug session time: Mon Nov 29 14: 50: 01.020 2010 (UTC + 1: 00)
System Uptime: 0 days 2: 53: 17.207
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff80003d8e980, 2, 1, fffff800030d6405}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+490 )
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: fffff80003d8e980, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800030d6405, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c70e0
fffff80003d8e980
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+490
fffff800`030d6405 41ff87004b0000 inc dword ptr [r15+4B00h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d6405 rsp=fffff880009a9c10 rbp=000000000000003f
r8=0000000000000000 r9=0000000000000000 r10=fffffa8003a80a20
r11=0000000000000016 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MmZeroPageThread+0x490:
fffff800`030d6405 41ff87004b0000 inc dword ptr [r15+4B00h] ds: 1040: 00000000`00004b00=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000308eca9 to fffff8000308f740
STACK_TEXT:
fffff880`009a9938 fffff800`0308eca9 : 00000000`0000000a fffff800`03d8e980 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`0308d920 : 00000000`00000000 00000000`00032440 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`030d6405 : fffffa80`03a80a00 00000000`00000008 00000000`0000003f 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`03333c06 : fffffa80`03b51040 00000000`00000080 fffffa80`03b506f0 fffff800`0306dc19 : nt!MmZeroPageThread+0x490
fffff880`009a9d40 fffff800`0306dc26 : fffff800`03209e80 fffffa80`03b51040 fffff800`03217c40 9090c35b`5d5f20c4 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+490
fffff800`030d6405 41ff87004b0000 inc dword ptr [r15+4B00h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+490
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+490
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+490
Followup: MachineOwner
---------
0: kd> lmvm nt
start end module name
fffff800`0301f000 fffff800`035fb000 nt (pdb symbols) c: \symbols\ntkrnlmp.pdb\30092BE745B24FE2A311A936E7B7486F2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c: \symbols\ntoskrnl.exe\4C1C44A95dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sat Jun 19 06: 16: 41 2010 (4C1C44A9)
CheckSum: 005489D7
ImageSize: 005DC000
File version: 6.1.7600.16617
Product version: 6.1.7600.16617
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16617
FileVersion: 6.1.7600.16617 (win7_gdr.100618-1621)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
No to kolejny...
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\112910-23696-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 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`0305d000 PsLoadedModuleList = 0xfffff800`0329ae50
Debug session time: Mon Nov 29 18: 57: 07.699 2010 (UTC + 1: 00)
System Uptime: 0 days 4: 06: 37.885
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8804701f988, 2, 0, fffff880046fb3fb}
Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+c43fb )
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: fffff8804701f988, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880046fb3fb, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033050e0
fffff8804701f988
CURRENT_IRQL: 2
FAULTING_IP:
athrx+c43fb
fffff880`046fb3fb 488b8c2488000000 mov rcx,qword ptr [rsp+88h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800301f770 -- (.trap 0xfffff8800301f770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004771e70
rdx=fffffa80083b8650 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880046fb3fb rsp=fffff8800301f900 rbp=0000000000000080
r8=0000000000000000 r9=0000000000000000 r10=fffffa800708fc90
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
athrx+0xc43fb:
fffff880`046fb3fb 488b8c2488000000 mov rcx,qword ptr [rsp+88h] ss: fffff880`0301f988=fffffa8004771e58
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030ccca9 to fffff800030cd740
STACK_TEXT:
fffff880`0301f628 fffff800`030ccca9 : 00000000`0000000a fffff880`4701f988 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0301f630 fffff800`030cb920 : fffffa80`04e80030 fffffa80`0734a470 fffffa80`07018620 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0301f770 fffff880`046fb3fb : fffffa80`04771e70 fffffa80`070ab7e8 fffffa80`083b8660 fffffa80`0734a470 : nt!KiPageFault+0x260
fffff880`0301f900 fffffa80`04771e70 : fffffa80`070ab7e8 fffffa80`083b8660 fffffa80`0734a470 00000000`00000000 : athrx+0xc43fb
fffff880`0301f908 fffffa80`070ab7e8 : fffffa80`083b8660 fffffa80`0734a470 00000000`00000000 fffffa80`080a8c50 : 0xfffffa80`04771e70
fffff880`0301f910 fffffa80`083b8660 : fffffa80`0734a470 00000000`00000000 fffffa80`080a8c50 00000000`00000000 : 0xfffffa80`070ab7e8
fffff880`0301f918 fffffa80`0734a470 : 00000000`00000000 fffffa80`080a8c50 00000000`00000000 00000000`00000000 : 0xfffffa80`083b8660
fffff880`0301f920 00000000`00000000 : fffffa80`080a8c50 00000000`00000000 00000000`00000000 fffff880`030d5016 : 0xfffffa80`0734a470
STACK_COMMAND: kb
FOLLOWUP_IP:
athrx+c43fb
fffff880`046fb3fb 488b8c2488000000 mov rcx,qword ptr [rsp+88h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: athrx+c43fb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrx
IMAGE_NAME: athrx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c105fdf
FAILURE_BUCKET_ID: X64_0xD1_athrx+c43fb
BUCKET_ID: X64_0xD1_athrx+c43fb
Followup: MachineOwner
---------
0: kd> lmvm athrx
start end module name
fffff880`04637000 fffff880`047c2000 athrx T (no symbols)
Loaded symbol image file: athrx.sys
Image path: \SystemRoot\system32\DRIVERS\athrx.sys
Image name: athrx.sys
Timestamp: Thu Jun 10 05: 45: 35 2010 (4C105FDF)
CheckSum: 00194CCE
ImageSize: 0018B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Post: #5
