black ice
13 Feb 2005, 06:36 PM
Avem in felul urmator:
1. Una bucata placa FX 5700VE noua + ultimele drivere
2. Una bucata WinXP SP 2
Problema:
1. Inainte de aceasta placa am avut un 9800 SE @ Pro careia ia cedat coolerul. Am instalat noua placa, noii driveri iar timp de jumatate de ora n-au fost nici un fel de probleme. Am rulat orice joc am vrut. Dupa aceasta jumatate de ora, in momentul in care intram intr-un joc, dupa o fractiune de secunda in care imi aparea unu BSOD, calculatorul se restarta, urmand ca la incarcarea win-ului la scandiskul aferent sa se blocheze iar. Orice aplicatie ce necesita accelerare grafica determina aceasta resetare, altfel totul merge perfect.
Am rulat un debugger care mi-a afisat urmatoarele:
| CODE |
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini011405-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:
Unable to load image 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, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri Jan 14 16:45:39.703 2005 (GMT+2)
System Uptime: 0 days 0:18:47.303
Unable to load image 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 unloaded module list
Mini Kernel Dump does not contain unloaded driver list
No unloaded module list present
Loading User Symbols
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll |
Evident, din driverele placii ATI mai ramasese ceva. Am rulat Driver Cleaner in safe mode, am inlaturat ce era de inlaturat, apoi am sters manual fisierul respectiv care continua sa faca probleme si am crezut ca problema s-a rezolvat. Nici pe departe. Acum debuggerul imi indica o probleme cu un .dll nvidia.
A urmat o formatare a partititiei cu win-ul, o reinstalare si o noua incercare.
Acelasi lucru. Debuggerul mi-a afisat urmatoarele:
| CODE |
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021205-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sat Feb 12 19:59:45.906 2005 (GMT+2)
System Uptime: 0 days 0:05:31.526
Loading Kernel Symbols
...................................................................... ........................................................
Loading unloaded module list
.........
Loading User Symbols
[b]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[/b]
********************************************************************** *********
* *
* Bugcheck Analysis *
* *
********************************************************************** *********
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {f7c59000, 0, bf180c35, 0}
Could not read faulting driver name
Probably caused by : nv4_disp.dll ( nv4_disp+16ec35 )
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: f7c59000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf180c35, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: f7c59000
FAULTING_IP:
nv4_disp+16ec35
bf180c35 0f6e06 movd mm0,dword ptr [esi]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from bf0ea2af to bf180c35
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f776eae4 bf0ea2af f7c58100 e1d62a00 00000051 nv4_disp+0x16ec35
00000008 00000000 00000000 00000000 00000000 nv4_disp+0xd82af
FOLLOWUP_IP:
nv4_disp+16ec35
bf180c35 0f6e06 movd mm0,dword ptr [esi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nv4_disp+16ec35
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 41acdded
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x50_nv4_disp+16ec35
BUCKET_ID: 0x50_nv4_disp+16ec35
Followup: MachineOwner |
Aveti vreo idee despre cum as putea rezolva problema?
Eu banuiesc ca e o problema hardware, de la placa video, avand in vedere ca am incercat mai multi driveri si ca am primit aceeasi eroare.
Justice
22 Feb 2005, 12:27 AM
In cazul in care vendorul placii este unul cunoscut iti sugerez sa folosesti ultimul driver "customizat" de respectivul vendor, in caz ca deja ai incercat asta, incearca driverele nVidia generice.
Si eu tind sa cred ca poate fi o problema hardware, dar inainte de a trage concluzia finala, ia placa si testeaza si pe alte 2 sisteme.
Ti-as mai recomanda sa ai ultimele drivere instalate de la chipsetul placii de baza.
Succes !