[Résolu] Écrans bleus code 0x1E - OS32bits vers OS64bits

[Invité Notpa]

Bonsoir JLD95,

Salut Tonton !

 

Puisqu'il y a eu plusieurs BSOD, pourquoi ne pas passer WhoCrashed ? Il peut donner plus d'infos sur la cause du problème.

 

"STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED" m'a l'air assez commun (lire la KB275678de chez MicroSoft). C'est pourquoi WhoCrached peut donner une piste.

 

D'accord, la KB275678 parle du noyau NT, mais si je ne dis pas de bêtises, Vista et Seven sont basés sur ce noyau. En tous cas, analyser les fichiers dumps peut aider à cerner le problème.

 

A votre service

 

Notpa01.

[JLD95]

Bonsoir Notpa01,

en fait j'utilise Bluescreenview: est-ce équivalent à WhoCrashed ?

[Invité Notpa]

Re JLD95,

 

Je ne connais pas Bleuescreenview, mais d'après les images/captures d'écrans que je vois, WhoCrached est plus complet. Il ne fournit pas un tableau mais une analyse du fichier dump. Voici un exemple de rapport de WhoCrashed :

 

computer name: DANIEL-PC

windows version: Windows 7 , 6.1, build: 7600

windows dir: C:\Windows

CPU: GenuineIntel Intel® Core™2 Duo CPU E4500 @ 2.20GHz Intel586, level: 6

2 logical processors, active mask: 3

RAM: 2952323072 total

VM: 2147352576, free: 2009919488

 

 

 

Crash Dump Analysis

 

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Sat 27/08/2011 08:29:24 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082711-36800-01.dmp

This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8C92C)

Bugcheck code: 0x116 (0xFFFFFFFF86A26008, 0xFFFFFFFF8FB298E0, 0x0, 0x2)

Error: VIDEO_TDR_ERROR

file path: C:\Windows\system32\drivers\dxgkrnl.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics Kernel

Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.

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.

Google query: dxgkrnl.sys Microsoft Corporation VIDEO_TDR_ERROR

 

 

A mon avis, bien plus précis que BleueScreenView. Non, je ne touche pas de royalties, mais ce logiciel me plait car il est clair (pour qui parle anglais !) et 'semble' assez complet. Je ne peux pas tester sur mes PCs car je n'ai pas de BSOD ! Et je n'ai pas envie d'en avoir !

 

De toutes façons, c'est complémentaire. Exécute-le (c'est un freeware) et colle dans ce sujet le résultat du logiciel d'analyse de dumps.

 

Merci et à bientôt

 

Notpa01

[Tonton]

Bonsoir JLD95 (salut Notpao1 ),

 

Je t'avais parlé de WhoCrashed de Resplendence ici : st-t188531-p1576800.html.

 

C'est effectivement une bonne variante à BlueScreenView de Nirsoft.

 

Bonne continuation,

Tonton

[JLD95]

Bonjour,

voici l'analyse de Whocrashed: je suis un peu déçu car il y a moins d'info qu'avec BlueScreenViewer:

 

 

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: PC3
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4293976064 total
VM: 2147352576, free: 1879674880



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 25/10/2011 15:08:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102511-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C83FC4, 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 Thu 20/10/2011 16:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-23088-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CD0FC4, 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 16/10/2011 07:44:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-21777-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C7EFC4, 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 Sat 15/10/2011 13:46:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CDAFC4, 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 09/10/2011 15:10:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-22744-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AE2028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 Sun 09/10/2011 15:10:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AE2028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 Sun 09/10/2011 15:09:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-23790-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004D6E028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 Sun 09/10/2011 02:53:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-22386-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AE7028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 08/10/2011 05:50:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100811-26535-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AEE028, 0xB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
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 30/09/2011 09:25:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-23478-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002ADFFC4, 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 Fri 30/09/2011 08:50:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-27627-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AC9FC4, 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 18/09/2011 07:52:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091811-17409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002ADDFC4, 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 Fri 16/09/2011 14:49:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091611-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x50 (0xFFFFF880089ECEC0, 0x0, 0xFFFFF80002ADCEDB, 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. 



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

13 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.

Modifié le 28 octobre 2011 par JLD95

[JLD95]

Il me reste à explorer la piste de l'overclocking: est-ce qu'un OC qui fonctionne bien sans aucun BSOD en 2 ans sous XP SP3 peut ne plus fonctionner en Win 7 64bits et générer des BSOD ?

 

 

j'ai une config à base de Q6600 2,4 overclocké à 3.2GHz (voir config dans mon profil) en laissant le SpeedStep activé qui fonctionne bien depuis 2 ans en XP SP3. Je viens d'installer Win 7 64bits à la place d'XP et de changer un HDD Caviar blue 650 Go pour un Caviar black 2To.

 

Le VID de mon Q6600 est de 1,2875V.

 

 

Mon overclocking qui donnait satisfaction en XP SP3:

 

Menu Ai Tweaker:
o	Ai Overclock Tuner : Manual
o	CPU Ratio Setting : 8
o	FSB Frequency : 400  MHz
o	DRAM Frequency: DDR2-801 MHz
o	CPU voltage : 1,3125 V
o	CPU Spread Spectrum : Disabled

 

Comme suggéré sur le site Forums Overclocking.net , je teste pour l'instant avec un incrément de tension de plus sur le VCore soit 1,31875V: j'attends 2 semaines pour savoir si les BSOD ont disparus.

 

Je voudrais tester sans SpeedStep mais a priori ce n'est pas accesible dans le menu du bios lorsque CPU ratio setting n'est pas sur Auto: j'ai essayé de le mettre sur Auto puis de désactiver le SpeedStep puis de remettre le CPU ratio à 8 mais sous Windows, CPU-Z continue de me montrer des fréquences de 2,4 à 3,2 GHz et une tension Vcore en x6 de 1,296V et en x8 de 1,304V

 

 

et pour la mémoire (j'ai l'impression que l'on peut gagner de la bande passante car le CAS4 n'est pas utilisé ?)

 

Modifié le 30 octobre 2011 par JLD95

[Invité Notpa]

Bonjour JLD95,

 

Je dois m'absenter une bonne heure. Je regarde ça après.

 

A+

 

Notpa01

[Invité Notpa]

Bonjour JLD95,

 

Tous les BSOD sont dus à ntoskrnl.exe. Je ne sais pas si l'overclocking sur Seven 64bit en est la cause : je ne connais rien en overclocking (on ne peut pas tout connaître !). A tout hasard, passe l'outil de réparation ntoskrnl.exe disponible sur RestaureGuard.

 

Si tu ne comprends pas l'anglais, la traduction est sur CCM.

 

A+

 

Notpa01

[JLD95]

Bonjour,

 

je pense que l'augmentation du Vcore du CPU a permis de résoudre mon problème de BSOD probablement dûs à des adressages 64bits erronés de temps à autre.

Auparavant, j'avais remarqué que mes softs photos Nikon étaient stables en mode compatibilité XP SP3 ce qui est logique car ça force l'adressage en 32bits.

Avec le Vcore augmenté, j'ai supprimé cette compatibilité XP SP3 et j'ai depuis plus de problèmes a priori.

Je laisse 2 semaines de stabilisation avant de conclure sur la solution.

[Invité Notpa]

Salut JLD95,

 

OK. Bonne piste. On va donc attendre... en croisant les doigts !

 

A+

 

Notpa01