PC Ekspert Forum

PC Ekspert Forum (https://forum.pcekspert.com/index.php)
-   Hardverski problemi (https://forum.pcekspert.com/forumdisplay.php?f=41)
-   -   (riješeno) Blue screen iz čista mira (https://forum.pcekspert.com/showthread.php?t=176045)

alitaa 28.01.2010. 11:04

(riješeno) Blue screen iz čista mira
 
Imam problem koji se ne javlja cesto al me zeza i hocu to riješiti, pa trebam vašu pomoc.
Otprilike jednom tjedno iz cista mira mi se pojavi blue screen, nemogu povezati s nicim...kad radim u bilo kom programu il je u mirovanju... temperature su ok i u pcwizardu i na dodir. kad se pojavi blue screen ne stignem ništa procitati, jer se odmah restarta. I napocetku ispiše da je bila greška...al ja tu nemogu ništa iscitati... E sad pitanje, postoji li negdje zabisano što ga ruši i kako to riješiti?
Konfa..pod moj komp. Instalirani su win7, prije bila vista i isti problem.
Hvala, pozdrav!

Joke 28.01.2010. 11:14

Trebao bi imat dump fajlove koji se kreiraju poslje crasha, a nalazi se u "%SystemRoot%\MEMORY.DMP".
Sto imas od errora u event viewer (pod system)?

alitaa 28.01.2010. 18:11

Pronašao sam dump fajl, al nemogu ga otvoriti (.dmp)
a error - u event viweru (The previous system shutdown at 0:36:41 on ‎28.‎1.‎2010. was unexpected.)



details

- System
- Provider
[ Name] EventLog
- EventID 6008
[ Qualifiers] 32768
Level 2
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2010-01-27T23:38:26.000000000Z
EventRecordID 4366
Channel System
Computer Neno-PC
Security

- EventData
0:36:41
‎28.‎1.‎2010.
8298
DA07010004001C000000240029007E00DA07010003001B001700240029007E003C0000003C000000000000000000000000000000000000000100000000000000
--------------------------------------------------------------------------------
Binary data:
In Words

0000: 000107DA 001C0004 00240000 007E0029
0008: 000107DA 001B0003 00240017 007E0029
0010: 0000003C 0000003C 00000000 00000000
0018: 00000000 00000000 00000001 00000000

In Bytes

0000: DA 07 01 00 04 00 1C 00 Ú.......
0008: 00 00 24 00 29 00 7E 00 ..$.).~.
0010: DA 07 01 00 03 00 1B 00 Ú.......
0018: 17 00 24 00 29 00 7E 00 ..$.).~.
0020: 3C 00 00 00 3C 00 00 00 <...<...
0028: 00 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 00 00 00 00 ........
0038: 01 00 00 00 00 00 00 00 ........


Ne znam kako bolje objasniti...

Joke 28.01.2010. 18:19

How to read the small memory dump files that Windows creates for debugging
Skini odavde debugging tool, pa otvori sa njim taj dump fajl i sadrzaj istoga iskopiraj tu na forum.

alitaa 28.01.2010. 18:45

ide jedino "open crash dump"



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

Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.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`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Thu Jan 28 00:37:22.568 2010 (GMT+1)
System Uptime: 0 days 2:19:00.472
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88001314c7c, 2, 8, fffff88001314c7c}

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for fltmgr.sys -
*** ERROR: Module load completed but symbols could not be loaded for eamon.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : eamon.sys ( eamon+6c33 )

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



Joke 28.01.2010. 19:26

Citiraj:

Probably caused by : eamon.sys ( eamon+6c33 )
Koristis Eset AV?

alitaa 28.01.2010. 19:38

Da, nod32 / 4

Joke 28.01.2010. 20:15

Citiraj:

Autor alitaa (Post 1553426)
Da, nod32 / 4

Vidis li u postu povise gdje je problem, (sto je razlog BSOD-a).
Probaj izbrisat NOD-a pocistit registry pa instalirat neki drugi AV..

alitaa 28.01.2010. 20:27

da, vidim...ok probat cu stavit nešto drugo.
...ja sam mislil da je problem u hardveru, al još bolje ak je softver :-)

Puno ti hvala.

Joke 29.01.2010. 03:40

A cuj to je sad samo gledajuci po logu, a inace ne bi skodilo provrtit i memtest.

alitaa 30.01.2010. 20:50

prevrtio sam memtest, sve ok
maknuo nod, počistio registry i instalirao BitDefender
za sad je ok, sad čekam dal će se opet pojaviti...

EDIT:

ali, pojavio se opet...proguglat cu ntkrnlmp.exe možda nađem rješenje



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


Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.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`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
Debug session time: Sat Jan 30 21:26:11.892 2010 (GMT+1)
System Uptime: 0 days 9:27:25.796
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdb018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002b2826d, fffff880078ebad0, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe ( nt!FsRtlQueryMaximumVirtualDiskNestingLevel+66d )

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



alitaa 06.02.2010. 10:45

I dalje ne mogu naci rješenje.
i dalje se javlja, al svaki put druga greška...
(zadnje) Probably caused by : Ntfs.sys
Ako netko ima ideju, što uciniti.....?
Zahvaljujem.

TheBEaST 06.02.2010. 11:31

Citiraj:

Autor alitaa (Post 1561903)
I dalje ne mogu naci rješenje.
i dalje se javlja, al svaki put druga greška...
(zadnje) Probably caused by : Ntfs.sys
Ako netko ima ideju, što uciniti.....?
Zahvaljujem.

Kolko sam vidio po netu, dosta ljudi ima takvih problema, posebice na Win x64, ali i u Visti 64. Većinom se radi o nekim softverskim problemima, odnosno driverima (pogotovo za grafičku). Neznam koje verzije drivera imaš, pa probaj neku drugu verziju staviti, al imaj na umu da ponekad i najnovija verzija drivera i nije najbolja.
Ako ovo neda nikakve rezultate, probaj defragmentirati registry sa tuneup utilities programom i ostale korisne sistemske programe koji su tamo, a možda da probaš staviti i novi bios na matičnu.

Lewis 06.02.2010. 11:37

Istu situaciju sam imao i ja. Evo ti topic gdje je opisano:
http://forum.pcekspert.com/showthrea...hlight=Memtest

Zakljucak - uzmi drugi program za testiranje RAMa ;).

Doink the Clown 06.02.2010. 12:58

Citiraj:

Autor alitaa (Post 1561903)
I dalje ne mogu naci rješenje.
i dalje se javlja, al svaki put druga greška...
(zadnje) Probably caused by : Ntfs.sys
Ako netko ima ideju, što uciniti.....?
Zahvaljujem.

Nadam se da si memtest pustio da skenira bar 2 passa, možeš i HD Tuneom provrtiti error scan sistemskog diska, može biti da imaš bad sector.

Dizel 06.02.2010. 13:12

Memtest86+ je toliko nepouzdan da to nije normalno. Ako zelite iole sigurne rezultate s tim testicem trebate ga ostaviti da radi bar 6-8h.

Lewis 06.02.2010. 13:48

Citiraj:

Autor Dizel (Post 1561996)
Memtest86+ je toliko nepouzdan da to nije normalno. Ako zelite iole sigurne rezultate s tim testicem trebate ga ostaviti da radi bar 6-8h.

Kod mene ni to nije pomagalo (testiroa sma danima) , sve je bilo "OK" a komp se srusi iz cista mira dva-tri puta dnevno ili jednom u 3 dana , totalno random. Kao sto napisah tamo Goldmemory mi je nasao greshe i sa tim screen grabovima sam dobio drugi RAM i od ond anema problema.

alitaa 06.02.2010. 14:35

Dal to mogu i s neregistriranim goldmemory?
probat cu i fizicki testirat...prvo jedna plocica tjedan dana pa druga... pa da vidim.
Hvala na odgovorima.

Dizel 06.02.2010. 14:35

Meni je tek nakon 7-8h pokazao greske na prvim krepanim Ballistix Tracerima.

Lewis 06.02.2010. 14:42

Citiraj:

Autor alitaa (Post 1562104)
Dal to mogu i s neregistriranim goldmemory?
probat cu i fizicki testirat...prvo jedna plocica tjedan dana pa druga... pa da vidim.
Hvala na odgovorima.

Nemam pojma, ja sam imao neki stariji Hirens Boot CD i na njemu je bio GM.

Citiraj:

Autor Dizel
Meni je tek nakon 7-8h pokazao greske na prvim krepanim Ballistix Tracerima.

Ja sam vrtio i po 15-16 sati - stavim navecer prije spavanja i prekinem kad se vratim s posla i nista, nema gresaka na Memtestu :(.

alitaa 02.03.2010. 16:51

Problem riješen, problem je bio u memoriji.
Testirao sam fizički samo s jednom pločicom i nakon 10 dana komp je radio bez greške, a s drugom pločicom, blue screen svaki drugi dan. Na kraju je i memtest pokazao greške, al tek nakon 10 sati...
Zamjenu sam riješio bez problema...poštom poslao u Esys (s Protisovim računom i opisom kvara) i nakon tjedan dana na adresu mi je stigla nova memorija :-)
Hvala svima na savjetima


Sva vremena su GMT +2. Sada je 18:02.

Powered by vBulletin®
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
© 1999-2024 PC Ekspert - Sva prava pridržana ISSN 1334-2940
Ad Management by RedTyger