الشاشة الزرقاء والتوافق , طلب علم
بسم الله الرحمن الرحيم
عرض المشكلة :
كما طالعت بابشبكة فهي قديمة بقدم إصدارات الإكس بي وهى الشاشة الزرقاء وما تسببه من إعادة تشغيل للحاسب دون أدنى إستئذان منك .
مما طالعته تنوعت مسببات الشاشة الزرقاء من سخونة لعدم توافق مكونات الجهاز إلى عدم توافق التعريفات حتى ملفات التجسس والفيروسات
لدى 6 أجهزة كمبيوتر جميعهم نفس المكونات قمت بتجميعهم منذ عامين وفقط كانوا بأفضل حال أول ثلاثة أشهر وبعد ذلك بدأت الشاشة الزرقاء تطارني مما افسد علي عملي وأدخلنى بمتاهات المسبب لذلك الريتسارت وحتى الآن مازلت عاجزا عن تحديد المسبب ووجه الخلل مع العلم أن الريستارت ليس له ألية للتوقيت حيث لا تدري متى سيأتي وليس له ألية للتكرار وليس متوقفا فقط على استخدام الألعاب ومستهلكات الجرافيك .
ربما من بعد إنتقاء مسبب النسخة ( خلل بنسخة الويندوز ) وكذا إنتفاء مسبب ملفات التجسس او الفيروسات وأيضا انتفاء مسبب سخونة المكونات ( البروسيسور , الماذربورد ) وايضا انتفاء مسبب عدم توافق التعريفات , وايضا انتفاء مسبب خلل الرامات ( فقط كون الستة أجهزة بذات الخلل ينفي وليس قطعيا وجود ذلك الخلل .
معلومات إضافيه:
تم مسح الفيروسات ببرنامج كاسبر سكاى ومسح ملفات التجسس ببرنامج اد ور وتم ترقية البيوس بأحد الأجهزة لأخر إصدار وتم تغيير الباور سبلاي لأحد الأجهزة بنوع حديث وجديد ولم تنتفى المشكلة .
نأمل الآن من أهل الخبرة أن يطلعوا على الصور التالية لبيانات الجهاز ببرنامج CPU-Z
ويخبرونا إن لاحظوا امرا ما يفترض كونه مسببا لذلك الريستارت وهل نوعية الرامات تتوافق مع مكونات الجهاز أم لا ؟
وبالحالة الإفتراضية كون الرامات غير متوافقة مع الجهاز فطلبا للعلم كيف كانت تعمل الأجهزة بشكل جيد من قبل مع ذات المكونات ؟
https://www.najmalsaba7.com/najm/res..._restart_1.jpg
https://www.najmalsaba7.com/najm/res..._restart_2.jpg
https://www.najmalsaba7.com/najm/res..._restart_3.jpg
https://www.najmalsaba7.com/najm/res..._restart_4.jpg
https://www.najmalsaba7.com/najm/res..._restart_5.jpg
__________________________________________________ _________
وبالإطلاع على البيانات التالية لبرنامج Windows Debugger مجرد نبذة من بعضها مع تنوعها وعددها
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini072808-02.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 = 0x8055a420
Debug session time: Mon Jul 28 19:14:14.265 2008 (GMT+3)
System Uptime: 0 days 0:04:25.813
************************************************** *******************
* 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 SiSGRV.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for SiSGRV.dll
*** ERROR: Module load completed but symbols could not be loaded for SiSGRV.dll
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, bfa36046, f58f4698, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
Probably caused by : SiSGRV.dll ( SiSGRV+63046 )
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini072808-03.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 = 0x8055a420
Debug session time: Mon Jul 28 21:23:52.186 2008 (GMT+3)
System Uptime: 0 days 1:22:45.339
************************************************** *******************
* 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 dxg.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 804ec3af, f58d5bc4, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
Probably caused by : dxg.sys ( dxg+3b5 )
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\Pc5\C\WINDOWS\Minidump\Mini080308-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 = 0x8055a420
Debug session time: Sun Aug 3 15:15:25.671 2008 (GMT+3)
System Uptime: 0 days 0:13:55.958
************************************************** *******************
* 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 ALCXWDM.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {8525bfdc, 2, 0, f9ab8bd4}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
Probably caused by : ALCXWDM.SYS ( ALCXWDM+5dbd4 )
Followup: MachineOwner
---------
شكرا لكل من طالع الموضوع والشكر أكثر لمن علمه الله علما نطلبة ولم يبخل به علينا
والسلام
