BSOD - što, zašto i kako izdvojena tema

poruka: 3.547
|
čitano: 976.238
|
moderatori: DrNasty, pirat, XXX-Man, Lazarus Long, vincimus
+/- sve poruke
ravni prikaz
starije poruke gore
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako
Nak kaže...

Ovdje su 2 mini dumpa za koje sam postao i BsoD:

http://www.megaupload.com/?d=AMI09ZBI

Ovdje su svi mini dumpovi koje imam (od zadnjih tjedan dana):

http://www.megaupload.com/?d=27ISOKYS

Ovo ti je analiza dump-ova

 

On Tue 10.11.2009 22:10:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x6800003FCC)
Error: MEMORY_MANAGEMENT

 

On Tue 10.11.2009 22:10:06 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001313C2, 0xFFFFF88007F8E910, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION

 

On Tue 10.11.2009 22:10:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800028BD0C1)
Error: UNEXPECTED_KERNEL_MODE_TRAP

 

On Tue 10.11.2009 22:10:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800028E31C0, 0xFFFFF88006C37900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION

 

itd.

Uglavnom i svi ostali su vezani za ntoskrnl.exe. Prvo testiraj memoriju, a zatim hard disk. Jedno od to dvoje je sigurno, s tim da ja prije mislim da je u pitanju memorija.

16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako
Groza kaže...

Na frendovom laptopu mi se jutros pojavia ovi BSOD (BAD_POOL_CALLER)i ne može bootat Windowse (ne može ni u niti jednu F8 opciju), zna li neko šta uzrokuje ovi problem ?

Ovo je STOP Code

STOP: 0x000000C2 (0x00000040, 0x00000000, 0x80000000, 0x00000000)

Surfajući nisam uspija nać kvalitetno rješenje !

Ne mogu postati dump jer ne mogu uć u WIN ni na koji način !

Zna li neko, već 2 dana surfam u potrazi za odgovorom ali ništa, nije valjda reinstall jedino rješenje ?

Život me naučio da nikad ne prekidam ženu dok šuti!
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako
Groza kaže...

Zna li neko, već 2 dana surfam u potrazi za odgovorom ali ništa, nije valjda reinstall jedino rješenje ?

 

BAD_POOL_CALLER ima više uzroka. Kao i kod ostalih BSOD-ova vrlo često je uzrokovan kvarom memorije, ali može biti i čisto softverski (loš ili oštećen drajver, virus itd)

Prvo moraš identifikovati fajl koji uzrokuje probleme. To ćeš učiniti tako da prvo spriječiš automatski restart kompa prilikom BSOD-a. Butanje prekineš sa F8 i odabereš opciju "Disable automatic restart....". Butanje dalje ide do BSOD-a i tu sačekaš da uradi dump memorije.

Pošto ne možeš ući u Win da taj fajl pokupiš onda imaš dvije opcije:

- Butaš sa miniPE ili HirensBoot CD-om, a prije toga u laptop ubodeš USB stick.

- Izvadiš hard disk iz laptopa i staviš ga u eksternu USB ladicu koju priključiš na drugi komp.

 

Dumpove memorije ćeš naći u Windows/MiniDump folderu. Prekopiraj ih i okači ovdje da ti neko od nas uradi analizu.

 

16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

E caka je da on uopće ne radi dump memorije, buta sam već sa Hirensom i u MiniDump folderu nema ništa !

BTW, testira sam RAM i HDD i nije nađena nikakva greška !

Život me naučio da nikad ne prekidam ženu dok šuti!
Poruka je uređivana zadnji put sri 11.11.2009 22:43 (Groza).
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Pa jesi li radio ovo prvo što sam ti rekao?

"Disable System Restart" na meniju koji dobijes sa F8?

Trebalo bi da sačeka na BSOD-u, a u donjoj liniji piše "Dumping Physical Memory". Nakon što to završi resetuješ komp i probaš sa Hirenom naći fajl.

Poruka je uređivana zadnji put sri 11.11.2009 22:49 (dragans).
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

To je prvo ta sam napravia a kako bi inače dozna o kjem je BSOD-u riječ, fora je da nema donje linije "Dumping Physical Memory", zadnaj linija je STOP code

Život me naučio da nikad ne prekidam ženu dok šuti!
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Ako ti ne kreira minidumpove probaj i ovo:

 

Botaj sa miniPE bootCD-om. Startuj neki od registri editora (sad se ne sjecam imena a ima ih vise tamo), i ucitas registri sa diska C. Nadji ove ključeve i probaj ih izmjeniti:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

  • AutoReboot = 1 (on) or 0 (off)
  • CrashDumpEnabled = 3 (64KB minidump)

 

Kod mene u registriju je ovako:

 

AutoReboot = 0

CrashDumpeEnabled = 3

 

 

Poruka je uređivana zadnji put sri 11.11.2009 23:03 (dragans).
16 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Probaću

Ništa, u Registry-u su mi jednake vrijednosti ka i kod tebe ali on ne baca minidump-ove !

Život me naučio da nikad ne prekidam ženu dok šuti!
Poruka je uređivana zadnji put sri 11.11.2009 23:13 (Groza).
14 godina
neaktivan
offline
BSOD - što, zašto i kako

OK ljudi možete li mi pomoći imam problem sa bsod a fajl koji prikaže da je problematičan je ati3display.sys tako nešto.

 
0 0 hvala 0
15 godina
odjavljen
offline
RE: BSOD - što, zašto i kako

Reinstaliraj (stavi nove) drivere od grafičke kartice.

A rifle is like a human. The stock is the skeleton, the scope is the eyes, the action is the brain, and the barrel is the heart. But you, the man behind the rifle, you are the soul.
14 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Probati ću ponovno grafu instalirati to je neki virus.

Opet ništa tačan naziv fajla je ati3duag.dll molim pomoć.

Ima li ko riješenje?

Poruka je uređivana zadnji put ned 22.11.2009 20:01 (fareee).
15 godina
neaktivan
offline
BSOD - što, zašto i kako

To je dio drivera za graficku. Obrisi ih u safe modu Driver sweeperom te restartaj komp i nanovo instaliraj.

World championships: 7, GP started: 250, GP wins: 91, Podium finishes: 154, Pole positions: 68, Fastest laps: 76, Points: 1,369
 
0 0 hvala 0
14 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Nije ni do tog.

Ukucao sam sada u search ati3duag.dll i pronašlo je 4 fajla šta da radim sa njima.

A šta mislite da skinem taj fajl sa interneta i replejcam ga sa ovim sada da li bi to riješilo problem?

Poruka je uređivana zadnji put pon 23.11.2009 19:49 (fareee).
15 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Hvala na ovoj korisnoj stvari...Sigurno ce pomoci....

15 godina
neaktivan
offline
BSOD - što, zašto i kako

Bio bih zahvalan kad bi mi netko pomogao naći uzrok bsod-a na sedmici x64 RTM 7600 - TARGET_MDL_TOO_SMALL 0x00000040. Radi sve super dok se ne spojim na net (Bez neta nema ni BSOD-a) i skidam (svejedno šta, npr. torrente). što se tiće neta, spojen sam preko Optime (WiMAX) i Siemens routera koji je dio paketa. Mislim da je on problem jer mi se ista stvar događala na xp-u dok nisam kupio najobičniji switcher. BSOD se pojavljuje u nepravilnim vremenskim razmacima (2 min. - 3 h) tako da nemam pojma o čemu je riječ. Uplodao sam zadnja tri .dmp file-a. Molim za pomoć.

 

dmp: http://ul.to/zke573

Poruka je uređivana zadnji put sub 28.11.2009 13:36 (Chamil20).
 
0 0 hvala 0
15 godina
neaktivan
offline
BSOD - što, zašto i kako

Molim nekog tko se razumije puno bolje nego ja da mi pomogne!!!

 
0 0 hvala 0
15 godina
offline
RE: BSOD - što, zašto i kako

Pitanje...

 

Siemens ti radi u router modu? Ili kao modem?! Čini mi se kao modem - kao što si i sam utvrdio u tom grmu leži zec. Koji model Siemensa je u pitanju? Ajd malo detalja daj...

 

Uglavnom, kao što si i sam utvrdio, kad si sve spojio na switch problem riješen...

I find your lack of faith disturbing!
Poruka je uređivana zadnji put sri 2.12.2009 19:22 (0v3r10rd).
15 godina
neaktivan
offline
BSOD - što, zašto i kako

Radi se o Siemens Gigaset SE 461 WiMAX i radi u bridge modu, odnosno kao modem. Swicher mi je riješio problem na XP-u, a šta da radim sa Sedmicom? Driveri su svi kompletno up to date! Pazio sam i koje programe instaliram. Jel se može zamjenit router, za neki drugi model? Zvao sam Optimu, a oni nemaju pojma u čemu je problem! Dali se može vidit dmp file-ovima nešto više? Pozz

Poruka je uređivana zadnji put čet 3.12.2009 19:52 (Chamil20).
 
0 0 hvala 0
15 godina
neaktivan
offline
BSOD - što, zašto i kako

meni bi trebala pomoc(link)

 

 
0 0 hvala 0
14 godina
neaktivan
offline
BSOD - što, zašto i kako

Pozdrav svima, upravo se registrirah, trebam pomoć kako slijedi Plač

Danas mi se pojavio bsod na sekundu i restartao komp. Jedino što sam mogla napraviti je pričekati da se digne ponovo i win su mi sami napisali u prozorcicu error:

BCCode: 1000008e

BCP1: C0000005

BCP2: BF82DE77

BCP3: A4C11A40

BCP4: 00000000

OSVer:5_1_2600

SP: 3_0

Product: 256_1

 

Kada sam to prepisala , zagasila sam prozor i javila se vama!!

Imam Acer Aspire Notebook 5810T/5810TZ/5410T series, model je MS 2272.

Frend koji je IT strucnjak mi je skinuo Linux koji je bio gore (maknula sam ga jer nije imao graficko sucelje) i stavila original XP (odnosno Corporate edition, skoro kao original).

 Komp je novi, kupljen u ljeto 2009. kod nas.

Ali... ovo je drugi , isti takav. Naime, prvi koji je kupljen je radio par dana i ugasio se , nije se moglo ni u BIOS ući.. A prije nego se to dogodilo , glazba je jaaako zavlačila često i preskakala.. Ne stalno..Onda je crknnuo skroz. Odnesla ga na servis i dobila novi. Onda je glazba opet preskakala par dana , ali svako toliko, ne stalno. I sada 2,3, mjeseca nista i danas plavi ekran :(((

 

Što mi je raditi, help Plač 

 

Inače, nemam ništa natrpano gore, nista skoro ne skidam, par filmova do sada, nemam wifi nego žični net vec jako dugo. Stalno upgrade-am antivirus, pokrecem ccleaner , aviru i 2 puta sam ga defragmentirala. nista novo nemam instalirano osim glary utilities što nikako ne bi trebalo biti problem... .. ..

 

TNX..

Poruka je uređivana zadnji put ned 10.1.2010 19:08 (Chica).
Moj PC  
0 0 hvala 0
14 godina
neaktivan
offline
BSOD - što, zašto i kako

daj spec od kompa

KOMPJUTER KO IZ NASE::: 486: cpu 80486 OVERCLOCKED @71 mhz 16MB ram Floppy Drive 500 mb HDD S3 86C911 1mb VRAM - ISA connection
Moj PC  
0 0 hvala 0
14 godina
neaktivan
offline
RE: BSOD - što, zašto i kako

Bas sam napisala..jel se vidi ? Ako ne u poruci , onda u profilu...

15 godina
offline
RE: BSOD - što, zašto i kako

-koristiš li Avast? (ili Adaware/Spybot&D)

-isključi restart ''../Sys.prop. /Start-Rec./..'' -auto odchekiraj. -tako ćeš barm vidjeti ispis na ekranu za BSoD.

-Mislim da je Avast kriv, ali nije samo on, vjerojatno je kombinacija softwarea... -ako imaš volje/vremena/malo znanja,. ... napravi clean install i koristi npr Aviru, i ne pretjerivati sa sistemskim softwareom...

-drugi (mogući) uzrok je 'original' i SP3, jer usprkos originalnosti, neke stvari su samo za legalnu upotrebu (mogu se očekivati problemi)...

C64/TurboModul-OpenSourceProject.org.cn.部分作品为网上收集整理,供开源爱好者学习使用
14 godina
neaktivan
offline
BSOD - što, zašto i kako

 

Meni izbacuje plavi ekran

 

i ovo

 

KERNEL_STACK_INPAGE_ERROR

 

 

 

Technical information:

 

STOP : 0x00000077 (0xC000000E,0x00000000,0x04FCD000)

 

 

Evo ljudi molio bih pomoći :(,izludit će me a laptop mi treba za posao u petak već :(

 

HVALA SVIMA UNAPRIJED!

 
0 0 hvala 0
14 godina
neaktivan
offline
BSOD - što, zašto i kako

ja imam isto problem s BSOD!

 

naime, kupio novu konfu, fino instalirao Vistu (32-bit), na nju odmah Win7 (32-bit), inst. drivere, neke još programčiće, i sljedeći put kad sam ga upalio nakon 15-ak minuta BSOD! međutim nakon toga komp je radio ko da se ništa nije dogodilo cijeli ostatak dana, sve do sljedeći puta kad sam ga palio, tada se ponavlja ista priča!

 

probao sam format C, instalirat fresh copy Win7 (64-bit), ista priča, probao Vistu, ista priča... Iznenađen

sad sam stavio XP sp2 i radi mi normalno sad već skoro 2 sata... Osmijeh

 

sad mene zanima dal nešt treba podesiti u BIOS-u pa da mi Vista i Win7 rade normalno??

inače HDD testiran HD-Tune-om i OK je, RAM testiran memtestom, nema errora!

 

jučer metnuo Vistu na čisti C disk samo sa driverima koje sam dobio uz komp... nakon 10min - BSOD!!! Viče i pisalo da je problem u nekakvom ntdll.dll

 

pisalo je i ovo:

 

Problem Signature:

 

Problem Event Name:   Startup RepairV2

Problem Signature 01:  External Media

-II-                         02:  6.0.6000.16386.6.0.6000.16386.

-II-                         03:  1

-II-                         04:  65537

-II-                         05:  unknown

-II-                         06:  0x24

-II-                         07:  0

-II-                         08:  2

-II-                         09:  WrpRepair

-II-                         10:  2

OS Version:                   6.0.6000.2.0.0.256.1

Locale ID:                      1033

 

a u Windowsima mi se, prije nego se pojavio BSOD, prikazalo ovo:

The instruction at 0x76c5e5c2 referenced memory at 0x76cb7348. The memory could not be written. Click on OK to terminate the program.

 

danas sam instalirao na čisti C disk XP sp2 i zasad radi oko 2 sata bez BSOD-a... s time da mi se Mozilla nakon 10-ak minuta srušila, al sad dalje je ok...

Moj PC  
0 0 hvala 0
14 godina
neaktivan
offline
BSOD - što, zašto i kako

BSOD mi se pojavi ,i nakon restarta se normalno podigao sistem ,da li je to znak da ce se ponovo pojaviti ,ili moze da se ne pojavi?:D,hvala.

Nemam pojma sta da uradim radi prevencije ,napravio sam scan sa avirom,pa antimalvare-om,nije mi pokazao nikakve viruse!

 
0 0 hvala 0
14 godina
online
RE: BSOD - što, zašto i kako

jel moguće kad mi dođe do BSOD-a zbog pokrenutog nekog inficiranog fajla,podić winse bez ono format i onda fresh install winsa

16 godina
neaktivan
moderator
offline
RE: BSOD - što, zašto i kako
softwaremaniac kaže...

jel moguće kad mi dođe do BSOD-a zbog pokrenutog nekog inficiranog fajla,podić winse bez ono format i onda fresh install winsa

  Ubaci instalacioni CD od Windows bootaj sa njega i uradi repair ili tako nesto

A poet who reads his verse in public may have other nasty habits. Lazarus Long
14 godina
online
RE: BSOD - što, zašto i kako
znam za to ali mislio sam jel se može nakon takvog BSOD-a pristupit winsima na neki način??
14 godina
online
RE: BSOD - što, zašto i kako

e ovako zadnja dva dana imam BSOD komp se restarta i poslije je sve normalno koristim win 7.Zašto mi je odjednom počeo BSOD?? Našao sam minidump datoteku ali neznam kaj s njom

uspio sam ju otvoriti

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


Loading Dump File [C:\Windows\Minidump\022010-26718-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8303c000 PsLoadedModuleList = 0x8317b570
Debug session time: Sat Feb 20 20:18:52.868 2010 (GMT+1)
System Uptime: 0 days 2:11:33.852
*********************************************************************
* 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 1000008E, {c0000005, 8325150e, 9679079c, 0}

*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : tdrpm251.sys ( tdrpm251+2b5cf )

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

 Molim analizu minidumpa

Poruka je uređivana zadnji put sub 20.2.2010 23:03 (softwaremaniac).
Nova poruka
E-mail:
Lozinka:
 
vrh stranice