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
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.
PC - CPU: Intel Core i5-4670K MB: MSI Z87-G45 Gaming RAM: Kingston KVR1333D3N9K2/8G GPU: Asus Radeon HD7970 3 GB HDD: Kingston SVP100/96GR, Samsung SpinPoint F3 HD502HJ, Western-Digital WD20EARS PSU: Corsair HX750 Chladiče: AC Freezer 13 Pro, 2x AC F9 PWM, 2x AC F12, AC F12 Pro PWM DVD-RW: Samusng SH-S223C Case: Thermaltake Armor VA8003BWS Monitor: LG IPS236V Keyb: Logitech Wave Keyboard Myš: Logitech MX610 Left-Hand OS: Microsoft Windows 7 Professional x86-64 Notebook - Lenovo ThinkPad E530
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 )
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 ***
*** ***
*************************************************************************
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 ...(
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.
PC - CPU: Intel Core i5-4670K MB: MSI Z87-G45 Gaming RAM: Kingston KVR1333D3N9K2/8G GPU: Asus Radeon HD7970 3 GB HDD: Kingston SVP100/96GR, Samsung SpinPoint F3 HD502HJ, Western-Digital WD20EARS PSU: Corsair HX750 Chladiče: AC Freezer 13 Pro, 2x AC F9 PWM, 2x AC F12, AC F12 Pro PWM DVD-RW: Samusng SH-S223C Case: Thermaltake Armor VA8003BWS Monitor: LG IPS236V Keyb: Logitech Wave Keyboard Myš: Logitech MX610 Left-Hand OS: Microsoft Windows 7 Professional x86-64 Notebook - Lenovo ThinkPad E530
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..
fakt nevim byla to BSOD ?
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..
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 ...(