BSOD Stop: 0x00...0109. With minidump.

Status
Not open for further replies.
I

ImmoDuck

Posts: 19   +0
I've been getting constant BSOD with no idea as to what the cause could be. I've memtested my RAM, formatted my drive, etc. to no avail. This is my first time getting a minidump on here, but I think I may have done it correctly, using the thread on how to read minidumps as a guide.

Here's my debuglog.txt:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800473e3d0, The pool entry we were looking for within the page.
Arg3: fffffa800473e4e0, The next pool entry.
Arg4: 0000000004110005, (reserved)

Debugging Details:
------------------


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fffffa800473e3d0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000199a05d to fffff800018ba390

STACK_TEXT:
fffffa60`017967b8 fffff800`0199a05d : 00000000`00000019 00000000`00000020 fffffa80`0473e3d0 fffffa80`0473e4e0 : nt!KeBugCheckEx
fffffa60`017967c0 fffffa60`00a10baa : 00000000`00000000 fffffa60`00a55703 00000000`00000000 fffff880`41677641 : nt!ExDeferredFreePool+0x9db
fffffa60`01796870 fffffa60`00a11f49 : fffffa80`0473e3e0 fffffa60`00a0a65f 00000000`00000003 fffff880`072cf5a0 : fltmgr!ExFreeToPagedLookasideList+0x2a
fffffa60`017968a0 fffffa60`00a13261 : fffffa80`0473e3e0 00000000`00000004 00000000`00000000 ffffffff`ffffffff : fltmgr!DoFreeContextMemory+0x79
fffffa60`017968d0 fffffa60`00a2bc04 : fffffa80`0473e3f8 fffffa60`00a06000 00000000`00000000 fffffa60`01796a00 : fltmgr!DoFreeContext+0x71
fffffa60`01796900 fffffa60`00a27ac1 : fffffa80`04abf8d0 fffffa80`03549180 fffff880`0c8cba10 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0xd80
fffffa60`01796930 fffffa60`00a27bac : fffffa80`04abf8d0 fffffa80`03549180 fffff880`0633eb01 fffffa80`04abf8d0 : fltmgr!CleanupStreamListCtrl+0x21
fffffa60`01796970 fffff800`01b23d06 : 00000000`00000000 fffff800`0189930e fffff880`0633ee00 fffff880`0633eb50 : fltmgr!DeleteStreamListCtrlCallback+0x6c
fffffa60`017969a0 fffffa60`010c7936 : fffff880`0c8cba10 fffffa60`01796a88 00000000`00000705 fffff880`0c8cb8e0 : nt!FsRtlTeardownPerStreamContexts+0xca
fffffa60`017969f0 fffffa60`01017579 : fffff880`0633ef68 fffff880`0c8cb8e0 00000000`00000000 fffff880`0633eed8 : Ntfs!NtfsDeleteScb+0xe6
fffffa60`01796a30 fffffa60`010c768b : fffff880`0c8cb8e0 fffff880`0c8cba10 fffff880`0c8cb800 fffff880`0633eed8 : Ntfs!NtfsPrepareFcbForRemoval+0x89
fffffa60`01796a80 fffffa60`0101eb92 : fffffa80`037c06f0 fffffa60`01796c70 fffff880`0c8cbc68 fffff880`0c8cb8e0 : Ntfs!NtfsTeardownStructures+0x8b
fffffa60`01796b10 fffffa60`010d2e18 : 00000000`00000000 fffff800`019f78a0 fffff880`0c8cb8e0 00000000`6366744e : Ntfs!NtfsDecrementCloseCounts+0xa2
fffffa60`01796b50 fffffa60`010bbe0e : fffffa80`037c06f0 fffff880`0c8cba10 fffff880`0c8cb8e0 fffffa80`03549180 : Ntfs!NtfsCommonClose+0x348
fffffa60`01796c20 fffff800`018c7066 : 00000000`00000000 fffff800`01a63800 fffffa80`02e42101 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15e
fffffa60`01796cf0 fffff800`01addde3 : fffffa60`0106cee8 00000000`00000000 fffffa80`024a3720 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`01796d50 fffff800`018f4536 : fffffa60`005ec180 fffffa80`024a3720 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01796d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
fltmgr!ExFreeToPagedLookasideList+2a
fffffa60`00a10baa eb0c jmp fltmgr!ExFreeToPagedLookasideList+0x38 (fffffa60`00a10bb8)

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: fltmgr!ExFreeToPagedLookasideList+2a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME: fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47919082

FAILURE_BUCKET_ID: X64_0x19_20_fltmgr!ExFreeToPagedLookasideList+2a

BUCKET_ID: X64_0x19_20_fltmgr!ExFreeToPagedLookasideList+2a

------------------------------------------

Could anyone help me out? If I'm missing anything, let me know.
 
0x19 errors are caused by device driver issues (and are probably the msot common), but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers.

1. When do you receive these errors?

2. Run a full harddrive diagnostics by using the free utility from your HD manufacturer.

If your HD is going or has bad sectors no amount of reformatting will help. let us know how the diagnostic analysis went.
 
Hey, thanks for the help. To answer question 1, I receive it at any time, it is entirely random to be honest. As for question number 2, how I find my hard drive manufacturer? Would it be HP, as I am using a hard drive from an old computer I had from them in my new custom computer?
 
HP buys their harddrives so look and see if you find a name brand. That will be your manufacturer. There is a really cool little utility simply called SIW. It is free and free of any adwaere, etc. Download and install. Often it will tell you make and model of your components. Go to your harrdrive manufacturer's website and download and install diagnostics utility and run it. This takes time.

It wouldn't hurt to run memTest on your RAM.
 
I've done a couple short tests with the diagnostic tool from Seagate for my HD, and now currently working on a long one. Just wanted to confirm that I did do a few memtests the other day with no errors. Also, the BSOD is random, however it seems to occur much more when I play games. I was just playing Neverwinter Nights and got 2 BSOD's in a very short time period.

Thanks a lot for the help so far, again.
 
How long did you run memTest? A minimum of 7 passes is the standard and keep in mind faulty RAM has been to pass.

I am wondering if you have a need for different viseo drivers.
 
Yes, definitely do it overnight. I personally know of those who ran it 5 times and found no errors and stopped but on the 6th Pass they found errors. I am not saying you'll find errors but it sure helps to know.

Place your system specs so we can take a look. If you have any more BSOD minifiles attach them.
 
System Specs:

GA-P35-DS3L Mobo
Intel Dual Core E2200 2.20GHz, before overclocked, but reset BIOS to defaults
2 GB Crucial Ballistix stable ram, got two more I haven't tested yet.
8800GT GeForce vidcard
500 or 550W PSU.
Vista x64

In the next post I'll put the last two BSOD minidumps in rapidshare.
 
Very few of us can open Rapidshare. Attach those minidumps here and Zip as needed (5 minidump files to 1 zip file).

When I see Crucial Ballistix a major Red Flag pops up because in both their DDR offerings and their DDR2 offerings TONS of people were having issues. I speak from personal experience plus what I have read from other tech forums across the 'net.

Run Memtest again for at least a minimum of 7 passes on each individual stick. Your crashes are suspiciously sounding like corrupted memory. But attach those minidumps.
 
I attached the zip of the last three minidumps, as the one before it was the first one posted in the beginning of the thread. I'll run the memtest overnight and tell you what I get tomorrow.
 
All 3 minidumps: CRITICAL_STRUCTURE_CORRUPTION (109)

This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:

1) A driver has inadvertently or deliberately modified critical kernel code
or data. Microsoft has an artical about 0x109 and patching Vista. The link didn't take. Sorry.

2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.

3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
 
So what could I do to fix it? I did the memtest overnight, and had 9 passes, 0 errors, so I don't think it's the RAM.
 
Update: I think it may have been my GeForce drivers. I had several unsigned drivers do to an update from them, and I just rolled back and I haven't BSOD all day. I'll leave it on overnight to see if it changes, too. But, how can I update to a working driver, because with mine rolled back I can't really play games.
 
Find the latest drivers from Nvidia that will work with your card and Vista 64 and download them to your desktop.

Find Driver Cleaner Pro free edition and download and install.

Uninstall your video card drivers.

Reboot into safe mode and let Driver Cleaner Pro search for any Nvidia drivers and clean. If it doesn't find anything that is quite okay.

Reboot again into normal mode. Don't let Windows install their version of drivers.

Intall the latest.

Let us know if that brings stability and if you can game.
 
I did all of that twice, but my computer still lags now when playing games. All my drivers are signed now, and I think having the unsigned drivers may have caused the BSOD before, but now my computer runs games/movies terribly, even with the newest nVidia drivers.

I did the Driver Cleaner pro thing for about an hour, but it became unresponsive so I just closed out and rebooted, and it said all my video card drivers had been erased, so I guess it worked. But after I installed the latest drivers, while disconnected from the internet so windows wouldn't install any, it still runs just as poorly.
 
Hmmm, somethings not right considering your system and especially your video card. Are you maxing out on resolution settings?
 
Just doing the standard old 1280x1024, and Neverwinter Nights is a considerably old game, my computer should have no problem running it. I'm not sure the cause at all.
 
Let's go a different rout just for curiosity sake. Scan for malware/viruses. Sometimes they can bring slowdowns.

One other question, are you receiving these slow downs when running more modern games/software?
 
I'll run a virus scan when I get back home. I just tried playing Fable, and it immediately BSOD'd again, with a new error, I think. I have the minidump file and attached it, I think it may be my drivers still.

If need be, I could possibly format my drive as a last option.
 
It's been a couple days with no replies, and I'm still having the issues. I tried formatting and installing from scrap, and still no dice.
 
Status
Not open for further replies.

Similar threads

P
BSoD upon non safe mode booting
Replies
2
Views
2K
patricia016
P
S
BSOD - help with minidump analysis
Replies
6
Views
3K
sphinx227
S
MacunRc
BSOD bad pool caller (c2) Windows10
Replies
6
Views
4K
Tmagic650
Tmagic650

Latest posts

Back