5 GÜNLÜK LAPTOBUMDA MAVİ EKRAN HATASI

Arkadaşlar öncelikle herkese merhaba. Benim sorunum daha 5 günlük olan dell marka b63f45 serisi i7 işlemci nvidia gt525 ekran kartlı güzel ortalama bilgisayarımda 2 gün önce mavi ekran hatasıyla karşılaştım. Ürün free-dos olarak geldi ben win7 ultime 64 bit işletim sistemi kurdum driverlarında ki tek sorun bluetooth sürücüsü onun için kaç tane lisanslı driver tarama programlarımı kurmadım ne yaptıysam kar etmedi ve o şekilde kaldı bende herhangi bir çakışma olmasın diye bu mavi ekrandan sonra sürücüyü devre dışı bıraktım 2 gündür bir sorun yok ama laptopun 5 günlük olması sebebiyle kuşkularımı çok doğal buluyorum.. Ürünü hepsiburadadan aldım dell yerinde desteği şu an için sabit hat bulamadığım için arayamıyorum ne olur yardım edin. Laptoptan çok memnunum ancak bu sorun sürekli kafamın bir köşesinde beynimi kurcalıyor.. Mavi ekran hatasının kodlarını alabilmek için minidump klasöründeki tek dosyayı açtım ve onu buraya koyuyorum hata kodu da dahil herşey orda var ben işin içinden çıkamadım.. Eğer bu sorunu çözersek beni ne kadar mutlu ediceğinizi bilemezsiniz. Umarım sorun donanımsal değildir..Şİmdiden ilgilenen arkadaşlara teşekkür ederim.. NOT: windows bütün güncelleştirmeleri yaptım..

HATA KODLARI:

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

Loading Dump File [C:\Windows\Minidump\071011-39561-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 \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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03015000 PsLoadedModuleList = 0xfffff800`0325a650
Debug session time: Sun Jul 10 23:36:34.840 2011 (UTC + 3:00)
System Uptime: 0 days 0:53:05.901
*********************************************************************
* 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 \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 CE, {fffff8802251d2c0, 8, fffff8802251d2c0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : btath_flt.sy ( btath_flt+12c0 )

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

5 GÜNLÜK LAPTOBUMDA MAVİ EKRAN HATASI

Benzer içerikler