reboot bluescreen

Image Aide et Dépannage (Installation, fonctionnement, problèmes rencontrés avec le système)
Règles du forum
Règlement de fonctionnement du forum
ImagePour les demandes de dépannage Windows 8, merci de préciser si vous utilisez Windows 8 ou Windows 8.1

reboot bluescreen

Messagede syroco » 12 Sep 2013 15:14

Bonjour a tous

je me présente David ,38 ans et j'habite en Ardennes.

J'ai un problème récurent que je n'arrive pas à résoudre et dont j'aurai besoin de vos lanternes.

je possède un pc Acer x1301 4G de mémoire ,disque de 500G ,Amd athlon II X2 250 PROCESSOR 250 3.00GHZ

C'est un pc que j'ai récupéré et qui ne cesse de me faire des reboots en écran bleu ,j'ai essaye de mettre un autre windows 7 (pro ) que celui livré avec la machine (windows familliale)pensant que celui ci était défectueux mais cela reste un échec les bluesceens sont revenus de plus belle malgré un mise a jour des derniers pilotes via le logiciel de tous les drivers.com (ma config).

Je suis donc revenue sur une install avec le Windows livré avec la machine après formatage en paramètre usine suivit de toutes les mises a jour windows adapte et j'ai deja eu 2 bluescreens dont voici quelque infos

rapport whocrashed:

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 12/09/2013 04:22:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091213-22620-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x2, 0xD, 0x1, 0xFFFFF80002C8F66F)
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 that cannot be identified at this time.



On Thu 12/09/2013 04:22:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0xA (0x2, 0xD, 0x1, 0xFFFFF80002C8F66F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 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.



On Mon 09/09/2013 14:49:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-25958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005F19630, 0xFFFFF8800C60DEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.




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

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.

rapport bluescreenview

Image[/URL][/img]

En espérant que vous pourrez m'aider ,je vous remercie par avance
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede maxou45 » 12 Sep 2013 18:04

Bonjour et bienvenue parmi nous.
Image


Tu peux lire le règlement de ce forum ICI


C'est typiquement un soucis "matériel", et non pas "driver" ou installation de windows, puisque tu as essayé avec plusieurs systèmes.


Fait ceci:
  • Télécharger Image GSI de Kaspersky (de XP à Seven): et l'enregistrer sur le bureau.
  • Double-cliquer sur GetSystemInfo puis cliquer sur I agree pour accepter la "licence agreement."
  • Cliquer sur Create Report et laisser l'outil travailler. Patienter le temps nécessaire.
  • L'outil va alors envoyer le rapport et ouvrir une page Web où un lien apparaîtra.


    Image
  • Copier le lien par clic droit/Tout sélectionner/copier.
  • Le coller dans la réponse sur le forum.
Helper-diplômé de Image

La vitesse de la lumière étant supérieure à la vitesse du son, bien des gens paraissent brillants jusqu'au moment où ils ouvrent la bouche
Avatar de l’utilisateur
maxou45
Admininistrateur
Admininistrateur
 
Années en tant que membreAnnées en tant que membre
 
Messages: 16022
Âge: 61
Inscription: 11 Nov 2011 20:42
Localisation: France - Loiret
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows 8 64 bits Windows 8 64 bits
Résolution d’écran: 1600 x 900 1600 x 900

reboot bluescreen

Messagede syroco » 12 Sep 2013 18:27

Bonsoir et merci maxou45

Voici le lien/rapport

http://www.getsysteminfo.com/read.php?f ... 54b8d33da8
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede maxou45 » 12 Sep 2013 18:34

La seule erreur, mais qui revient des dizaines de fois est celle ci
Product: Google Update Helper -- Error 1316. A network error occurred while attempting to read from the file: C:\Program Files (x86)\Google\Update\1.3.21.153\SoftwareUpdateHelper.msi

Mais je ne pense pas que ceci soit la cause de tes bsod

Neanmois reinstalle chrome
Helper-diplômé de Image

La vitesse de la lumière étant supérieure à la vitesse du son, bien des gens paraissent brillants jusqu'au moment où ils ouvrent la bouche
Avatar de l’utilisateur
maxou45
Admininistrateur
Admininistrateur
 
Années en tant que membreAnnées en tant que membre
 
Messages: 16022
Âge: 61
Inscription: 11 Nov 2011 20:42
Localisation: France - Loiret
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows 8 64 bits Windows 8 64 bits
Résolution d’écran: 1600 x 900 1600 x 900

reboot bluescreen

Messagede syroco » 12 Sep 2013 19:26

Merci

je viens de desinstaller /reinstaller chrome

donc je suis actuellement avec uniquement Windows 7 familiale livré avec la machine avec les mise Windows update faite,pack office 2010 installé, imprimante et Avast

Je vais tourné un peu comme ça voir si les bsods apparaissent toujours avant d'effectuer les mises a jours drivers

encore merci ,je reviens vers vous vous informer de l’évolution de la chose.
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede maxou45 » 12 Sep 2013 19:31

OK, je laisse ce sujet ouvert
a+
Helper-diplômé de Image

La vitesse de la lumière étant supérieure à la vitesse du son, bien des gens paraissent brillants jusqu'au moment où ils ouvrent la bouche
Avatar de l’utilisateur
maxou45
Admininistrateur
Admininistrateur
 
Années en tant que membreAnnées en tant que membre
 
Messages: 16022
Âge: 61
Inscription: 11 Nov 2011 20:42
Localisation: France - Loiret
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows 8 64 bits Windows 8 64 bits
Résolution d’écran: 1600 x 900 1600 x 900

reboot bluescreen

Messagede syroco » 14 Sep 2013 13:16

Bonjour a tous

Bon après 48 h de répit c'est repartie(erreur.sys pas eu le temps de la noter)

rapport get:

http://www.getsysteminfo.com/read.php?f ... ff417d303c

Rapport bluecreenview

Image

c'est étonnant que ça fonctionne bien quelque temps puis que ce reboot de façon aléatoire ainsi

Merci en attendant vos réponses
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede maxou45 » 14 Sep 2013 13:23

L'erreur est celle ci
Le chargement du pilote \Driver\WUDFRd a échoué pour le périphérique WpdBusEnumRoot\UMB\2&37c186b&1&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.01#7&2C5E86A3&0&058F63636476&0#.

Ce driver est celui des USB
remet les drivers usb a jour
Helper-diplômé de Image

La vitesse de la lumière étant supérieure à la vitesse du son, bien des gens paraissent brillants jusqu'au moment où ils ouvrent la bouche
Avatar de l’utilisateur
maxou45
Admininistrateur
Admininistrateur
 
Années en tant que membreAnnées en tant que membre
 
Messages: 16022
Âge: 61
Inscription: 11 Nov 2011 20:42
Localisation: France - Loiret
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows 8 64 bits Windows 8 64 bits
Résolution d’écran: 1600 x 900 1600 x 900

reboot bluescreen

Messagede syroco » 14 Sep 2013 13:45

Bonjour maxou

je viens dans le panneau de config de faire Click droit sur chacun des ports USB ,pour Windows j'ai les mises a jour correctement effectuer ...

J'ai donc réinstaller ma config, le logiciel de tous les drivers.com,l'analyse me ressort ceci

Image

je suppose que je dois installer un des pilotes des contrôleurs de stockage mais lequel pour une carte GeForce 9200 integrer ,le pilote 15.56 ne parait le plus approprier.
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede maxou45 » 14 Sep 2013 13:50

Je te signale, que tous les drivers que ça te présente en téléchargement sont plus récents que ceux installés sur ton PC, il te faut tous les mettre à jour, pas seulement ceux de tes stockages usb...

Par exemple tes drivers de stockage Nvidia, tu as déjà pas mal de versions de retard ...
Helper-diplômé de Image

La vitesse de la lumière étant supérieure à la vitesse du son, bien des gens paraissent brillants jusqu'au moment où ils ouvrent la bouche
Avatar de l’utilisateur
maxou45
Admininistrateur
Admininistrateur
 
Années en tant que membreAnnées en tant que membre
 
Messages: 16022
Âge: 61
Inscription: 11 Nov 2011 20:42
Localisation: France - Loiret
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows 8 64 bits Windows 8 64 bits
Résolution d’écran: 1600 x 900 1600 x 900

reboot bluescreen

Messagede syroco » 14 Sep 2013 14:09

ok je réinstalle tous ce qui m'ai proposé ,mais je voulais pas allez trop vite en installant que le minimum pour voir si parfois ,ce n'était une mise a jour la cause de mon soucis

c'est partie pour les mise a jour ,je tiens au courant

merci maxou45
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 29.0.154 Google Chrome 29.0.154
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede syroco » 03 Oct 2013 19:51

Bonjour,

Me voici de retour ,j'ai du m’absenter pour le travail ,mais mes problème ne sont pas réglés pour autant.

Toutes les mises a jour ont été effectuées, et voici tout les écrans blue qui sont apparut pendant mon abscence

Image


rapport whoscrashed
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 03/10/2013 17:10:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-15865-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
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 that cannot be identified at this time.



On Thu 03/10/2013 17:10:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 that cannot be identified at this time.



On Mon 30/09/2013 19:04:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-14352-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002CD20DF)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 30/09/2013 18:54:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-18220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFF86E02C920EA, 0x8, 0xFFFFF86E02C920EA, 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 that cannot be identified at this time.



On Sat 28/09/2013 19:17:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-15319-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x88CEF963, 0x2, 0x1, 0xFFFFF80002C95E14)
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 that cannot be identified at this time.



On Sat 28/09/2013 19:16:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-14414-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1E1956)
Bugcheck code: 0xD1 (0x5, 0x2, 0x1, 0xFFFFF8800432CDCC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 326.98
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 326.98
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 326.98 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 24/09/2013 17:21:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092413-17097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80049807DF, 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 that cannot be identified at this time.



On Sat 21/09/2013 08:08:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092113-19983-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1440B1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001940B1, 0xFFFFF8800E9C50F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Thu 19/09/2013 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-19484-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x7644B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600007644B, 0xFFFFF8800D9BA0A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Sun 15/09/2013 21:14:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-19593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x2, 0xD, 0x1, 0xFFFFF80002C8066F)
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 that cannot be identified at this time.



On Sun 15/09/2013 14:09:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-27159-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A5E6348, 0xFFFFF8800A5E5BA0, 0xFFFFF80002C4C293)
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 that cannot be identified at this time.



On Sun 15/09/2013 14:06:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091513-27752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002C8509B, 0xFFFFF8800DB6A7F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.



On Sat 14/09/2013 11:01:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091413-29140-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88007D89855)
Bugcheck code: 0x50 (0xFFFFFA8064899C30, 0x0, 0xFFFFF88007D89855, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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.



On Thu 12/09/2013 04:22:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091213-22620-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x2, 0xD, 0x1, 0xFFFFF80002C8F66F)
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 that cannot be identified at this time.



On Mon 09/09/2013 14:49:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-25958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005F19630, 0xFFFFF8800C60DEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.




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

15 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 326.98 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 30.0.159 Google Chrome 30.0.159
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

reboot bluescreen

Messagede syroco » 03 Oct 2013 19:55

Je met le lien du rapport getsysteminfos



http://www.getsysteminfo.com/read.php?f ... 069f024d05

merci de votre aide
syroco
Nouveau membre
Nouveau membre
 
Messages: 11
Inscription: 12 Sep 2013 14:56
Sexe: Homme
Google Chrome 30.0.159 Google Chrome 30.0.159
Windows Seven 64 bits Windows Seven 64 bits
Résolution d’écran: 1920 x 1080 1920 x 1080

Suivante

Retourner vers Système

Qui est en ligne

Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 11 invités