Bonjour à tous,
ça va faire 7 mois que je poste tous les 2 mois en espérant avoir de l'aide mais en vain.
je vous informe que mon anti-virus est à jour, que Hijack ne présente aucune anomalie, que je n'ai aucun Spy etc....
Le problème est système ou matériel.
Que le pc soit en IDLE ou quoi que ce soit d'autre, le PC se fige et je dois redemarrer manuellement. Cela peut se produire toutes les 30 minutes.
Je n'ai aucun élément qui chauffe trop ! L'alim marche bien.
Après 2 mois de tests, changement de RAM, de Disque system, de multiples formatages, de Carte graphique, j'ai décidé de changer ma carte mère.
Je n'ai eu aucun problème pendant 2 semaines, et là, les bugs sont de retour.
Je précise qu'avant l'écran bleu s'affichait, maintenant le pc se fige juste sans annoncer l'écran bleu.
Il m'arrive que des fois au boot il me dise qu'il manque un .dll ou qu'il est défectueux, je débranche la prise de l'alim quelques secondes, je la rebranche et ça boot par miracle.
1)
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {780, c035aa80, 812e99d8, ef914cda}
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+3e2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00000780, The PTEs mapping the argument system cache view have been
corrupted.
Arg2: c035aa80
Arg3: 812e99d8
Arg4: ef914cda
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_780
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 80527ebc to 805373aa
STACK_TEXT:
f78bec18 80527ebc 0000001a 00000780 c035aa80 nt!KeBugCheckEx+0x1b
f78bec68 8056fb5a d6aa0000 88bb0970 00000000 nt!MmUnmapViewInSystemCache+0x3e2
f78bec80 804f4638 89bef448 89780ed0 00000000 nt!CcUnmapVacb+0x2a
f78becb0 804f4b44 00000000 00000000 89780f34 nt!CcUnmapVacbArray+0xe5
f78beccc 804f4ab6 89780ed0 806ffa4c 89780ed0 nt!CcUnmapAndPurge+0x20
f78becfc 804ed808 00000001 8055e690 896cd688 nt!CcDeleteSharedCacheMap+0xc5
f78bed34 804e67c8 89bfc098 805694c0 89bfc830 nt!CcWriteBehind+0x357
f78bed7c 804e23b5 89bfc098 00000000 89bfc830 nt!CcWorkerThread+0x12f
f78bedac 80574120 89bfc098 00000000 00000000 nt!ExpWorkerThread+0xef
f78beddc 804ec781 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmUnmapViewInSystemCache+3e2
80527ebc 008bcee8e8a0 add byte ptr [ebx-5F171732h],cl
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmUnmapViewInSystemCache+3e2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a401b1
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_780_nt!MmUnmapViewInSystemCache+3e2
BUCKET_ID: 0x1a_780_nt!MmUnmapViewInSystemCache+3e2
Followup: MachineOwner
2)
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00000781, The PTEs mapping the argument system cache view have been
corrupted.
Arg2: c035aa80
Arg3: 00000000
Arg4: e3eabc80
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_781
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 80527ebc to 805373aa
STACK_TEXT:
f78bac18 80527ebc 0000001a 00000781 c035aa80 nt!KeBugCheckEx+0x1b
f78bac68 8056fb5a d6aa0000 88b08340 00000000 nt!MmUnmapViewInSystemCache+0x3e2
f78bac80 804f4638 89be86c8 88b9c0a8 00000000 nt!CcUnmapVacb+0x2a
f78bacb0 804f4b44 00000000 00000000 88b9c10c nt!CcUnmapVacbArray+0xe5
f78baccc 804f4ab6 88b9c0a8 806ffa4c 88b9c0a8 nt!CcUnmapAndPurge+0x20
f78bacfc 804ed808 00000001 8055e690 893cd0d8 nt!CcDeleteSharedCacheMap+0xc5
f78bad34 804e67c8 89c22080 805694c0 89bfcd20 nt!CcWriteBehind+0x357
f78bad7c 804e23b5 89c22080 00000000 89bfcd20 nt!CcWorkerThread+0x12f
f78badac 80574120 89c22080 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+3e2
80527ebc 008bcee8e8a0 add byte ptr [ebx-5F171732h],cl
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MmUnmapViewInSystemCache+3e2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a401b1
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_781_nt!MmUnmapViewInSystemCache+3e2
BUCKET_ID: 0x1a_781_nt!MmUnmapViewInSystemCache+3e2
Followup: MachineOwner
---------
3)
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {ffaeb0c8, 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: ffaeb0c8, 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: ffaeb0c8
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:
f78bac68 8056fb5a d7ae0000 88a50818 00000000 nt!MmUnmapViewInSystemCache+0x322
f78bac80 804f4638 89bf00d8 890fb8e0 00000000 nt!CcUnmapVacb+0x2a
f78bacb0 804f4b44 00000000 00000000 890fb944 nt!CcUnmapVacbArray+0xe5
f78baccc 804f4ab6 890fb8e0 806ffa4c 890fb8e0 nt!CcUnmapAndPurge+0x20
f78bacfc 804ed808 00000001 8055e690 8946fa88 nt!CcDeleteSharedCacheMap+0xc5
f78bad34 804e67c8 89c22080 805694c0 89bfcd20 nt!CcWriteBehind+0x357
f78bad7c 804e23b5 89c22080 00000000 89bfcd20 nt!CcWorkerThread+0x12f
f78badac 80574120 89c22080 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
---------
Voilà des exemples de bugs, les mêmes qu'avec mon ancienne Carte mère, qui est le même modèle.
Si vous avez une idée, franchement, je la prend avec grand plaisir !
Merci beaucoup et bon dimanche !
MSI P35 Platinum
C2D E6750
Alim Corsair 520W
CG : Ati radeon x1950xtx
ram : 2x1Go PC28500
FORUM HardWare.fr
