» »

BSOD problem

BSOD problem

Andrej_ID ::

Prilagam 4 zadnje BSOD debug informacije. (WIN 7: AMD Phenom II X4 965 BE, GIGABYTE MA770-US3 rev 2.0, GIGABYTE GTX 470, 3x1 GB OCZ DDR2 memory 800, X-fi xtreme music)
BSOD se dogaja naključno, večkrat zapored, ko uspem pridt v windows hitim, preden ne gre spet use v maloro...

CRASH No.1


Microsoft Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symb...
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`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Sat Oct 30 10:40:45.157 2010 (UTC + 2:00)
System Uptime: 0 days 0:53:39.952
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd5018). Type ".hh dbgerr001" for details
Loading unloaded module list
...............
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88005fecdbe, 0, ffffffffffffffff}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
Probably caused by : luafv.sys ( luafv!LuafvPreCreate+12 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005fecdbe, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
luafv!LuafvPreCreate+12
fffff880`05fecdbe 4156 push r14

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR: 0x1E_c0000005

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff880098b12f8 -- (.exr 0xfffff880098b12f8)
ExceptionAddress: fffff88005fecdbe (luafv!LuafvPreCreate+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880098b13a0 -- (.trap 0xfffff880098b13a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000249c380 rbx=0000000000000000 rcx=00000000098b1558
rdx=fffff880098b15d8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005fecdbe rsp=fffff880098b1538 rbp=fffffa8006020590
r8=fffff880098b15b0 r9=0000000000000000 r10=fffffa8006611710
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
luafv!LuafvPreCreate+0x12:
fffff880`05fecdbe 4156 push r14
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d05a39 to fffff80002ccb740

STACK_TEXT:
fffff880`098b0b28 fffff800`02d05a39 : 00000000`0000001e ffffffff`c0000005 fffff880`05fecdbe 00000000`00000000 : nt!KeBugCheckEx
fffff880`098b0b30 fffff800`02ccad82 : fffff880`098b12f8 fffffa80`0249c420 fffff880`098b13a0 fffffa80`0249c2d0 : nt!KiDispatchException+0x1b9
fffff880`098b11c0 fffff800`02cc968a : 000002ed`b34c8274 000002ee`2a821674 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`098b13a0 fffff880`05fecdbe : fffffa80`05fb1980 00000000`0000004e 00000000`1000000c fffffa80`0249c2d0 : nt!KiGeneralProtectionFault+0x10a
fffff880`098b1538 00000000`00000124 : fffffa80`025a8000 fffff880`098b15b0 fffff880`0483e2dc 00000000`00000000 : luafv!LuafvPreCreate+0x12
fffff880`098b1568 fffffa80`025a8000 : fffff880`098b15b0 fffff880`0483e2dc 00000000`00000000 00000000`00000801 : 0x124
fffff880`098b1570 fffff880`098b15b0 : fffff880`0483e2dc 00000000`00000000 00000000`00000801 00000000`00000000 : 0xfffffa80`025a8000
fffff880`098b1578 fffff880`0483e2dc : 00000000`00000000 00000000`00000801 00000000`00000000 fffffa80`035e1800 : 0xfffff880`098b15b0
fffff880`098b1580 fffffa80`05fb1980 : 00000000`00000000 00000000`00000010 00000000`00000020 fffffa80`0343ede0 : nvlddmkm+0x192dc
fffff880`098b1600 00000000`00000000 : 00000000`00000010 00000000`00000020 fffffa80`0343ede0 fffffa80`06611ab0 : 0xfffffa80`05fb1980


STACK_COMMAND: kb

FOLLOWUP_IP:
luafv!LuafvPreCreate+12
fffff880`05fecdbe 4156 push r14

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: luafv!LuafvPreCreate+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: luafv

IMAGE_NAME: luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc295

FAILURE_BUCKET_ID: X64_0x1E_c0000005_luafv!LuafvPreCreate+12

BUCKET_ID: X64_0x1E_c0000005_luafv!LuafvPreCreate+12

Followup: MachineOwner
---------

CRASH No.2


Microsoft Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symb...
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`02c0f000 PsLoadedModuleList = 0xfffff800`02e4ce50
Debug session time: Sat Oct 30 10:55:12.895 2010 (UTC + 2:00)
System Uptime: 0 days 0:01:07.315
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
....
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff8800413dcf7, fffff88003acf6a8, fffff88003acef10}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

Followup: MachineOwner
---------

2: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800413dcf7, The address that the exception occurred at
Arg3: fffff88003acf6a8, Exception Record Address
Arg4: fffff88003acef10, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`0413dcf7 0fba63540d bt dword ptr [rbx+54h],0Dh

EXCEPTION_RECORD: fffff88003acf6a8 -- (.exr 0xfffff88003acf6a8)
ExceptionAddress: fffff8800413dcf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b )
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88003acef10 -- (.cxr 0xfffff88003acef10)
rax=fffff8a001a7d490 rbx=72fff8a001a796e0 rcx=fffffa8005ef6000
rdx=fffffa800676ac20 rsi=fffffa8005ef6000 rdi=fffffa8005ef6000
rip=fffff8800413dcf7 rsp=fffff88003acf8e0 rbp=fffffa80067e7068
r8=fffffa8006761500 r9=0000000000000000 r10=0000000000000000
r11=0000000000000015 r12=fffffa800676ac20 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
fffff880`0413dcf7 0fba63540d bt dword ptr [rbx+54h],0Dh ds:002b:72fff8a0`01a79734=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
fffff880`0413dcf7 0fba63540d bt dword ptr [rbx+54h],0Dh

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff8800413aed3 to fffff8800413dcf7

STACK_TEXT:
fffff880`03acf8e0 fffff880`0413aed3 : 00000000`00000000 fffffa80`066d0020 00000000`00000011 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
fffff880`03acf910 fffff880`0415565d : 00000000`00000000 fffff8a0`01a98750 fffffa80`00000000 fffffa80`06761520 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`03acfae0 fffff880`04155398 : fffff800`00b96080 fffff880`04154d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03acfcd0 fffff880`04154e96 : 00000000`00000000 fffffa80`05f45660 00000000`00000080 fffffa80`05ed6010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03acfd00 fffff800`02f23c06 : 00000000`03f739d4 fffffa80`05ef5060 fffffa80`024d2040 fffffa80`05ef5060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03acfd40 fffff800`02c5dc26 : fffff800`02df9e80 fffffa80`05ef5060 fffff800`02e07c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03acfd80 00000000`00000000 : fffff880`03ad0000 fffff880`03aca000 fffff880`03acf690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff88003acef10 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

Followup: MachineOwner
---------

CRASH No.3


Microsoft Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symb...
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`0205b000 PsLoadedModuleList = 0xfffff800`02298e50
Debug session time: Sat Oct 30 12:27:20.664 2010 (UTC + 2:00)
System Uptime: 0 days 0:00:15.164
Loading Kernel Symbols
...............................................................
.....................................
Loading User Symbols

Loading unloaded module list
..
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff88001709085, fffff88001fa6e08, fffff88001fa6670}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001709085, The address that the exception occurred at
Arg3: fffff88001fa6e08, Exception Record Address
Arg4: fffff88001fa6670, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
ndis!ndisGetMiniportOffloadCapabilty+5
fffff880`01709085 488900 mov qword ptr [rax],rax

EXCEPTION_RECORD: fffff88001fa6e08 -- (.exr 0xfffff88001fa6e08)
ExceptionAddress: fffff88001709085 (ndis!ndisGetMiniportOffloadCapabilty+0x0000000000000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000000b
Attempt to write to address 000000000000000b

CONTEXT: fffff88001fa6670 -- (.cxr 0xfffff88001fa6670)
rax=000000000000000b rbx=fffff88001fa7400 rcx=fffffa80039571a0
rdx=00000000ffffffff rsi=4000000000000002 rdi=fffffa80039571a0
rip=fffff88001709085 rsp=fffff88001fa7048 rbp=0000000000000001
r8=fffff88001759000 r9=0000000000000001 r10=0000000000000000
r11=fffff80002245e80 r12=0000000000000000 r13=0000000001010101
r14=fffff88001710f38 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
ndis!ndisGetMiniportOffloadCapabilty+0x5:
fffff880`01709085 488900 mov qword ptr [rax],rax ds:002b:00000000`0000000b=????????????????
Resetting default scope

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 000000000000000b

WRITE_ADDRESS: 000000000000000b

FOLLOWUP_IP:
ndis!ndisGetMiniportOffloadCapabilty+5
fffff880`01709085 488900 mov qword ptr [rax],rax

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LOCK_ADDRESS: fffff800022cf400 -- (!locks fffff800022cf400)

Resource @ nt!PiEngineLock (0xfffff800022cf400) Exclusively owned
Contention Count = 1
NumberOfExclusiveWaiters = 1
Threads: fffffa8002507040-01
Threads Waiting On Exclusive Access:
fffffa8002509680

1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff800022cf400
Thread Count : 1
Thread address: 0xfffffa8002507040
Thread wait : 0x3cc

LAST_CONTROL_TRANSFER: from fffff8000243ac84 to fffff800020cb740

STACK_TEXT:
fffff880`01fa7048 fffff880`0170a71f : 00000005`00000006 fffff880`01fa7400 00000000`001001aa fffffa80`03953770 : ndis!ndisGetMiniportOffloadCapabilty+0x5
fffff880`01fa7050 fffff880`0176428c : fffffa80`03958188 00000000`00000005 00000000`00000001 00000000`c0000001 : ndis!ndisGetMiniportInfo+0xcff
fffff880`01fa7270 fffff880`0175e793 : fffffa80`0406f730 fffffa80`03955020 00000000`00000000 01cb781d`08c425b7 : ndis! ?? ::LNCPHCLB::`string'+0x326f
fffff880`01fa7630 fffff880`0176086c : fffffa80`0406f730 fffffa80`03957050 00000000`00000000 fffffa80`02547700 : ndis!ndisInitializeAdapter+0x113
fffff880`01fa7690 fffff880`0175e466 : fffffa80`039571a0 fffffa80`0406f730 00000000`00000000 fffffa80`02db6c80 : ndis!ndisPnPStartDevice+0xac
fffff880`01fa76f0 fffff800`0248a06e : 00000000`00000000 fffffa80`0406f730 fffffa80`03957050 fffff880`01fa7820 : ndis!ndisPnPDispatch+0x246
fffff880`01fa7790 fffff800`021c514d : fffffa80`02547700 fffff880`01fa78e0 fffff800`021cac70 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`01fa77d0 fffff800`02494f07 : 00000000`ffffffff fffffa80`02547430 fffffa80`02547430 fffffa80`025475d8 : nt!PnpStartDevice+0x11d
fffff880`01fa7890 fffff800`02495054 : fffffa80`02547430 fffffa80`02520016 fffffa80`0252bd90 00000000`00000001 : nt!PnpStartDeviceNode+0x2a7
fffff880`01fa7920 fffff800`024b8346 : fffffa80`02547430 fffffa80`0252bd90 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`01fa7950 fffff800`024b87fc : fffff800`022ccd80 00000000`00000000 00000000`00000001 fffff800`02338840 : nt!PipProcessDevNodeTree+0x296
fffff880`01fa7bc0 fffff800`021cd382 : 00000001`00000003 fffff800`022705f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`01fa7c10 fffff800`020d8961 : fffff800`021cd080 fffff800`02522e01 fffffa80`02507000 fffff880`00f9f0d0 : nt!PnpDeviceActionWorker+0x302
fffff880`01fa7cb0 fffff800`0236fc06 : 00000000`00000000 fffffa80`02507040 00000000`00000080 fffffa80`0244c440 : nt!ExpWorkerThread+0x111
fffff880`01fa7d40 fffff800`020a9c26 : fffff880`01e5c180 fffffa80`02507040 fffff880`01e66fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`01fa7d80 00000000`00000000 : fffff880`01fa8000 fffff880`01fa2000 fffff880`01fa6d10 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !ndis
165 errors : !ndis (fffff88001709007-fffff8800170cfbf)
fffff88001709000 83 60 11 00 00 ff c7 *00 08 07 00 00 16 35 22 00 .`...........5".
fffff88001709010 48 89 8b 08 02 00 00 *00 8a e8 75 17 48 8b 8b *00 H.........u.H...
fffff88001709020 11 00 00 48 85 c9 74 *00 45 33 c0 33 d2 ff 15 *00 ...H..t.E3.3....
fffff88001709030 6f 00 00 48 83 a3 08 *00 00 00 00 83 a3 08 07 00 o..H............
...
fffff88001709080 48 89 5c 24 10 48 89 *00 24 18 48 89 74 24 20 *00 H.\$.H..$.H.t$ .
fffff88001709090 41 54 41 55 41 56 41 *00 48 81 ec c0 01 00 00 *00 ATAUAVA.H.......
fffff880017090a0 8b 05 5a 50 01 00 48 *00 c4 48 89 84 24 b0 01 00 ..ZP..H..H..$...
fffff880017090b0 00 48 8b f9 48 8d 4c *00 30 33 d2 41 b8 f0 00 00 .H..H.L.03.A....
...
fffff88001709100 01 00 00 44 8d 78 01 *00 8d 4c 24 30 44 09 bc *00 ...D.x...L$0D...
fffff88001709110 34 01 00 00 33 d2 41 *00 f0 00 00 00 44 89 bc *00 4...3.A.....D...
fffff88001709120 20 01 00 00 c7 84 24 *00 01 00 00 1c 00 00 00 *00 .....$.........
...
fffff88001709180 34 48 89 4c 24 20 45 *00 c9 33 d2 48 8b cf 48 *00 4H.L$ E..3.H..H.
fffff88001709190 84 24 98 00 00 00 c6 *00 24 30 96 44 88 7c 24 *00 .$......$0.D.|$.
fffff880017091a0 c7 44 24 50 01 02 01 *00 c7 44 24 60 90 00 00 00 .D$P.....D$`....
fffff880017091b0 e8 cb 8e fb ff 45 33 *00 41 3b c3 0f 85 39 05 00 .....E3.A;...9..
...
fffff88001709200 44 01 00 00 44 89 99 *00 01 00 00 b8 00 fc ff *00 D...D...........
fffff88001709210 21 81 30 01 00 00 21 *00 38 01 00 00 b8 00 ff *00 !.0...!.8.......
fffff88001709220 ff 21 81 48 01 00 00 *00 81 40 01 00 00 44 89 *00 .!.H.....@...D..
fffff88001709230 4c 01 00 00 44 89 99 *00 01 00 00 44 89 99 50 *00 L...D......D..P.
...
fffff88001709280 94 14 20 01 00 00 e9 *00 04 00 00 83 7a 04 18 *00 .. .........z...
fffff88001709290 85 65 04 00 00 44 8b *00 10 43 8d 44 11 14 3d *00 .e...D...C.D..=.
fffff880017092a0 00 00 00 0f 87 51 04 00 00 44 8b 42 08 45 3b *00 .....Q...D.B.E;.
fffff880017092b0 0f 84 25 02 00 00 45 *00 c7 0f 84 94 00 00 00 *00 ..%...E.........
...
fffff88001709310 00 45 8a e7 8b 42 1c *00 81 54 01 00 00 8b 42 *00 .E...B...T....B.
fffff88001709320 89 81 50 01 00 00 44 *00 5a 1c 74 0c 44 39 5a *00 ..P...D.Z.t.D9Z.
fffff88001709330 45 0f b6 e4 45 0f 45 *00 45 3a e7 0f 85 99 03 00 E...E.E.E:......
...
fffff8800170c780 33 c0 48 8b d9 41 c6 *00 08 00 49 89 43 80 49 *00 3.H..A....I.C.I.
fffff8800170c790 43 88 48 8b 0d 77 19 *00 00 4c 8d 3d 70 19 01 00 C.H..w...L.=p...
fffff8800170c7a0 44 8d 70 01 49 3b cf *00 22 44 84 71 2c 74 1c *00 D.p.I;.."D.q,t..
fffff8800170c7b0 79 29 04 72 16 48 8b *00 18 8d 50 59 4c 8d 05 *00 y).r.H....PYL...
...
fffff8800170c800 3f 00 00 65 48 8b 14 *00 88 01 00 00 c7 87 90 00 ?..eH...........
fffff8800170c810 00 00 f8 1a 20 00 83 *00 90 00 00 00 00 48 89 *00 .... ........H..
fffff8800170c820 88 00 00 00 48 83 a7 *00 00 00 00 00 0f ba 67 *00 ....H.........g.
fffff8800170c830 08 8a d0 48 8d 8f 80 00 00 00 73 38 ff 15 26 *00 ...H......s8..&.
...
fffff8800170c880 84 e4 75 67 41 8a d6 *00 8b cb e8 51 da fb ff *00 ..ugA......Q....
fffff8800170c890 33 db 48 8d 44 24 30 *00 89 5c 24 30 41 8d 6b *00 3.H.D$0..\$0A.k.
fffff8800170c8a0 44 89 5c 24 38 45 8d *00 08 48 8d 54 24 40 45 *00 D.\$8E...H.T$@E.
fffff8800170c8b0 c0 48 8b cb 89 6c 24 *00 c6 44 24 30 80 48 89 *00 .H...l$..D$0.H..
...
fffff8800170c900 f6 85 c0 41 0f 44 f6 *00 8b cf e8 31 f0 ff ff *00 ...A.D.....1....
fffff8800170c910 d9 fe ff ff 44 01 b4 *00 d8 00 00 00 8b 84 24 *00 ....D.........$.
fffff8800170c920 00 00 00 83 f8 32 72 *00 41 b8 3e 1b 20 00 e9 *00 .....2r.A.>. ...
fffff8800170c930 fe ff ff 40 84 f6 74 *00 33 d2 48 8b cb e8 9e *00 ...@..t.3.H.....
...
fffff8800170c980 24 80 00 00 00 48 8d *00 24 78 48 8b cb 48 89 *00 $....H..$xH..H..
fffff8800170c990 24 20 c6 44 24 58 a3 *00 88 74 24 59 66 89 7c *00 $ .D$X...t$Yf.|.
fffff8800170c9a0 5a e8 3a c9 fb ff 48 *00 44 24 58 44 8d 4f d1 *00 Z.:...H.D$XD.O..
fffff8800170c9b0 8d 54 24 40 45 33 c0 *00 8b cb 89 7c 24 28 48 *00 .T$@E3.....|$(H.
...
fffff8800170ca00 80 79 29 04 72 18 48 *00 49 18 4c 8d 05 8f 4b 00 .y).r.H.I.L...K.
fffff8800170ca10 00 ba 5a 00 00 00 4c *00 cb e8 42 a2 fd ff 48 *00 ..Z...L...B...H.
fffff8800170ca20 c4 90 00 00 00 41 5f *00 5e 41 5c 5f 5e 5d 5b *00 .....A_.^A\_^][.
fffff8800170ca30 90 90 90 90 90 90 90 *00 90 90 90 90 90 90 90 *00 ................
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xfffff88001fa6670 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

CRASH No.4


Microsoft Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symb...
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`0205a000 PsLoadedModuleList = 0xfffff800`02297e50
Debug session time: Sat Oct 30 12:44:04.604 2010 (UTC + 2:00)
System Uptime: 0 days 0:00:32.494
Loading Kernel Symbols
...............................................................
......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdc018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001b3925, fffff880072f5120, 0}

Page 90f03 not present in the dump file. Type ".hh dbgerr004" for details
Page acd63 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32k.sys ( win32k!RawInputThread+985 )

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: fffff960001b3925, Address of the instruction which caused the bugcheck
Arg3: fffff880072f5120, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

Page acd63 not present in the dump file. Type ".hh dbgerr004" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!RawInputThread+985
fffff960`001b3925 ff1545cb1d00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00390470)]

CONTEXT: fffff880072f5120 -- (.cxr 0xfffff880072f5120)
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa800429bc10
rdx=00000000000007ff rsi=0000000000000004 rdi=0000000000000001
rip=fffff960001b3925 rsp=fffff880072f5af0 rbp=fffff960003cfa90
r8=fffffa8004309bb8 r9=0000000000000000 r10=fffffffffffffff7
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=0000000000000002 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
win32k!RawInputThread+0x985:
fffff960`001b3925 ff1545cb1d00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00390470)] ds:002b:fffff960`00390470={nt!ExEnterPriorityRegionAndAcquireResourceExclus ive (fffff800`020d61c0)}
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff96000144708 to fffff960001b3925

STACK_TEXT:
fffff880`072f5af0 fffff960`00144708 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000290 : win32k!RawInputThread+0x985
fffff880`072f5bc0 fffff960`001c429a : fffffa80`00000002 fffff880`072d3f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`072f5bf0 fffff800`020c9993 : fffffa80`04386060 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`072f5c20 000007fe`fd7a3d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`008afc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd7a3d3a


FOLLOWUP_IP:
win32k!RawInputThread+985
fffff960`001b3925 ff1545cb1d00 call qword ptr [win32k!_imp_ExEnterPriorityRegionAndAcquireResourceExclusive (fffff960`00390470)]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!RawInputThread+985

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c7dc13c

STACK_COMMAND: .cxr 0xfffff880072f5120 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!RawInputThread+985

BUCKET_ID: X64_0x3B_win32k!RawInputThread+985

Followup: MachineOwner
---------

Lahko kdo prepozna vzrok?

mare87 ::

Ram si stestiral z memtest86+? Zalaufaj pa če bodo napake (rdeča polja) ramom zvišaj voltažo. Ti OCZ-ji so povečini rabili 2v, namesto 1.8. Lahko pa je tudi kak gonilnik,..

Andrej_ID ::

tudi na drugih forumih se omenjajo gonilniki, ker tokrat piše VISTA DRIVER FAULT... Rami ne dajo napak.

Sam kako za boga nej ugotovim ker driver je u k****?

ncc2000 ::

lahko postopoma izključuješ naprave in ko bo nehalo bsodat....

a kakšnih virusov nimaš?

Andrej_ID ::

Okej ta nasvet mi ni cist jasen, s katerimi napravami naj zacnem? in kako bom vedu da sm dubu bsod ce ne bo graficna prikljucena?

Valvoline ::

Poskusi samo z 2gb rama ce bo boljse oz 2x1gb v dual nacinu delovanja.

ncc2000 ::

grafično rukni na vga driver in če bodo še bsodi, potem problem z driverji grafe nimajo veze in lahko disablaš katero od drugih naprav.

virusov nimaš?

Zgodovina sprememb…

  • spremenil: ncc2000 ()

Andrej_ID ::

Virusov ni.

Kaj mislis s tem, da dam grafo na vga?

ncc2000 ::

če je z hardverom vse vredu, potem bi jaz najprej iskal probleme okoli šoferjev GPU-ja. deinštaliraj vse driverje za tvojo grafo in probaj, kako grafa laufa na driver, ki je že v win7, če sploh je not za to grafo. Če še vedno bodo bsodi, izbriši še te nvidia grafične driverje s kakšnim programom za čiščenje driverjev, tako da se ti bo grafa po zagonu zalaufala z standardnim vga driverjem, ki ga razume vsaka grafa in je v vseh winsih. Pozoren bodi še na to, da ne pobrišeš driverjev za kaatero od drugih naprav poleg gpu-ja. Če potem bsodov ne bo, lahko iščeš napako na relaciji nvidia driverjev za grafo.

V biosu lahko verjetno izključiš zvočno, pa mrežno, pa še katero opremo matične in probaš tako, če je kaj bolje. V nadzorni plošči pod hw devices pa tudi lahko onemogočiš nekaj naprav, da vidiš, če je kaj sprememb, v kolikor bi telovadba z grafični driverji ne pokazala novenih sprememb

Oktan ::

Lahko kdo na hitro odgovori!
Prijatelj me je klical da je imel v chrome-u odprtih ogromno zavihkov, in ko je zaprl celo okno je dobil bsod, sedaj ko prižge računalnik, se ta normalno prižge, brez kakšnih opozorilnih piskov in podobno (je pa rekel da je že od vedno tako da računalnik nikoli ni nič pisknil), vendar sedaj ne dobi signala v monitor. Je to potem verjetno grafična?

Kakšna ideja kaj bi še lahko takoj poiskusil?


Vredno ogleda ...

TemaSporočilaOglediZadnje sporočilo
TemaSporočilaOglediZadnje sporočilo
»

BSOD 0x00000124

Oddelek: Pomoč in nasveti
441050 (491) s1m0n
»

BSOD

Oddelek: Operacijski sistemi
111314 (988) Bolf3nk
»

Resetiranje/bluescreen računalnika

Oddelek: Pomoč in nasveti
10550 (422) Duhec
»

Win 7 blue screen in restart

Oddelek: Operacijski sistemi
131602 (1341) Duhec
»

Adobe Flash povzroča BSOD !!???

Oddelek: Programska oprema
5543 (468) noraguta

Več podobnih tem