Page 1 sur 1
Pc qui plante au lancement d 'un media
Posté : dim. 13 déc. 2015 19:55
par circus929
Bonsoir, bonsoir.
Je me retrouve face a un problème récurent que je n'arrive pas a résoudre. A partir du moment ou je lance un média ou une application gourmande en ressource je me retrouve face a divers BSOD avec toujours une raison variable.
Je pense que cela doit venir des driver. J'ai été contraint de télécharger un nouveau Windows 10 car j'ai perdu les licences dans un déménagement.
Et des que j'ai à utilisé les ressources audio ou vidéo le pc se freeze, BSOD et redémarre voir s’éteint.
Pour ma config:
http://www.partage-facile.com/AUGWN6...ig_pc.pdf.html
et pour le sfc /scannow:
http://www.partage-facile.com/QP9TZANE0N/cbs.log.html
Si quelqu'un pouvait m'aider à éclaircir et résoudre se problème se serait vraiment sympathique.
Vu que je fais beaucoup de musique avec mon Pc c'est très gênant.
Merci d'avance =)
Re: Pc qui plante au lancement d 'un media
Posté : dim. 13 déc. 2015 19:55
par circus929
Rapport WhoCrashed:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 13/12/2015 13:47:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121315-21609-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 that cannot be identified at this time.
On Sun 13/12/2015 13:47:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalpTimerClockIpiRoutine+0x15)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 that cannot be identified at this time.
On Sat 12/12/2015 18:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121215-52984-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0x0, 0xFFFFE000355A5630, 0x2, 0xFFFFFFFFFFFFFE00)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.