Bonjour,
 
Voilà 3 mois que je suis victime de BSOD à GOGO !!!!
Il y a 8 jours, j’ai démonté la CM, mis la ram sur le channel 2. Et j’ai eu un uptime de 8 jours… Miraculeux !!!!
Mais depuis hier soir, j’ai un écran bleu toutes les 10 min en moyenne.
 
Config :  
CM : MSI P35 Platinum
CG : ATI RADEON X1950XTX 512Mo ddr4
RAM : 2x1Go Crucial balistix pc2 8500
CPU : E6750
ALIM : Corsair HX520W
Je n’ai  pas de virus, pas de surchauffe, pas de vers, pas de Trojan, aucun problem avec hijackthis, Ram testé, cpu changé, hd changé, cg changée… Et le problème est revenu…
J’aimerais avoir l’avis de quelqu’un capable d’identifier un problème sous windebug uniquement .
Comment expliquer le fait que je n’ai eu aucune problème en 8 jours et que la j’en suis a 12 bsod en 2h  ?
Voici les erreurs sous Windebug :
En voici 4, si vous en voulez plus, je peux vous en proposer plus.
Si vous souhaitez m’aider via msn je suis connecté quand l’ordi ne plante pas :
Cut_ludo@hotmail.com
 
---------- BUG 1er !!! ---------
BugCheck 1000000A, {ffbe0000, 2, 0, 804f4d86}
 
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+322 )
 
Followup: MachineOwner
---------
 
1: 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: ffbe0000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804f4d86, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  ffbe0000  
 
CURRENT_IRQL:  2
 
FAULTING_IP:  
nt!MmUnmapViewInSystemCache+322
804f4d86 3906            cmp     dword ptr [esi],eax
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
LAST_CONTROL_TRANSFER:  from 8056fb5a to 804f4d86
 
STACK_TEXT:  
f78c6c68 8056fb5a ce745000 88d04128 00000000 nt!MmUnmapViewInSystemCache+0x322
f78c6c80 804f4638 89bf1e90 889d03d0 00000000 nt!CcUnmapVacb+0x2a
f78c6cb0 804f4b44 00000000 00000000 889d0434 nt!CcUnmapVacbArray+0xe5
f78c6ccc 804f4ab6 889d03d0 806ffa4c 889d03d0 nt!CcUnmapAndPurge+0x20
f78c6cfc 804ed808 00000001 8055e690 88a08818 nt!CcDeleteSharedCacheMap+0xc5
f78c6d34 804e67c8 89bfa288 805694c0 89bfc3c8 nt!CcWriteBehind+0x357
f78c6d7c 804e23b5 89bfa288 00000000 89bfc3c8 nt!CcWorkerThread+0x12f
f78c6dac 80574120 89bfa288 00000000 00000000 nt!ExpWorkerThread+0xef
f78c6ddc 804ec781 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
nt!MmUnmapViewInSystemCache+322
804f4d86 3906            cmp     dword ptr [esi],eax
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt!MmUnmapViewInSystemCache+322
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  48a401b1
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+322
 
BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+322
 
Followup: MachineOwner
---------
 
----- BUG 2 ------
BugCheck 1000000A, {ffbe0000, 1, 0, 804f48dc}
 
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+144 )
 
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: ffbe0000, memory referenced
Arg2: 00000001, IRQL
Arg3: 00000000, 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: 804f48dc, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  ffbe0000  
 
CURRENT_IRQL:  1
 
FAULTING_IP:  
nt!MmUnmapViewInSystemCache+144
804f48dc 3907            cmp     dword ptr [edi],eax
 
CUSTOMER_CRASH_COUNT:  2
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
LAST_CONTROL_TRANSFER:  from 8056fb5a to 804f48dc
 
STACK_TEXT:  
f78b6c68 8056fb5a cf745000 89a5f718 00000000 nt!MmUnmapViewInSystemCache+0x144
f78b6c80 804f4638 89bead38 89a7cb60 00000000 nt!CcUnmapVacb+0x2a
f78b6cb0 804f4b44 00000000 00000000 89a7cbc4 nt!CcUnmapVacbArray+0xe5
f78b6ccc 804f4ab6 89a7cb60 806ffa4c 89a7cb60 nt!CcUnmapAndPurge+0x20
f78b6cfc 804ed808 00000001 8055e690 88e43ad0 nt!CcDeleteSharedCacheMap+0xc5
f78b6d34 804e67c8 89c3fd90 805694c0 89bfcb30 nt!CcWriteBehind+0x357
f78b6d7c 804e23b5 89c3fd90 00000000 89bfcb30 nt!CcWorkerThread+0x12f
f78b6dac 80574120 89c3fd90 00000000 00000000 nt!ExpWorkerThread+0xef
f78b6ddc 804ec781 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
nt!MmUnmapViewInSystemCache+144
804f48dc 3907            cmp     dword ptr [edi],eax
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt!MmUnmapViewInSystemCache+144
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  48a401b1
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+144
 
BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+144
 
Followup: MachineOwner
---- BUG 3 ----
BugCheck 1000000A, {ffbe0000, 2, 0, 804f4d86}
 
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+322 )
 
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: ffbe0000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 804f4d86, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  ffbe0000  
 
CURRENT_IRQL:  2
 
FAULTING_IP:  
nt!MmUnmapViewInSystemCache+322
804f4d86 3906            cmp     dword ptr [esi],eax
 
CUSTOMER_CRASH_COUNT:  3
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
LAST_CONTROL_TRANSFER:  from 8056fb5a to 804f4d86
 
STACK_TEXT:  
f78bac68 8056fb5a d862b000 88e19848 00000000 nt!MmUnmapViewInSystemCache+0x322
f78bac80 804f4638 89be7168 88cf9008 00000000 nt!CcUnmapVacb+0x2a
f78bacb0 804f4b44 00000000 00000000 88cf906c nt!CcUnmapVacbArray+0xe5
f78baccc 804f4ab6 88cf9008 806ffa4c 88cf9008 nt!CcUnmapAndPurge+0x20
f78bacfc 804ed808 00000001 8055e690 88e9d420 nt!CcDeleteSharedCacheMap+0xc5
f78bad34 804e67c8 89c3f030 805694c0 89bfcda8 nt!CcWriteBehind+0x357
f78bad7c 804e23b5 89c3f030 00000000 89bfcda8 nt!CcWorkerThread+0x12f
f78badac 80574120 89c3f030 00000000 00000000 nt!ExpWorkerThread+0xef
f78baddc 804ec781 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
nt!MmUnmapViewInSystemCache+322
804f4d86 3906            cmp     dword ptr [esi],eax
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt!MmUnmapViewInSystemCache+322
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
DEBUG_FLR_IMAGE_TIMESTAMP:  48a401b1
 
IMAGE_NAME:  memory_corruption
 
FAILURE_BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+322
 
BUCKET_ID:  0xA_nt!MmUnmapViewInSystemCache+322
 
Followup: MachineOwner
----------- BUG 4 ----------
BugCheck 24, {1902fe, aabaa6f4, aabaa3f0, 6a48689d}
 
Probably caused by : Ntfs.sys ( Ntfs!NtfsIsFatNameValid+69 )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 001902fe
Arg2: aabaa6f4
Arg3: aabaa3f0
Arg4: 6a48689d
 
Debugging Details:
------------------
 
 
EXCEPTION_RECORD:  aabaa6f4 -- (.exr 0xffffffffaabaa6f4)
ExceptionAddress: 6a48689d
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 6a48689d
Attempt to read from address 6a48689d
 
CONTEXT:  aabaa3f0 -- (.cxr 0xffffffffaabaa3f0)
eax=aabaa7d8 ebx=00000000 ecx=e22ef7a2 edx=0000000a esi=aaba000a edi=aabaa848
eip=6a48689d esp=aabaa7bc ebp=aabaa7fc iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
6a48689d ??              ???
Resetting default scope
 
CUSTOMER_CRASH_COUNT:  4
 
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
 
PROCESS_NAME:  uTorrent.exe
 
ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction   "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas  tre "%s".
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction   "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas  tre "%s".
 
EXCEPTION_PARAMETER1:  00000000
 
EXCEPTION_PARAMETER2:  6a48689d
 
READ_ADDRESS:  6a48689d  
 
FOLLOWUP_IP:  
Ntfs!NtfsIsFatNameValid+69
ba6bc822 85c0            test    eax,eax
 
FAILED_INSTRUCTION_ADDRESS:  
+6a48689d
6a48689d ??              ???
 
BUGCHECK_STR:  0x24
 
LAST_CONTROL_TRANSFER:  from ba6bc822 to 6a48689d
 
STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
aabaa7b8 ba6bc822 aabaa7d8 aabaa848 00000000 0x6a48689d
aabaa7fc ba6bcaa0 aabaa848 00000000 e22ef7a0 Ntfs!NtfsIsFatNameValid+0x69
aabaa86c ba6bcba2 88cb4488 e2682928 e2659648 Ntfs!NtfsAddNameToParent+0x9b
aabaa8b4 ba6c7d87 88cb4488 00000001 e2682928 Ntfs!NtfsAddLink+0x77
aabaaab8 ba6c7445 88cb4488 88dae328 88c8b008 Ntfs!NtfsSetRenameInfo+0xbb6
aabaab2c ba68d698 88cb4488 88c8b008 88c8b190 Ntfs!NtfsCommonSetInformation+0x3fb
aabaab94 804e13d9 89b68020 88c8b008 88c8b1b4 Ntfs!NtfsFsdSetInformation+0xa3
aabaaba4 ba7db7a7 88c8b008 000000a4 00000000 nt!IopfCallDriver+0x31
aabaac94 ba7dbf0e 89b6b768 88c8b008 88c8b198 sr!SrpSetRenameInfo+0x527
aabaacb0 804e13d9 89b6b768 88c8b008 00000000 sr!SrSetInformation+0x142
aabaacc0 80592306 aabaad64 0012f7c8 80582bbd nt!IopfCallDriver+0x31
aabaad48 804dd99f 000003e8 0012f83c 001c0f88 nt!NtSetInformationFile+0x523
aabaad48 7c91eb94 000003e8 0012f83c 001c0f88 nt!KiFastCallEntry+0xfc
0012f880 00000000 00000000 00000000 00000000 0x7c91eb94
 
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  Ntfs!NtfsIsFatNameValid+69
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: Ntfs
 
IMAGE_NAME:  Ntfs.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  45cc56a7
 
STACK_COMMAND:  .cxr 0xffffffffaabaa3f0 ; kb
 
FAILURE_BUCKET_ID:  0x24_BAD_IP_Ntfs!NtfsIsFatNameValid+69
 
BUCKET_ID:  0x24_BAD_IP_Ntfs!NtfsIsFatNameValid+69
 
Followup: MachineOwner
---------
 
à vos claviers mesdames et messieurs, qu'en pensez-vous ?
 
Merci à tous pour cette lecture, bonne soirée.

salut
a tu une carte son PCI ?

Salut,  
non interne, j'ai déjà test en la désactivant.

1.Test les ram (memtest86) puis le disque dur avec ubcd.iso
2. Si pas de problème, tenter de réparer XP (booter sur le cd, choisir installer puis réparer la partition).
3. Si toujours pareil, réinstaller XP.

on est en train de cerné le probleme, probablement la cle wifi usb installé recement (oct) donc il fait des test dans ce sens : ethernet
bon courage .

j'ai reinstall 4x windows, deja fait memtest