Se connecter avec
S'enregistrer | Connectez-vous
Votre question

Ecran Bleu Vista Problème

Tags :
  • Système d'exploitation
  • Écrans
Dernière réponse : dans Systèmes d'exploitation
Partagez
23 Août 2008 14:01:22

Bonjour,
Depuis quelques temps mon pc portable sous vista a des écrans bleus à répétition! Je ne sais plus quoi faire!
Après une recherche sur internet, j'ai analysé mes fichier "minidump" avec windbg dont voici les rapports:

1)

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini081608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x82c40000 PsLoadedModuleList = 0x82d57c70
Debug session time: Sat Aug 16 20:11:09.647 2008 (GMT+2)
System Uptime: 0 days 3:34:40.082
Loading Kernel Symbols
..........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 868d3000, 868d3a00, 9400000}

*** WARNING: Unable to verify timestamp for MPRIFL.SYS
*** ERROR: Module load completed but symbols could not be loaded for MPRIFL.SYS
Probably caused by : MPRIFL.SYS ( MPRIFL+50d4 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 868d3000, The pool entry we were looking for within the page.
Arg3: 868d3a00, The next pool entry.
Arg4: 09400000, (reserved)

Debugging Details:
------------------


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 82d77868
Unable to read MiSystemVaType memory at 82d57420
868d3000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82d2e00c to 82d0d163

STACK_TEXT:
c55bc9e4 82d2e00c 00000019 00000020 868d3000 nt!KeBugCheckEx+0x1e
c55bca5c 833f80d4 868d3008 00000000 865e2c5c nt!ExFreePoolWithTag+0x17f
WARNING: Stack unwind information not available. Following frames may be wrong.
c55bca78 82cfc053 86b5b898 00000ae6 8667d8b4 MPRIFL+0x50d4
c55bca90 82e60ce5 45724e27 856c56f0 8640e008 nt!IofCallDriver+0x63
c55bcb60 82e69e96 86b5b898 00000000 8566b160 nt!IopParseDevice+0xf61
c55bcb98 82e85f48 856c56f0 00000000 8566b160 nt!IopParseFile+0x46
c55bcc28 82e5e0ca 00001bc0 c55bcc80 00000040 nt!ObpLookupObjectName+0x11e
c55bcc88 82e5fbc7 07cedf38 00000000 866e1401 nt!ObOpenObjectByName+0x13c
c55bccfc 82e50639 0a55eda8 00060080 07cedf38 nt!IopCreateFile+0x63b
c55bcd44 82c97a7a 0a55eda8 00060080 07cedf38 nt!NtOpenFile+0x2a
c55bcd44 77809a94 0a55eda8 00060080 07cedf38 nt!KiFastCallEntry+0x12a
07cedf58 00000000 00000000 00000000 00000000 0x77809a94


STACK_COMMAND: kb

FOLLOWUP_IP:
MPRIFL+50d4
833f80d4 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: MPRIFL+50d4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MPRIFL

IMAGE_NAME: MPRIFL.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 475af92c

FAILURE_BUCKET_ID: 0x19_20_MPRIFL+50d4

BUCKET_ID: 0x19_20_MPRIFL+50d4

Followup: MachineOwner
---------












2)

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini082208-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x82c04000 PsLoadedModuleList = 0x82d1bc70
Debug session time: Fri Aug 22 23:29:18.379 2008 (GMT+2)
System Uptime: 0 days 2:30:44.530
Loading Kernel Symbols
........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1580004, 2, 1, 839c212c}

Probably caused by : NETIO.SYS ( NETIO!RtlContractHashTable+65 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 01580004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 839c212c, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d3b868
Unable to read MiSystemVaType memory at 82d1b420
01580004

CURRENT_IRQL: 2

FAULTING_IP:
NETIO!RtlContractHashTable+65
839c212c 897304 mov dword ptr [ebx+4],esi

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: svchost.exe

TRAP_FRAME: bff50ae8 -- (.trap 0xffffffffbff50ae8)
ErrCode = 00000002
eax=866798e8 ebx=01580000 ecx=86700000 edx=866798e8 esi=867088e8 edi=87a71dd0
eip=839c212c esp=bff50b5c ebp=bff50b68 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
NETIO!RtlContractHashTable+0x65:
839c212c 897304 mov dword ptr [ebx+4],esi ds:0023:01580004=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 839c212c to 82c5ed84

STACK_TEXT:
bff50ae8 839c212c badb0d00 866798e8 87a71f28 nt!KiTrap0E+0x2ac
bff50b68 839b2b6f 866798e8 87a692a8 bff50b8c NETIO!RtlContractHashTable+0x65
bff50b78 839ba9ea 87a71dd0 85db5c50 879f8b30 NETIO!WfpRestructureHashtable+0x46
bff50b8c 839bc672 87a692a8 85d6a2c8 00000ae0 NETIO!IndexHashDelete+0x45
bff50bb0 839baa38 00000032 00000002 00010880 NETIO!DeleteFilterFromIndex+0x175
bff50be0 839bcf03 85000004 8794c0e8 bff50c1c NETIO!KfdCommitTransaction+0x94
bff50bf0 83a226c6 00000000 00000000 8794c104 NETIO!IoctlKfdCommitTransaction+0x4d
bff50c1c 83a6165d 85ef5188 00000000 bff50c44 tcpip!KfdDispatchDevCtl+0x124
bff50c2c 82cc0053 85ef5188 8794c0e8 8794c0e8 tcpip!NlDispatchDeviceControl+0x3c
bff50c44 82e505e5 87a2ae70 8794c0e8 8794c158 nt!IofCallDriver+0x63
bff50c64 82e50d8a 85ef5188 87a2ae70 00000000 nt!IopSynchronousServiceTail+0x1d9
bff50d00 82e3aa61 85ef5188 8794c0e8 00000000 nt!IopXxxControlFile+0x6b7
bff50d34 82c5ba7a 00000090 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
bff50d34 76f79a94 00000090 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01caf614 00000000 00000000 00000000 00000000 0x76f79a94


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!RtlContractHashTable+65
839c212c 897304 mov dword ptr [ebx+4],esi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NETIO!RtlContractHashTable+65

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47919103

FAILURE_BUCKET_ID: 0xD1_W_NETIO!RtlContractHashTable+65

BUCKET_ID: 0xD1_W_NETIO!RtlContractHashTable+65

Followup: MachineOwner
---------






Après une courte analyse, j'en deduis que la cause de tous mes problèmes sont les fichiers "NETIO.SYS" et "MPRIFL.SYS" malheureusement je ne sais pas à quoi ils correspondent!
Pouvez-vous m'aider?

Merci, Wakfu

ps: je post sur le forum "logiciels" car je ne sais pas trop où poster
:(  Merci :hello: 

Autres pages sur : ecran bleu vista probleme

23 Août 2008 14:51:12

svp personne?
24 Août 2008 16:39:18

J'ai besoin d'aide :( 

merci
Contenus similaires
24 Août 2008 19:20:35

Entre les moments où ça marchait et ton problème, as-tu ajouté un nouveau périphérique (USB ou carte), as-tu installé de nouveaux drivers ?
25 Août 2008 16:17:35

Salut et merci de m'avoir répondu!

j'ai installé plein de choses depuis!
Et des logiciels et périphérique dont j'ai besoin, donc je préfère identifier quel est LE drivers qui pose problème!

Merci et désolé pour avoir posté dans la mauvaise section!

Wakfu
25 Août 2008 19:44:51

svp!

merci
26 Août 2008 12:47:53

up
26 Août 2008 16:04:13

personne? :sweat: 
28 Août 2008 13:39:55

:cry: 
29 Août 2008 19:24:22

help :bounce: 
30 Août 2008 22:17:14

ce genre de chose m'est arrive souvent en branchant des clef usb..
qui surement contenaient des virus :S
31 Août 2008 20:24:49

Merci yoyo mais j'aimerais vraiment examiner la cause de mes écrans bleus :hello: 
Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS