Alors depuis le dépanneur à changé les barrettes, la carte mère et l'alimentation, j'ai des écrans bleus au bout de 2 heures si Windows est en pause alors que quand je joue depuis le matin par exemple il y a aucun problème. Les écrans bleus arrivent seulement quand Windows est en pause, voici les BSOD depuis whocrashed :
Code : Tout sélectionner
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 18/06/2016 00:01:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061716-47625-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x40, 0x2, 0x0, 0xFFFFF802754C8E3E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 18/06/2016 00:01:43 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: 0xA (0x40, 0x2, 0x0, 0xFFFFF802754C8E3E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Wed 15/06/2016 02:30:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061416-19140-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF680002E9878, 0xDBE000009BD52867, 0xFFFFE0015B69D510)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
On Wed 15/06/2016 00:33:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061416-13312-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800FECEB63F, 0xFFFFD0005ACB8770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Tue 14/06/2016 00:30:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061316-38078-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip!TcpTlConnectionSend+0x76)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803E8133F2D, 0xFFFFD001575898D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 Mon 13/06/2016 23:40:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061316-25578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFFA800605C298, 0x8000000000900121, 0xFFFFD0013DE93F70, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 12/06/2016 01:55:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061116-20796-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x8C9, 0x236029A8DB0, 0xFFFFD001EB73D000)
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 Sun 12/06/2016 01:13:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061116-40875-01.dmp
This was probably caused by the following module: pxhlpa64.sys (PxHlpa64+0x34D5)
Bugcheck code: 0xA (0x151, 0x2, 0x1, 0xFFFFF800F2532FFF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\pxhlpa64.sys
product: PxHelp64
company: Sonic Solutions
description: Px Engine Device Driver for 64-bit Windows
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.
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: pxhlpa64.sys (Px Engine Device Driver for 64-bit Windows, Sonic Solutions).
Google query: Sonic Solutions IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
pxhlpa64.sys (Px Engine Device Driver for 64-bit Windows, Sonic Solutions)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
,oui j'avais windows 10 avant le changement de matériel.