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.


BSOD Windows XP

  • Please log in to reply
3 replies to this topic

#1 pimpo


  • Members
  • 23 posts
  • Local time:05:49 AM

Posted 28 September 2014 - 02:07 PM



I have a Pc with XP SP3 which  is continously resetting. I can´t see the error of bluescreen screen. I tried the safe mode but it didn´t work because the PC resetted again. Whit the last known configuration it didn´t work too. With the same disk and another PC I could logged in the Pc but after a short period of time it resetted again. Before I logged in the PC I got the message:

The system proccess C:\Windows\system32\services.exe terminated Unexpectedly with Status Code... (I can´t see anymore)

I could get the minidump file and from it:


PAGE_FAULT_IN_NONPAGED_AREA 0x10000050 0xfff7fff8 0x00000000 0x80551211 0x00000000 ntoskrnl.exe ntoskrnl.exe+7a211



Could anybody help me to debug the error and to know the cause?

Best Regards and thanks in advance.

BC AdBot (Login to Remove)


#2 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 7,011 posts
  • Gender:Male
  • Location:Scotland
  • Local time:04:49 AM

Posted 30 September 2014 - 06:26 PM

This problem can be caused by a faulty RAM stick, see this article from Techspot -




The advice given is to run Memtest86, which is a free download you can get from here -




on each stick of RAM in your computer in turn. By that I mean one at a time. If your computer only has one stick - and you can tell this either by running 'speccy' or looking at the motherboard - then you only need to run the test once. If you have two or more, leave one in, run the test, take that one out, change it for another, test, and so on until you have tested them all individually. Memtest will produce a report on each stick which will tell you its condition.


You will then be able to make decision as to whether or not you have a faulty stick and how and what to replace if necessary. Note that Memtest86 downloads as a file which needs to be burnt to a CD, which will be self booting, before you can use it. When removing RAM sticks, ensure that the computer is powered down and disconnected from the mains supply, and exercise normal precautions with regard to static electricity - touch a metal part of the case before you go handling the sticks.


Chris Cosgrove

I am going to be away until about the 22nd October. Time on-line will be reduced and my internet access may be limited. PMs may not be replied to as quickly as normal !

#3 pimpo

  • Topic Starter

  • Members
  • 23 posts
  • Local time:05:49 AM

Posted 06 October 2014 - 12:38 PM

Thanks Chris,


I will try to run memtest. Here are the information from windbg:


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

Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arg1: fff7fff8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80551211, If non-zero, the instruction address which referenced the bad memory
Arg4: 00000000, (reserved)

Debugging Details:

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 805630e8
GetPointerFromAddress: unable to read from 805630e0
GetUlongFromAddress: unable to read from 80567ce8

80551211 668b4efa        mov     cx,word ptr [esi-6]





PROCESS_NAME:  explorer.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 80585717 to 80551211

aa401c3c 80585717 fff7fffe 00000000 e2e01cd8 nt!ExFreePoolWithTag+0x23a
aa401c58 805db77e e2e06828 e2e01cd8 e100dad4 nt!CmpCleanUpKcbValueCache+0x51
aa401c6c 805db82a e2e06828 e2667b60 80572e7c nt!CmpCleanUpKcbCacheWithLock+0x19
aa401c78 80572e7c aa401c8c 80572dbd e2e01cd8 nt!CmpGetDelayedCloseIndex+0x16
aa401c80 80572dbd e2e01cd8 aa401c98 80572d86 nt!CmpAddToDelayedClose+0xa
aa401c8c 80572d86 e2e01cd8 aa401cb0 80573475 nt!CmpDereferenceKeyControlBlockWithLock+0x50
aa401c98 80573475 e2e01cd8 00000000 e2cd9ea0 nt!CmpDereferenceKeyControlBlock+0x12
aa401cb0 8056d73d e2cd9eb8 00000000 e2cd9ea0 nt!CmpDeleteKeyObject+0x92
aa401ccc 804e1947 e2cd9eb8 00000000 000004e2 nt!ObpRemoveObjectRoutine+0xe0
aa401ce4 8056fba7 81598298 e29fa430 81585ba0 nt!ObfDereferenceObject+0x4c
aa401cfc 8056fac5 e29fa430 e2cd9eb8 000004e2 nt!ObpCloseHandleTableEntry+0x155
aa401d44 8056fb0f 000004e2 00000001 00000000 nt!ObpCloseHandle+0x87
aa401d58 804dd98f 000004e2 019df6fc 7c91e4f4 nt!NtClose+0x1d
aa401d58 7c91e4f4 000004e2 019df6fc 7c91e4f4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
019df6fc 00000000 00000000 00000000 00000000 0x7c91e4f4


80551211 668b4efa        mov     cx,word ptr [esi-6]


SYMBOL_NAME:  nt!ExFreePoolWithTag+23a

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


IMAGE_VERSION:  5.1.2600.5512

FAILURE_BUCKET_ID:  0x50_nt!ExFreePoolWithTag+23a

BUCKET_ID:  0x50_nt!ExFreePoolWithTag+23a


FAILURE_ID_HASH_STRING:  km:0x50_nt!exfreepoolwithtag+23a

FAILURE_ID_HASH:  {772a6cc1-5eb2-1276-2b6d-082fdec5b7df}

Followup: MachineOwner


Do you or anybody see more things tan faulty memory?

#4 JohnC_21


  • Members
  • 24,448 posts
  • Gender:Male
  • Local time:11:49 PM

Posted 10 October 2014 - 06:32 PM

Were you able to run memtest+ using a bootable disk?


Does the computer reset itself before you can get to the safe mode option screen. There is an option to disable Reboot on System Failure. Select that option and it should throw a blue screen.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users