Prev: Replacement hard drive problem/ account access
Next: Several Ntoskrnl BSOD crashes over the last week, but different stop codes
From: Yousuf Khan on 7 Jan 2010 10:25
I've experienced 3 different BSOD's in the last week. I've started using
the Microsoft Windbg debugger to trace through them. I'm also using a
3rd party utility called BlueScreenView in addition to Windbg for
analysis. Each crash has a different Stop code number, but so far they
all seem to have a common origin in the NTOSKRNL.EXE installed with
Windows XP SP3. Meanwhile, HAL.DLL is involved with 2 of the 3 crashes
so far.

The first BSOD occurred on Dec 29th, 2009 and the most recent occurred
last night, Jan 6th, 2010. There were some previous BSOD's even before
that, but I didn't have the save kernel dump feature turned on, so I
missed those early ones.

Question is should I roll back to an earlier version of NTOSKRNL, and if
so which patch was it installed with?

Yousuf Khan

***
The following are the summaries of each mini-dump:

(1) 31/12/2009 9:27:06 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0x8b55ffaf
Parameter 2 : 0x00000000
Parameter 3 : 0x804f1b2c
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2aa8
File Description : Hardware Abstraction Layer DLL

Stack:
hal.dll+2aa8
ntoskrnl.exe+1db2c

(2) 02/01/2010 9:49:05 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x8942aab8
Parameter 3 : 0x8942af40
Parameter 4 : 0x8a915628
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6067a

Stack:
Ntfs.sys+212aa
ntoskrnl.exe+6067a

(3) 06/01/2010 11:22:38 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x00000c3e
Parameter 3 : 0x000027ca
Parameter 4 : 0x8ab31114
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+14e3f

Stack:
fltmgr.sys+14e3f
hal.dll+2900
ntoskrnl.exe+909b4
 | 
Pages: 1
Prev: Replacement hard drive problem/ account access
Next: Several Ntoskrnl BSOD crashes over the last week, but different stop codes