Bonjour   , voilà mon problème depuis quelques temps, mon pc redémarre tout seul avec un message indiquant :  
 
Windows à redémarré après un arrêt non planifié
 
Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.1.7601.2.1.0.768.3
  Identificateur de paramètres régionaux: 1036
 
Informations supplémentaires sur le problème :
  BCCode: d1
  BCP1: FFFFF88007F25562
  BCP2: 0000000000000002
  BCP3: 0000000000000000
  BCP4: FFFFF880026B6ED1
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1
 
Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\101411-27924-01.dmp
  C:\Users\Moi\AppData\Local\Temp\WER-4213867-0.sysdata.xml
 
Lire notre déclaration de confidentialité en ligne :
  http://go.microsoft.com/fwlink/?li [...] cid=0x040c
 
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt
 
 
Je ne sais pas du tout pourquoi   , je ne suis pas devant l'écran quand ça plante    
 
Config du PC :
 
Edition Windows
 
Windows 7 Edition Familiale Premium
Service pack 1
 
 Système
 
Fabricant : Hewlett-Packard Company
Evaluation : 4.3 Indice de performance Windows
Processeur : AMD Athlon(tm) II X2 245 Processor 2.90GHz
Mémoire installée (RAM) : 4,00 Go (3,75 Go utilisable)
Type du système : Système d'exploitation 64 bits
 
Activation de Windows
 
Windows est activé.
ID de produit : 00359-OEM-8992687-00010
 
Merci de votre aide  

Personne pour m'aider alors ?

pilote de la carte graphique ?

je trouve ça ou? désolé je suis novice

J'ai trouvé ^^ c'est ATI Radeon 3000 Graphics

Bon vraiment personne pour m'aider? Pourtant le sujet a été vu une centaine de fois !!!!!!!!!!!!!!!!

J'ai fais une analyse avec WhoCrashed et voici le résultat :  
 
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Sun 16/10/2011 23:32:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101711-28064-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40E002E, 0xFFFFFA80088B1480)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time.  
 
 
On Sun 16/10/2011 23:32:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wna1000m.sys (WNA1000M+0x1A964)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40E002E, 0xFFFFFA80088B1480)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\wna1000m.sys
product: Realtek RTL8192C Wireless USB 2.0 Adapter  
company: Realtek Semiconductor Corporation  
description: Realtek RTL8192C USB NDIS Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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: wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation ).  
Google query: wna1000m.sys Realtek Semiconductor Corporation BAD_POOL_CALLER
 
 
 
 
On Sun 16/10/2011 15:23:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-25911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40E001E, 0xFFFFFA8003AE9D90)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time.  
 
 
On Fri 14/10/2011 23:53:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-49748-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88009A1F2B2, 0x2, 0x0, 0xFFFFF880026D7ED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Fri 14/10/2011 19:17:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-37112-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88000BE8E32, 0x2, 0x0, 0xFFFFF88005B0CED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Fri 14/10/2011 15:20:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-27924-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88007F25562, 0x2, 0x0, 0xFFFFF880026B6ED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Thu 13/10/2011 22:20:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-51246-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88008C385BA, 0x2, 0x0, 0xFFFFF88005B61ED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Thu 13/10/2011 20:15:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101311-25864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88009A3B952, 0x2, 0x0, 0xFFFFF88002711ED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Thu 13/10/2011 17:04:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101311-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xD1 (0xFFFFF88000B29682, 0x2, 0x0, 0xFFFFF88004F67ED1)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
On Thu 13/10/2011 04:52:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101311-25209-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40E0004, 0xFFFFFA8008576F30)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time.  
 
 
On Wed 12/10/2011 21:40:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-29874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0xE0015, 0xFFFFFA8003C01160)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time.  
 
 
On Wed 12/10/2011 12:46:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101211-53305-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xC2 (0x7, 0x109B, 0x40E000D, 0xFFFFFA8008CC3780)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 which cannot be identified at this time.  
 
 
On Mon 10/10/2011 06:35:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101011-19281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)  
Bugcheck code: 0xD1 (0xFFFFFA800ACA5F70, 0x2, 0x0, 0xFFFFF88005307D2D)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
13 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:  
 
wna1000m.sys (Realtek RTL8192C USB NDIS Driver, Realtek Semiconductor Corporation )
 
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.  
 
 
Je tiens à préciser que c'est un pc de bureau et j'ai une clé wifi en usb sur l'arrière de la tour, je sais pas si c'est important mais bon. Si j'ai bien compris le problème viendrait de Realtek Usb machin, j'ai téléchargé le zip de realtek, dé-zippé installé et la avast me dit qu'il y a peut-être un danger, et ma clé wifi ne marche plus. Enfin bon vu que j'y connait rien j'ai désinstallé le truc usb realtek je sais plus quoi et ma clé wifi remarche !!!!! Mon pc a 2semaines !!!! L'écran bleu s'affiche que quand je fais tourner utorrent !!! Je n'y comprend rien
 
Merci de votre aide (si j'en ai une -_- )