BSOD - podle analyzi ntfs.sys & ntkrnlpa.exe

[KaBecko]

Zdravim, mam tu od znameho jeden notebook (Toshiba satellite L300d). Pro prohlednuti minidumpu, jsem se zdesil, kolik BSOD mu to zpusobuje. Podle enalyzi WhoCrashed jsem nasel mnoho problemu s AVG (vyreseno) a prave s ntfs.sys a ntkrnlpa.exe.
Bohuzel s temito si nevim moc rady. Tipuju to na nejake ovladace, ale tezko odhadovat. Analyzu BSOD delam snad po druhe v zivote. Za jakykoliv tip budu moc vdecny.

Prikladam samozrejme soubory z minidumpu v raru (bylo jich mnoho) a vypis z WhoCrashed.



computer name: PAVEL-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57 AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3084521472 total
VM: 2147352576, free: 1993383936



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 30.9.2011 10:02:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-50700-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x8E9F0)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
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 which cannot be identified at this time.


On Fri 30.9.2011 10:02:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x8E9F0)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
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 which cannot be identified at this time.


On Thu 29.9.2011 21:17:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093011-51932-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Sat 24.9.2011 16:07:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092511-58656-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1AA7B)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
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 which cannot be identified at this time.


On Fri 16.9.2011 14:40:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091711-37377-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x744E)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 which cannot be identified at this time.


On Wed 14.9.2011 20:07:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091511-24804-01.dmp
This was probably caused by the following module: avgidsshim.sys (AVGIDSShim+0x18D4)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\avgidsshim.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Loader 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsshim.sys (IDS Application Activity Monitor Loader Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsshim.sys AVG Technologies CZ, s.r.o. BAD_POOL_HEADER




On Wed 14.9.2011 17:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091411-27268-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1197E)
Bugcheck code: 0xA (0x100007F, 0x2, 0x1, 0xFFFFFFFF82AB41B9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Wed 14.9.2011 8:45:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091411-26176-01.dmp
This was probably caused by the following module: avgidsdriver.sys (AVGIDSDriver+0x947C)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF82B637FF)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\avgidsdriver.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsdriver.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsdriver.sys AVG Technologies CZ, s.r.o. DRIVER_CORRUPTED_EXPOOL




On Thu 8.9.2011 20:36:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090811-34335-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Wed 7.9.2011 16:15:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090711-30342-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x12296)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520DB00, 0x9600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 which cannot be identified at this time.


On Sun 4.9.2011 12:08:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090411-40872-01.dmp
This was probably caused by the following module: avgidsdriver.sys (AVGIDSDriver+0x9410)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82B42D30, 0xFFFFFFFF82B42D30, 0xFFFFFFFFA1FF8B89)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\avgidsdriver.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgidsdriver.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsdriver.sys AVG Technologies CZ, s.r.o. BAD_POOL_HEADER




On Wed 31.8.2011 14:47:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083111-39437-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520DB00, 0x19600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Tue 9.8.2011 18:27:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-25958-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xCC0C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8520D308, 0xFFFFFFFF85009120, 0xFFFFFFFFEFE086CD)
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 which cannot be identified at this time.


On Tue 9.8.2011 15:51:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080911-26598-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1AFE)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8520D000, 0xFFFFFFFF8520D300, 0x8600000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
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 which cannot be identified at this time.


On Sat 30.7.2011 4:56:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073011-40950-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0x28, 0x2, 0x1, 0xFFFFFFFF82A730E9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

51 crash dumps have been found and analyzed. Only 15 are included in this report. 5 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

avgidsshim.sys (IDS Application Activity Monitor Loader Driver., AVG Technologies CZ, s.r.o. )

avgidsfilter.sys (IDS Application Activity Monitor Filter Driver., AVG Technologies CZ, s.r.o. )

avgtdix.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)

rtl8187b.sys (Realtek RTL8187B NDIS Driver, Realtek Semiconductor Corporation )

avgidsdriver.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. )

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[KaBecko]

Nejak mi neslo vlozit ten .rar proto sem ho upnul na leteckou postu.
LINK: http://leteckaposta.cz/115843873

[StrejdaProšek]

Ahoj přednostně doporučím otestovat paměti pomocí:
http://www.viry.cz/forum/viewtopic.php?f=53&t=106788

Proveď test několikrát za sebou (nevh ho běžet například přes noc) pokud se neobjeví nějaká chyba budeme pokračovat ve zjišťování chyb.

[KaBecko]

Pameti jsou OK. Projeto memtestem pres 15 hodin >> 0 error. Disk zkontrolovan pomoci HD tune, opet zadna chyba. Urcite se neprehriva (ntb byl rozdelan a zaneseni minimalni). Bude tam nekde softwarova chybka... Podle reportu AVG, co sem nagooglil, tak za urcitou cast problemu mohl i ovladac k bezdratu (aktualizovan).

[StrejdaProšek]

V tom případě doporučím nainstalovat program slimdrivers:
http://download.cnet.com/SlimDrivers-Fr ... 79940.html
Doinstaluje ti chybějící ovladače.
Potom by to chtělo nahradit soubor ntfs.sys z instalačního média Windows.

[KaBecko]

Děkuji, omlouvam se, ze reaguji az ted. Byl jsem mimo PC. Tento program určitě zkusím. Zkoušel jsem nainstalovat znovu cely system (format disku + reinstall WIN 7). Nainstalovany jen ovladace na GF ATI RADEON X1200 + ovladace na touchped. Jinak par programu od apple + autocad, invertor atd.. Nic co by mohlo zpusovat kolizi se systemem, jako AVG atd.. (aspon myslim) Modra smrt se opet ukazala

Jinak prikladam minidump z posledniho padu.
http://leteckaposta.cz/703748082

[StrejdaProšek]

Znovu je problém se souborem ntfs.sys, podle všeho je na vině nějaký driver.
Dej Start >> eventvwr.msc
A zde se podívej do protokolů, jestli tam nejsou nějaké chybové hlášení.
Použij ten program slimdrivers na aktualizaci všech driverů.
Potom napiš

[KaBecko]

Pouzil jsem ten programek slimdrivers a zatim vse bezi v pohode. Uvidim, kdyby neco, zase se ozvu. Dekuji moc za pomoc.

[StrejdaProšek]

Zatím nemáš vůbec zač a kdyby něco tak naše fórum je tu příště zas