مشكلة انطفاء الجهاز فجأة+الشاشة الزرقاء مع ان الجهاز قوي بمواصفات عالية أرجو المساعده
بسم الله الرحمن الرحيم
السلام عليكم ورحمة الله وبركاته
اخواني الكرام جهازي مجمعه من شهر تقريباً ما شا ءالله عليه قوي بس فيه مشكلة يفصل كل فتره لوحده بدون shutdown فجاة يوقف و يسوي ريستارت ويعلق اول الstartup ويوقف ويكون فيه اشاره (-) تضوي وتطفي :eek: الان أعرض مواصفات الجهاز و وصور عن الاختبارات الي عملتها
نظام التشغيل الحالي Windows 7 64bit وجربت النظام Vista ultimat 64bit كمان نفس المشكلة كان يعطيني شاشة زرقاء ومرات في الليل أصحى القى الجهاز مطفي
مواصفات الجهاز
M.B: MSI 790FX-GD70
CPU: AMD Phenom II X4 955 HDZ955FBGIBOX 3.2 GHz/6 MB L3/125W Processor(Arctic Silver 5 Thermal)
CPU Cooler: Thermalright Ultra-120 eXtreme - Heat sink
Memory: OCZ OCZ3P1600LVAM4GK DDR3 1600MHz 1.65v 7-7-7-24 PC3-12800 Platinum AMD Edition
Graphic Card:SAPPHIRE Toxic 100269TXSR 4890 1GB
H.D.D: Western Digital Caviar Black (640 GB WD6401AALS for OS 1TB WD1001FALS for Data)
P.S : Thermaltake Toughpower 850w
Case: CoolerMaster HAF 932
الان صور CPU-Z
نتيجة اختبار 3Dmark06
نتيجة اختبار 3DMark Vantage
نتيجة اختبار FurMark
اختبار LightsMark2008
نتائج أقراص الهارد ديسك البلاك في HD Tune
ولكن مرات الاكسس تايم يعطيني 13 مع انه في اختبارات قديمة هي الي شجعتني على شرائه كانت 11.9 فقط:eek:
والان تحليل الملف الناتج في فولدر MiniDump بعد اعادة التشغيل الفجائية من خلال برنامج Windows Debugger Version 6
لا ادري المشكلة من وين بس أظن انها من الذواكر والله أعلم أرجو المساعدةكود PHP:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\No.9\Desktop\100609-21574-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: D:\Downloads\Fix Blue Screen\win 7
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Tue Oct 6 22:56:09.626 2009 (GMT+4)
System Uptime: 0 days 1:19:10.296
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8005da8ab0, fffff80000b9c518, fffffa8003dd0570}
***** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+71f00 )
Followup: MachineOwner
---------
وجزاكم الله خيرا
رد مع اقتباس
المفضلات