المساعد الشخصي الرقمي

مشاهدة النسخة كاملة : مشكلة فى جهاز DELL 6400 , الجهاز ينطفئ (عنوان معدل)



ماجدالماجد
08-11-2010, 03:06
السلام عليكم

اخواني ماابغى اطول عليكم

جهازي نوع ديل 640m اسبايرون

/
المشكله عندي ان الجهاز يطفي فجاءه وانا اشتغل على الانترنت والا البرامج والا اسمع اي شيء

المصيبه الشاشه تصير زرقاء ويطفي على طوووول مايعطيني فرصه

وتعبني جدا

بحثت في قوقل ولقيت موضوع ورابط وحملته والبرنامج وظيفته يجيب لك الاعطال واسبابها

طبعا سويت اللي قريته


واعطاني كتابات ورموز مافهمت عليها مامرت علي

المهم انتم اكيد تعرفوووووووووون هالامور


ابغى منكم تحليل المشكله وين وايش الحل


وتفضلووووووووووووووووووو


هذا اللي طلع من تحليل المشكله


وانتم اشرحوها لي



@@@@@@@@@@@@@@@@@@@@@@@@@@@@


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

Loading Dump File [C:\WINDOWS\Minidump\Mini110810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Nov 8 02:56:56.375 2010 (GMT+3)
System Uptime: 0 days 1:40:37.949
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. .......................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image idmtdi.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for idmtdi.sys
*** ERROR: Module load completed but symbols could not be loaded for idmtdi.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {feeed000, 2, 0, 80535e23}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Unable to load image mrxdav.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for NETw4x32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4x32.sys
Probably caused by : idmtdi.sys ( idmtdi+2d15 )
Followup: MachineOwner
---------

@@@@@@@@@@@@@@@@@@@@@@


واتمنى منكم التجااااااااوب

تحياااااتي لكم

ماجدالماجد
08-11-2010, 13:17
وينكم اخواني انتظركم

ماجدالماجد
09-11-2010, 02:33
تتحديث

Dr Mohammad
09-11-2010, 03:31
هل جربت عمل RECOVERY للجهاز ؟

ماجدالماجد
10-11-2010, 11:28
اشكرك عى تجاوبك معي

بس ماسويت شي الى الان

اتمنى اجد عندك الطريقه لاني مادري اش فيه

Dr Mohammad
10-11-2010, 21:45
https://www.arabhardware.net/forum/showthread.php?t=182365