Aller au contenu

Change
Photo

Msi Gt70 2Pe Bsod Non Stop


  • Veuillez vous connecter pour répondre
3 réponses à ce sujet

#1
silver55x

silver55x

    En attente de Visa

  • Membre
  • 4 messages

Bonjour,

 

J'ai eu un MSI GT70 2PE neuf y'a 1 semaine
quelque jours, et depuis le premier jour, 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\ntoskrnl.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\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
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\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
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\ntoskrnl.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\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
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\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
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\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
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\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
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\ntoskrnl.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.


Modifié par silver55x, 05 juillet 2014 - 23:51.

  • 0

#2
TomoHatchi

TomoHatchi

    En attente de Visa

  • Membre
  • 37 messages
  • LocalisationParis

Je crois que c'est un driver qui *part sur zone anatomique suspendue*, peut etre une erreur au telechargement. Je te conseille de tout desinstaller et reinstaller au propre. Assures toi de prendre les drivers compatible et associés. 

 

tiens nous au courant :P 


  • 0

Msi GT60 2 OC 

 

 


#3
silver55x

silver55x

    En attente de Visa

  • Membre
  • 4 messages

J'ai remis a neuf windows et y'a eu un BSOD pendant la configuration de windows a la fin de l'installation, un bad pool header

 

 

Donc vu que j'avais tout remis a neuf, que y'avais rien de installer juste windows, on peut en deduire quoi ? Probleme materiel ?

 

C'est juste ou on me demander de donné un nom a l'ordi juste apres

 

 

Voici :

 

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 05/07/2014 18:44:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070514-17234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00323A540, 0xFFFFF8A00323A570, 0x5030103)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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.



On Sat 05/07/2014 18:44:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1EF07)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00323A540, 0xFFFFF8A00323A570, 0x5030103)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
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 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.


Modifié par silver55x, 05 juillet 2014 - 20:04.

  • 0

#4
silver55x

silver55x

    En attente de Visa

  • Membre
  • 4 messages

Maintenant :

 

Crash dumps are enabled on
your computer.

On Sat 05/07/2014 21:39:10 GMT your computer
crashed

crash dump file: C:\Windows\Minidump\070514-15500-01.dmp
This
was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xDA
(0x504, 0xFFFFF6FC40016FF0, 0x0, 0x2DFE)
Error: SYSTEM_PTE_MISUSE
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 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 21:39:10 GMT your computer
crashed

crash dump file: C:\Windows\memory.dmp
This was probably
caused by the following module: storport.sys (storport!StorPortQuerySystemTime+0x1528)

Bugcheck code: 0xDA (0x504, 0xFFFFF6FC40016FF0, 0x0, 0x2DFE)
Error: SYSTEM_PTE_MISUSE
file path:
C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage
Port Driver
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 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. 

 

 

 Crash Dump Analysis



Crash dump
directory: C:\Windows\Minidump

Crash dumps are enabled on your
computer.

On
Sat 05/07/2014 22:09:23 GMT your computer crashed

crash dump file:
C:\Windows\Minidump\070614-14437-01.dmp
This was probably caused by the
following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x133
(0x1, 0x780, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path:
C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &
System
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 the Windows
kernel. Possibly this problem is caused by another driver that cannot be
identified at this time.



On Sat 05/07/2014 22:09:23 GMT your computer
crashed

crash dump file: C:\Windows\memory.dmp
This was probably
caused by the following module: hal.dll (hal!HalSetTimeIncrement+0x3F54)
Bugcheck
code: 0x133 (0x1, 0x780, 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. 


Modifié par silver55x, 05 juillet 2014 - 23:53.

  • 0




0 utilisateur(s) li(sen)t ce sujet

0 membre(s), 0 invité(s), 0 utilisateur(s) anonyme(s)