Bonjour,
mon pc plante constamment et de manière aléatoire, j'ai droit à des écrans bleu en pagaille (une bonne 30aine en 3 jours) et surtout lorsqu'il ne bosse pas.
Les infos qui apparaissent alors sont:
STOP 0x0000001E (0xffffffffC0000005,0xFFFFF80002DE59AC,0X0000000000000000,0XFFFFFFFFFFFFFFFF)
dans le fichier minidump:
*******************************************************************************
* *
* 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002afaa36, The address that the exception occurred at
Arg3: fffff88003139868, Exception Record Address
Arg4: fffff880031390c0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L
FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+49955
fffff800`02afaa36 488b00 mov rax,qword ptr [rax]
EXCEPTION_RECORD: fffff88003139868 -- (.exr 0xfffff88003139868)
ExceptionAddress: fffff80002afaa36 (nt! ?? ::FNODOBFM::`string'+0x0000000000049955)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031390c0 -- (.cxr 0xfffff880031390c0)
rax=b800000000000000 rbx=0000000000000000 rcx=b800000000000000
rdx=fffffa8004536000 rsi=fffff88003139b60 rdi=fffffa8006a9ddb8
rip=fffff80002afaa36 rsp=fffff88003139aa0 rbp=0000000000000002
r8=fffff80002beec38 r9=fffffa8006a9ddb8 r10=fffff88003139870
r11=fffff80002a8c6b0 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt! ?? ::FNODOBFM::`string'+0x49955:
fffff800`02afaa36 488b00 mov rax,qword ptr [rax] ds:002b:b8000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - L
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb00e0
ffffffffffffffff
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+49955
fffff800`02afaa36 488b00 mov rax,qword ptr [rax]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002a8e6e2 to fffff80002afaa36
STACK_TEXT:
fffff880`03139aa0 fffff800`02a8e6e2 : 00000000`0000270d 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x49955
fffff880`03139b40 fffff800`02a8e96f : 00000000`00000008 fffff880`03139bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03139b90 fffff800`02d1d166 : fffffa80`03d0c040 00000000`00000080 fffffa80`03cec040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03139d00 fffff800`02a58486 : fffff800`02bf2e80 fffffa80`03d0c040 fffff800`02c00c40 3b660000`01fdb96f : nt!PspSystemThreadStartup+0x5a
fffff880`03139d40 00000000`00000000 : fffff880`0313a000 fffff880`03134000 fffff880`031396d0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49955
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880031390c0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49955
BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49955
Followup: MachineOwner
---------
là je sèche complet.Le bios de ma carte mère est à jour, tous les pilotes également, il n'y a pas de conflit matériel. Seul le bios de ma carte graphique n'est pas à jour car le dernier firmware fait apparaître des artefacts.
ma config:
carte mére: asus P5E3 Pro
proc: E8400
mémoire: 2x2go DDR3 1600 elixir
carte graphique: sapphire 4870x2
merci d'avance