BSOD - ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

[blackpuffle]

Zdravím.. Pořád mi systém háže BSOD... Naposledy ještě před tím, než jsem se stačil přihlásit na účet..
Mám log z WhoCrashed:
On Sat 19.1.2013 10:17:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC5 (0x11253A, 0x2, 0x0, 0xFFFFF800031F7B05)
Error: DRIVER_CORRUPTED_EXPOOL
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

V adresáři minidump jsem žádný soubor nenašel.

Co mám odstranit? Co zakázat? A jak? Jen prosím, až už nemám BSOD, je to hrozně otravný! Nedávno jsem projížděl notebook přes noc memtestem a ten nic nenašel.. Děkuji moc za pomoc..

[Rudy]

Také zdravím!
Pošlete s vaším příštím postem soubor C:\Windows\memory.dmp . Vlákno přesouvám do správné sekce.

[blackpuffle]

Ale ten soubor má 784 MB.. Můžu ho uploadnout na uloz.to?
edit: V archivu má jen 137 MB
edit2: Nechce se mi to ani nahrát na uloz.to.. Mám nestabilní internet :/

[Rudy]

OK. Budeme tedy vycházet z dostupných informací. Nemáte v PC něco přetaktováno? Pokud ano, vraťte taktování na defaultní hodnotu. Pokud ne, přeinstalujte ovladače základní desky.

[blackpuffle]

Nic jsem v notebooku netaktoval.. Nebo pokud software něco taktoval automaticky, tak o tom nevím.. Který z těchto ovladačů mám nainstalovat?

drivers.png (34 KiB) Zobrazeno 6727 x

Ovladače jsou původní.. Byly už na disku, když jsem notebook koupil..

[Rudy]

Chipset.

[blackpuffle]

Napsalo mi to, že byl úspěšně nainstalován do počítače.. Co dál?

[Rudy]

Vyčkejte, zda se problém bude opakovat.

[blackpuffle]

Dobře, když tak založit nové vlákno nebo pokračovat v tomhle?

[Rudy]

Zatím to tu ponechám otevřené.

[blackpuffle]

Tak mi BSOD naskočilo hned po startu systému.. Jak se načítá systém a skáče do obrazovky s uživateli, tak to do ní neskočilo a nahodilo se BSOD. Log z WhoCrashed není, nic se nezapsalo..
edit: Co koukám, tak se mi dnes nainstalovala důležitá aktualizace (12:05:55)

[Rudy]

Problém nastal po té aktualizaci, nebo před ní?

[blackpuffle]

i před ní mi skočil. Ale jak se nainstalovala aktualizace a vypnul se počítač (manuálně). Potom se zapl a už nenaskočili ani účty. Musel jsem dát Poslední známou funkční kofiguraci. Počítač jsem vrátil do doby před aktualizací. Nechcete z něčeho nějaký log, aby se dalo něco smazat nebo tak?

[Rudy]

Stáhněte, nainstalujte a spusťte CrystalDiskInfo: http://www.stahuj.centrum.cz/utility_a_ ... ldiskinfo/ a přes Úpravy>kopírovat sem dejte log.

[blackpuffle]

No, tak mi to hodilo znova BSOD.. Když jsem se podíval do WhoCrashed, tak se tam zázrakem objevili všechny logy:

On Mon 21.1.2013 18:39:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012113-44522-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0xCD29)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800001ADA0, 0xFFFFFA800001B550, 0x47BD68A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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 Mon 21.1.2013 18:39:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: networx.sys (networx+0x701A)
Bugcheck code: 0x19 (0x20, 0xFFFFFA800001ADA0, 0xFFFFFA800001B550, 0x47BD68A)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\networx.sys
product: NetFilter SDK
company: NetFilterSDK.com
description: NetFilter SDK TDI Hook Driver (WPP)
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: networx.sys (NetFilter SDK TDI Hook Driver (WPP), NetFilterSDK.com).
Google query: networx.sys NetFilterSDK.com BAD_POOL_HEADER




On Wed 16.1.2013 17:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-19843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8007AC2970, 0xFFFFF800049893D8, 0xFFFFFA80075AC010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.


On Wed 16.1.2013 17:12:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-48641-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC5 (0xFFFFFA7FFFFFFFF1, 0x2, 0x0, 0xFFFFF8000320E9BF)
Error: DRIVER_CORRUPTED_EXPOOL
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 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.
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 16.1.2013 6:43:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-56643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030D1EC5, 0xFFFFF8800CCFAE20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.


On Thu 10.1.2013 16:07:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-25896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA80079152C0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.


On Mon 7.1.2013 17:21:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010713-47330-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800A0F4710)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.


On Wed 2.1.2013 10:19:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010213-21715-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800722D030)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.


On Fri 28.12.2012 14:24:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122812-19812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800C404C20)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.


On Sat 22.12.2012 17:52:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122212-35069-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800E1186D0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.


On Tue 18.12.2012 15:50:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121812-52728-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA800A2C4710)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.



CrystalDiskInfo hned pošlu