Bonjour à vous, j'ai un problème avec mon PC, lorsque j'installe win 7 ultimate ou vista en 64 bits, après l'installation et pendant le téléchargement des premiers mise à jour sur windows update, j'ai toujours des blue sceen qui apparaient, et le monsieur est pas mal tannée là !! J'ai downloader le programme et j'ai fais un copier-coller sur le rapport. Donc vou allez voir les infos sur mon PC ainsi que les screen blue. Je l'ai essayer en 32 bits et je n'ai eu aucun problème et pourtant il est compatible en 64 bits. Ce PC bien je l'ai acheter en mai 2011 (Neuf) mais le OS n'était pas installer et le vendeur a déclarer faillite; (Pas de chance pour moi).Alors je l'ai installer en 64 bits mais sans succès, par la suite je me suis résigner a le fair fonctionner en 32 bits et tout allait très bien, sauf, qu'en 32 bits je perds 8 g sur 12 de mémoire (RAM) DDR3. Alors ce matin, je me suis réessayer en le formatant et le remettre en 64 bits, mais toujours avec le même problème.... A l'aide quelqu' un ????? Voici le rapport WHO CRASHED et malheureusement il est en anglais, mais bon.
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit http://www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: JACKLUCE01
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12882894848 total
VM: 2147352576, free: 1980936192[/b][/color]
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 2011-10-28 23:27:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012610-16859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xD1 (0xFB, 0x2, 0x0, 0xFFFFF88001660505)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Fri 2011-10-28 23:27:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5D505)
Bugcheck code: 0xD1 (0xFB, 0x2, 0x0, 0xFFFFF88001660505)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Fri 2011-10-28 23:24:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-16765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xD1 (0xFFFFF88023361EF8, 0x2, 0x0, 0xFFFFF8800165F516)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Fri 2011-10-28 22:43:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-19109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xD1 (0x1D, 0x2, 0x0, 0xFFFFF88001642516)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Fri 2011-10-28 21:58:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-29265-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x36504)
Bugcheck code: 0xD1 (0x1000, 0x2, 0x1, 0xFFFFF88001638504)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Fri 2011-10-28 21:11:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-28640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xD1 (0xFFFFF880233770C8, 0x2, 0x0, 0xFFFFF8800165F516)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Fri 2011-10-28 19:49:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-26140-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x17504)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88001619504, 0xFFFFF88003361938, 0xFFFFF88003361190)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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 Fri 2011-10-28 18:46:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-17062-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x62507)
Bugcheck code: 0xD1 (0xFFFFF8802BCA89A0, 0x2, 0x1, 0xFFFFF88001662507)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Fri 2011-10-28 18:38:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-22843-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x2D525)
Bugcheck code: 0xD1 (0xFFFFFA80550ACD6C, 0x2, 0x1, 0xFFFFF88001630525)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Fri 2011-10-28 16:28:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-26890-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x57515)
Bugcheck code: 0xD1 (0xFFFFFA8052C0DFAC, 0x2, 0x1, 0xFFFFF88001659515)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 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 Fri 2011-10-28 16:04:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-25880-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFFFF90909090, 0x0, 0xFFFFF8800184051D, 0x5)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed.
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.
Blue Screen seulement avec win 7 en 64 bits ?
-
mecano8701
- Messages : 1
- Enregistré le : sam. 29 oct. 2011 02:17
- Etes vous un robot ? : Non
Re: Blue Screen seulement avec win 7 en 64 bits ?
Bonjour
Es-tu sûr de la compatibilité des barrettes mémoire avec ta carte-mère ?
Avec Memtest
Voir sur ce site
Il faut graver un CD ou l'installer sur une clé USB bootable et démarrer sur ce médium pour lancer l'analyse.
Un cycle dure environ 15 à 25 minutes avec une machine assez récente.
Il ne faut pas d'erreur dans le cadre en bas à droite.
@+
Es-tu sûr de la compatibilité des barrettes mémoire avec ta carte-mère ?
Avec Memtest
Voir sur ce site
Il faut graver un CD ou l'installer sur une clé USB bootable et démarrer sur ce médium pour lancer l'analyse.
Un cycle dure environ 15 à 25 minutes avec une machine assez récente.
Il ne faut pas d'erreur dans le cadre en bas à droite.@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Re: Blue Screen seulement avec win 7 en 64 bits ?
Bonjour a vous 2,
Après le test des mémoires, tu regarderas de plus pret le driver de ta carte réseaux qui a mon avis te provoque des plantages en faisant des tentatives d’accès a des zones mémoires qui lui sont interdite.
"description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high."
A+
Après le test des mémoires, tu regarderas de plus pret le driver de ta carte réseaux qui a mon avis te provoque des plantages en faisant des tentatives d’accès a des zones mémoires qui lui sont interdite.
"description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high."
A+
