YoUpIeN

Bon alors c'est ce que je craignais, je n'ai plus qu'a faire marcher la garantie c'est ça! Boaf, j'espere que celle de top achat n'est pas trop longue sinon bonjour la galére!!! Merci en tous cas!

Salut !!! J'ai un probleme avec mon pc, il plante et m'affiche le fameux ecran bleu. J'ai reussit a analyser le fichier minidump avec WinDGB, et le voici : ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} Unable to load image klif.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys Probably caused by : memory_corruption Followup: memory_corruption --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION LAST_CONTROL_TRANSFER: from 804dbde0 to 804dbf4d STACK_TEXT: f8989d20 804dbde0 f8989d6c 823c83c8 ffdff120 nt!SwapContext+0x95 f8989d34 804dc6a6 823c8438 823c83c8 804e4611 nt!KiSwapContext+0x2e f8989d40 804e4611 80553ae0 80561b7c 823c83c8 nt!KiSwapThread+0x46 f8989d6c 804e47d0 00000001 48847801 00000000 nt!KeRemoveQueue+0x20e f8989dac 8057dfed 00000001 00000000 00000000 nt!ExpWorkerThread+0xd6 f8989ddc 804fa477 804e4729 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt 804dbec3-804dbec9 7 bytes - nt!SwapContext+a [ 83 bb 94 09 00 00 00:e9 60 e0 f4 75 90 90 ] 7 errors : !nt (804dbec3-804dbec9) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: LARGE STACK_COMMAND: kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE BUCKET_ID: MEMORY_CORRUPTION_LARGE Followup: memory_corruption A Votre avis?? probleme de memoire? mauvaise emplacement? Barette HS? J'ai lance MemTest86+, et la j'y comprends rien! A priorie il m'indique des erreur au test5 (block moves, 64 moves), quelqu'un pourrait m'aider???