Bluescreen avec bruit de machine à raser

Bonsoir

Essayer de reperer le bruit est ce
Le ventilatteur ou le DD

Sur votre ecran bleu donner le code Erreur : Stop erreur 0x00xxxxxxxx

A+

Merci beaucoup pour votre intervention, le pc est très silencieux, peut être si serai été le ventilo (je crois), le bruit sera présent même quand je suis sur la session, mais mon cas le bruit c'est juste au moment de la page bleu puis dès le redémmarage le bruit disparai complétement. Merci d'avance

Bonsoir,
Le PC doit chauffer puis la carte graphique avec, ce qui provoque un écran bleu.
Un conflit se créer entre la TV et le PC je pense.

Merci aussi, j'ai changé la résolution dans modifier les paramètre d'affichage, parce que la résolution ça change parfois après que j'allume mon, pc le lendemain sans que moi je la change, je vais voir et vous dire quoi. Merci d'avance

Merci Edawards.

Il y a de ces phenomènes inexpliqué commeca mais il faut reperer le problème pour pouvoir agir dessus.

Alors je peu vous dir qu'à un moment un conflit entre drivers fait que cela pousse la carte graphique fonctionne de tel manière qui la chauffe et son ventillo s'affole pour la refroidir

Ou aussi quand les tete de lecture arrive à un emplacement préci de votre DD Kouak Bruit (ce qui m'etonne, mais mais )

Detectez le bruit et on avisera A+ pour moi ce sera demain

Voici le rapport

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

computer name: SONY7PRO
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2137448448 total
VM: 2147352576, free: 1951666176

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 18/05/2011 20:01:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051811-25521-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0x48C9E)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAA4C6000, 0xFFFFFFFFAA4C6EA0, 0xBD40800)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd32.sys Intel Corporation BAD_POOL_HEADER

On Wed 18/05/2011 20:01:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32!hybDriverEntry+0x472EE)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAA4C6000, 0xFFFFFFFFAA4C6EA0, 0xBD40800)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd32.sys Intel Corporation BAD_POOL_HEADER

On Wed 18/05/2011 13:47:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051811-25084-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0x124D17)
Bugcheck code: 0x50 (0xFFFFFFFF8A97F000, 0x1, 0xFFFFFFFF8E92CD17, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that invalid system memory has been referenced.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: igdkmd32.sys Intel Corporation PAGE_FAULT_IN_NONPAGED_AREA

On Wed 6/04/2011 12:42:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-28002-01.dmp
This was probably caused by the following module: prisma02.sys (PRISMA02+0x29D98)
Bugcheck code: 0xD1 (0x2448281B, 0x2, 0x0, 0xFFFFFFFF98B41D98)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\prisma02.sys
product: PRISM 802.11 Wireless LAN
company: Conexant Systems, Inc.
description: PRISM Wireless NDIS 5.1 Driver
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.
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: prisma02.sys (PRISM Wireless NDIS 5.1 Driver, Conexant Systems, Inc.).
Google query: prisma02.sys Conexant Systems, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Tue 25/01/2011 12:05:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012511-24710-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x9F (0x3, 0xFFFFFFFF855BDB60, 0xFFFFFFFF82D7BAE0, 0xFFFFFFFF853C73D8)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. 4 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:

prisma02.sys (PRISM Wireless NDIS 5.1 Driver, Conexant Systems, Inc.)

igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel 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.

Merci d'avance

Merci beaucoup à tous, j'essayrai de faire ça . Merci d'avance

Bonjour,

Le problème, c'été la résolution d'ecran elle été sur 1280x720, alors qui devai être sur 1280x768, c'est par rapport à l'ecran LCD de ma TV. C'est parfoi rae que elle qui bascule sans que je la change vers 1280x720 quand j'allume mon pc Merci d'avance

A vous aussi également.

De rien. Et merci beaucoup à tous pour votre aide.