BSOD - help needed understanding dump files

Toggle sidebar Toggle sidebar
Solution
J
-most likely a driver is corrupting system memory and causing another driver to crash.
- remove unused raid controller drivers, update various drivers from HP. Particularly the realtek card media driver if it is out of date.

-if you continue getting the errors you might want to confirm your memory settings are ok with memtests86
(most likely ok) but if the memory is ok, and you remove/update the drivers that you can then all you can do is try to track down the bad driver using driver verifier.exe and a kernel memory dump (rather than a mini dump)



-------------
pretty strange system you have there. You have 5 or 6 different Raid drivers loaded.
and some of them are really old. 2006, 2007, 2008.

I would also check or disable ...
Sort by date Sort by votes
P

pmurray0

Reputable
Feb 13, 2015
4
0
4,510
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 2/13/2015 2:54:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021215-17206-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003114A70, 0xFFFFF8800C910B10, 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 that cannot be identified at this time.



On Wed 2/11/2015 5:34:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021115-32495-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFA80000032FF)
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 that cannot be identified at this time.



On Wed 2/11/2015 5:11:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021115-56815-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x7, 0xFFFFFA8000009C0A)
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 that cannot be identified at this time.



On Fri 2/6/2015 6:47:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020615-15927-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880032F0698, 0xFFFFF880032EFEF0, 0xFFFFF80003097F81)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.



On Fri 2/6/2015 6:39:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020615-14383-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003463C7B, 0xFFFFF88021353EE0, 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 that cannot be identified at this time.



On Tue 2/3/2015 9:44:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020315-17269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88003920350, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2/3/2015 8:56:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020315-16005-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x34 (0x71C, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 a problem occurred in the file system's cache manager.
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 that cannot be identified at this time.



On Tue 2/3/2015 7:46:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020315-15958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008663A30, 0xFFFFFA8008663AF0, 0xC0C000C)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 1/27/2015 9:12:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012715-14898-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007A920E0, 0xFFFFFA8007A92190, 0x40B000E)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 1/25/2015 11:02:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012515-20124-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0x19 (0x20, 0xFFFFFA80041EC6A0, 0xFFFFFA80041EC740, 0x40A0004)
Error: BAD_POOL_HEADER
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-most likely a driver is corrupting system memory and causing another driver to crash.
- remove unused raid controller drivers, update various drivers from HP. Particularly the realtek card media driver if it is out of date.

-if you continue getting the errors you might want to confirm your memory settings are ok with memtests86
(most likely ok) but if the memory is ok, and you remove/update the drivers that you can then all you can do is try to track down the bad driver using driver verifier.exe and a kernel memory dump (rather than a mini dump)



-------------
pretty strange system you have there. You have 5 or 6 different Raid drivers loaded.
and some of them are really old. 2006, 2007, 2008.

I would also check or disable : Realtek Pcie CardReader Driver for 2K/XP/Vista/Win7
some of the older versions tended to corrupt memory.

go here and pick up new drivers:
http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=6943835&swLangOid=8&swEnvOid=4059

I would also remove any raid driver you are not using.

 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom