lut, merci de ton aide
d'origine la 4coredual sata 2 accepte 2 x 1mo de mémoire
avec mise a jour 2.10 elle accepte 2 x2 mais seulement 3,3 sont exploitable
je ne trouve pas de CG sur site zalman compatible pour mon vf1000 en pci e, vu le silence ca me ferais mal de retrouver de nouveau un airbus dans ma tour ^^
pour les codes desole y'en a une tartine
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E6300 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488931840 total
VM: 2147352576, free: 1866412032
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 08/01/2012 12:56:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-13687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028AAA4F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/01/2012 12:56:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800028AAA4F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/01/2012 12:31:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-14593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/01/2012 12:30:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-22906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF5, 0x0, 0xFFFFF80002BA83ED, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/01/2012 11:40:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-13156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4E (0x9A, 0x8593D, 0x2, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/01/2012 11:15:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010812-15031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FBC6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800028DEBC6, 0xFFFFF88002FFF848, 0xFFFFF88002FFF0B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 19:33:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-21953-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002FAB1C8, 0xFFFFF88002FAAA30, 0xFFFFF88001250A38)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 07/01/2012 19:02:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-21296-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88001E3C4E8, 0xFFFFF88001E3BD50, 0x40170289C874)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 07/01/2012 18:10:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-12843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800000A560, 0x3C8000001CA90867, 0xFF00F6800000C16A)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 16:36:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-16484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001822380, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 15:59:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-15718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x4E (0x99, 0x33E81, 0x5, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 15:51:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-17296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x1A (0x61940, 0xFFFFF98035F12000, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 11:25:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-31812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 11:22:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-26062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002A06BE0, 0x54004E00000008, 0xFFFFF80002A06BE0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/01/2012 07:54:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-18390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x1ABCFF96, 0x2, 0x1, 0xFFFFF8000287D4D8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
20 crash dumps have been found and analyzed. Only 15 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
3 fois que je le re formate via pc de ma femme , car et étrangement il refuse de booter sur dvd pour tant dans bios c'est comme il faut
il lance le cd mais juste avant le choix de la langue cela s'arrête et repart direct dur le dd
a la dernière prise de tête me suis dit vais refaire seven et installer les mise a jour avant tout autre programme, bah même là ai des bsod
impossible visiblement de "charger" du lourd pourtant ni le proc ni les ram ne sont exploité a fond
Message édité par rey95 le 10-01-2012 à 19:53:39
FORUM Aideonline
![[:warmachine]](/static/images/perso/warmachine.gif "[:warmachine]")
••• ![[:wildfire:6]](/static/images/perso/6/wildfire.gif "[:wildfire:6]")
Amateur de Thinkpads 
•••
