Dá se zpětně dohledat, proč došlo k BSOD?*

[.:M@rt!n:.]

Ahoj,
před chvilkou na mě vyskočil BSOD a PC se restartovalo. Jelikož mám nové pc, tak jsem byl tak překvapen, že jsem si ani nestihl všimnou z jakého důvodu se to stalo. Dá se zpětně dohledat, proč se to stalo?

díky

//prodloužen název

//mmmartin

[Reklama]

[tux]

Jo.
C:\Windows\Minidump\*název souboru*.dmp
Ale musíš vědět jak to z toho vyčíst, tady z fóra to umí například uživatel MiliNess.

[Žbeky]

Stáhni si a nainstaluj WhoCrashed
Otevři ho a klikni na Analyze. Program vytvoří zprávu, celou ji zkopíruj a vlož prosím sem.

[.:M@rt!n:.]

Tady to je:
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 21.12.2012 13:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122112-5148-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0144705D0, 0xFFFFF8A014470ED0, 0x5D9004C0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 21.12.2012 13:01:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x31F06)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0144705D0, 0xFFFFF8A014470ED0, 0x5D9004C0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

[MiliNess]

Upneš mi ty soubory ze složky C:\Windows\Minidump na www.leteckaposta.cz?

[.:M@rt!n:.]

Jj upnu, ale az tak v nedeli na vecer. Ted nejsem doma na pc

[MiliNess]

Ok

[.:M@rt!n:.]

tak tady to je: http://leteckaposta.cz/804430101 Byl tam jen tenhle jeden soubor

[MiliNess]

Nedá se z toho zjistit nic konkrétního. Prostě chybná velikost bloku v hlavičce bloku paměťového fondu.
Nejprve udělej test paměti.
Netaktuješ?

Také zaRARuj a upni soubor Windows\Memory.dmp.

[.:M@rt!n:.]

Paměť se zdá být v pořádku.
Netaktuji.
tady je ten soubor: http://leteckaposta.cz/616625462