Sign in with
Sign up | Sign in
Your question

BSOD - Bad pool header

Last response: in Windows 7
Share
October 16, 2012 9:22:34 PM

Hello people! i've just recently started getting LOTS of BSOD when im streaming for example, and some at just random times.
It usually says as a head line i suppose "bad pool header" i've tried reading other forums but i cant find any good solutions on them. Would appriciate help :D  , im using Windows 7 ultimate 64 bit

More about : bsod bad pool header

October 16, 2012 10:38:58 PM

I got this error recently. It was bad ram.
m
0
l
Related resources
October 16, 2012 10:39:37 PM

Hello and thanks, I've tested that program, it says this :

On Tue 10/16/2012 7:56:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101612-7753-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6051)
Bugcheck code: 0x19 (0x21, 0xFFFFF900C20BD000, 0x1240, 0x10001240)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.
m
0
l
October 17, 2012 11:06:23 AM

When i try to install it the update says "The update is not applicable for your computer" and i have to turn it down, i searched through my installed updates but cant find it there
m
0
l
October 17, 2012 11:12:14 AM

I will try to push my computer, thats when it usually gets the BSOD, when im streaming and playing it usually crashes with BSOD. Ill come back with the answer later on!
m
0
l
a b $ Windows 7
October 17, 2012 11:25:54 AM

try running memtest on the ram to rule it out.
m
0
l
October 17, 2012 11:48:08 AM

I've done one of those hard drive check, went fine, havent done a memtest though, ill try it later today! ill come back with results! thank you for advice smorizio
m
0
l
October 17, 2012 2:28:40 PM

On Wed 10/17/2012 14:23:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-8190-01.dmp
This was probably caused by the following module: asmtxhci.sys (asmtxhci+0x1BBF6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800FDB5BF6, 0xFFFFF8800C627708, 0xFFFFF8800C626F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\asmtxhci.sys
product: ASMedia USB 3.0 Host Drivers
company: ASMedia Technology Inc
description: ASMEDIA XHCI Host Controller Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: asmtxhci.sys (ASMEDIA XHCI Host Controller Driver, ASMedia Technology Inc).
Google query: asmtxhci.sys ASMedia Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




AND


On Wed 10/17/2012 14:23:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: asmtxhci.sys (asmtxhci+0x1BBF6)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800FDB5BF6, 0xFFFFF8800C627708, 0xFFFFF8800C626F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\asmtxhci.sys
product: ASMedia USB 3.0 Host Drivers
company: ASMedia Technology Inc
description: ASMEDIA XHCI Host Controller Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: asmtxhci.sys (ASMEDIA XHCI Host Controller Driver, ASMedia Technology Inc).
Google query: asmtxhci.sys ASMedia Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



AND


On Wed 10/17/2012 14:10:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101712-8205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x99, 0x209E0C, 0x1, 0x5220C)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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.

m
0
l
October 17, 2012 3:09:14 PM

I just ran Memtest86, wasent any problem with that, done windows memory diagonstic also, no problem
m
0
l
October 17, 2012 3:48:21 PM

Also done Error checking on my C-disk and turned out without any problem aswell, i've stopped using USB 3.0 since they seemed to make me BSOD, still havent tested any hard cpu usage yet, ill come back if i still get BSOD's.

Got all drivers at latest updates aswell.
m
0
l
a b $ Windows 7
October 17, 2012 8:45:53 PM

the asmedia is the one in case seen on asus forum that there is a firware out in 2011 check with your board model if you could find that update on the maker or they maybe have a bios update for this
m
0
l
a b $ Windows 7
December 6, 2012 4:57:53 PM

sorry for bumping and old thread..saw some new info..check the sata ports your using from the crash dump files it looks like you have your drive plugged into the acmedia sata ports.
m
0
l
!