silix
Nouveau membre
Bonjour,
Je rencontre depuis l'acquisition de ma nouvelle machine un petit "pour ne pas dire gros..." soucis d'écran qui se fige et ou l'ordinateur devient totalement inutilisable et ne répond plus du tout...
Ma config n'a qu'un mois, et ne se fige qu'en jeux, notamment sur BF1 "ultra" ou encore H1Z1 "Low avec une résolution 2103x1183... (dsr)"
voici ma config
Je n'ai pas l'impression que l'ordinateur chauffe plus que ça, mis à part la CG qui est bien sollicitée en jeux...
voici un exemple de BSOD :
On Wed 22/02/2017 23:00:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\022217-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFF802341B4288, 0xD, 0x0, 0xFFFFF802674E9B78)
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 Wed 22/02/2017 23:00:14 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x245)
Bugcheck code: 0xA (0xFFFFF802341B4288, 0xD, 0x0, 0xFFFFF802674E9B78)
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.
Par avance, merci de l'aide que vous pourriez m'apporter...
Je rencontre depuis l'acquisition de ma nouvelle machine un petit "pour ne pas dire gros..." soucis d'écran qui se fige et ou l'ordinateur devient totalement inutilisable et ne répond plus du tout...
Ma config n'a qu'un mois, et ne se fige qu'en jeux, notamment sur BF1 "ultra" ou encore H1Z1 "Low avec une résolution 2103x1183... (dsr)"
voici ma config
Vous devez être connecté pour voir les liens.
Je n'ai pas l'impression que l'ordinateur chauffe plus que ça, mis à part la CG qui est bien sollicitée en jeux...
voici un exemple de BSOD :
On Wed 22/02/2017 23:00:14 your computer crashed
crash dump file: C:\WINDOWS\Minidump\022217-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFF802341B4288, 0xD, 0x0, 0xFFFFF802674E9B78)
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 Wed 22/02/2017 23:00:14 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x245)
Bugcheck code: 0xA (0xFFFFF802341B4288, 0xD, 0x0, 0xFFFFF802674E9B78)
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.
Par avance, merci de l'aide que vous pourriez m'apporter...