BSOD BugCheck 10000050 nv4_disp.dll

Post28 sie 2009, 00:26

*******************************************************************************
*                                                                             *
*                        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: e4b2ceec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bd0b8bd3, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  e4b2ceec 

FAULTING_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  Gothic3.exe

LAST_CONTROL_TRANSFER:  from bd0b8d41 to bd0b8bd3

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b718ea90 bd0b8d41 e2877ee8 00000000 e2877ee8 nv4_disp+0xa6bd3
b718eac8 8053b58c 85a4c7b8 8535f098 85cc7b00 nv4_disp+0xa6d41
b718eaec 80517c27 8535f098 034a0000 00000000 nt!CcPfLogPageFault+0x18
b718eb48 805452e1 85333e10 029c4fff 85333e34 nt!MmCheckCachedPageState+0x50b
b718ebe4 bf80197c 85a4c7b8 b718ec0c b718ebb8 nt!ExAllocatePoolWithTag+0x3e1
b718ec24 bd004e5f 029c3960 0000072c bd004e82 win32k!GreReleaseSemaphore+0xa
b718ec5c bd00b771 bd00b830 b718ed64 00c3e02c dxg!bDdSecureSystemMemorySurface+0x5f
bd004e82 cccccccc 8b55ff8b 658351ec 575600fc dxg!DxDdCreateSurfaceObject+0xbd
bd004e9e 85f08bff f61a74f6 0000d086 0e740100 0xcccccccc
bd004ea2 f61a74f6 0000d086 0e740100 00ff34a1 0x85f08bff
bd004ea6 00000000 0e740100 00ff34a1 3450ffbd 0xf61a74f6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+a6bd3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a891ca7

FAILURE_BUCKET_ID:  0x50_nv4_disp+a6bd3

BUCKET_ID:  0x50_nv4_disp+a6bd3

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

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: e4b2ceec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bd0b8bd3, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  e4b2ceec 

FAULTING_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  Gothic3.exe

LAST_CONTROL_TRANSFER:  from bd0b8d41 to bd0b8bd3

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b718ea90 bd0b8d41 e2877ee8 00000000 e2877ee8 nv4_disp+0xa6bd3
b718eac8 8053b58c 85a4c7b8 8535f098 85cc7b00 nv4_disp+0xa6d41
b718eaec 80517c27 8535f098 034a0000 00000000 nt!CcPfLogPageFault+0x18
b718eb48 805452e1 85333e10 029c4fff 85333e34 nt!MmCheckCachedPageState+0x50b
b718ebe4 bf80197c 85a4c7b8 b718ec0c b718ebb8 nt!ExAllocatePoolWithTag+0x3e1
b718ec24 bd004e5f 029c3960 0000072c bd004e82 win32k!GreReleaseSemaphore+0xa
b718ec5c bd00b771 bd00b830 b718ed64 00c3e02c dxg!bDdSecureSystemMemorySurface+0x5f
bd004e82 cccccccc 8b55ff8b 658351ec 575600fc dxg!DxDdCreateSurfaceObject+0xbd
bd004e9e 85f08bff f61a74f6 0000d086 0e740100 0xcccccccc
bd004ea2 f61a74f6 0000d086 0e740100 00ff34a1 0x85f08bff
bd004ea6 00000000 0e740100 00ff34a1 3450ffbd 0xf61a74f6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+a6bd3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a891ca7

FAILURE_BUCKET_ID:  0x50_nv4_disp+a6bd3

BUCKET_ID:  0x50_nv4_disp+a6bd3

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

Jestem świeżo po formacie i instalacji windowsa sterowniki z strony producenta najnowsze jakie były karta graficzna Geforce Asus 6600 128mb/128bit

proszę o pomoc jeśli jest możliwa

Post28 sie 2009, 00:35

afgan1939, pobierz program Everest Ultimate Edition.
Otwórz program -> Komputer -> Podsumowanie -> spisz informacje z pozycji:
-> Nazwa płyty głównej
-> Mikroukład płyty głównej

Post28 sie 2009, 00:38

Post28 sie 2009, 00:41

Odinstaluj obecny sterownik karty graficznej:
(Start -> Panel sterowania -> Dodaj/Usuń programy -> NVIDIA DISPLAY DRIVER /usuń/)
Po zakończeniu deinstalacji uruchom ponownie komputer.
Teraz zainstaluj sterownik do chipsetu płyty głównej VIA Hyperion Pro 4in1 5.24A Chipset Driver.
Po zakończeniu instalacji uruchom ponownie komputer.
Następnie zainstaluj Dostępne tylko dla zarejestrowanych użytkowników.
Po zakończeniu instalacji uruchom ponownie komputer.

Na końcu zainstaluj najnowsze biblioteki DirectX 9.0c (Instrukcja instalacji bibliotek DirectX 9.0c).

Post28 sie 2009, 00:44

juz sie pobiera wszystko a zawsze sie zastanawialem po co sa te pliki

VIA Hyperion Pro 4in1 5.24A Chipset Driver

zaraz dam edita

Post28 sie 2009, 00:48

afgan1939 pisze:juz sie pobiera wszystko a zawsze sie zastanawialem po co sa te pliki
VIA Hyperion Pro 4in1 5.24A Chipset Driver

To sterowniki do chipsetu Twojej płyty głównej.
Chipset, to mikroukład składający się z mostka północnego i południowego, sterujący poszczególnymi elementami płyty głównej.

Post28 sie 2009, 00:53

tylko ze nigdy ich nie instalowałem bo nie słyszałem że są do czegokolwiek potrzebne teraz będę je instalował już zawsze

Post28 sie 2009, 01:02

Sterowniki do chipsetu płyty głównej to podstawa.
Powinno instalować się je zawsze jako pierwsze po instalacji systemu operacyjnego.

Post28 sie 2009, 01:27

ok teraz tylko DirectX 9.0c

-- Dzisiaj, 01:30 --

DirectX zainstalowany uruchomić ponownie kompa ??

Post28 sie 2009, 01:38

DirectX zainstalowany uruchomić ponownie kompa ??

Uruchom ponownie.
Jak coś instalujesz to wyłącz wszystkie programy i nie korzystaj z przeglądarki.

Post06 wrz 2009, 09:11

i znów

Kod: Zaznacz cały

*******************************************************************************
*                                                                             *
*                        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: e4b2ceec, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bd0b8bd3, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS:  e4b2ceec 

FAULTING_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x50

PROCESS_NAME:  Gothic3.exe

LAST_CONTROL_TRANSFER:  from bd0b8d41 to bd0b8bd3

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b718ea90 bd0b8d41 e2877ee8 00000000 e2877ee8 nv4_disp+0xa6bd3
b718eac8 8053b58c 85a4c7b8 8535f098 85cc7b00 nv4_disp+0xa6d41
b718eaec 80517c27 8535f098 034a0000 00000000 nt!CcPfLogPageFault+0x18
b718eb48 805452e1 85333e10 029c4fff 85333e34 nt!MmCheckCachedPageState+0x50b
b718ebe4 bf80197c 85a4c7b8 b718ec0c b718ebb8 nt!ExAllocatePoolWithTag+0x3e1
b718ec24 bd004e5f 029c3960 0000072c bd004e82 win32k!GreReleaseSemaphore+0xa
b718ec5c bd00b771 bd00b830 b718ed64 00c3e02c dxg!bDdSecureSystemMemorySurface+0x5f
bd004e82 cccccccc 8b55ff8b 658351ec 575600fc dxg!DxDdCreateSurfaceObject+0xbd
bd004e9e 85f08bff f61a74f6 0000d086 0e740100 0xcccccccc
bd004ea2 f61a74f6 0000d086 0e740100 00ff34a1 0x85f08bff
bd004ea6 00000000 0e740100 00ff34a1 3450ffbd 0xf61a74f6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+a6bd3
bd0b8bd3 894208          mov     dword ptr [edx+8],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+a6bd3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a891ca7

FAILURE_BUCKET_ID:  0x50_nv4_disp+a6bd3

BUCKET_ID:  0x50_nv4_disp+a6bd3

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

Kod: Zaznacz cały

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: e29ee3e0, Address of the block of pool being deallocated

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


POOL_ADDRESS:  e29ee3e0 

BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME:  MOHA.exe

LAST_CONTROL_TRANSFER:  from 80544b06 to 804f8cc5

STACK_TEXT:  
b6e6bc24 80544b06 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
b6e6bc74 bf802ae5 e29ee3e0 00000000 b6e6bc9c nt!ExFreePoolWithTag+0x2a0
b6e6bc84 bf80e7c5 e29ee3e0 b6e6bd14 e29ee3e0 win32k!HeavyFreePool+0xbb
b6e6bc9c bf92eec8 e29ee3e0 e124f6a8 b6e6bce8 win32k!HMFreeObject+0xa0
b6e6bcac bf801c24 e29ee3e0 b6e6bd64 00000000 win32k!FreeHidData+0x21
b6e6bce8 bf803754 00000001 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x2b2
b6e6bd48 8053d648 0d2fff98 00000000 00000000 win32k!NtUserPeekMessage+0x40
b6e6bd48 7c90e514 0d2fff98 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0d2fff44 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HeavyFreePool+bb
bf802ae5 5d              pop     ebp

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!HeavyFreePool+bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49e85edc

FAILURE_BUCKET_ID:  0xc2_7_win32k!HeavyFreePool+bb

BUCKET_ID:  0xc2_7_win32k!HeavyFreePool+bb

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

Kod: Zaznacz cały

*******************************************************************************
*                                                                             *
*                        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: bf9277a0, The address that the exception occurred at
Arg3: f785fb48, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
win32k!FreeInputContext+16
bf9277a0 8b80c4000000    mov     eax,dword ptr [eax+0C4h]

TRAP_FRAME:  f785fb48 -- (.trap 0xfffffffff785fb48)
ErrCode = 00000000
eax=00000000 ebx=00000087 ecx=b9e73488 edx=b9d10001 esi=b9e73488 edi=00000654
eip=bf9277a0 esp=f785fbbc ebp=f785fbc0 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
win32k!FreeInputContext+0x16:
bf9277a0 8b80c4000000    mov     eax,dword ptr [eax+0C4h] ds:0023:000000c4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x8E

PROCESS_NAME:  spoolsv.exe

LAST_CONTROL_TRANSFER:  from bf8b6833 to bf9277a0

STACK_TEXT:  
f785fbc0 bf8b6833 b9e73488 f785fc04 bf898921 win32k!FreeInputContext+0x16
f785fbcc bf898921 b9d10654 863c2590 e1daeca0 win32k!HMDestroyUnlockedObject+0x1c
f785fbe0 bf8990ef 8641bda8 00000000 00000000 win32k!DestroyThreadsObjects+0x72
f785fc04 bf819d44 00000001 f785fc2c bf819e08 win32k!xxxDestroyThreadInfo+0x1cf
f785fc10 bf819e08 8641bda8 00000001 00000000 win32k!UserThreadCallout+0x4b
f785fc2c 805c877d 8641bda8 00000001 863c82d8 win32k!W32pThreadCallout+0x3d
f785fcf0 805c8b31 00000000 f785fd4c 804fdbed nt!PspExitThread+0x3f3
f785fcfc 804fdbed 863c82d8 f785fd48 f785fd3c nt!PsExitSpecialApc+0x23
f785fd4c 8053d6b1 00000001 00000000 f785fd64 nt!KiDeliverApc+0x1af
f785fd4c 7c90e514 00000001 00000000 f785fd64 nt!KiServiceExit+0x58
WARNING: Frame IP not in any known module. Following frames may be wrong.
00a3ffb4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!FreeInputContext+16
bf9277a0 8b80c4000000    mov     eax,dword ptr [eax+0C4h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!FreeInputContext+16

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49e85edc

FAILURE_BUCKET_ID:  0x8E_win32k!FreeInputContext+16

BUCKET_ID:  0x8E_win32k!FreeInputContext+16

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

i ostatni póki co

Kod: Zaznacz cały

*******************************************************************************
*                                                                             *
*                        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: bf851516, The address that the exception occurred at
Arg3: b8186ccc, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
win32k!zzzUnhookWindowsHookEx+a
bf851516 f6472080        test    byte ptr [edi+20h],80h

TRAP_FRAME:  b8186ccc -- (.trap 0xffffffffb8186ccc)
ErrCode = 00000000
eax=b9ebd968 ebx=bf851575 ecx=b9d10e94 edx=000003a5 esi=0012fe7c edi=b9ebd968
eip=bf851516 esp=b8186d40 ebp=b8186d48 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
win32k!zzzUnhookWindowsHookEx+0xa:
bf851516 f6472080        test    byte ptr [edi+20h],80h     ds:0023:b9ebd988=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Tibia.exe

LAST_CONTROL_TRANSFER:  from bf851594 to bf851516

STACK_TEXT:  
b8186d48 bf851594 b9ebd968 0012fe7c b8186d64 win32k!zzzUnhookWindowsHookEx+0xa
b8186d58 8053d648 00360137 0015cf04 7c90e514 win32k!NtUserUnhookWindowsHookEx+0x23
b8186d58 7c90e514 00360137 0015cf04 7c90e514 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fe6c 7e37d5ff 00576b29 00360137 0078c290 0x7c90e514
0012fee8 804ffed7 ff676980 ffffffff 409c49f7 0x7e37d5ff
0012ff30 80543e41 865f2000 000000a5 0055b273 nt!KiInsertTimerTable+0x1b
0012ffa8 806175e7 0012ffe0 0055adb4 005cf698 nt!MiFreePoolPages+0x65f
0012ffa8 00000000 0012ffe0 0055adb4 005cf698 nt!CcPfBeginAppLaunch+0x19f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!zzzUnhookWindowsHookEx+a
bf851516 f6472080        test    byte ptr [edi+20h],80h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!zzzUnhookWindowsHookEx+a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49e85edc

FAILURE_BUCKET_ID:  0x8E_win32k!zzzUnhookWindowsHookEx+a

BUCKET_ID:  0x8E_win32k!zzzUnhookWindowsHookEx+a

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

jak widać podczas rożnych procesów się to dzieje

mogę na was liczyć ??

Post06 wrz 2009, 11:10

Z nowu karta graficzna, zobacz starszy sterownik Dostępne tylko dla zarejestrowanych użytkowników

Post06 wrz 2009, 11:37

zainstalowałem teraz 175 zobaczę jak będzie chodziło