Bonjour,
J'ai eu un MSI GT70 2PE neuf y'a quelque jours, et depuis le premier jous, j'ai des BSOD, meme apres avoir re installé windows 8 au propre, et avoir mis a jours les drivers ect.
qui pour m'aider ? car j'ai tout tester, verification du disque dur ect, quand je joue un jeu le pc ne bug pas meme apres plusieurs heure, et quand je suis sur le bureau ou sur mozilla au bou d'un moment y'a un bsod
Merci
Voici :
On Sat 05/07/2014 10:14:09
GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070514-16625-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xDA
(0x504, 0xFFFFF6FC400CFEB0, 0x0, 0x19FD6)
Error: SYSTEM_PTE_MISUSE
file path:
C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a page table entry (PTE)
routine has been used in an improper way.
There is a possibility this problem
was caused by a virus or other malware.
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 05/07/2014 10:14:09 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:
0xDA (0x504, 0xFFFFF6FC400CFEB0, 0x0, 0x19FD6)
Error: SYSTEM_PTE_MISUSE
Bug check description: This
indicates that a page table entry (PTE) routine has been used in an improper
way.
There is a possibility this problem was caused by a virus or other
malware.
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 05/07/2014 09:57:22 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070514-32875-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA
(0xFFFFFD7FFFFFFF80, 0x2, 0x1, 0xFFFFF800296EC977)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 22:42:14 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070514-30968-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA
(0xFFFFFD7FFFFFFF78, 0x2, 0x1, 0xFFFFF801206E84A4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 19:29:44 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-13546-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E
(0xFFFFFFFFC0000005, 0xFFFFF803F4088276, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 19:04:44 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-14218-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA
(0xFFFFFD7FFFFFFF78, 0x2, 0x1, 0xFFFFF8028DF5B414)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 18:49:24 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-13531-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA
(0x8002, 0x2, 0x0, 0xFFFFF803AF282276)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 18:43:38 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-14625-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0x10,
0x2, 0x1, 0xFFFFF800E0D56380)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 16:01:39 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-30640-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA
(0xFFFFFD7FFFFFFF80, 0x2, 0x1, 0xFFFFF8035D5468E7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path:
C:\\Windows\\system32\
toskrnl.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
Fri 04/07/2014 15:20:16 GMT your computer crashed
crash dump file:
C:\\Windows\\Minidump\\070414-61343-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xF7
(0x697309A7885, 0x697309A7887, 0xFFFFF968CF658778, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path:
C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
Bug check description: This indicates that a driver has overrun a
stack-based buffer.
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.