Blue Screen-problem


(Korsaż) #1

Podczas gry np.MOTOGP3 lub Medieval Lords podczas gry lub ładowania poziomu wyskakuje Blue Screen (błąd stop=0x0000008e 0xc0000090 0x007d55c6 0xf3b765dc 0x00000000) czy możecie mi pomóc?

MÓJ PC

Windows XP Professional (5.1, Build 2600) Dodatek Service Pack 2

Intel® Celeron® CPU 2.53GHz

DirectX 9.0c

NVIDIA GeForce FX 5200


(Joan Sunshine) #2

Hard raczej. Przeczytaj to: KLIK i wklej zawartość pliku minidump :slight_smile:


(Korsaż) #3

Jest to zawartość jednego z 6 plików minidump zrobiłem to w programie debugging tools for windows tyko to zrobiłem i nic więcej sprawdż proszę

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Tue Jan 16 19:53:04.328 2007 (GMT+1)

System Uptime: 0 days 0:43:38.897

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

......................................................................................................................

Loading User Symbols

Loading unloaded module list

..........

*** 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, {c0000090, 4cc90b, ba70d774, 0}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

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

*** WARNING: Unable to verify timestamp for mssmbios.sys

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

Probably caused by : nv4_disp.dll ( nv4_disp+fc6e5 )

Followup: MachineOwner


kd>

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: c0000090, The exception code that was not handled

Arg2: 004cc90b, The address that the exception occurred at

Arg3: ba70d774, Trap Frame

Arg4: 00000000

Debugging Details:


ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

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

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 434b4ba5

EXCEPTION_CODE: (NTSTATUS) 0xc0000090 - {WYJ

FAULTING_IP:

+4cc90b

004cc90b ?? ???

TRAP_FRAME: ba70d774 -- (.trap ffffffffba70d774)

Unable to read trap frame at ba70d774

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to bf10e6e5

STACK_TEXT:

ba70d7e4 00000000 e1b1c800 00000000 e1c096c8 nv4_disp+0xfc6e5

STACK_COMMAND: kb

FOLLOWUP_IP:

nv4_disp+fc6e5

bf10e6e5 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+fc6e5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


kd> lmvm nv4_disp

start end module name

bf012000 bf3cf480 nv4_disp T (no symbols)

Loaded symbol image file: nv4_disp.dll

Image path: \SystemRoot\System32\nv4_disp.dll

Image name: nv4_disp.dll

Timestamp: Tue Oct 11 07:20:37 2005 (434B4BA5)

CheckSum: 003BFE50

ImageSize: 003BD480

Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0


(Heniu133) #4

http://www.download.net.pl/21/NVIDIA-ForceWare-Drivers-Windows-2000-XP/


(Korsaż) #5

a to wszystko przez program myspy (oj ci rodzice) :slight_smile: