| | |
| Stránka: 1 z 1
| [ Príspevkov: 8 ] | |
Autor | Správa |
---|
Registrovaný: 22.07.10 Prihlásený: 30.08.10 Príspevky: 5 Témy: 1 | Napísal Q.Q: 22.07.2010 23:10 | |
|
zdravim mam problem, pri hrani hier mi hadze BSOD a neviem co s tym, v tomto sa moc nevyznam
tu je log z windbg
Unable to load image nv4_disp.dll, Win32 error 0n2
*** 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 1000007E, {c000001d, bf19d6d0, b5ba7b8c, b5ba7888}
Probably caused by : hardware ( nv4_disp+18b6d0 )
Followup: MachineOwner
---------
0: 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: c000001d, The exception code that was not handled
Arg2: bf19d6d0, The address that the exception occurred at
Arg3: b5ba7b8c, Exception Record Address
Arg4: b5ba7888, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nv4_disp+18b6d0
bf19d6d0 ff ???
EXCEPTION_RECORD: b5ba7b8c -- (.exr 0xffffffffb5ba7b8c)
ExceptionAddress: bf19d6d0 (nv4_disp+0x0018b6d0)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: b5ba7888 -- (.cxr 0xffffffffb5ba7888)
eax=00000000 ebx=e1e005c0 ecx=e1e005c0 edx=0001c84a esi=e1fed800 edi=e2016c0c
eip=bf19d6d0 esp=b5ba7c54 ebp=e2016c04 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nv4_disp+0x18b6d0:
bf19d6d0 ff ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: war3.exe
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
MISALIGNED_IP:
nv4_disp+18b6d0
bf19d6d0 ff ???
LAST_CONTROL_TRANSFER: from e1fed800 to bf19d6d0
FAILED_INSTRUCTION_ADDRESS:
nv4_disp+18b6d0
bf19d6d0 ff ???
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b5ba7c50 e1fed800 e1fed800 e1e005c0 e1e005c0 nv4_disp+0x18b6d0
b5ba7c54 e1fed800 e1e005c0 e1e005c0 00000071 0xe1fed800
b5ba7c58 e1e005c0 e1e005c0 00000071 00000002 0xe1fed800
b5ba7c5c e1e005c0 00000071 00000002 00000000 0xe1e005c0
b5ba7c60 00000000 00000002 00000000 00000000 0xe1e005c0
FOLLOWUP_IP:
nv4_disp+18b6d0
bf19d6d0 ff ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nv4_disp+18b6d0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xffffffffb5ba7888 ; kb
FAILURE_BUCKET_ID: IP_MISALIGNED_nv4_disp.dll
BUCKET_ID: IP_MISALIGNED_nv4_disp.dll
Followup: MachineOwner
|
|
Registrovaný: 22.07.10 Prihlásený: 30.08.10 Príspevky: 5 Témy: 1 | Napísal autor témy Q.Q: 24.07.2010 19:35 | |
|
nejake napady?
|
|
Registrovaný: 31.01.08 Prihlásený: 22.10.22 Príspevky: 2299 Témy: 100 Bydlisko: Komjatice |
Co tak skusit iny ovladac na vga???
_________________ PC: CPU: Intel I5 8400, MB: Tomahawk, RAM: 16 GB Patriot Viper, HDD: 240 gb adata ssd, Seagate Barracuda 1TB, VGA: MSI Gaming 1060 6gb, PSU: Seasonic 520W 80Plus Bronze,HDD: NZXT Phantom 630 Mon: MSI 27´, mouse: Asus Sica, Mousepad: Razer ProSolution
cing cing: Tamtung Note10+ Vehicle Škoda Rapid 2017 |
|
Registrovaný: 20.08.08 Prihlásený: 08.02.16 Príspevky: 623 Témy: 16 Bydlisko: Limbach[SK]... |
tento typ BSOD mi vyskakoval po otvoreni a nacitani GPU-Z
nahod najnovsie drivery 258.96 WHQL a snad problem zmizne (mne pomohol uz predchadzajuci update)
_________________ Notebook Lenovo ThinkPad X201 CPU Intel Core i7-620M RAM 4 GB DDR3 SSD Lite-On LCS-256L9S-11 256 GB OS Windows 7 Ultimate 64bit Dock Station LCD LG 25UM65-P Mouse+Pad A4Tech Bloody V5 + Steel Pad QcK Mini Phone Xiaomi Redmi (Hongmi) | MIUIv7 |
|
Registrovaný: 22.07.10 Prihlásený: 30.08.10 Príspevky: 5 Témy: 1 | Napísal autor témy Q.Q: 24.07.2010 21:26 | |
|
po nainstalovani noveho drivera mi hodilo dalsi BSOD
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {3000, 2, 1, 806e6a2a}
Probably caused by : win32k.sys ( win32k!GreReleaseSemaphore+a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00003000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806e6a2a, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00003000
CURRENT_IRQL: 2
FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLock+3a
806e6a2a 8902 mov dword ptr [edx],eax
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: war3.exe
LAST_CONTROL_TRANSFER: from bf801974 to 806e6a2a
STACK_TEXT:
b3f3fbb0 bf801974 bf80621d e20d19c0 bd0779ca hal!KeAcquireInStackQueuedSpinLock+0x3a
b3f3fbb4 bf80621d e20d19c0 bd0779ca 81b9e130 win32k!GreReleaseSemaphore+0xa
b3f3fc28 bf8e9bc8 b3f3fc78 e1777714 bf8e9b94 win32k!EngReleaseSemaphore+0x21
b3f3fc60 bd009af4 b3f3fc78 b3f3fd30 0012fb14 win32k!WatchdogDdLock+0x38
b3f3fcd8 bd00af49 e1777714 00000000 b3f3fd0c dxg!pDdLockSurfaceOrBuffer+0x288
b3f3fd50 8054163c 0840000a 0012fae4 00000000 dxg!DxDdLock+0x69
b3f3fd50 7c90e514 0840000a 0012fae4 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fb18 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!GreReleaseSemaphore+a
bf801974 ff2538de98bf jmp dword ptr [win32k!_imp__KeLeaveCriticalRegion (bf98de38)]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k!GreReleaseSemaphore+a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bdd0c20
FAILURE_BUCKET_ID: 0xA_win32k!GreReleaseSemaphore+a
BUCKET_ID: 0xA_win32k!GreReleaseSemaphore+a
Followup: MachineOwner
|
|
Registrovaný: 31.01.08 Prihlásený: 22.10.22 Príspevky: 2299 Témy: 100 Bydlisko: Komjatice |
No podla toho ako som sa docital tak problem s BSOD s tymto privlastkom by mali sposobovat napr. zastaralé a beta ovládače pre zvukovky od creative.
Ale skor ako to uvedene vyssie skus reinstal win (zabudol si uviest o aky win ide). Ak ti to bude robit aj nadalej daj sem o tom report.
_________________ PC: CPU: Intel I5 8400, MB: Tomahawk, RAM: 16 GB Patriot Viper, HDD: 240 gb adata ssd, Seagate Barracuda 1TB, VGA: MSI Gaming 1060 6gb, PSU: Seasonic 520W 80Plus Bronze,HDD: NZXT Phantom 630 Mon: MSI 27´, mouse: Asus Sica, Mousepad: Razer ProSolution
cing cing: Tamtung Note10+ Vehicle Škoda Rapid 2017 |
|
Registrovaný: 22.07.10 Prihlásený: 30.08.10 Príspevky: 5 Témy: 1 | Napísal autor témy Q.Q: 25.07.2010 14:23 | |
|
tuto temu som zalozil az po reinstale windows
mam win XP
nenasiel by sa niekto, kto by vedel poradit ake ovladace su pre mna najvhodnejsie?
grafika - geforce 9600 gt
doska - ASUS M2N-SLI DELUXE
procesor - amd athlon 64 X2 dual core 6400+
po pripade ak budete potrebovat nejake dalsie info, dopisem np
|
|
Registrovaný: 22.07.10 Prihlásený: 30.08.10 Príspevky: 5 Témy: 1 | Napísal autor témy Q.Q: 26.07.2010 17:31 | |
|
dalsi bsod
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: 00077b37, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b4529a8a, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00077b37
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!DeliverToUserEx+7e3
b4529a8a ff5008 call dword ptr [eax+8]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from b4529836 to b4529a8a
STACK_TEXT:
b84f7bfc b4529836 00077b2f 899e3268 b84f7d18 tcpip!DeliverToUserEx+0x7e3
b84f7cb4 b4535ce6 899e3268 89bb0a10 889a5610 tcpip!IPRcvPacket+0x6cb
b84f7d60 b84503e4 b4569680 899e3268 b4569690 tcpip!LoopXmitRtn+0x195
b84f7d7c 80538789 899e3268 00000000 89db7b30 TDI!CTEpEventHandler+0x32
b84f7dac 805cff62 b4569680 00000000 00000000 nt!ExpWorkerThread+0xef
b84f7ddc 8054611e 8053869a 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
TDI!CTEpEventHandler+32
b84503e4 5f pop edi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: TDI!CTEpEventHandler+32
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TDI
IMAGE_NAME: TDI.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 48025834
FAILURE_BUCKET_ID: 0xD1_TDI!CTEpEventHandler+32
BUCKET_ID: 0xD1_TDI!CTEpEventHandler+32
Followup: MachineOwner
|
|
| Stránka: 1 z 1
| [ Príspevkov: 8 ] | |
| Nemôžete zakladať nové témy v tomto fóre Nemôžete odpovedať na témy v tomto fóre Nemôžete upravovať svoje príspevky v tomto fóre Nemôžete mazať svoje príspevky v tomto fóre
|
|