Spero di aver scelto il giusto trhead
ho un pc che ogni tanto si crasha e non sono ancora riuscito a capire bene cosa c'è che ogni tanto lo fa bloccare però dal memory dump ho recuperato queste informazioni:
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.130307-0422
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b340
Debug session time: Sun Jun 9 14:41:20.812 2013 (UTC + 2:00)
System Uptime: 0 days 1:34:00.375
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
..........................................................
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 8054bd34, b57d5f98, 0}
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+d442 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8054bd34, The address that the exception occurred at
Arg3: b57d5f98, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".
FAULTING_IP:
nt!ExAllocatePoolWithTag+673
8054bd34 897104 mov dword ptr [ecx+4],esi
TRAP_FRAME: b57d5f98 -- (.trap 0xffffffffb57d5f98)
ErrCode = 00000002
eax=8a2fb290 ebx=8a2eb028 ecx=ffffffff edx=00000041 esi=8a2eb290 edi=000001ff
eip=8054bd34 esp=b57d600c ebp=b57d6060 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExAllocatePoolWithTag+0x673:
8054bd34 897104 mov dword ptr [ecx+4],esi ds:0023:00000003=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: TeamViewer_Desk
LAST_CONTROL_TRANSFER: from 8051d955 to 805338fe
STACK_TEXT:
b57d5b60 8051d955 0000008e c0000005 8054bd34 nt!KeBugCheckEx+0x1b
b57d5f28 804df235 b57d5f44 00000000 b57d5f98 nt!KiDispatchException+0x3b1
b57d5f90 804df1e6 b57d6060 8054bd34 badb0d00 nt!CommonDispatchException+0x4d
b57d5fc0 8056a493 00000000 00000023 00000023 nt!KiExceptionExit+0x18a
b57d6060 8057de81 00000001 00000001 67727453 nt!CmpCompareCompressedName+0x58
b57d6074 805ffcab 00000200 887ce1c8 e3827258 nt!ExpAllocateStringRoutine+0x14
b57d60e4 b97c1c69 00000000 e3827190 b57d610c nt!RtlQueryRegistryValues+0x4f
b57d6158 b97cea1d 8996a350 e3827190 00000000 VIDEOPRT!VPGetRegistryParameters+0xed
b57d617c b97e1442 8996a350 887ce1c8 00000000 VIDEOPRT!VideoPortGetRegistryParameters+0x2d
WARNING: Stack unwind information not available. Following frames may be wrong.
b57d61c0 b9de526c 8996a350 887ce1c8 00000000 nv4_mini+0xd442
00000000 00000000 00000000 00000000 00000000 nv4_mini+0x61126c
STACK_COMMAND: kb
FOLLOWUP_IP:
nv4_mini+d442
b97e1442 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: nv4_mini+d442
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_mini
IMAGE_NAME: nv4_mini.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 481c068d
FAILURE_BUCKET_ID: 0x8E_nv4_mini+d442
BUCKET_ID: 0x8E_nv4_mini+d442
Followup: MachineOwner
---------
ho tutti i driver installati e aggiornarti fatte diverse scansioni antivirus e test memorie senza trovare problemi
sembrerebbe causato da nv4_mini.sys che da quello che ho capito è un file dei driver della scheda video qualcuno sa dirmi cosa potrei fare per evitare questo errore???