Ecran bleu pendant nettoyage disque

Ecran bleu pendant nettoyage disque - Win NT/2K/XP - Windows & Software

Marsh Posté le 04-04-2009 à 17:54:36    

Bonjour,
 
Suite à mes problèmes de redémarrage intempestif du PC, j'ai récupérer les fichiers Minidump du PC en question.
Au début j'ai trouvé un problème de pilote de carte graphique. J'ai mis le pilote à jour et le PC redémarre un peu moins souvent.
 
Ensuite j'ai désinstaller Avast et là, encore un peu d'amélioration.
 
Maintenant j'ai encore des redémarrage (surtout en lancant le nettoyage de disque quand j'essaye de compresser les fichiers non utilisés) et le Minidump me dit ceci (j'ai beau chercher mais je ne trouve rien à faire....je deviens  :pt1cable: ):
 
Merci pour vos lumières @+
 

Code :
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  5. Loading Dump File [I:\Mini040409-11.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  8. Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 2600.xpsp_sp3_gdr.080814-1236
  13. Machine Name:
  14. Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
  15. Debug session time: Sat Apr  4 16:19:13.515 2009 (GMT+2)
  16. System Uptime: 0 days 0:08:40.121
  17. Loading Kernel Symbols
  18. ...............................................................
  19. .................................................
  20. Loading User Symbols
  21. Loading unloaded module list
  22. ..........
  23. *******************************************************************************
  24. *                                                                             *
  25. *                        Bugcheck Analysis                                    *
  26. *                                                                             *
  27. *******************************************************************************
  29. Use !analyze -v to get detailed debugging information.
  31. BugCheck 1000008E, {c0000005, 804f0efe, b929bcec, 0}
  33. Probably caused by : ntoskrnl.exe ( nt!NtYieldExecution+54 )
  35. Followup: MachineOwner
  36. ---------
  38. kd> !analyze -v
  39. *******************************************************************************
  40. *                                                                             *
  41. *                        Bugcheck Analysis                                    *
  42. *                                                                             *
  43. *******************************************************************************
  45. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
  46. This is a very common bugcheck.  Usually the exception address pinpoints
  47. the driver/function that caused the problem.  Always note this address
  48. as well as the link date of the driver/image that contains this address.
  49. Some common problems are exception code 0x80000003.  This means a hard
  50. coded breakpoint or assertion was hit, but this system was booted
  51. /NODEBUG.  This is not supposed to happen as developers should never have
  52. hardcoded breakpoints in retail code, but ...
  53. If this happens, make sure a debugger gets connected, and the
  54. system is booted /DEBUG.  This will let us see why this breakpoint is
  55. happening.
  56. Arguments:
  57. Arg1: c0000005, The exception code that was not handled
  58. Arg2: 804f0efe, The address that the exception occurred at
  59. Arg3: b929bcec, Trap Frame
  60. Arg4: 00000000
  62. Debugging Details:
  63. ------------------
  66. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction   "0x%08lx" emploie l'adresse m moire "0x%08lx". La m moire ne peut pas  tre "%s".
  68. FAULTING_IP:
  69. nt!NtYieldExecution+54
  70. 804f0efe 8a4063          mov     al,byte ptr [eax+63h]
  72. TRAP_FRAME:  b929bcec -- (.trap 0xffffffffb929bcec)
  73. ErrCode = 00000000
  74. eax=0000012e ebx=804f0ea6 ecx=00000000 edx=00f8ff58 esi=00f8ff58 edi=b929bd64
  75. eip=804f0efe esp=b929bd60 ebp=b929bd64 iopl=0         nv up ei ng nz na pe cy
  76. cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
  77. nt!NtYieldExecution+0x54:
  78. 804f0efe 8a4063          mov     al,byte ptr [eax+63h]      ds:0023:00000191=??
  79. Resetting default scope
  81. CUSTOMER_CRASH_COUNT:  11
  83. DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
  86. BUGCHECK_STR:  0x8E
  88. PROCESS_NAME:  cleanmgr.exe
  90. LAST_CONTROL_TRANSFER:  from badb0d00 to 804f0efe
  92. STACK_TEXT: 
  93. b929bd68 badb0d00 00f8ff58 ff7b7b7b ffb6b6b6 nt!NtYieldExecution+0x54
  94. WARNING: Frame IP not in any known module. Following frames may be wrong.
  95. b929bd6c 00f8ff58 ff7b7b7b ffb6b6b6 00000000 0xbadb0d00
  96. b929bd70 ff7b7b7b ffb6b6b6 00000000 00000000 0xf8ff58
  97. b929bd74 ffb6b6b6 00000000 00000000 00000000 0xff7b7b7b
  98. b929bd78 00000000 00000000 00000000 00000000 0xffb6b6b6
  101. STACK_COMMAND:  kb
  103. FOLLOWUP_IP:
  104. nt!NtYieldExecution+54
  105. 804f0efe 8a4063          mov     al,byte ptr [eax+63h]
  107. SYMBOL_STACK_INDEX:  0
  109. SYMBOL_NAME:  nt!NtYieldExecution+54
  111. FOLLOWUP_NAME:  MachineOwner
  113. MODULE_NAME: nt
  115. IMAGE_NAME:  ntoskrnl.exe
  117. DEBUG_FLR_IMAGE_TIMESTAMP:  48a404ab
  119. FAILURE_BUCKET_ID:  0x8E_nt!NtYieldExecution+54
  121. BUCKET_ID:  0x8E_nt!NtYieldExecution+54
  123. Followup: MachineOwner
  124. ---------


Message édité par yucki68 le 04-04-2009 à 18:49:24
Reply

Marsh Posté le 04-04-2009 à 17:54:36   

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed