System reboots unexpectedly

My Windows XP system reboots unexpectedly and it generates the Minidump.I have attached the Minidump and the event.Can anyone help me to fix the issue.

Event Type:      Information
Event Source:      Save Dump
Event Category:      None
Event ID:      1001
Date:            9/16/2013
Time:            9:18:34 PM
User:            N/A
Computer:      COMPUTER_1
The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000008e (0xc0000005, 0x8052c18e, 0xba207b24, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini091613-09.dmp.

For more information, see Help and Support Center at
LVL 11
Venugopal NAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:

Your mini dump file says

Probably caused by : memory_corruption

Thomas GrassiSystems AdministratorCommented:
I would first check the fan make sure you clean the fan see what happens
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
What service Pack are you running?

Are you up to date MS security/hotfix wise?

Did you update any driver or defer a reboot after application/driver installation?  

Venugopal NAuthor Commented:
System is upto to the date and have SP3.

No hardware has been added recently, The issue started of last 15 days.
Pradeep DubeyConsultantCommented:
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: 8052c18e, The address that the exception occurred at
Arg3: ba207b24, Trap Frame
Arg4: 00000000

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

8052c18e 320f            xor     cl,byte ptr [edi]

TRAP_FRAME:  ba207b24 -- (.trap 0xffffffffba207b24)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=fffffff8 edx=ba207bff esi=00000011 edi=00000000
eip=8052c18e esp=ba207b98 ebp=ba207bc8 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
8052c18e 320f            xor     cl,byte ptr [edi]          ds:0023:00000000=??
Resetting default scope




PROCESS_NAME:  svchost.exe

LAST_CONTROL_TRANSFER:  from 8052110d to 8052c18e

ba207bc8 8052110d ba207be8 ff000011 00000004 nt!RtlFindClearBits+0x200
ba207bf4 805b169f 00101600 00010000 00000000 nt!MiFindEmptyAddressRange+0x61
ba207c44 805b1f8e 8a02e838 89d6d958 ba207d18 nt!MiMapViewOfDataSection+0x1c1
ba207ca4 805b232b 00000002 89d6da48 ba207d18 nt!MmMapViewOfSection+0x164
ba207d34 805417e8 0000006c ffffffff 0007ecfc nt!NtMapViewOfSection+0x2bd
ba207d34 7c90e514 0000006c ffffffff 0007ecfc nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0007ef34 00000000 00000000 00000000 00000000 0x7c90e514


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    8052c18e - nt!RtlFindClearBits+200
      [ 72:32 ]
1 error : !nt (8052c18e)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption





Followup: memory_corruption

MEMORY_CORRUPTION_ONE_BIT so first of all scan memory. to do so boot the machine with the windows 7/2008 dvd and when halted at boot menu press TAB key and hit enter to run memory scan.

let us know the result.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Crash dmp points to  internal or external floppy disk driver.

Install updated driver or disconnect the floppy disk drive and monitor the system
(can be a  hardware issue).

If the issue persist then enable verifier and upload the latest dmp file for analysis

Enable driver verifier
1) Open an elevated command prompt
2) Type "verifier /standard /all"  (no quotes)
3) Reboot your machine
4) Use machine again until it crashes

After the crash & reboot, go into safe mode with networking.  

Disable driver verifier
1) Open an elevated command prompt
2) Type "verifier /reset" (no quotes)
3) Reboot your machine

upload the latest dmp file for analysis

Patrick BogersDatacenter platform engineer LindowsCommented:
@Ded9, as a learning moment for me, how did you find the floppy part (i do not see any comment in the Windows Debugger (output is below this post)

@Venurajav, i did stumble upon a post which describes a compatabillity issue with AVG. If you have installed this please remove and install/update Microsoft Essentials.

Please keep us posted.
Patrick BogersDatacenter platform engineer LindowsCommented:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\mycomputername\Desktop\Mini091613-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at start of path element
Symbol search path is: SRV*downstream_store*
Executable search path is: c:\windows\System32; c:\windows\system\System32;
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130704-0421
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 16 17:47:49.250 2013 (UTC + 2:00)
System Uptime: 0 days 0:00:24.937
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8052c18e, ba207b24, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
Any update ????

Venugopal NAuthor Commented:
Tried with Memory scan and also tried with Memory slot clenup.
I have worked ont eh system for 2 hours and the system had not rebooted after that.
If again the system get reboots , will try with other steps and keep you update.
Pradeep DubeyConsultantCommented:
Also I would like to say "Configure full memory dump".
See below link for the configuration :
if you want to test the ram, i suggest to use memtest86+
you can find it on the net, or on the UBCD, along with other diagnostics :
Hardware diagnostic CD    UBCD
 i suggest the UBCD  to run some diags first - to be sure about the basics
go to the download page, scroll down to the mirror section, and  click on a mirror to start the download
Download the UBCD and make the cd   <<==on a WORKING PC, and boot the problem PC from it
Here 2 links, one to the general site, and a direct link to the download

since the downloaded file is an ISO file, you need to use an ISO burning tool
if you don't have that software, install cdburnerXP :

If you want also the Ram tested - run memtest86+ at least 1 full pass,  - you should have NO errors!
For disk Diagnostics run the disk diag for your disk brand (eg seagate diag for seagate drive)  from the HDD section -  long or advanced diag !  (runs at least for30 minutes)                        ultimate boot cd             download page
Thomas GrassiSystems AdministratorCommented:
Do you have another hard drive?

I would do a complete fresh install on another hard drive.

Boot up and see what happens.

If the install fails then I would say it is time for a new computer.
Dear, can you try Repair the Window As fallow the Steps
Venugopal NAuthor Commented:
After the RAM cleanup, the system is not rebooting.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.