Niespodziewane resety komputera, plik nvlddmkm.sys

[djkamil09061991]

Sterownik do chipsetu ze strony producenta:
Dostępne tylko dla zarejestrowanych użytkowników

[XMan]

J/w.
Jeszcze możesz sprawdzić Chipset :
http://www.hotfix.pl/infusions/pro_down ... n-p203.htm

[grzyman12]

Stery są wporządku poprzeglądałem.Jedyny błąd to Kernel Power i nim się trzeba zając chyba.Narazie posprawdzam jakie sa odczyty ze skanerów...
Ogólnie wiecie co może być przyczyna takiego stanu rzeczy ??

-- 28 lut 2011, 16:53 --

Witam Kolejny BSOD możecie pomóc w przybliżeniu błędu

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\022811-21465-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82c1a000 PsLoadedModuleList = 0x82d62810
Debug session time: Mon Feb 28 16:46:54.880 2011 (GMT+1)
System Uptime: 0 days 1:49:07.846
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
Unable to load image 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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 91e2fee5, 8d4e55f4, 8d4e51d0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+42fee5 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 91e2fee5, The address that the exception occurred at
Arg3: 8d4e55f4, Exception Record Address
Arg4: 8d4e51d0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

FAULTING_IP:
nvlddmkm+42fee5
91e2fee5 8901            mov     dword ptr [ecx],eax

EXCEPTION_RECORD:  8d4e55f4 -- (.exr 0xffffffff8d4e55f4)
ExceptionAddress: 91e2fee5 (nvlddmkm+0x0042fee5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT:  8d4e51d0 -- (.cxr 0xffffffff8d4e51d0)
eax=00000000 ebx=86c03a88 ecx=00000000 edx=99a03330 esi=87029008 edi=00000000
eip=91e2fee5 esp=8d4e56bc ebp=8d4e56e0 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nvlddmkm+0x42fee5:
91e2fee5 8901            mov     dword ptr [ecx],eax  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d82718
Unable to read MiSystemVaType memory at 82d62160
 00000000

FOLLOWUP_IP:
nvlddmkm+42fee5
91e2fee5 8901            mov     dword ptr [ecx],eax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 91e3f628 to 91e2fee5

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
8d4e56e0 91e3f628 00000000 86888a90 8703b200 nvlddmkm+0x42fee5
8d4e57c4 91d362c6 00000041 00000073 8d4e58b0 nvlddmkm+0x43f628
8d4e58c8 91d34aa6 8703ebb8 0000002d 00000000 nvlddmkm+0x3362c6
8d4e5900 91d34c58 86c07068 00000041 0000002d nvlddmkm+0x334aa6
8d4e593c 91b5b92e 00000002 87029008 00000041 nvlddmkm+0x334c58
8d4e59a8 91b55462 87029008 00000001 00000000 nvlddmkm+0x15b92e
8d4e59d8 91b55517 872bb7b8 00000000 8d4e5a9c nvlddmkm+0x155462
8d4e59f0 91b591e0 c1d00411 ff080038 8d4e5a9c nvlddmkm+0x155517
8d4e5a70 91ade69f 8d4e5a9c 8d4e5aac 872b9b88 nvlddmkm+0x1591e0
8d4e5a8c 91ae0505 8d4e5a9c 872b9c28 c1d00411 nvlddmkm+0xde69f
8d4e5aac 91a4569f ff020000 ff080038 872b9e8c nvlddmkm+0xe0505
8d4e5ad8 91a4523c 872b9b88 91a43c36 86b39768 nvlddmkm+0x4569f
8d4e5af8 91a451c4 872b9b88 91a45547 86b39768 nvlddmkm+0x4523c
8d4e5b0c 91a21361 00000001 86b39768 86b1f000 nvlddmkm+0x451c4
8d4e5b44 91aeda02 86b1f000 00000000 923a8928 nvlddmkm+0x21361
8d4e5b78 91fdebaa 8302f6ee 8739f000 8739f000 nvlddmkm+0xeda02
8d4e5b90 970b13f4 91fdeb78 85f42510 8739f000 nvlddmkm+0x5debaa
8d4e5bb4 970b27c8 87362408 85f42510 00000000 dxgkrnl!DXGADAPTER::DdiResetFromTimeout+0x42
8d4e5bdc 970b9adc 85f42510 85f42510 8b99707e dxgkrnl!DXGADAPTER::PrepareToReset+0xdb
8d4e5bf8 970e992c 00000000 00000000 87362408 dxgkrnl!TdrIsRecoveryRequired+0x14e
8d4e5c70 97113944 fffffcfb 00063791 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8d4e5c98 970f09af 00000000 85b6fd18 8812fb60 dxgmms1!VidSchiCheckHwProgress+0x68
8d4e5d28 971153c9 87362408 82c563e1 87362408 dxgmms1!VidSchiScheduleCommandToRun+0x169
8d4e5d3c 97115485 87362408 00000000 873b0c48 dxgmms1!VidSchiRun_PriorityTable+0xf
8d4e5d50 82e289df 87362408 a09e23c9 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8d4e5d90 82cda1d9 97115406 87362408 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+42fee5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c60e

STACK_COMMAND:  .cxr 0xffffffff8d4e51d0 ; kb

FAILURE_BUCKET_ID:  0x7E_nvlddmkm+42fee5

BUCKET_ID:  0x7E_nvlddmkm+42fee5

Followup: MachineOwner

[cosik_ktosik]

To nadal błąd sterownika karty graficznej. Może Masz kartę jakiejś konkretnej firmy?

[grzyman12]

ta karta jaką mam to Nividia Geforce 9500 gt czy jakoś tak... Ale stery pozmieniałem i bsod już nie wyskakuje.
Ale mam inny problem czyli kernel power... Dodam że jek się zawiesza jest to twarde zawieszenie systemu tzn np jak wduszę Caps lock na klawiaturze to nie zapali się dioda.