"System odzyskał sprawność..." - komunikat


(Pinkol) #1

Witam.

Otóż od pewnego czasu,w sumie od okresu około 2tyg. pojawia się komunikat http://img315.imageshack.us/my.php?image=screenlukassy3.jpg Komunikat ten pojawia się przy mniej więcej po 5 uruchomieniach kompa.Najbardziej dziwi mnie to,iż system jest poprawnie zamykany.Raz na jakiś czas,(przy uruchomieniu kompa i pojawieniu sie komunikatu)przy pracy około 5 minut na kompie następuje restart systemu oraz niebieskie tło z Microsoft'owskim texcikiem (...)Trwa zrzucanie pamięci fizycznej na dysk...(...)

Jaki może występować problem lub jaki występuje problem gdy ukazuje się w/w komunikat.

Z góry dziękuje za pomoc.

Pozdrawiam


(wieszak) #2

http://portal.centrumxp.pl/forums/threa ... .aspx#faq1

Ustaw BSODa

I jak następnym razem wyskoczy blue screen to spisz kod błędu i podaj nam , wtedy może coś poradzimy. Przyczyn może być wiele więc nie będe wymyślał teraz co może być przyczyną. :slight_smile:


(Rafalskora) #3

Mam ten sam problem niewiem czy spisalem to co trzeba 0x000000D1(0x00000000,0x0000001C,0x00000000,0x00000000)


(Pavko89) #4

Mozna jeszcze zobaczyc jaki plik powoduje ten blad

Zrob tak:

Pobierz program

http://msdl.microsoft.com/download/symb ... 6.07.5.exe

Gdy juz zainstalujesz program wchodzisz: Start - Programy - Debugging Tools For Windows - WinDbg.exe

klikasz File - Open Crash Dump i odnajdujesz plik Memory.dmp znajduje sie on w katalogu Windows potem gdy go otworzysz skopjuj cala zawatros na forum albo odnajdz linijke

Probably caused by :

I zobacz jaki plik powoduje ten blad


(Rafalskora) #5

Zrobilem to co powiedziales tylko nie moge tego skopiowac ale jest napisane : Probably caused by : ntoskrnl.exe Co to może być ?


(Pinkol) #6

to przepisz :slight_smile:

...a jednak :? ...blue screen

kod błędu 1000008E,c0000005,4d108051,f28f48d6,0

...zastosowałem się do poleceń Szanownego Kolegi i odnalazłem "wqrzacza" :slight_smile:

,a mianowicie :

Przyczyna: niekompatybilne oprogramowanie?Tak! A dokładnie "za świeże" stery do grafiki,niestety musiałem powrócić do starszych.

Blue Screen....jak ręką odjął :slight_smile:

Pozdrawiam

LukaS


(De Niro) #7

sprawdz

:arrow: pamieć Memtest86

:arrow: podmień zasilacz

:arrow: z konsoli odzyskiwania podaj komende CHKDSK /R


(Rafalskora) #8

Prosze o wiecej wskazówek bo nadal nie niem co robic . Nawet nie wiem co to jest konsola odzyskiwania. :frowning:


(boczi) #9

http://www.searchengines.pl/phpbb203/in ... opic=14270

Jeśli czegoś konkretnie nie wiesz, to napisz.


(Rafalskora) #10

Probably caused by : ntoskrnl.exe Co to jest i w czym jest problem ?


(wieszak) #11

W tym linku jest wszystko co znalazłem

http://forum.dobreprogramy.pl/viewtopic ... highlight=


(Dorocia ) #12

mianowicie mam ten sam problem .Ściągnęłam ten program windbg i tam wyskoczyła mi cała strona jakiś napisów a kod który jest potrzebny brzmi:Probably caused by:Unknown_Image(ANALISYS_INCONCLUSIVE) to chyba nie jest to co wam jest potrzebne.Nie mam pojęcia co mam z tym zrobić ,do tego nie znam się za bardzo na komputerach,a problem powtarza sie coraz częściej.Prosze o pomoc w tej sprawie.I z góry dziekuje


(system) #13

Proszę wybaczyć że się wtrącę, ale niedawno borykałem się z wyżej wymienionym problemem. W moim przypadku nie uzyskałem pomocy na forum. Więc w akcie desperacji przeinstalowałem XP. Nie pomogło. Po dłuższym zastanowieniu odinstalowalem programik EWIDO i ... można było obetrzeć pot z czoła:) Pomogło


(Pawelu1981) #14

U mnie natomiast pomogl formacik i reinstalka systemu, ale za to musialem zmienic wielkosc partycji systemowej bo na starej nie chcialo sie nic zmienic mimo formatow. Co ciekawe zauwazylem ze po otrzymaniu komunikatu ze system odzyskal sprawnosc w folderze windows za kazdym razem po tym komunikacie pojawilal mi sie folder o nazwie 3mdx pojecia nie mam o co chodzilo z tym folderem kasowanie go nic nie pomagalo bo problem powracal srednio co 2 lub 3 uruchomienie kompa sie konczylo pojawieniem sie tego komunikatu i pojawianiem sie tego folderu!


(Omegab6) #15

Witam,

Mam podobny problem z blue screenem, a mianowicie:

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Fri Sep 19 13:25:47.859 2008 (GMT+2)

System Uptime: 0 days 1:53:08.581

*********************************************************************

* 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+ *

*********************************************************************

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 NDIS.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for NDIS.sys

*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 8, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for Epfwndis.sys

*** ERROR: Module load completed but symbols could not be loaded for Epfwndis.sys

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for WlanBZXP.sys

*** ERROR: Module load completed but symbols could not be loaded for WlanBZXP.sys

*** WARNING: Unable to verify timestamp for USBPORT.SYS

*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS

Probably caused by : Epfwndis.sys ( Epfwndis+2f49 )

Followup: MachineOwner


Proszę o pomoc, nie wiem co z tym zrobić.


(Cosik Ktosik) #16

Epfwndis.sys, to sterownik od Eset Smart Security - Eset. Uaktualnij to oprogramowanie lub je zainstaluj na nowo.


(Szczuki1990) #17

witam widze ze ogarniacie temat, pojawil mi sie wlasnie taki błędzik i widze ze są na tym forum osoby kompetentne w porównaniu do innych portali.

oczywiscie blu skrin i krasz damp itp itd ..

zrobilem analize błędów i wyskoczyło mi ich 5. mianowicie :

On Sun 2010-05-30 20:48:36 your computer crashed

This was likely caused by the following module: ntfs.sys

Bugcheck code: 0x24 (0xC08A2, 0x0, 0x0, 0x0)

Error: NTFS_FILE_SYSTEM

Dump file: C:\Windows\Minidump\053010-18876-01.dmp

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010-05-30 20:36:52 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0x50 (0xFFFFFA8004F3F668, 0x0, 0xFFFFF80002BBB94C, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

Dump file: C:\Windows\Minidump\053010-19858-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010-05-30 19:35:11 your computer crashed

This was likely caused by the following module: ntfs.sys

Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006C291B8, 0xFFFFF88006C28A20, 0xFFFFF800028827C4)

Error: NTFS_FILE_SYSTEM

Dump file: C:\Windows\Minidump\053010-22245-01.dmp

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 2010-05-30 13:50:17 your computer crashed

This was likely caused by the following module: fastfat.sys

Bugcheck code: 0x23 (0xE0107, 0xFFFFF88005B356A8, 0xFFFFF88005B34F10, 0xFFFFF8800FFBD3DC)

Error: FAT_FILE_SYSTEM

Dump file: C:\Windows\Minidump\053010-19344-01.dmp

file path: C:\Windows\system32\drivers\fastfat.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Fast FAT File System Driver

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 2010-05-29 10:34:44 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0x1A (0x41790, 0xFFFFFA800124F7A0, 0xFFFF, 0x0)

Error: MEMORY_MANAGEMENT

Dump file: C:\Windows\Minidump\052910-19671-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Byłbym bardzo wdzieczny o szybką odpowiedź co tu jest nie tak i co mam zmienić. Pozdrawiam i licze na uprzejmość z waszej strony :slight_smile:


(Black Sabath) #18

witam, ja mam takiego typu problem:

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 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 3) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040

Debug session time: Mon Nov 22 10:16:15.515 2010 (GMT+1)

System Uptime: 0 days 0:06:33.086

*********************************************************************

* 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+ *

*********************************************************************

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 IDSxpx86.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for IDSxpx86.sys

*** ERROR: Module load completed but symbols could not be loaded for IDSxpx86.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {5b4, 2, 0, ec978557}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for SYMTDI.SYS

*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS

*** WARNING: Unable to verify timestamp for tcpip.sys

*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

*** WARNING: Unable to verify timestamp for psched.sys

*** ERROR: Module load completed but symbols could not be loaded for psched.sys

*** WARNING: Unable to verify timestamp for NDIS.sys

*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

*** WARNING: Unable to verify timestamp for b57xp32.sys

*** ERROR: Module load completed but symbols could not be loaded for b57xp32.sys

Probably caused by : IDSxpx86.sys ( IDSxpx86+44557 )

Followup: MachineOwner



(system) #19

Witam

Mam podobny problem co założyciel wątku. TO znaczy podczas normalnej pracy na komputerze (normalnej czyli przeglądanie internetu, korzystanie z worda, ewentualenia power pointa) w ciągu miesiące jakieś 3 czy 4 razy wyskoczył mi blue screen :frowning: dzieje się to w najmniej oczekiwanych momentach.

Pobrałem program debugging tools for windows. Poniżej informacje które podał program. Niestety kompletnie nic z nich nie rozumiem :frowning: Proszę o pomoc.

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 Vista Kernel Version 7600 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Kernel base = 0xfffff80002053000 PsLoadedModuleList = 0xfffff80002290e50

Debug session time: Thu Dec 30 18:10:25.802 2010 (GMT+1)

System Uptime: 0 days 6:44:35.443

*********************************************************************

* 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

Loading unloaded module list

.........

*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys -

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a554390, fffff88000dd3c98, 0, 2}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: dxgkrnl!_TDR_RECOVERY_CONTEXT ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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: dxgkrnl!DXGADAPTER ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys -

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Probably caused by : atikmpag.sys ( atikmpag+5c98 )

Followup: MachineOwner