Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD DRIVER_CORRUPTED_MMPOOL


  • Please log in to reply
18 replies to this topic

#1 JCIM

JCIM

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 16 June 2010 - 10:27 AM

How can I fix this error?

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\jciminello\Desktop\Mini061610-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jun 16 07:19:30.000 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:54.734
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
......................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D0, {90028, 2, 1, 80548ed8}

Unable to load image Ntfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
Probably caused by : ntoskrnl.exe ( nt!CpDoesPortExist+42 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 00090028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80548ed8, address which referenced memory
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool. You can also set
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
to a DWORD 1 value and reboot. Then the system will unmap freed nonpaged pool,
preventing drivers (although not DMA-hardware) from corrupting the pool.

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


WRITE_ADDRESS: 00090028

CURRENT_IRQL: 2

FAULTING_IP:
nt!CpDoesPortExist+42
80548ed8 8908 mov dword ptr [eax],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD0

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8054b49a to 80548ed8

STACK_TEXT:
f7a8938c 8054b49a 85d80000 85d81000 85d8ae28 nt!CpDoesPortExist+0x42
f7a893cc f72c4ddb 85d80000 00000000 f7a895c4 nt!MiReleaseSystemPtes+0xe9
f7a893dc f72c4ffb 856e7380 85d80000 f72c4fc5 Ntfs!NtfsDeleteMdlAndBuffer+0x31
f7a893e0 856e7380 85d80000 f72c4fc5 804ef912 Ntfs!NtfsCommonWrite+0x1889
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a895c4 f72c4c18 f7a895d4 85d8ae28 0110070a 0x856e7380
f7a89738 804ef19f 867c5770 85d8ae28 85d8ae28 Ntfs!NtfsFsdWrite+0xf3
f7a89774 804ef19f 8674cee8 85d8ae28 85dda030 nt!MiFlushSectionInternal+0x256
f7a89794 804ef19f 86757020 85d8ae28 85d8ae28 nt!MiFlushSectionInternal+0x256
f7a897c8 f73cc06b f7a897e8 867e06e8 00000000 nt!MiFlushSectionInternal+0x256
f7a89800 804ef19f 867e06e8 85d8ae28 00000000 fltMgr!FltpDispatch+0x11f
f7a89824 f72e513c 86749b0a 86755538 f7a898c8 nt!MiFlushSectionInternal+0x256
f7a898f0 f72e5089 e1463930 e173f958 e12b13d8 Ntfs!LfsFlushLfcb+0x429
f7a89914 f72e651f e1463930 e173f958 867c5a60 Ntfs!LfsFlushLbcb+0x81
f7a8996c f72e5cf8 e1463930 000000e0 00000001 Ntfs!LfsWriteLfsRestart+0x16a
f7a899b8 f72e6278 e146e648 00000068 f7a89a20 Ntfs!LfsWriteRestartArea+0x158
f7a89be8 f72e6174 f7a89c1c 867c5850 00000000 Ntfs!NtfsCheckpointVolume+0xe0a
f7a89d7c 80538789 00000000 00000000 867c3340 Ntfs!NtfsCheckpointAllVolumes+0xd2
f7a89dac 805cff62 00000000 00000000 00000000 nt!MiTrimPte+0x20a
f7a89ddc 8054611e 8053869a 00000000 00000000 nt!IopQueryReconfiguration+0x15
f7a89df8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0xab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CpDoesPortExist+42
80548ed8 8908 mov dword ptr [eax],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CpDoesPortExist+42

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a9cac

FAILURE_BUCKET_ID: 0xD0_nt!CpDoesPortExist+42

BUCKET_ID: 0xD0_nt!CpDoesPortExist+42

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 16 June 2010 - 11:22 AM

Hi :thumbsup:.

Does the system boot into XP?

Boot into safe mode?

System manufacturer and model?

"You can also set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ProtectNonPagedPool
to a DWORD 1 value and reboot. Then the system will unmap freed nonpaged pool, preventing drivers (although not DMA-hardware) from corrupting the pool."

Did you try this? Not saying you should...just want to know if you did.

If the system boots (either normally or into safe mode), try this:

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All.

File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Louis

#3 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 16 June 2010 - 01:53 PM

Yes, I can boot normal. When I went to website nirsoft I received the following message - the request lookup key was not found in any active activation context

#4 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 16 June 2010 - 02:30 PM

==================================================
Dump File : Mini061610-01.dmp
Crash Time : 6/16/2010 7:22:19 AM
Bug Check String : DRIVER_CORRUPTED_MMPOOL
Bug Check Code : 0x100000d0
Parameter 1 : 0x00090028
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x80548ed8
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+1e3c
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini061610-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

EDIT: Deleted useless list of drivers without problems ~ Hamluis.

Edited by hamluis, 16 June 2010 - 03:16 PM.


#5 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 16 June 2010 - 03:22 PM

STOP errors (BSODs) involving ntfs.sys as the stated problem driver...are somewhat misleading.

Some can be overcome by running chkdsk /r...some are NTFS file system problems (may require format/clean install of the O/S...some may indicate hard drive problems.

IMO, it's a process of elimination.

Running chkdsk /r is easiest and may provide additional clues.

From within XP...Start/Run...type chkdsk /r (space between k and /) and hit Enter. Type Y in response to new screen and hit Enter. Reboot the system.

The chkdsk /r command will execute and then try to boot into XP on completion. If chkdsk /r cannot complete, it will give an error message. Write that message down, if it comes.

Louis

#6 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 17 June 2010 - 06:47 AM

Ran chkdsk /r with no errors.

#7 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 17 June 2010 - 08:52 AM

OK...now let's see if we can replace the current ntfs.sys file...on the premise that it is damaged and really is the cause for the STOP error.

Let's try to run the sfc /scannow command, using a CD reflecting the same version of Windows and SPs...as the system currently has.

How To Use Sfc.exe To Repair System Files - http://www.bleepingcomputer.com/forums/t/43051/how-to-use-sfcexe-to-repair-system-files/

Louis

#8 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 17 June 2010 - 10:16 AM

Ran sfc.exe /scannow. There were no errors. Should I try doing a windows xp repair with a different windows xp sp3 cd?

#9 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 17 June 2010 - 10:24 AM

<<Should I try doing a windows xp repair with a different windows xp sp3 cd?>>

I guess that I don't see the point...of using a "different windows xp sp3 cd"...did you use a Genuine XP CD reflecting the same SP as is currently installed on your system?

For all intents and purposes...running sfc /scannow and a repair install...result in the same outcome, damaged/missing system files are replaced.

FWIW: the sfc /scannow command doesn't detect errors, it merely replaces missing/damaged system files.

Louis

#10 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 17 June 2010 - 10:32 AM

I used a windows xp sp 3 that came from Dell different then the one original sent with the PC having the problem. Original was windows xp sp 2.

#11 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 17 June 2010 - 10:43 AM

Well...is the Dell CD a true copy of the XP install files?

Dell...muddies the water with the CDs it issues. Some are restore/recovery CDs, some are full copies of XP (as I understand it). Depends on what Dell's intent was for that system, at that time.

What system did the Dell CD come with?

For that matter...what is the manufacturer and model of the system in question here? If custom/self-built...what is the motherboard manufacturer and model?

Louis

#12 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 17 June 2010 - 11:41 AM

Dell Precision T3400. The cd is a reinstall cd.

Edited by JCIM, 17 June 2010 - 11:42 AM.


#13 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 17 June 2010 - 11:54 AM

I guess that I expected 2 answers...one for which system is troubled currently, one for the system tied to the CD used to run sfc /scannow.

Can you clarify?

Page 136 of the manual for that Precision Workstation...states that the installation CD can only do a clean install, wiping anything that's currently on the hard drive. I would not try to do a repair install with it.

http://support.dell.com/support/edocs/syst...en/ug/ug_en.pdf

Louis

Edited by hamluis, 17 June 2010 - 12:01 PM.


#14 JCIM

JCIM
  • Topic Starter

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Local time:10:03 PM

Posted 17 June 2010 - 01:15 PM

I did the clean install and that is when I got the BSOD. Had talked to Dell and they said to uninstall Office 2007 and reinstall Office 2007. I do not belive Office 2007 is causing the problem.

I am hoping that what you asked me to do on the troubled PC, like verify and sfc worked. I can only let the pc continue to run as is and see what happens.

I do appreciate the help you have giving me.

Thanks

Jo Anne

#15 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:03 PM

Posted 17 June 2010 - 02:20 PM

Personally...I would not expect sfc /scannow to work properly with anything other than a MS Genuine XP CD.

Disks from OEMs, including Dell, are made for their own purposes. Even if they happen to contain the basic install files for XP...they may not be stored in the same manner, same file format...as used on a MS XP CD.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users