Résolu J'ai des BDOS en sortie de veille prolongée, comment les réparer ?

Statut
N'est pas ouverte pour d'autres réponses.

MisTer_Freyss

Membre
Inscription
19 Août 2013
Messages
211
Réactions
18
Points
2 436
RGCoins
25
Bonjour,
Comme dit dans le titre j'ai des bdos en sortie de veille prolonger et je ne sait pas comment reparer ceci !
J'ai besoin d'aide merci d'avance ! :)
 

Rivals

Ancien staff
Inscription
27 Août 2016
Messages
1 706
Réactions
898
Points
13 164
RGCoins
201
J'ai édité http://reality-gaming.fr/attachments/edition-png.20322/ le titre de ta discussion pour que celle-ci soit plus compréhensible.

A l'avenir essaie de faire des titres plus longs et détaillés, plus le titre est long et détaillé, plus tu obtiendras de vues http://reality-gaming.fr/attachments/vues-png.20315/ ainsi que des réponses http://reality-gaming.fr/attachments/reponses-png.20332/. :tchuss:
 

MisTer_Freyss

Membre
Inscription
19 Août 2013
Messages
211
Réactions
18
Points
2 436
RGCoins
25
J'ai édité http://reality-gaming.fr/attachments/edition-png.20322/ le titre de ta discussion pour que celle-ci soit plus compréhensible.

A l'avenir essaie de faire des titres plus longs et détaillés, plus le titre est long et détaillé, plus tu obtiendras de vues http://reality-gaming.fr/attachments/vues-png.20315/ ainsi que des réponses http://reality-gaming.fr/attachments/reponses-png.20332/. :tchuss:
Merci
 

MisTer_Freyss

Membre
Inscription
19 Août 2013
Messages
211
Réactions
18
Points
2 436
RGCoins
25
Ouais si tu veux ;)
On Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100714-18127-01.dmp
This was probably caused by the following module: (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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 Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
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 Sun 05/10/2014 17:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100514-34538-01.dmp
This was probably caused by the following module: (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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.


Voila et j'en est un autre qui n'apparait pas mais il est causer par l'usb 3.0 mais j'arrive pas a trouver de solution !!!
 

flodes80

Membre
Inscription
24 Février 2012
Messages
2 516
Réactions
451
Points
10 326
RGCoins
0
On Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100714-18127-01.dmp
This was probably caused by the following module: (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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 Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
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 Sun 05/10/2014 17:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100514-34538-01.dmp
This was probably caused by the following module: (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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.


Voila et j'en est un autre qui n'apparait pas mais il est causer par l'usb 3.0 mais j'arrive pas a trouver de solution !!!
Met à jours tes drivers je crois que c'est ça ;)
 

titi-killer57

Premium
Inscription
20 Janvier 2013
Messages
1 750
Réactions
414
Points
10 101
RGCoins
0
On Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100714-18127-01.dmp
This was probably caused by the following module: (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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 Tue 07/10/2014 18:15:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003286AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
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 Sun 05/10/2014 17:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100514-34538-01.dmp
This was probably caused by the following module: (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
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.


Voila et j'en est un autre qui n'apparait pas mais il est causer par l'usb 3.0 mais j'arrive pas a trouver de solution !!!

Salut essaye de mettre tes drivers a jours avec le site :
 
Dernière édition:

flodes80

Membre
Inscription
24 Février 2012
Messages
2 516
Réactions
451
Points
10 326
RGCoins
0
mes drivers sont tous deja a jour !!
Bah à mon avis essayes de les désinstaller un par un puis de les réinstaller ou de réinstaller windows carrèment si c'est trop génant
 
Cette réponse a aidé l'auteur de cette discussion !
D

delete221380

Salut,

J'ai déplacé http://reality-gaming.fr/attachments/deplacement-png.20319/ ta discussion en section "Résolu" http://reality-gaming.fr/attachments/verifier-png.20313/

Cordialement.
 
Statut
N'est pas ouverte pour d'autres réponses.
Haut