thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Windows 7 Professional x64 bluescreen 2-7 razy dziennie
Instalowałeś czystego OEM'a czy fabryczne recovery. Sterowniki tylko ze strony Della czy też było coś spoza (referencyjne) ?
Bsody są spowodowane niewłaściwym dostępem sterowników do pamięci. Tak na dobrą sprawę postawienie systemu raz jeszcze, tylko fabrycznych sterowników i obserwowanie. Potem podmiana pamięci RAM. Na koniec zostaje już tylko wysyłka gwarancyjna. Już nie raz miałem w Dellach tak, ze wszystkie testy przechodził OK a jak się okazało zawsze coś było uszkodzone.
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\dmp12\Minidump\123011-105893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03251670
Debug session time: Fri Dec 30 00: 53: 31.780 2011 (UTC + 1: 00)
System Uptime: 0 days 4: 20: 33.717
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff88202fdb2e0, 2, 0, fffff80003094a9b}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
Followup: MachineOwner
---------
3: 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: fffff88202fdb2e0, 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: fffff80003094a9b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bb100
fffff88202fdb2e0
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiInsertTimerTable+13b
fffff800`03094a9b 488b42f8 mov rax,qword ptr [rdx-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: uTorrent.exe
TRAP_FRAME: fffff8800867e750 -- (.trap 0xfffff8800867e750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000003
rdx=fffff88202fdb2e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003094a9b rsp=fffff8800867e8e0 rbp=fffff88002fdb2e8
r8=ffffffffffffffff r9=00000000000000eb r10=fffff88002fd7180
r11=fffff88002fd7100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiInsertTimerTable+0x13b:
fffff800`03094a9b 488b42f8 mov rax,qword ptr [rdx-8] ds: fffff882`02fdb2e0=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030881e9 to fffff80003088c40
STACK_TEXT:
fffff880`0867e608 fffff800`030881e9 : 00000000`0000000a fffff882`02fdb2e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0867e610 fffff800`03086e60 : fffffa80`0798cf20 fffff880`0112f3e6 00000000`00000000 fffffa80`07ad0c20 : nt!KiBugCheckDispatch+0x69
fffff880`0867e750 fffff800`03094a9b : 00000014`00000000 00000000`02d40003 00000001`00000000 fffff880`03189180 : nt!KiPageFault+0x260
fffff880`0867e8e0 fffff800`0308e092 : fffffa80`07ad0b60 fffffa80`07ad0b60 fffffa80`00000000 fffffa80`00000003 : nt!KiInsertTimerTable+0x13b
fffff880`0867e940 fffff800`0309074f : 00000000`000001dc fffff800`030761e5 fffffa80`000000eb fffff880`0867eb60 : nt!KiCommitThreadWait+0x332
fffff880`0867e9d0 fffff800`0337f44e : fffff880`0867eb00 fffffa80`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`0867ea70 fffff800`03087ed3 : fffffa80`07ad0b60 00000000`000001dc fffff880`0867eab8 fffffa80`079cc4e0 : nt!NtWaitForSingleObject+0xde
fffff880`0867eae0 00000000`73c32e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0072f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73c32e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiInsertTimerTable+13b
fffff800`03094a9b 488b42f8 mov rax,qword ptr [rdx-8]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiInsertTimerTable+13b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+13b
BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+13b
Followup: MachineOwner
---------
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\dmp12\Minidump\122911-46472-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: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_b00d463b`5d69b18e, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_b00d463b`5d69b18e
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_b00d463b`5d69b18e
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a8670
Debug session time: Thu Dec 29 17: 09: 02.268 2011 (UTC + 1: 00)
System Uptime: 0 days 4: 08: 33.204
Unable to load image Unknown_Module_b00d463b`5d69b18e, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_b00d463b`5d69b18e
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_b00d463b`5d69b18e
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800feff334, fffff88008658150, 0}
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800feff334, Address of the instruction which caused the bugcheck
Arg3: fffff88008658150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
+0
fffff880`0feff334 48399048080000 cmp qword ptr [rax+848h],rdx
CONTEXT: fffff88008658150 -- (.cxr 0xfffff88008658150)
rax=fa800a4300000000 rbx=fffff88008658bd0 rcx=fffff88008658bd0
rdx=fffffa80075697b0 rsi=fffff88008658f30 rdi=0000000000000000
rip=fffff8800feff334 rsp=fffff88008658b30 rbp=fffff8a00dba4190
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=00000000001a2c48 r12=0000000000000003 r13=fffff8a00dba4250
r14=fffff8a00df60be0 r15=fffff8a0103fa010
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
fffff880`0feff334 48399048080000 cmp qword ptr [rax+848h],rdx ds: 002b: fa800a43`00000848=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8a0103fa010 to fffff8800feff334
STACK_TEXT:
fffff880`08657888 fffff800`030df1e9 : 00000000`0000003b 00000000`c0000005 fffff880`0feff334 fffff880`08658150 : 0xfffff800`030dfc40
fffff880`08657890 00000000`0000003b : 00000000`c0000005 fffff880`0feff334 fffff880`08658150 00000000`00000000 : 0xfffff800`030df1e9
fffff880`08657898 00000000`c0000005 : fffff880`0feff334 fffff880`08658150 00000000`00000000 fffff880`02e10000 : 0x3b
fffff880`086578a0 fffff880`0feff334 : fffff880`08658150 00000000`00000000 fffff880`02e10000 b923777a`40000000 : 0xc0000005
fffff880`086578a8 fffff880`08658150 : 00000000`00000000 fffff880`02e10000 b923777a`40000000 b923777a`40000000 : 0xfffff880`0feff334
fffff880`086578b0 00000000`00000000 : fffff880`02e10000 b923777a`40000000 b923777a`40000000 408d3c00`00000000 : 0xfffff880`08658150
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
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\dmp12\Minidump\122911-32651-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`0325d670
Debug session time: Thu Dec 29 20: 32: 22.556 2011 (UTC + 1: 00)
System Uptime: 0 days 3: 15: 38.382
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffffa82c5c07a3c, b, 1, fffff8800f398338}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+12f338 )
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: fffffa82c5c07a3c, memory referenced
Arg2: 000000000000000b, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800f398338, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c7100
fffffa82c5c07a3c
CURRENT_IRQL: b
FAULTING_IP:
nvlddmkm+12f338
fffff880`0f398338 f08384863c0a0000ff lock add dword ptr [rsi+rax*4+0A3Ch],0FFFFFFFFh
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: NGStudio.exe
TRAP_FRAME: fffff8800a21b610 -- (.trap 0xfffff8800a21b610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000aef30000 rbx=0000000000000000 rcx=fffffa80083555e8
rdx=000000000034f36f rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f398338 rsp=fffff8800a21b7a0 rbp=fffffa800a705010
r8=fffffa800a7045b0 r9=fffffa800b1b14b0 r10=000000000034f36f
r11=00000000aef30000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr ac po cy
nvlddmkm+0x12f338:
fffff880`0f398338 f08384863c0a0000ff lock add dword ptr [rsi+rax*4+0A3Ch],0FFFFFFFFh ds: e000: 00000002`bbcc0a3c=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030941e9 to fffff80003094c40
STACK_TEXT:
fffff880`0a21b4c8 fffff800`030941e9 : 00000000`0000000a fffffa82`c5c07a3c 00000000`0000000b 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a21b4d0 fffff800`03092e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0833d000 : nt!KiBugCheckDispatch+0x69
fffff880`0a21b610 fffff880`0f398338 : fffffa80`0833d970 fffffa80`084181a0 fffffa80`0e047b60 00000aad`0d914a3c : nt!KiPageFault+0x260
fffff880`0a21b7a0 fffffa80`0833d970 : fffffa80`084181a0 fffffa80`0e047b60 00000aad`0d914a3c 00000aad`84c6de3c : nvlddmkm+0x12f338
fffff880`0a21b7a8 fffffa80`084181a0 : fffffa80`0e047b60 00000aad`0d914a3c 00000aad`84c6de3c 00000aad`0d914a3c : 0xfffffa80`0833d970
fffff880`0a21b7b0 fffffa80`0e047b60 : 00000aad`0d914a3c 00000aad`84c6de3c 00000aad`0d914a3c 00000aad`84c6de3c : 0xfffffa80`084181a0
fffff880`0a21b7b8 00000aad`0d914a3c : 00000aad`84c6de3c 00000aad`0d914a3c 00000aad`84c6de3c 00000000`00000000 : 0xfffffa80`0e047b60
fffff880`0a21b7c0 00000aad`84c6de3c : 00000aad`0d914a3c 00000aad`84c6de3c 00000000`00000000 00000000`00000000 : 0xaad`0d914a3c
fffff880`0a21b7c8 00000aad`0d914a3c : 00000aad`84c6de3c 00000000`00000000 00000000`00000000 00000021`00000000 : 0xaad`84c6de3c
fffff880`0a21b7d0 00000aad`84c6de3c : 00000000`00000000 00000000`00000000 00000021`00000000 00000000`00000000 : 0xaad`0d914a3c
fffff880`0a21b7d8 00000000`00000000 : 00000000`00000000 00000021`00000000 00000000`00000000 fffff800`030974da : 0xaad`84c6de3c
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+12f338
fffff880`0f398338 f08384863c0a0000ff lock add dword ptr [rsi+rax*4+0A3Ch],0FFFFFFFFh
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+12f338
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db0d461
FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+12f338
BUCKET_ID: X64_0xD1_nvlddmkm+12f338
Followup: MachineOwner
---------
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\dmp12\Minidump\122811-30295-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e70
Debug session time: Wed Dec 28 22: 34: 56.907 2011 (UTC + 1: 00)
System Uptime: 0 days 6: 09: 08.999
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800ff012dc, fffff8800a4119f0, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+382dc )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800ff012dc, Address of the instruction which caused the bugcheck
Arg3: fffff8800a4119f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nvlddmkm+382dc
fffff880`0ff012dc c181e987000000 rol dword ptr [rcx+87E9h],0
CONTEXT: fffff8800a4119f0 -- (.cxr 0xfffff8800a4119f0)
rax=0000000000000015 rbx=0000000000000000 rcx=0000000000000007
rdx=0000000000000000 rsi=fffff8800a412780 rdi=fffffa80087c5000
rip=fffff8800ff012dc rsp=fffff8800a4123c8 rbp=0000000000000000
r8=0000000000000028 r9=fffffa800bfd6ce0 r10=fffff8800a412780
r11=0000000000000002 r12=0000000000000000 r13=fffff8a001ddc5b0
r14=fffff8a0174ea200 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0x382dc:
fffff880`0ff012dc c181e987000000 rol dword ptr [rcx+87E9h],0 ds: 002b: 00000000`000087f0=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800ff012dc
STACK_TEXT:
fffff880`0a4123c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x382dc
FOLLOWUP_IP:
nvlddmkm+382dc
fffff880`0ff012dc c181e987000000 rol dword ptr [rcx+87E9h],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+382dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db0d461
STACK_COMMAND: .cxr 0xfffff8800a4119f0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+382dc
BUCKET_ID: X64_0x3B_nvlddmkm+382dc
Followup: MachineOwner
---------
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\dmp12\Minidump\122711-40482-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a1e50
Debug session time: Tue Dec 27 19: 57: 22.923 2011 (UTC + 1: 00)
System Uptime: 0 days 22: 09: 25.000
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffce807727063b, 1, fffff8800805d44f, 7}
Unable to load image \SystemRoot\system32\drivers\luafv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for luafv.sys
*** ERROR: Module load completed but symbols could not be loaded for luafv.sys
Could not read faulting driver name
Probably caused by : luafv.sys ( luafv+144f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffce807727063b, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800805d44f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c0e0
ffffce807727063b
FAULTING_IP:
luafv+144f
fffff880`0805d44f 00b4f39b200000 add byte ptr [rbx+rsi*8+209Bh],dh
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88013f0d310 -- (.trap 0xfffff88013f0d310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a781003 rbx=0000000000000000 rcx=fffffa800d3d3680
rdx=fffff88013f0d528 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800805d44f rsp=fffff88013f0d4a8 rbp=fffffa800a782650
r8=fffff88013f0d500 r9=0000000000000000 r10=fffffffffffdd224
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
luafv+0x144f:
fffff880`0805d44f 00b4f39b200000 add byte ptr [rbx+rsi*8+209Bh],dh ds: 00000000`0000209b=?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003153b19 to fffff800030d5f00
STACK_TEXT:
fffff880`13f0d1a8 fffff800`03153b19 : 00000000`00000050 ffffce80`7727063b 00000000`00000001 fffff880`13f0d310 : nt!KeBugCheckEx
fffff880`13f0d1b0 fffff800`030d3fee : 00000000`00000001 fffffa80`0d3d3720 fffff880`13f0d300 fffffa80`076f14e0 : nt! ? : FNODOBFM: `string'+0x40edb
fffff880`13f0d310 fffff880`0805d44f : fffff880`0103f027 fffffa80`0d3d3700 fffffa80`0d3d3720 fffff880`13f0d500 : nt!KiPageFault+0x16e
fffff880`13f0d4a8 fffff880`0103f027 : fffffa80`0d3d3700 fffffa80`0d3d3720 fffff880`13f0d500 fffff880`00ff4f00 : luafv+0x144f
fffff880`13f0d4b0 fffff880`0103fbe9 : fffff880`13f0d600 00000000`00000004 00000000`00000000 fffffa80`0c5d4b01 : fltmgr!FltpPerformPreCallbacks+0x2f7
fffff880`13f0d5b0 fffff880`0103e6c7 : fffffa80`076f14e0 fffffa80`07b5b0c0 fffffa80`07c83880 00000000`00000000 : fltmgr!FltpPassThrough+0x2d9
fffff880`13f0d630 fffff800`030c4b4f : fffffa80`076f14e0 fffff880`13f0dc18 fffff880`13f0d840 fffff800`0324ee80 : fltmgr!FltpDispatch+0xb7
fffff880`13f0d690 fffff800`030c41c7 : 00000000`00000000 fffff880`13f0dc18 fffffa80`064abb30 00000000`00000000 : nt!IoSynchronousPageWrite+0x24f
fffff880`13f0d710 fffff800`030c2044 : fffff8a0`034aa040 fffff8a0`034aa048 fffffa80`08d2e610 fffffa80`08d2e610 : nt!MiFlushSectionInternal+0xa58
fffff880`13f0d950 fffff800`030c1a99 : 00000000`004e051a 00000000`00000000 00000000`00001000 00000000`00000000 : nt!MmFlushSection+0xa4
fffff880`13f0da10 fffff800`030c918b : fffffa80`08d362e8 fffff800`00000001 00000000`00000001 00000000`00001000 : nt!CcFlushCache+0x5e9
fffff880`13f0db10 fffff800`030c9d60 : fffff880`03d48d00 fffff880`13f0dc18 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
fffff880`13f0dbc0 fffff800`030e3161 : fffffa80`06cf2550 fffff800`033cf504 fffff800`032db140 fffffa80`00000000 : nt!CcWorkerThread+0x1c8
fffff880`13f0dc70 fffff800`03379166 : 00000000`00000000 fffffa80`0ba4b1a0 00000000`00000080 fffffa80`06cd49e0 : nt!ExpWorkerThread+0x111
fffff880`13f0dd00 fffff800`030b4486 : fffff800`0324ee80 fffffa80`0ba4b1a0 fffffa80`095a9b60 fffff880`01212534 : nt!PspSystemThreadStartup+0x5a
fffff880`13f0dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
luafv+144f
fffff880`0805d44f 00b4f39b200000 add byte ptr [rbx+rsi*8+209Bh],dh
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: luafv+144f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: luafv
IMAGE_NAME: luafv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x50_luafv+144f
BUCKET_ID: X64_0x50_luafv+144f
Followup: MachineOwner
---------
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\dmp12\Minidump\122611-30654-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e50
Debug session time: Mon Dec 26 21: 47: 17.690 2011 (UTC + 1: 00)
System Uptime: 0 days 4: 27: 30.769
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys ( NETwNs64+34793 )
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+60232faf01dedecc
00000000`00000000 ? ?
PROCESS_NAME: Studio.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff80000ba2c30 -- (.trap 0xfffff80000ba2c30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008fa7e50
rdx=fffffa8009124cb0 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff80000ba2dc8 rbp=0000000000000000
r8=0000000000000000 r9=fffff80000ba2ea0 r10=0000000000148000
r11=fffff88012206ba0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`00000000 ? ?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030cb469 to fffff800030cbf00
FAILED_INSTRUCTION_ADDRESS:
+60232faf01dedecc
00000000`00000000 ? ?
STACK_TEXT:
fffff800`00ba2dc8 fffff880`048d0793 : fffffa80`0b7ae8b0 fffffa80`07d78560 fffffa80`07b07520 00000000`00000000 : 0x0
fffff800`00ba2dd0 fffffa80`0b7ae8b0 : fffffa80`07d78560 fffffa80`07b07520 00000000`00000000 fffffa80`07b061a0 : NETwNs64+0x34793
fffff800`00ba2dd8 fffffa80`07d78560 : fffffa80`07b07520 00000000`00000000 fffffa80`07b061a0 fffff880`01174df0 : 0xfffffa80`0b7ae8b0
fffff800`00ba2de0 fffffa80`07b07520 : 00000000`00000000 fffffa80`07b061a0 fffff880`01174df0 00000000`00000000 : 0xfffffa80`07d78560
fffff800`00ba2de8 00000000`00000000 : fffffa80`07b061a0 fffff880`01174df0 00000000`00000000 00000000`00000000 : 0xfffffa80`07b07520
STACK_COMMAND: .trap 0xfffff80000ba2c30 ; kb
FOLLOWUP_IP:
NETwNs64+34793
fffff880`048d0793 ? ?
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: NETwNs64+34793
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETwNs64
IMAGE_NAME: NETwNs64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d10df1b
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_NETwNs64+34793
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_NETwNs64+34793
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Post: #2
