Reset kompa po odpaleniu gier, BSOD nv4_disp.dll, Windows XP

[pawel9212]

Witam ostatnio mam problem z komputerem, który po właczeniu jakiej kolwiek gry resetuje się czasami wyskakuje bluescreen
tutaj jest kilka zrzutów z pamieci


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


Loading Dump File [C:\WINDOWS\Minidump\Mini123101-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:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120504-1619
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b2c0
Debug session time: Tue Aug 21 14:54:13.546 2012 (GMT+2)
System Uptime: 0 days 1:42:58.121
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image nv4_disp.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, b7637ae4, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : nv4_disp.dll ( nv4_disp+1b5840 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 00000000, The address that the exception occurred at
Arg3: b7637ae4, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4fb206eb

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

FAULTING_IP:
+0
00000000 ?? ???

TRAP_FRAME: b7637ae4 -- (.trap ffffffffb7637ae4)
ErrCode = 00000000
eax=afa30006 ebx=00000004 ecx=00000002 edx=e158c800 esi=00000000 edi=e24d0800
eip=00000000 esp=b7637b58 ebp=e24d0800 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bd1c7840 to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b7637b54 bd1c7840 e24d0800 e24d0800 00000000 0x0
e24d0800 00000000 0002a478 e252a840 00000191 nv4_disp+0x1b5840


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp+1b5840
bd1c7840 ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_disp+1b5840

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

BUCKET_ID: WRONG_SYMBOLS

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











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


Loading Dump File [C:\WINDOWS\Minidump\Mini082112-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120504-1619
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b2c0
Debug session time: Tue Aug 21 20:54:52.781 2012 (GMT+2)
System Uptime: 0 days 0:02:21.362
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
Unable to load image atapi.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {78, 5, 0, f847ed55}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : atapi.sys ( atapi+5d55 )

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

kd> .reload
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
................Unable to load image atapi.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
....................................................................................................
Loading User Symbols
Loading unloaded module list
.........
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: 00000078, memory referenced
Arg2: 00000005, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f847ed55, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


MODULE_NAME: atapi

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802539d

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000078

CURRENT_IRQL: 5

FAULTING_IP:
atapi+5d55
f847ed55 f6402802 test byte ptr [eax+0x28],0x2

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f847b7b2 to f847ed55

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b74ffcf8 f847b7b2 812a9a14 00000004 81f6e898 atapi+0x5d55
b74ffd2c f847e696 50f98370 81f6eafc 029ed008 atapi+0x27b2
b74ffd40 804da915 81f6e898 81f98030 00010005 atapi+0x5696
b74ffd64 00ae14a3 badb0d00 00000000 00000000 nt!KeSynchronizeExecution+0x23f
b74ffd68 badb0d00 00000000 00000000 00000000 0xae14a3
b74ffd6c 00000000 00000000 00000000 00000000 0xbadb0d00


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atapi+5d55
f847ed55 f6402802 test byte ptr [eax+0x28],0x2

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi+5d55

IMAGE_NAME: atapi.sys

BUCKET_ID: WRONG_SYMBOLS

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






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


Loading Dump File [C:\WINDOWS\Minidump\Mini082112-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120504-1619
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b2c0
Debug session time: Tue Aug 21 17:07:41.578 2012 (GMT+2)
System Uptime: 0 days 0:06:08.156
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image nv4_disp.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, bd1c5a55, b7b57a1c, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : nv4_disp.dll ( nv4_disp+1b3a55 )

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

[seba86mu]

Jaką posiadasz kartę graficzną ?

Podaj odczyty temperatur z programu => Dostępne tylko dla zarejestrowanych użytkowników (screen okna programu)

[pawel9212]

Moja karta graficzna to Leadtek WinFast A400

Dostępne tylko dla zarejestrowanych użytkowników

[seba86mu]

Zaktualizuj:
Grafika => ftp://ftp.leadtek.com/entertainment_gra ... x_7777.exe
DirectX => Dostępne tylko dla zarejestrowanych użytkowników