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 keeps coming back


  • Please log in to reply
1 reply to this topic

#1 scramjet

scramjet

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 27 August 2009 - 01:37 PM

Hi, I was wondering if someone could help...I have a recurring problem. I have not installed any new software or hardware, but have been having this problem since day 1.
I got a new hard drive, reformatted it on my laptop (thinkpad 600X), and installed XP. I periodically get BSOD with the same message each time...
The mini dump datafile is below. Could anyone shed some light as to the cause?
I really appreciate it...thanks in advance



BugCheck 100000D0, {81c00010, 2, 1, 80549fb8}

Probably caused by : HTTP.sys ( HTTP!UlIsLowNPPCondition+55 )

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

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

DRIVER_CORRUPTED_MMPOOL (d0)
Arguments:
Arg1: 81c00010, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80549fb8, 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: 81c00010

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiFreePoolPages+45d
80549fb8 897310 mov dword ptr [ebx+10h],esi

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD0

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8054b90b to 80549fb8

STACK_TEXT:
f6344c94 8054b90b 0000e260 f6344d4c 00000012 nt!MiFreePoolPages+0x45d
f6344cd4 f5e76505 8143e000 00000000 000c018c nt!ExFreePoolWithTag+0x1b7
f6344d50 f5e7a656 f5e84ea0 8193a310 00000000 HTTP!UlIsLowNPPCondition+0x55
f6344d88 f5e9bd7f f5e9bbb0 f5e86f20 00000000 HTTP!UlpTimeoutCheckExpiry+0x48
f6344d8c f5e9bbb0 f5e86f20 00000000 81715998 HTTP!UlpTimeoutMonitorWorker+0x5
f6344dac 8057aeff 00000001 00000000 00000000 HTTP!UlpThreadPoolWorker+0x1c0
f6344ddc 804f88ea f5e9b9f0 8193a310 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
HTTP!UlIsLowNPPCondition+55
f5e76505 46 inc esi

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: HTTP!UlIsLowNPPCondition+55

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HTTP

IMAGE_NAME: HTTP.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480256bc

FAILURE_BUCKET_ID: 0xD0_HTTP!UlIsLowNPPCondition+55

BUCKET_ID: 0xD0_HTTP!UlIsLowNPPCondition+55

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,744 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:53 AM

Posted 27 August 2009 - 02:29 PM

Hi :thumbsup:.

Http.sys is a Windows file, the scene of the crime.

If it were me, I'd try the registry edit suggested...but lets's try something else first.

Worth reading, http://www.linkroll.com/Operating-Systems-...ptedMmpool.html

What I would suggest is running either sfc /scannow or doing a repair install of XP. A repair install will probably take the same amount of time as running sfc /scannow, but will result in your needing to reinstall critical updates issues since the date the CD used will have been created.

Doing either of these...requires a CD that reflects the same version of XP and at least the same level of SPs installed as your system currently reflects.

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

How to Perform a Windows XP Repair Install - http://www.michaelstevenstech.com/XPrepairinstall.htm

OTOH..you can elect to try the registry edit suggested in the analysis you provided. Since this involves editing the registry, the typical caution goes out to you. Editing the registry is something that can produce unwanted effects, so users are requested to back up the registry before considering such. A good tool for backing up the registry can be found at ERUNT Registry Backup Tool - http://www.snapfiles.com/get/erunt.html .

If you are comfortable editing the registry or attempting such, then I would consider that suggestion.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users