[Brickstin]

Hello,
For the past few months I have been having major hardware issues..

mainly with the south bridge and hard drive areas.


I have been getting errors like this one for example:

DRIVER_CORRUPTED_EXPOOL (c5)
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.
Arguments:
Arg1: ffe7006d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8054a0ba, address which referenced memory

FAULTING_IP:
nt!ExDeferredFreePool+b4
8054a0ba 8b10 mov edx,dword ptr [eax]

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: firefox.exe

TRAP_FRAME: aebb57d8 -- (.trap 0xffffffffaebb57d8)
ErrCode = 00000000
eax=0000000f ebx=0000000e ecx=dd851c00 edx=00000000 esi=8a5b8020 edi=00000000
eip=80569209 esp=aebb584c ebp=aebb5898 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!CcMapData+0xef:
Page a61d9 not present in the dump file. Type ".hh dbgerr004" for details
80569209 8a0c0a mov cl,byte ptr [edx+ecx] ds:0023:dd851c00=??
Resetting default scope

LAST_CONTROL_TRANSFER: from 8054a0ba to 805444e8
SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+b4

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_VRF_nt!ExDeferredFreePool+b4

BUCKET_ID: 0xC5_2_VRF_nt!ExDeferredFreePool+b4


For days I have been multiple ID events:

Example
7/22/2012 10:25:30 PM
EVENT ID : 11
Thev driver detected a controller error on \Device\Harddisk2\D.
This ID event happened 17 times in one day.. from a period of the time listed above to the end time of 10:29 PM

I also got multiple A parity error was detected on \Device\Ide\IdePort3. errors..


including ID events :

57 The system failed to flush data to the transaction log. Corruption may occur.


So.. I decided to replace my C Drive cable. because disk 2 was actually the C:\ Drive with the operating system..

I had no more problems for a while now.. for nearly a week. then this happened.. just today...


ID: 12
The device 'ST3300622AS' (IDE\DiskST3300622AS_____________________________3.AAD___\5&12b1a7d3&0&0.0.0) disappeared from the system without first being prepared for removal.


ID : 12
The device 'Primary IDE Channel' (PCIIDE\IDEChannel\4&1033e3e0&0&0) disappeared from the system without first being prepared for removal.



ID 12 with the model ST3300622AS : how in the heck is that possible? That is an internal Sata Drive...

What in the world could be causing that... ? I came back this morning after I woke up and refreshed the system.. the hard drive returned back into the system management and device manager..

Please.. anyone with help. I would in great gratitude ....


Sincerely,
Brickstin


P.S : My apologies if I wrote in the wrong section or did not properly post: I am completely new to this form and some what flighty and having an anxiety attack over this situation: this computer is my life line



Edit : 1:16 PM 7/31/2012

Here is my setup information I forgot to include that..

Processor(s)
Number of processors 1
Number of cores 1 per processor
Number of threads 2 per processor
Name Intel Pentium 4
Code Name Prescott
Specification Intel® Pentium® 4 CPU 3.20GHz
Package Socket 478 mPGA
Family/Model/Stepping F.4.1
Extended Family/Model F.4
Core Stepping E0
Technology 90 nm
Core Speed 3192.1 MHz
Multiplier x Bus speed 16.0 x 199.5 MHz
Rated Bus speed 798.0 MHz
Stock frequency 3200 MHz
Instruction sets MMX, SSE, SSE2, SSE3
L1 Data cache (per processor) 16 KBytes, 8-way set associative, 64-byte line size
Trace cache (per processor) 12 Kuops, 8-way set associative
L2 cache (per processor) 1024 KBytes, 8-way set associative, 64-byte line size
Chipset & Memory
Northbridge Intel i865P/PE/G/i848P rev. A2
Southbridge Intel 82801EB (ICH5) rev. 02
Graphic Interface AGP
AGP Revision 3.0
AGP Transfer Rate 8x
AGP Side Band Addressing supported, enabled
Memory Type DDR
Memory Size 4096 MBytes
Memory Frequency 199.5 MHz (1:1)
CAS# Latency (tCL) 3.0 clocks
RAS# to CAS# (tRCD) 3 clocks
RAS# Precharge (tRP) 3 clocks
Cycle Time (tRAS) 8 clocks
Performance Mode enabled
System
System Manufacturer IBM
System Name 814822U
System S/N KCCK6FH
Mainboard Vendor Intel
Mainboard Model D865GKD
BIOS Vendor IBM
BIOS Version 2CKT25AUS
BIOS Date 01/21/2008
Memory SPD
Module 1 DDR, PC3200 (200 MHz), 1024 MBytes, Corsair
Module 2 DDR, PC3200 (200 MHz), 1024 MBytes, Crucial Technology
Module 3 DDR, PC3200 (200 MHz), 1024 MBytes, Micron Technology
Module 4 DDR, PC3200 (200 MHz), 1024 MBytes, Micron Technology
Software
Windows Version Microsoft Windows XP Professional Service Pack 2 (Build 2600)
DirectX Version 9.0c

Edited by Brickstin, 31 July 2012 - 11:36 AM.

[Advertisements]

Can't anyone help me please... :/

[Brickstin]

Can't anyone help me please... :/

[Macboatmaster]

Brickslin

Welcome to Geeks to Go I am sorry that you have waited for a reply.

Occasionally a post does get overlooked, there being so many and it appears this is what has indeed happened with yours.

With that range of errors and having changed the cable. I recommend the following

1. I would start with a memtest.
I would in view of your ram spec as pasted below, start with the physical test. I would mark on a peice of card, SLOT ONE, SLOT TWO, to FOUR
I would then take out the ram sticks from two of the slots, so that you have just one stick in each of the slots coloured - blue for example, whichever of the slots it is recommended are populated with just two sticks

PLACE the two taken out in the appropriate position on the card.
I APOLOGISE if this sounds too basic for you, but it is easy to forget which stick was where and indeed which stick has been tested.

IF it still crashes MAKE a note on the card crashes with sticks in slots etc from original configuration.
NOW change one of the sticks that is still in place for one that was taken out originally and again make a note.
Of course place the stick that was taken out last in its original place on the card.

I am sure you have the idea by now.

So running that test, you will eventually have tested each stick of ram.

If it still crashes, using that test described, then check your motherboard manual and proceed to test with JUST ONE stick of ram, the manual will tell you where that one stick must be placed.

IT IS IMPORTANT when testing using this method, not merely to boot the computer but to work the ram.

If those results are inconclusive, then I would run memtest, using a similar system, insofar as by changing ram the crash address can be identified, if it does crash.
The instructions for memtest are on the link with the download.
Here is the explanation of what I mean by identifying the crash address
.

Please be aware that not all errors reported by Memtest86 are due to bad memory. The test implicitly tests the CPU, L1 and L2 caches as well as the motherboard. It is impossible for the test to determine what causes the failure to occur. However, most failures will be due to a problem with memory module. When it is not, the only option is to replace parts until the failure is corrected.

Once a memory error has been detected, determining the failing SIMM/DIMM module is not a clear cut procedure. With the large number of motherboard vendors and possible combinations of memory slots it would be difficult if not impossible to assemble complete information about how a particular error would map to a failing memory module. However, there are steps that may be taken to determine the failing module. Here are four techniques that you may wish to use:

1) Removing modules
This is simplest method for isolating a failing modules, but may only be employed when one or more modules can be removed from the system. By selectively removing modules from the system and then running the test you will be able to find the bad modules. Be sure to note exactly which modules are in the system when the test passes and when the test fails.

2) Rotating modules
When none of the modules can be removed then you may wish to rotate modules to find the failing one. This technique can only be used if there are three or more modules in the system. Change the location of two modules at a time. For example put the module from slot 1 into slot 2 and put the module from slot 2 in slot 1. Run the test and if either the failing bit or address changes then you know that the failing module is one of the ones just moved. By using several combinations of module movement you should be able to determine which module is failing.

3) Replacing modules

POSTED with ack to Memtest site.

Make the CD and boot from the CD.
The full instructions are here

http://www.geekstogo...sing-memtest86/

Module 1 DDR, PC3200 (200 MHz), 1024 MBytes, Corsair
Module 2 DDR, PC3200 (200 MHz), 1024 MBytes, Crucial Technology
Module 3 DDR, PC3200 (200 MHz), 1024 MBytes, Micron Technology
Module 4 DDR, PC3200 (200 MHz), 1024 MBytes, Micron Technology


2. If that all proves inconclusive
I would run a chkdsk /r on all Hard disk drives.

That is either open cmd prompt and at C:\ prompt type
chkdsk /r
note space between chkdsk and the /r

OR you may open My Computer right click the drive click properties, click tools, click error checking, click check now and click to check the second box - check for bad sectors etc.
BOTH boxes should now be checked.
Click START and agree to run on restart

When complete go Control Panel Admin tools, event viewer, click application on left pane and then when that loads, click the source column heading ONCE and that will sort the entries alphabetically.
Scroll to the winlogon entries and open the one that refers to that chkdsk. It may very well be the most recent winlogon.

When you have it open, click once on the double page symbol to the right of the window, near to the up and down arrows.
That will copy the results, now paste to your reply - that is of course right click and click paste.
YOU may of course paste first to a word doc and then copy and paste to reply when ready.

PLEASE send that as a copy and paste not as your file that I have to open.

A common cause of these errors you have is a failing hard drive with bad sectors and of course the previously mentioned memory - ram faults.

3. If BOTH the ram and the chkdsk do not show results then AND if you have not already checked open the computer case and check for dirt and dust on the fans and especially the CPU cooling fins.
BE careful with this and await advice if you are unsure please.

There are more tests to do but please post back when you have done these.

CAUTION
When removing ram, take anti static precautions, gently release clips at each end of stick and do not touch components on stick, hold stick by egdes of ram card.
Here is a guide.
http://www.crucial.c...stall/dimm.aspx

[Macboatmaster]

Brickstin

You asked for help on 31 July.

I posted on 10 August, apologising for the delay in you receiving a response and provided a comprehensive reply

I just wondered if you have managed to make any progress with your problem

[Brickstin]

ok I will let you know that I have tested all the memory ; every single module individually just a month ago: All Ram is brand new and they all tested fine with no errors what so ever; I even tested them all differently on different DIMMs and swapping the memory around..

As far as the hard drives concerned..

For some reason this is happening on ALL Hard drives now..

it first started with the C drive.. now it's starting with the the other two drives as well... And because Windows was recently infected with a Virus. I had to switch to my back up drive... which is an Itachi Drive.. but its practically Brand new as I only used it a total of seven times in a course of five years.. The Drive was always handled carefully and put in a anti static bag.. Infact The reason why I saved the HItachi drive as a back up is because I decided to switch over to a SATA interface type Hard drive.. so I cloned the drive and moved the partition and the MFT NTFS properties and tracks to the new drive I Purchased and left the old new drive in cool storage away from heat and any spots that would be subjected to shock and possibly damaging the unit..

Considering that I fix computers my self and have a wide knowledge of them.. I know for a fact that the memory is in perfect condition.

The Drives are in perfect health and I have done Scans with three different tools at least once every month or two months.. And no bad sectors have ever been found; no problems with the spin up times or anything

The fact that the Hitachi drive returned a CHDKDSK Error was a major shock to me.. the report as you requested as follows:


Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Volume label is IBM_PRELOAD.

The volume is dirty.
The attribute of type 0x80 and instance tag 0x0 in file 0x9
has allocated length of 0x2cb000 instead of 0x2cc000.
Deleted corrupt attribute list entry
with type code 128 in file 9.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x6fe0000000006c6. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $SDS)
from file record segment 1734.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x22200000003911c. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $SDS)
from file record segment 233756.
The attribute of type 0xa0 and instance tag 0x3 in file 0x1cb
has allocated length of 0xa1000 instead of 0xa2000.
Deleting corrupt attribute record (160, $O)
from file record segment 459.
The attribute of type 0x80 and instance tag 0x4 in file 0xb20
has allocated length of 0x10000 instead of 0xe000.
Deleting corrupt attribute record (128, "")
from file record segment 2848.
The attribute of type 0x80 and instance tag 0x0 in file 0x37b6
has allocated length of 0xa2f000 instead of 0x1000.
Deleted corrupt attribute list entry
with type code 128 in file 14262.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x10000000087ad. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 34733.
The attribute of type 0x80 and instance tag 0x0 in file 0x37b7
has allocated length of 0x69000 instead of 0x1000.
Deleted corrupt attribute list entry
with type code 128 in file 14263.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1000000000010. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, "")
from file record segment 16.
The attribute of type 0x80 and instance tag 0x3 in file 0x37b8
has allocated length of 0xb000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 14264.
The attribute of type 0x80 and instance tag 0x3 in file 0x37c0
has allocated length of 0x5000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 14272.
The attribute of type 0x80 and instance tag 0x3 in file 0x37c1
has allocated length of 0x7000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 14273.
The attribute of type 0x80 and instance tag 0x4 in file 0x5d02
has allocated length of 0x2000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 23810.
The attribute of type 0x80 and instance tag 0x4 in file 0x5d10
has allocated length of 0x7000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 23824.
The attribute of type 0x80 and instance tag 0x4 in file 0x5d1f
has allocated length of 0x2000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 23839.
The attribute of type 0x80 and instance tag 0x4 in file 0x5d32
has allocated length of 0x9000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 23858.
The attribute of type 0x80 and instance tag 0x5 in file 0x5d62
has allocated length of 0x2000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 23906.
The attribute of type 0x80 and instance tag 0x5 in file 0x886a
has allocated length of 0x3000 instead of 0x1000.
Deleting corrupt attribute record (128, "")
from file record segment 34922.
The attribute of type 0x80 and instance tag 0x0 in file 0x8eb8
has allocated length of 0x1f1430000 instead of 0x1f14b0000.
Deleted corrupt attribute list entry
with type code 128 in file 36536.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x13c2000000000f26. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $J)
from file record segment 3878.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x1049000000000f8f. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $J)
from file record segment 3983.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x6f00000000bbb6. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $J)
from file record segment 48054.
Unable to locate attribute with instance tag 0x0 and segment
reference 0x100000000d3a4. The expected attribute type is 0x80.
Deleting corrupt attribute record (128, $J)
from file record segment 54180.
The attribute of type 0x80 and instance tag 0x3 in file 0x2ab56
has allocated length of 0xc000 instead of 0xb000.
Deleting corrupt attribute record (128, "")
from file record segment 174934.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xe2740 for possibly 0x1 clusters.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0xe2740 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2af29 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 175913.
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x950b32 for possibly 0x500 clusters.
Deleting orphan file record segment 16.
Deleting orphan file record segment 3878.
Deleting orphan file record segment 3983.
Correcting cross-link for file 203588.
Cleaning up sparse flag for file 0x8eb8.
The index bitmap for index $O in file 0x1cb is invalid or missing.
Correcting error in index $O for file 459.
The index bitmap $O is present but there is no corresponding
index allocation attribute in file 0x1cb.
Correcting error in index $O for file 459.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff d6 50 18 12 77 4c cb 01 .........P..wL..
d6 50 18 12 77 4c cb 01 60 2a db 7c 4f 54 cd 01 .P..wL..`*.|OT..
Sorting index $O in file 459.
The object id in file 0x3 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x5 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x14 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x18 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x20 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0xdf does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0xe0 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0xe6 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0xe8 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x1e5 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x1e6 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x233 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x234 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x24c does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x26a does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x26c does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2a3 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2a7 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2a9 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2b3 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2f0 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2f4 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2f9 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x2fe does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x309 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x32b does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x32d does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x35e does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x35f does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x364 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x366 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x381 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x38d does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x395 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x39c does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x39d does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3bd does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3d0 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3d9 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3ec does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3f6 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x3f8 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x401 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x412 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x418 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x42a does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x433 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x450 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x452 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x458 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x466 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x46b does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x485 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x494 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x498 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4ac does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4ad does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4c0 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4c6 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4c9 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4cc does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4d7 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4da does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4dc does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4de does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x4e0 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x502 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x503 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x507 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x50b does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x510 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x511 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x513 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x519 does not appear in the object
id index in file 0x1cb.
Inserting an index entry into index $O of file 459.
The object id in file 0x523 does not appear in the object
id index in file 0x1




This unit above is the Hitachi drive scan from CHKDSK ... There is NO way this hard drive could have gone bad... There is no bad sectors.. But again.. I have been having strange problems now starting to pop up everywhere..

Every drive that is connected to this system somehow sustains system file damage, the MFT sector because corrupted, the file system becomes written with errors..

And it is doing this to every single drive; and at a time the subsystem was getting errors with attachable drives too; example.. external drives would suddenly vanish from the system and it would give out the pop up box to the lower right corner " Windows was unable to save all the data to file : $mft " Drive <letter> ; Please save this data elswhere. " ect.. i would get strange warnings of that sorts.. which makes no sense..

This computer never used to do that either.. I just noticed that the drives were progessively getting worse every month..

I strongly believe that the Mother board may be at fault.. my G: Drive just became unaccessable today... The entire partion is gone..

IT is no longer visible: So now I am going to have to use a RAW recovery to retrieve the data that is still sitting on my storage drive.. Which really is rocking me hard considering a lot of my recovery tools reside on that drive itself.

I know for a fact there is no bad sectors to that drive; I have scanned that drive recently within the last month returning no errors what so ever; it wasn't until now that it became damaged.

And when I do smart checks and other checks with the tools I have available to me now; it returns no errors at all; no bad sectors, no issues with the read or writes.

I just came to my Computer today and checked the system event log on the Backup OS that I am running off of right now, ( The Hitachi Drive);

[b]
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume G:.
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume F:.

12:12:03 AM - 12:15:47 AM
An error was detected on device \Device\Harddisk4\D during a paging operation.
it kept doing this there's over 200 entries of this event 51


Recently my GPU also failed; excessive heat.. I guess the compartment was just not getting enough circulation

There was dust in the entire unit but I cleaned all of that.



Again I also wish to note that the System Case fan connector just recently died as well. The fan no longer works; tried two brand new ones on this power port.. It still does not work. .Tested all three fans (third one being the original fan)on the main power supply of the PC I use.. and they all turned on.. So there for that area of the motherboard has already failed..

My only strong thought with all the activity that has been going on: and yesterday with all drives suddenly getting index issues, mft structure damage and other issues has put me into the thought that there is no way.. FOUR hard drives could suddenly all go bad at once so it must be the motherboard.

I am going to use my second PC which is a gaming rig I never put together and I am putting it together now to start doing a data recovery on my G drive and also chkdsk the other drives that are still accessible via windows.. G was the only one that became corrupted to the point it cannot mount in windows.

[Macboatmaster]

Well before I word my reply, may I apologise now if you find any of it insulting.

Please be assured that it is NOT meant that way.

1. I of course had no way of knowing this

Considering that I fix computers my self and have a wide knowledge of them

as all I had to go on was your original post.. All informationon that post really did tend to point to a memory issue and of course my comprehensive reply was forumulated so that you had ALL the information you needed to perform all checks on the ram that could be made.

I posted it that way, as you had already waited, far longer than we would wish for a reply.

2. I of course did not know that you had already checked the ram and that information included in your roginal post would have saved both of us a lot of time and effort.

ok I will let you know that I have tested all the memory ; every single module individually just a month ago

3. In view of the results from the dirty bit being set on the Hitachi drive AND the most concerning aspects of what is occurring on your system generally, I would as you say suspect a motherboard error
OR a processor fault
OR less likely I suspect a power supply issue.

4. In regard to the possibility of the CPU and if you have not already done so, you may most usefully refer back I think to the expla\nantion of memtest, bearing in mins that it tests NOT just the actual ram sticks.

5. In respect of the possible other causes and especially the failure of the system fan connector on the board, apparently NOT supplying power to the fan, one tends to think I opine of a motherboard issue.

In view of this

Recently my GPU also failed; excessive heat.. I guess the compartment was just not getting enough circulation

There was dust in the entire unit but I cleaned all of that.

and all the other points you mention in your post, it is in my opinion, as YOU say nothing to do with a hard drive issue, but a motherboard or as I said a PSU issue.

Please remember that a fan connected to a PSU, that works, does NOT mean that the PSU remains stable and working when it is placed under load of driving the system.
That is why, testing PSU`s with a multimeter is ONLY the most basic of tests.

The test is WHAT are the results when the PSU is required to deliver the watts necessary to drive the system, and therefore the amps drawn at load - does it still supply what it is supposed to do.

In view of your experience I am hesitant to post basic suggestions and guidance.

If you do reply please note there is no benefit in quoting the whole of my post, please only quote any point you wish to highlight in your reply.

Thank you and good luck with it.

The above is NOT to suugest that we will not of course endeavour to assist you further with any testing you wish to conduct.

[Brickstin]

Well before I word my reply, may I apologise now if you find any of it insulting.

Please be assured that it is NOT meant that way.

1. I of course had no way of knowing this

I wish to state that you in no way gave any indication of insulting me in any form; in fact I wish to thank you in taking the time to assist me in this dire matter that I am within.

There is no need for apology; I know that in this forum your only following standard procedures.

I failed to state the tests I have already had done and not done; that would have given more clear sight as to were I was at in figure this out with you: but again thank you for your help.

I also thank you for taking the time to reply; and I can understand your reasons or any other techs reasons on here on trying to reply to everyone and taking a while sometimes: Many people seem to traffic through this website; not to mention the people involved in geekstogo take their free time to assist people around the world with their daily computer problems and there isn't that many techs around that do this kind of thing for free.

I am just glad to have been forwarded to this website from Avast forums which I suffered from a recent viral attack which was taken care of 95%. I couldn't complete the process because the computer hardware wise finally took a dive.

So once again: thank you kindly.

..."I would as you say suspect a motherboard error
OR a processor fault..."

I recall in your first post that you stated that memtest was to be used to test all ram and all modules and dimms.

Just out of ponder; doesn't memtest also include C1 errors and other error testing that tests the cache L1 L2 and so fort inside the processor? I remember you mentioned that to me as it also returned no errors; infact the processor was fairly new.

I know there is options in the bootdiskette that allows you to select certain tests.

What best methods could be used to just mainly focus on CPU testing?

And if you may recommend a secondary program that can be ran outside in DOS perhaps? to test the CPU for any flaws?

I have tried a variety of test selections inside memtest to test the ram. Considering ram and CPU go hand in hand.

I never seen an error before. But it is possible that it may have been missed as back then this was almost two months ago that I did these mem tests.

Note: The Computer system was not acting up as bad as it started acting up now; now it is acting more erratic.

Perhaps I should run some tests on this board again to see if the CPU In mind may be faulting more often, it is possible that memtest cannot catch these errors all the time, which is why most forums suggest multiple tests done in over a course of a few days.

Please remember that a fan connected to a PSU, that works, does NOT mean that the PSU remains stable and working when it is placed under load of driving the system.
That is why, testing PSU`s with a multimeter is ONLY the most basic of tests.

The test is WHAT are the results when the PSU is required to deliver the watts necessary to drive the system, and therefore the amps drawn at load - does it still supply what it is supposed to do

In regards to this statement; As much knowledge that I have about computers: I am most certainly not an electrician. So if you have some good knowledge on testing the PSU then I most welcome the advise or steps you may offer me, I have done some basics tests on the PSU last night; Used two different Power supply testers.

Both testers show green lights accross the bourd.

But the wattage as you mention is something I am concerned about as even though a power supply may be green across the board; the ability to push out max amps can change over a course period of time during normal wear and tare use.


I do have a Multimeter but it is a basic analog multimeter tester.

this meter has five functions with 12 ranges... Only problem is.. I lost the instruction manual .. So any help on what modes to put this analog multimeter in to test the Power supply is welcome. I need to remove the power supply to night to get the wattage rating.

If this PSU proves to be good still; I am going to clean it out and re grease the bearings in the fan considering it is starting to hum.

But you are correct: I recall working on a Client's computer a year ago; his computer had a surge issue because of a major storm and his house was struck by lighting. The Computer booted up but then a month later there was issues in the consistency of the Hard drive.

I tested the hard drive even did a hard drive swap to test.. Original hard drive was in perfect condition; checked the event logs in the system and application, I was getting those errors just like I mentioned in you asking to check for it in my system.
Same kind of errors.

We tested the CPU, even the ram.. Everything was green across the board.

We never would have suspected it to be the Power supply, Tested the darn thing by switching out the power supply even though it had a power supply tester done to it with two different types of tests and had all green lights.

Upon switching out the PSU; the errors.. completely stopped..

The only thing we did not have at the time was using a multimeter to do theses kinds of tests.



I wish to note something else too; I did use the analog multimeter to test power being supplied to the Case fan port on the motherboard and it was getting the correct amount of power, but when plugging in a fan into the port and upon re-testing to that port for the same amount of power; the power was reduced to nearly 4Volts.



Final Note:

I removed the motherboard and found the following conditions:

1. The motherboard was no longer horizontally flat in it's original shape; heat over the years of use has warped the Main board and it now has a horrible curve: it is very possible that because of the heat and pressure now in the board because of this warping, is causing tension points on the balling and flowed solder all over the circuiting. Infact the same kind of warping occured with my recently failed GPU AGP card. IT was warped badly due to excessive heat and over the years use, so the balling solder points on the chipsets on the PCB where cracked due to this.

The south bridge and north bridge including the CPU area all show signs of warping and curving on the Motherboard. So it is possible that parts of the chipsets printed on the board have poor contacts now and fractures in the soldering joints: Which may explain as to why suddenly the Primary IDE Channels in the Sata range are suddenly vanishing from the system; this is part of the chipset and south bridge connecting to the North, infact even a simple bad diode or resister going out would cut off connection to certain parts to the motherboard, even cracked solder joints with poor connection and when the board heats up the metal expands, contracts ect, creating an perfect scenario for internal motherboard parts vanishing from the system.


2. There was a lot of hidden dust and I noticed there was oxidation in some parts of the board.

3. The capacitors however seem to be in good condition; no swelling of the caps what so ever.


Any advise will do me well; I may be well experienced and have knowledge in computers, but I am no Ace Expert


Sincerely in thanks,
Erick @ PC ER Services.

Edited by Brickstin, 14 August 2012 - 06:18 PM.

[Macboatmaster]

To save me typing a long reply.

In short the problem on all the evidence available, most certainly appears to be the motherboard.

I consider the overwhelming evidence, as indeed you say, to be

Which may explain as to why suddenly the Primary IDE Channels in the Sata range are suddenly vanishing from the system;

and the obvious poor physical state of the board

The motherboard was no longer horizontally flat in it's original shape; heat over the years of use has warped the Main board and it now has a horrible curve: it is very possible that because of the heat and pressure now in the board because of this warping, is causing tension points on the balling and flowed solder all over the circuiting. Infact the same kind of warping occured with my recently failed GPU AGP card

In fact, whilst we always of course wish to help, however many posts the topic, eventually runs to, this sort of problem, is unlikely to be resolved in an online situation.

If it were me, I would certainly not risk testing the board, with known good components.

[rshaffer61]

May I suggest a simple bench test outside the system? This way you use minimum components to simply see if the motherboard will boot.

Simply remove the motherboard from the case and then place the motherboard on a piece of card board larger than the motherboard,

this will eliminate a short from the mobo to the case which could be a possibility

Install the cpu with, 1 stick ram in dimm 1, power supply, case switch and case speaker
Connect ps2 mouse and keyboard along with the monitor
Repeat the above and power on
If the computer now boots into bios you most likely had a case short so make sure when installing the motherboard in the case that you use standoffs,
and they line up with the mounting holes in the motherboard and none of the standoffs touch anything else on the underside of the board.


Thanks to Cbarnard for these instructions

[Brickstin]

this will eliminate a short from the mobo to the case which could be a possibility

Actually the motherboard does boot entirely, but parts of the south bridge vanish; like the primary IDE/EIDE 0/ even the Primary Sata Zone 2 device vanishes.

As though if the hardware on the motherboard is vanishing it self.

Unless you mean to post and run the System for a while outside of the case? Yes I could try that..:

The board may be warped but it's not horridly warped to the point it was contacting the case back plate support where the stand off mounts are.

Funny thing is the system only acts up the most is when the system board starts to heat up after start up, it works fine for the first 25-40 mins, then it starts to slow down and i get application hangs at times.

Sometimes even Blue screens.

I didn't really notice any areas of the motherboard plate holder being contacted by the motherboard other then the mounting areas.

So.. I don't know... ? I have a spare drive somewhere around here I can use as a Test. Install a OS and then run it, see if any issues arise again.

If it were me, I would certainly not risk testing the board, with known good components.

Honestly I have already ordered a replacement board for this system, although I may just take this to someone I know in the next two towns to see if I can have them test it.

But.. I still need testing advice on how to test the Power supply as it is quite old as well. I've had it since 2008 in the spring.

So please with the multimeter I have, how do I test the wattage or rating on this to ensure it's still pushing out the right amount of power?

I want to do it anyways since it's old and I am going to need more wattage as I ordered a more powerfully and new graphics Card: besides I can use the old PSU for something else.

Edited by Brickstin, 15 August 2012 - 11:41 PM.

[rshaffer61]

Unless you mean to post and run the System for a while outside of the case? Yes I could try that..:

Yes


The testing of the PSU is something I don't know how to do to be honest.
We can check the voltages with a couple of programs but IMHO it does look like a MB issue.

[rshaffer61]

Some of the newer bios actually have the voltages you can see in them. If not then we will have to use Speedfan and HwMonitor to check it.


Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

Please download and run Hardware Monitor
Installation (setup version only)
HWMonitor is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, fans speed.
The program handles the most common sensor chips, like ITE® IT87 series, most Winbond® ICs, and others. In addition, it can read modern CPUs on-die core thermal sensors, as well has hard drives temperature via S.M.A.R.T, and video card GPU temperature.

[deggitt]

Hi Brickstin, have you inspected the capacitors around the cpu & by the dimm slots. Are any of them bulging at the top or do they appear to be oozing electro from the base. I have been replacing faulty / bad capacitors for some time & it is surprising the unusual faults they cause. A good site / forum to check out is BADCAPS. net. Hope this may be of interest.

[Brickstin]

So far so good I had gotten a replacement board for the PC I was having trouble with.. I haven't seen any blue screens or odd goings on. So it must have been the Motherboard, Still going to wait a few more days and do some stress tests and the likes to see if anything else happens: gott's all new cables for sata and IDEs as well.

[Macboatmaster]

Good news, keep us posted
Thanks