MAJ 3.03

Chez Nirsoft, l'application BlueScreenView a les mêmes fonctions d'affichage de la cause du crash... et il peut être mis en français.

Pour ceux que ça intéresserait, voilà le lien.

Bonjour à tous, Je rencontre un problème depuis la mise à jour de Windows 10, souvent des écrans bleus apparaissent, sans demande mon avis, avec ce message d'erreur présent dans le titre de ma demande. Il est fâcheux de voir son ordi planter lorsqu'on est en plein travaux ... Auriez-vous une solution ? Mercii beaucoup.

Voici le rapport ! Merci beaucoup :) Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Thu 12/11/2015 08:54:49 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\111215-33875-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0) Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x824, 0xFCC2C3F690, 0xFFFFD0002595F000) Error: FAULTY_HARDWARE_CORRUPTED_PAGE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error. This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 12/11/2015 08:54:49 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: 0x12B (0xFFFFFFFFC00002C4, 0x824, 0xFCC2C3F690, 0xFFFFD0002595F000) Error: FAULTY_HARDWARE_CORRUPTED_PAGE Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error. This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 12/11/2015 05:06:40 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\111215-65687-01.dmp This was probably caused by the following module: hal.dll (hal+0x1B01) Bugcheck code: 0xC2 (0x7, 0x1254, 0x4160004, 0xFFFFE000CE71DD40) Error: BAD_POOL_CALLER file path: C:\WINDOWS\system32\hal.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL Bug check description: This indicates that the current thread is making a bad pool request. 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 that cannot be identified at this time.

Ça ressemble à un pilote (son, graphique, réseau) qui se plante. Les drivers installés par Windows 10 sont parfois inadaptés. Il faut rechercher quel pilote est en cause et ensuite télécharger le pilote fourni par le constructeur du périphérique en cause.

La version en téléchargement sur Resplendence porte le numéro 6.50 , je pense qu'il s'agit d'une erreur de mise à jour du site car disposant encore de cette version 6.50, la taille du fichier n'est pas la même 6.50 = 8873ko 6.60 = 8861ko On constate que la version 6.60 est un poil plus légère