DirectX problem please help

Status
Not open for further replies.
Hmmm....

All those error messages about indexes occur when chkdsk is in Stage 2. I included (below) a description of what it's actually doing in stages 1 - 3 (Stages 4 and 5 pertain to checking for bad sectors).

If new errors start appearing soon after old errors fixed and the volume had been reported as no errors, it could be signs of that drive starting to go bad. Suggest also start running disk drive diagnostics on it, check its SMART data, etc. And if need be, of course, replace it before it really goes bad (and btw... if you're also running chkdsk with no args then it only reports errors without fixing tho i know u said you did repairs so assume you did chkdsk /r plus indicator for the drive volume letter

and, btw.. have the other (original problems) all gone away now?

Stage 1: Chkdsk verifies each file record segment in the master file table
During stage 1, Chkdsk examines each file record segment in the volume’s master file table (MFT). A specific file record segment in the MFT uniquely identifies every file and directory on an NTFS volume. The percent complete that Chkdsk displays during this phase is the percent of the MFT that has been verified.

Stage 2: Chkdsk checks the directories in the volume
During stage 2, Chkdsk examines each of the indexes (directories) on the volume for internal consistency and verifies that every file and directory represented by a file record segment in the MFT is referenced by at least one directory. Chkdsk also confirms that every file or subdirectory referenced in each directory actually exists as a valid file record segment in the MFT, and it checks for circular directory references. Chkdsk then confirms that the time stamps and the file size information associated with files are up to date in the directory listings for those files.

The percent complete that Chkdsk displays during this phase is the percent of the total number of files on the volume that are checked. For volumes with many thousands of files and folders, the time required to complete this stage can be significant.

Stage 3: Chkdsk verifies the security descriptors for each volume
During stage 3, Chkdsk examines each of the security descriptors associated with each file and directory on the volume by verifying that each security descriptor structure is well formed and internally consistent. The percent complete that Chkdsk displays during this phase is the percent of the number of files and directories on the volume that are checked.
 
If new errors start appearing soon after old errors fixed and the volume had been reported as no errors, it could be signs of that drive starting to go bad. Suggest also start running disk drive diagnostics on it, check its SMART data, etc.

Man I just GOT this computer and it's crapping out on me. I honestly hope it's not though. Thank god I'm still within warranty so I can send this piece back if it's causing me more trouble. I'm still not even sure my video card is working right with this irritating DX problem.

I ran chkdsk again and got errors

I don't think it will help at all if you see it but:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Deleting an index entry from index $O of file 25.
Missing object id index entry or duplicate object id detected
for file record segment 137864.
Deleting index entry Sti_Trace.log in index $I30 of file 28.
Deleting index entry STI_TR~1.LOG in index $I30 of file 28.
Deleting index entry resume.dat in index $I30 of file 7287.
Deleting index entry resume.dat.old in index $I30 of file 7287.
Deleting index entry RESUME~1.OLD in index $I30 of file 7287.
Deleting index entry fla18.tmp in index $I30 of file 9824.
Deleting index entry downloads.rdf in index $I30 of file 11586.
Deleting index entry DOWNLO~1.RDF in index $I30 of file 11586.
Deleting index entry sessionstore.js in index $I30 of file 11586.
Deleting index entry SESSIO~1.JS in index $I30 of file 11586.
Deleting index entry BACKUP.RDB in index $I30 of file 31110.
Deleting index entry A0040002.RDB in index $I30 of file 152855.
Deleting index entry 91C37181d01 in index $I30 of file 155717.
Deleting index entry 91C371~1 in index $I30 of file 155717.
Deleting index entry D46B9557d01 in index $I30 of file 155717.
Deleting index entry D46B95~1 in index $I30 of file 155717.
Deleting index entry DE46543Dd01 in index $I30 of file 155717.
Deleting index entry DE4654~1 in index $I30 of file 155717.
Deleting index entry DE699690d01 in index $I30 of file 155717.
Deleting index entry DE6996~1 in index $I30 of file 155717.
Deleting index entry EAA06B11d01 in index $I30 of file 155717.
Deleting index entry EAA06B~1 in index $I30 of file 155717.
Index verification completed.

Errors found.  CHKDSK cannot continue in read-only mode.

Just ran it to see if I had errors still.

I'm getting seatools right now to do this, since my drives are seagate drives. Is there anything better than chkdsk or will using seatools be fine?

(and btw... if you're also running chkdsk with no args then it only reports errors without fixing tho i know u said you did repairs so assume you did chkdsk /r plus indicator for the drive volume letter

Yeah I ran chkdsk C:/r chkdsk C:/f and even went into my computer > C: properties > Tools tab > error checking and checked everything and restarted.

When I did the "my computer > C: properties > Tools tab > error checking and checked everything and restarted." and left it. I woke up today and my desktop theme was reset to the default windows theme. All my settings were reset for programs and all. But all my files were still there. I simply restarted my computer again and everything was back to normal.

and, btw.. have the other (original problems) all gone away now?

I don't know. I don't know how to induce the problem. It hasn't happened after I turned the hardware acceleration down one notch. But some games that I have that require the cursor and bitmap accelerations don't show the mouse correctly.

So, I'm putting hardware acceleration back to full. I'll see if the problem happens again (which probably will). Which could take awhile since I honestly don't know what triggers it.

I'll edit my C: drive status as I go along since it's going to take awhile I assume.

For my C: drive:
SMART = pass
Short DST - pass
 
The hard drive is bad... Replace it. The bad hard drive is probably causing the DX errors too

But it passed all the seatools tests. And each time I run a chkdsk /f , /r ,/f r it doesn't have any problems. It supposedly has nothing to fix.

/edit/

I'm going to try spinrite over night. It's supposed to be a really good disk diagnostic tool.
 
So the only drive I have a problem with is my main one C:

After running a repair I ran chkdsk again on it and there's still errors.
There's alot of "Missing object id index entry or duplicate object id detected for file record segment *" Where * is something starting from.. I think 3000 to the last one which is 155819.

And a bunch of deleting index entries.

Is there a log of my very first chkdsk repair anywhere? I wasn't watching when it first went through and it just restarted my computer without telling me anything when it finished.

/edit/

Nevermind, I reran another repair and watched the entire thing. It told me there was no errors, and the volume was clean.

Funny, running another chkdsk right now with cmd.exe and it tells me I have errors.

So you don't have any hard drive errors???
 
I'm having the same problem. I just found this thread, so I haven't tried everything you have yet.

I built this over the summer:

Intel E2200 (@ 2.6 ghz)
EVGA 650i Ultra
3 gb OCZ PC 6400
ASUS ATI Radeon 3850
OCZ Stealth Xtreme 600W PSU

I'm running XP SP3, slipstreamed from an SP2 disk. I've tried every video driver on the website, with no success. Not much help, but at least you know someone else shares your pain :-/

/edit: I run FRAPs, and have the FPS set to display... sometimes it shows up in games, sometimes not. Only when fullscreen though... IDK if that has anything to do with it, but there you go.
 
I'm having the same problem. I just found this thread, so I haven't tried everything you have yet.

I built this over the summer:

Intel E2200 (@ 2.6 ghz)
EVGA 650i Ultra
3 gb OCZ PC 6400
ASUS ATI Radeon 3850
OCZ Stealth Xtreme 600W PSU

I'm running XP SP3, slipstreamed from an SP2 disk. I've tried every video driver on the website, with no success. Not much help, but at least you know someone else shares your pain :-/

/edit: I run FRAPs, and have the FPS set to display... sometimes it shows up in games, sometimes not. Only when fullscreen though... IDK if that has anything to do with it, but there you go.

Try some of the things here: http://forums.guru3d.com/showthread.php?p=2917776#post2917776

Same person, same problem. But you should probably make your own thread.

Anyways, after 21 hours or so of scanning my main disk with spinrite. It found a critical error that cannot be recovered. Great. I guess. So I'm going to send this disk back to ncix and get another one because I can. I guess that loud clicking sound I heard every now and then (I don't hear much since I'm using headphones whenever I'm on the computer) was something important.

Here's the code for reference. Spinrite asked me to copy it down so it could locate and repair it buut I don't see any option to do this and it's too much work now. I just want a working HDD now.

Code:
At 5672

eax: 3EC00000
ebx: 00000000
ecx: 3EC00000
efx: 000000FF
esi: 00000000
edi: 0000003F
ebp: EB050000
esp: 00003FF6

ds: 10E4       es: 10E4        fs:7049
gs:0040         ss: 3473        fl: 0246

It's barely been 2 months since I had my new computer. Wicked stuff. It will probably be a week or so before I can see if the problem happens on a "new" HDD. I'm pretty lucky that my HDDs have wicked warranty though.

I'll post if it, the problem I posted about, happens again.

/-----------------------edit---------------------------------/

chkdsk is prone to giving false positives for NTFS volumes. That's why I was getting false positives in command prompt while when I restarted and checked it in a static state there was no errors. spinrite sucks for my drives and seatools is probably the best. it's probably not my hdd but video card. i'm going to get it tested somewhere.
 
Status
Not open for further replies.
Back