Home > Help On > Help On Xp Crash On Error Code 1000000a

Help On Xp Crash On Error Code 1000000a

Sorting index $I30 in file 1702. Meanwhile, you should go into the BIOS: Load (Optimized) Defaults and set your Date an Time. started using it, and within minutes died. Yes, my password is: Forgot your password?

Thanks Event Type: Error Event Source: System Error Event Category: (102) Event ID: 1003 Date: 8/31/2010 Time: 4:43:34 AM User: N/A Computer: CCVIEW Description: Error code 1000000a, parameter1 00000000, parameter2 00000002, You may cancel the disk check, but it is strongly recommended that you continue. Change the second drive to the C or Main Drive Once that is done then click F10 to Save and Exit You will prompted to enter Y to verify Save and Disregard those which are not checked. > > Remove any dust bunnies from inside the computer casing using an Air > Duster and check all fans are running. > > -- you could try here

Join our site today to ask your question. On Mon 6/13/2011 9:43:11 PM GMT your computer crashed crash dump file: C:\WINXP\Minidump\Mini061311-03.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x5C846) Bugcheck code: 0x4E (0x8F, 0x530B3, 0x53153, 0x0) Error: Boot.ini with Safe Mode switch[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /safeboot:minimalBoot.ini without Safe Mode switch[boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect 0 #15 Macboatmaster Posted 14 June 2011 I am signing off now and will pick this up again about 1800 UK time it is now 0040.

be aa 8c 00 00 00 00 00 62 a6 ec 0a 00 00 00 00 ........b....... 7a 1e c1 00 00 00 00 00 06 39 3e 78 00 00 Indicate which also appear in > a previous boot. > > You can access Event Viewer by selecting Start, Control Panel, > Administrative Tools, and Event Viewer. > > A tip Truncating badly linked attribute records from file record segment 1500. The index bitmap for index $I30 in file 0x6a6 is invalid or missing.

Quick Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: Separate names with a comma. Join the community here. Possibly this problem is caused by another driver which cannot be identified at this time. http://www.pcreview.co.uk/threads/bsod-error-code-1000000a-parameter1-0000bab4-parameter2-000000.3385618/ Usn Journal verification completed.

Two things... 1. Make sure this is the first paste after exiting from > Event Viewer. > > Are there any yellow question marks in Device Manager? The down pointer of current index entry with length 0x78 is invalid. Rob, Oct 17, 2010, in forum: Windows XP Help Replies: 1 Views: 4,414 Yousuf Khan Oct 25, 2010 Loading...

thanks in advance.P.S. Open ImgBurn, and click on Write image file to disc7. It is possible for memory checking programs to find parity errors if the memory is extremely faultyClick to expand... Possibly this problem is caused by another driver which cannot be identified at this time.

You may cancel the disk check, but it is strongly recommended that you continue. Entirely my fault. Locate memtest86+-2.11.iso file, and click Open button.9. Once the CD is created, boot from it, and memtest will automatically start to run.

or !} listed drivers. Any advise? Possibly this problem is caused by another driver on your system which cannot be identified at this time. The power of accurate observation is commonly called cynicism by those who haven't got it.--George Bernard Shaw Back to top #3 usasma usasma Still visually handicapped (avatar is memory developed by

For full access please Register. Windows will now check the disk. Attached Files: Mini052111-01.dmp File size: 104 KB Views: 0 Mini052211-02.dmp File size: 64 KB Views: 0 Mini052211-03.dmp File size: 104 KB Views: 0 May 22, 2011 #1 Route44 TechSpot Ambassador Posts:

More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

directory file 1702. Defective memory chips may not be detected by memory checking tools. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level Stay logged in Welcome to PC Review!

Usn Journal verification completed. I reformatted to win7, and almost immediately crashed again, then back to xp (full format rather than quick) and get it this morning. What you will need to do is boot with an XP disk and go into recovery console. BTW - you deleted 3 of 4 of the images...!Assuming the RAM is good, it leaves Windows and IF MSCONFIG / Diagnostic mode eliminates the BSOD it would strongly suggest its'

About Us PC Review is a computing review website with helpful tech support forums staffed by PC experts. Will be interesting to see what happens Pete C Microsoft MVP Internet Explorer 2004 - 2011 Keep all responses to BBS posts on the BBS so that others may benefit thanks! Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Checking file system on I: The type of the file system is NTFS.