Prev: Several Ntoskrnl BSOD crashes over the last week, but different stopcodes
Next: Windows can't handle NTFS on external hard disks?
From: Yousuf Khan on 11 Jan 2010 10:56
Mark Hobley wrote:
> Yousuf Khan <bbbl67(a)spammenot.yahoo.com> wrote:
>> The Windows crashes are spaced out 3 or 4 days apart, and I can't run
>> Ubuntu on it for this long to test it. This
>> particular system is a home server, it runs a few background apps that
>> are only available on Windows, so it is limited to running Ubuntu only
>> occasionally, like for example when Windows crashes. :-)
>
> To run a Windows application in Ubuntu:
>
> apt-get install wine


Already have it, and it does run a few apps, which is fine. But not the
one I need it to run (needs access to low-level hardware interfaces).
I've also been looking at getting Virtualbox to run on this thing, but I
don't really have time to get it working at the moment. And regardless,
when you have virtualization, you still need Windows.

Yousuf Khan
From: Yousuf Khan on 12 Jan 2010 10:02
Jose wrote:
> If you are using the small memory dump you will have that message.
>
> You need to adjust your Startup and Recovery Debugging information to
> do a complete memory dump and try again with a new dump file.
>
> Did you get nothing useful from !analyze -v


Okay, I've had another crash, and this time I got a full core dump
saved. It was the following Stop code:

BugCheck 24, {1902fe, f78beba0, f78be89c, b83fb504}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteCcb+84 )


I can't see anything particularly wrong when I run the Debugger's
"!verifier" command, and get the following output:

> 1: kd> !verifier
>
> Verify Level 9b ... enabled options are:
> Special pool
> Special irql
> All pool allocations checked on unload
> Io subsystem checking enabled
> DMA checking enabled
>
> Summary of All Verifier Statistics
>
> RaiseIrqls 0xd50089c4
> AcquireSpinLocks 0x6f16d5ff
> Synch Executions 0x0
> Trims 0x19e7df6
>
> Pool Allocations Attempted 0x426ff0e3
> Pool Allocations Succeeded 0x426ff0e3
> Pool Allocations Succeeded SpecialPool 0xddd6d41
> Pool Allocations With NO TAG 0x0
> Pool Allocations Failed 0x0
> Resource Allocations Failed Deliberately 0x0
>
> Current paged pool allocations 0x23b7f for 059076CC bytes
> Peak paged pool allocations 0x23b88 for 05910BDC bytes
> Current nonpaged pool allocations 0x29871 for 014AED80 bytes
> Peak nonpaged pool allocations 0x29888 for 014BF6E4 bytes

However, when I run the "!verifier 3" command, I get what looks like an
endless list of not-freed pool allocations. The list just scrolls off
the debugger window and there isn't enough to time or space to capture
them all. Is this normal?

Yousuf Khan
From: Peter Foldes on 12 Jan 2010 12:21
Yousuf

See the following
http://support.microsoft.com/kb/314477

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Yousuf Khan" <bbbl67(a)yahoo.com> wrote in message news:4b4a4b5e$1(a)news.bnb-lp.com...
> I've been attempting to get to the bottom of a recurring BSOD crash happening on
> my system. I've already had 4 crashes so far over the past two weeks. So I've
> identified that NTOSKRNL.EXE is involved in all of them so far. It always
> somewhere in the stack. So I enabled Driver Verifier on NTOSKRNL, as well as
> HAL.DLL, NTFS.SYS, and FLTMGR.SYS which were also identified on the stack during
> various of the events.
>
> Okay so I had my latest crash yesterday, and it occurred on NTOSKRNL as well. The
> Verifier was already enabled on the system prior to this crash, and then when go
> to Windbg and execute the "!verifier" command, it comes back with the message,
> "Unable to get verifier list". Why not, it should be enabled?
>
> When I check them on the command-prompt I get the following output back, and they
> confirm that all of the files are being monitored. So can somebody familiar with
> Driver Verifier and Windbg help me out here?
>
> Yousuf Khan
>
> ***
>
> >verifier /query
> 10/01/2010, 3:30:34 PM
> Level: 0000009B
> RaiseIrqls: 314843045
> AcquireSpinLocks: 1893615496
> SynchronizeExecutions: 0
> AllocationsAttempted: 90514901
> AllocationsSucceeded: 90514901
> AllocationsSucceededSpecialPool: 7614086
> AllocationsWithNoTag: 0
> AllocationsFailed: 0
> AllocationsFailedDeliberately: 0
> Trims: 2452146
> UnTrackedPool: 2872921
>
> Verified drivers:
>
> Name: ntoskrnl.exe, loads: 1, unloads: 0
> CurrentPagedPoolAllocations: 83397
> CurrentNonPagedPoolAllocations: 77485
> PeakPagedPoolAllocations: 87305
> PeakNonPagedPoolAllocations: 77674
> PagedPoolUsageInBytes: 49624396
> NonPagedPoolUsageInBytes: 11791484
> PeakPagedPoolUsageInBytes: 49827760
> PeakNonPagedPoolUsageInBytes: 12139000
>
> Name: hal.dll, loads: 1, unloads: 0
> CurrentPagedPoolAllocations: 0
> CurrentNonPagedPoolAllocations: 4
> PeakPagedPoolAllocations: 8
> PeakNonPagedPoolAllocations: 6
> PagedPoolUsageInBytes: 0
> NonPagedPoolUsageInBytes: 992
> PeakPagedPoolUsageInBytes: 768
> PeakNonPagedPoolUsageInBytes: 32784
>
> Name: fltmgr.sys, loads: 1, unloads: 0
> CurrentPagedPoolAllocations: 2
> CurrentNonPagedPoolAllocations: 7161
> PeakPagedPoolAllocations: 16
> PeakNonPagedPoolAllocations: 7173
> PagedPoolUsageInBytes: 16
> NonPagedPoolUsageInBytes: 1166244
> PeakPagedPoolUsageInBytes: 3440
> PeakNonPagedPoolUsageInBytes: 1169508
>
> Name: ntfs.sys, loads: 1, unloads: 0
> CurrentPagedPoolAllocations: 32443
> CurrentNonPagedPoolAllocations: 28514
> PeakPagedPoolAllocations: 33133
> PeakNonPagedPoolAllocations: 29174
> PagedPoolUsageInBytes: 9261776
> NonPagedPoolUsageInBytes: 1880368
> PeakPagedPoolUsageInBytes: 9472944
> PeakNonPagedPoolUsageInBytes: 1965028

First  |  Prev  | 
Pages: 1 2 3
Prev: Several Ntoskrnl BSOD crashes over the last week, but different stopcodes
Next: Windows can't handle NTFS on external hard disks?