PCTuning fórum

Cau mam takovej problem.. asi pred tremi dny sem si koupil tv kartu winfast tv 2000xp vse v pohode jede.. az dnes nastal problem.. instaloval jsem counter strike 1.6nonsteam instalace mi strasne dosekla system.. zmizelo mi pozadi a ikony start panel byl v pulce monitoru.. o to by tak neslo..pockal jsem tedy az se cs nainstaluje (celou dobu sem sledoval televizi pres winfast pvr 2)
po tom co se cs nainstalovalo cekal jsem ze se mi vrati pozadi.. a ikony ale nic tak jsek klepl na start a dal odhlasit uzivatele.. odhlasil jsem se znova prihlasil a vse bylo jak ma.. az do doby kdy jsem spustil winfast pvr2 a htel pokracovat ve sledovani tv natvrdo se mi restartoval komp! proste zapl jsem winfast a bum ! uz jsem jen videl jak mi znova nabihaji XP... nikde nebyla zadna modra obrazovka z kodem chyby.. proste jen restart.. potom jsem zapl everest podival se do karty operacni system-doba provozu a tam jse mi ukazalo ze to byla BSOD... jen je divne ze jsem zadnou modrou obrazovku nevidel.. uz jsem premyslel napadlo me ze to treba neutahne zdroj.. jenze nevim co to presne BSOD je.. cpu mam stabilni v prime jel 8hodin tak fakt nevim cim to je... je to SW nebo HW chyba (chyba te tv karty) ? .... dik za rady

Analyzuj si minidump file a hned budes vedet, jestli je BSOD chyba sw (a jakyho) nebo HW

a mohl by jsi mi rict jak to provedu ??

Google vi, google zna....

Kód: Vybrat vše

http://www.memecode.com/docs/minidump.php

a tam pak

Kód: Vybrat vše

Analyse The MiniDump
To extract useful information out of the minidump file created:

   1. Open a command prompt (Start -> Run -> "cmd")
   2. cd \program files\debugging tools (Or wherever they are installed to)
   3. kd -z C:\WINDOWS\Minidump\Mini???????-??.dmp
   4. kd> .logopen c:\debuglog.txt
   5. kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
   6. kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
   7. You now have a debuglog.txt in c:\, open it in a text edit (Notepad?). 

Post Mortem
Look for the MODULE_NAME and IMAGE_NAME headings. This is the program that caused the error. Sometimes when it's a device driver it means that that device is causing the BSOD and by disabling it or updating the driver your system will run stable.

ale nejak to nechapu.. jak to mohla byt BSOD? kdyz sem zadnou modrou obrazovku nevidel.. proste jen hard reset ...

fakt nevim byla to BSOD ?

No doufej, ze tam BSOD mas zaznamenanej...

hm... ten debuglog je sam bug..
jediny co sme tim zjistil je
Opened log file 'c:/debuglog.txt'
kd> .sympath srv*c:/symbols*http://msdl.mirosoft.com/download/symbols
Symbol search path is: srv*c:/symbols*http://msdl.mirosoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;imnt;.logclose;q
..... ! OMFG

mohl by mi prosim nekdo ten minidump analyzovat ??:) tady je odkaz
Mini072108-01.dmp

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

Loading Dump File [C:\Mini072108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Program Files\Debugging Tools for Windows 64-bit\symbols
Executable search path is:
Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jul 21 15:21:41.062 2008 (GMT+2)
System Uptime: 0 days 3:18:54.628
Unable to load image 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 4E, {99, 5ef3a, 3, 0}

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

*** WARNING: Unable to verify timestamp for atkosdmini.dll
*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.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 ***
*** ***
*************************************************************************

Probably caused by : atkosdmini.dll ( atkosdmini+128b )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0005ef3a, page frame number
Arg3: 00000003, current page state
Arg4: 00000000, 0

Debugging Details:
------------------

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

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 431548df

BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 806411a2 to 804f8925

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a4fa765c 806411a2 0000004e 00000099 0005ef3a nt+0x21925
a4fa76a4 80505e0f 07271010 01deb1e0 00000003 nt+0x16a1a2
a4fa76b8 bf05128b 06f50010 88561008 a4fa7ac4 nt+0x2ee0f
a4fa7bb8 bf8855df a4fa7ce8 e13c19c0 00000000 atkosdmini+0x128b
a4fa7bf0 bf00bdbd a4fa7ce8 a4fa7d64 0012c0b4 win32k+0x855df
a4fa7d3c 8053c808 16200009 00186308 0012c1c8 dxg+0xbdbd
a4fa7d64 7c90eb94 badb0d00 0012c094 a53cdd98 nt+0x65808
a4fa7d68 badb0d00 0012c094 a53cdd98 a53cddcc 0x7c90eb94
a4fa7d6c 0012c094 a53cdd98 a53cddcc 00000000 0xbadb0d00
a4fa7d70 a53cdd98 a53cddcc 00000000 00000000 0x12c094
a4fa7d74 a53cddcc 00000000 00000000 00000000 0xa53cdd98
a4fa7d78 00000000 00000000 00000000 00000000 0xa53cddcc

STACK_COMMAND: kb

FOLLOWUP_IP:
atkosdmini+128b
bf05128b ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: atkosdmini+128b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atkosdmini

IMAGE_NAME: atkosdmini.dll

BUCKET_ID: WRONG_SYMBOLS

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

moc dík...tet by me jen zajimalo podle toho jak ctu..tak je to SW chyba ? a konkretne SW

MODULE_NAME: atkosdmini

IMAGE_NAME: atkosdmini.dl
nebo se mylim a je to HW chyba... jen jeste v tomhle me ujistete

jesli je to SW nebo HW jesli je to hw chyba tak to neak vyresim.. jesli sw tak me to nezajima protoze asi budu muset reinstalovat win... uz tolik driveru na vse sem skousel atd.. takze bych se nedivil..

jen fakt se mi nehce verit zda to byla BSOD protoze sem modrou obrazovku s chybou nevidel... i tohle muze byt bsod ? ze to je jen jako hard reset ??:)
dik...

ja totiz windows moc nerozumim drive sem pouzival ubuntu..

a win jen na hrani.. tet uz ubuntu nemam...BSOD sem zazil naposledy na win 98.. tam to byla modra obrazovka z textem a pak reset ale tady nic ...(

Hele, ono vazne staci hledat, opet google vi, google zna...

zadal sem googlu frazi "atkosdmini" a vyplado mi

Kód: Vybrat vše

http://www.google.cz/search?q=atkosdmini&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:cs:official&client=firefox-a

a hned prvni vysledky se o tom zminuji
viz

Kód: Vybrat vše

http://forums.techguy.org/windows-nt-2000-xp/669512-solved-irql_not_less_or_equal-when-trying-watch.html
http://www.bleepingcomputer.com/forums/lofiversion/index.php/t24959.html
http://forums.techguy.org/windows-nt-2000-xp/663529-bluescreen-video-playback-other-woes.html

Alias shazuje ti to nejaky asus enhanced driver a resenim je jej odistalovat (nebo zaktualizovat) a vse co s tim souvisi (zrejmne nejake doplnkove programy ASUS). Ale podobrobnosti si precti sam.

hm... sw chyba takze to resit nebudu.. zatim.. az budu reinstalovavat wokna tak tam ten driver nedam.. jenom sem zadnej BSOD nevidel... proste hard reset :d tak nevim no....protoze znamy mi rikal ze tam musi byt modra obrazovka a tu sem ja nemel..

PCTuning fórum

BSOD- SW nebo HW chyba ?

BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?

Re: BSOD- SW nebo HW chyba ?