[Résolu] BSOD • page 2

[Untenshu]

Bonjour EZ ;
Lorsque je recevrais mon SSD , je ne mettrais qu'une seule barrette mémoire pour l'installation puis j'en rajouterais au fur et à mesure car j'ai commandé d'autres barrettes mémoire aussi .Mais je verrais aussi en installant Windows 7.64 Pro si ça beugue ou pas avec une seule barrette mémoire.Pourtant j'ai utilisé Memtest pour vérifier les barrettes mémoire et aucun problème donc je penche plus sur le problème avec acronis.
Cordialement.

[EinsteinZero]

Bonjour

Ok on met le sujet en "pause" et tu appuieras sur "marche" quand tu auras le SSD & fait la réinstall

A++

[Untenshu]

Bonjour EZ ;
Dans Roguekiller j'ai eu ceci par rapport au MBR :


+++++ PhysicalDrive0: ST31000524AS ATA Device +++++
--- User ---
[MBR] 12f969e997edc7db16b16c92c4bb0118
[BSP] 587e5ab931fa53aced1b5112d3f453e8 : Windows 7 MBR Code
Partition table:
0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 2048 | Size: 100 Mo
1 - [XXXXXX] NTFS (0x07) [VISIBLE] Offset (sectors): 206848 | Size: 953764 Mo
User = LL1 ... OK!
User = LL2 ... OK!

+++++ PhysicalDrive1: WD 5000AAK External USB Device +++++
--- User ---
[MBR] 3f8c10ea8506003090572ae380ceb422
[BSP] 9116bfa1c36ef7ffd43e365e4a8259da : Windows 7 MBR Code
Partition table:
0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 63 | Size: 339127 Mo
1 - [XXXXXX] EXTEN (0x05) [VISIBLE] Offset (sectors): 694534142 | Size: 137811 Mo
User = LL1 ... OK!
Error reading LL2 MBR!

+++++ PhysicalDrive2: Seagate Desktop USB Device +++++
--- User ---
[MBR] 1649140216512825775d77ffcb22b32d
[BSP] 7d8c4f1e15fe70b6a7af01277c433a4d : Windows XP MBR Code
Partition table:
0 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 63 | Size: 1907726 Mo
User = LL1 ... OK!
Error reading LL2 MBR!

Quand penses tu ? Y-a-t'il un problème de ce côté là . Je suis toujours en attente de mon SSD !
Cordialement.

[EinsteinZero]

Bonjour

au vus du sujet >>ici<<

(cherche les réponse du 29/01/2012 à la fin) il semblerait que ce soit sans importance il est écrit "je cite"

la méthode LL2 (APTI) ne marche pas pour tous les disques d'où la remontée d'erreur
Rien d’inquiétant

donc..attendons le SSD

[Untenshu]

Bonjour EZ.
J'ai bien reçu et mis en place mon SSD mais il n'y a que 11.8 Go de libre , crois tu qu'il y ait une incidence ou puis je virer certains " trucs " ?
Cordialement.
PS :l'idéal pour moi serait de n'avoir que Win sur le SSD mais comment faire pour mes programmes ?

[Untenshu]

Bonsoir Ez .
résultats des courses , nouvel BSOD avec le rapport qui suit :


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: GILLES-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 12882337792 total
VM: 2147352576, free: 1968316416



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 07/03/2012 15:22:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-18376-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000001.sys (Unloaded_Unknown_Module_00000000`00000001+0x2FE710)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800039BF5C3, 0xFFFFF880035CB968, 0xFFFFF880035CB1C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: unknown_module_00000000`00000001.sys .
Google query: unknown_module_00000000`00000001.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

1 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:

unknown_module_00000000`00000001.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Qu'en penses tu ? Personnellement , je n'y comprends plus rien !
Cordialement.

[EinsteinZero]

Bonjour

visiblement le DD n'est pas le seul soucis en plus le rapport dump n'apporte rien...c'est le brouillard

peut-être une mise à jour du Bios serait utile....car avec les SSD il' y a parfois des pb si celui-ci n'est pas suffisamment à jour

sinon, faudrait faire des stress test des autres composant pour voir ou ça plante >>logiciels test en tout genre ici<<

[Untenshu]

Bonsoir EZ.
Mise à jour du BIOS effectuée , différents tests effectués sans aucun résultat ! j'attend le prochain blue screen of the dead ! je lui ferais bien la peau à celui-là un de ces jours . J'espère que ce n'était qu'un reliquat !
Cordialement.
PS : je te tiens au courant , vu que les tests vont super vite avec ce que j'ai mis dans la bécane !

[EinsteinZero]

Re

ouai..espérons "wait en see" comme dirait l'autre

[Untenshu]

Bonjour EZ;
Nouveau BSOD

System Information (local)
--------------------------------------------------------------------------------

computer name: GILLES-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 12882337792 total
VM: 2147352576, free: 1968033792



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 08/03/2012 11:39:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x4E (0x99, 0x6A573, 0x2, 0x63C55)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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.
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: Unknown .
Google query: Unknown PFN_LIST_CORRUPT




On Wed 07/03/2012 15:22:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-18376-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000001.sys (Unloaded_Unknown_Module_00000000`00000001+0x2FE710)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800039BF5C3, 0xFFFFF880035CB968, 0xFFFFF880035CB1C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: unknown_module_00000000`00000001.sys .
Google query: unknown_module_00000000`00000001.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. 2 third party drivers have 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:

unknown_module_00000000`00000001.sys

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Si tu y comprends quelque chose....alors que mes drivers sont à jour.
Cordialement.

[EinsteinZero]

Bonjour

la je n'y comprend pas grand chose moi même, aux vus du rapport, un pilote "inconnu" se prendrait les pieds dans le tapis et ne serait "pas à jour"....

mais comme tu dis que tout est à jour...c'est le grand mystère

[Untenshu]

Bonjour EZ.
Finalement j'ai tout reformaté et réinstallé l'OS sur le SSD . Pourvu que ça tienne maintenant. Je crois que l'on peut mettre le sujet en résolu car si ça se reproduisait , j'ouvrirais un nouveau post. Encore merci de ton aide EZ.
Cordialement.

[EinsteinZero]

Bonsoir

Ok je mets en résolu