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.

Photo

Error detected in index $I30 for file 78923


  • Please log in to reply
12 replies to this topic

#1 RandyMarsh

RandyMarsh

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 15 July 2013 - 09:47 PM

Hello everyone!

 

I was brought a computer to work on and it seems i'm having some trouble.

 

Specs:

Windows 7 professional x86 SP1

2 GB DDR3 RAM

250gb Hard Drive

AMD

Nvidia integrated graphics

(It's a newer base level HP. If you want the full specs I'd be happy to post.

 

 

 

 

 

Originally the PC was brought in because of a BSOD crash. I attached an image of the bluescreen dump. The dump produced a stop code 05 as well as invalid_process_attach_attempt caused by the driver ntoskrnl.exe. I did some research on this error and there wasn't much to be found. From what I could gather, the error can be caused by failing hardware (more commonly the GPU), multiple antiviruses running simultaniously, viruses, as well as other things. The computer did have mcafee installed as well as AVG and symantic endpoint protection. I removed mcafee and avg. Malwarebytes found 5 threats and was able to remove them all. I also updated the GPU driver to the latest version. I have yet to have the PC crash and I've been running it for days. Do you think that the crash was something that is unlikely to happen again? Can anyone provide more insight into this issue?

 

The second issue with this PC is an error I'm getting when running the chkdsk utility.

 

CHKDSK is verifying files (stage 1 of 3)...
  602368 file records processed.                                         

File verification completed.
  223 large file records processed.                                   

  0 bad file records processed.                                     

  4 EA records processed.                                           

  57 reparse records processed.                                      

CHKDSK is verifying indexes (stage 2 of 3)...
The multi-sector header signature for VCN 0x0 of index $I30
in file 0x1344b is incorrect.
00 00 06 04 56 66 41 54 78 47 6d 86 00 00 00 00  ....VfATxGm?....
00 00 00 00 00 00 00 00 00 70 ed 95 00 40 04 00  .........pí?.@..

Error detected in index $I30 for file 78923.
The index bitmap $I30 in file 0x1344b is incorrect.
Error detected in index $I30 for file 78923.
  643880 index entries processed.                                        

Index verification completed.

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

 

 

I've done some research on this error as well and can't find much.

Microsoft has an article: http://support.microsoft.com/kb/976329 that talks about storage issues. In the article, it recommends downloading a hotfix. However, this hotfix is supposed to be included in windows 7 SP1, which the customer already has. I downloaded the hotfix anyways, and it will not run on the machine, saying something along the lines of not being compatible (even though I downloaded windows 7 x86 version). There is plenty of storage space on the machine too.

 

I ran memtest 86+ to test for ram problems. No problems found.

Ran a HDD testing program that was included on HBCD and no problems were found.

I've used the windows 7 OS CD to try to repair the filesystem, no luck.

I've ran a disk defrag, registry cleaner, ect. to see if that would even help.

 

I'm totally stumped as to what the chkdsk issue is or how to fix it. If anyone could help out on this, that would be great! The chkdsk results are also attached.

Attached Files


Edited by RandyMarsh, 15 July 2013 - 09:48 PM.


BC AdBot (Login to Remove)

 


#2 SpywareDoc

SpywareDoc

  • Members
  • 687 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland, USA
  • Local time:09:24 PM

Posted 16 July 2013 - 08:00 AM

Try running the command "chkdsk /r" (not the quotes) to allow chkdsk to attempt to /repair the problem.



#3 RandyMarsh

RandyMarsh
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 16 July 2013 - 11:27 AM

Try running the command "chkdsk /r" (not the quotes) to allow chkdsk to attempt to /repair the problem.

 

I have tried this already. No luck.



#4 SpywareDoc

SpywareDoc

  • Members
  • 687 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Maryland, USA
  • Local time:09:24 PM

Posted 16 July 2013 - 11:32 AM

What is the error message?



#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:24 PM

Posted 16 July 2013 - 12:16 PM

Chkdsk will balk at file system, partition, or hard drive situations that won't allow continuation.

 

I would download/run the respective hard drive extended diagnostic from the website of the hard drive manufacturer...and try to ensure that the base item is not the problem...as Step One

 

Louis



#6 RandyMarsh

RandyMarsh
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 16 July 2013 - 11:40 PM

A ran a few other tests and they all passed. Makes me believe the HDD itself is good, but something on the filesystem is corrupt.

Vivard:
http://imgur.com/iJqNd5x
http://imgur.com/wtrAFlV

Seatools for DOS
http://imgur.com/yf6sR1P

Some program on HBCD:
http://imgur.com/3sHekLj
http://imgur.com/z0wMrNG
http://imgur.com/kp3zIuS

Anyone have any idea on how to repair it?
 



#7 hamluis

hamluis

    Moderator


  • Moderator
  • 56,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:24 PM

Posted 17 July 2013 - 03:43 AM

Try running the chkdsk /r command.

 

If it fails, post the onscreen error message, please.

 

Louis



#8 RandyMarsh

RandyMarsh
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 17 July 2013 - 10:13 AM

Try running the chkdsk /r command.

 

If it fails, post the onscreen error message, please.

 

Louis

 

chkdsk /r and chkdsk /f seem to both run and complete just fine. However, when I run a normal chkdsk after chkdsk /r is complete, I get the same error.

 

I tried running sfc /scannnow and get this:      http://imgur.com/pPMNd0L



#9 hamluis

hamluis

    Moderator


  • Moderator
  • 56,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:24 PM

Posted 17 July 2013 - 11:32 AM

Chkdsk /r is the best command to use.

 

Chkdsk with nothing else...just runs in read-only mode.

 

Chkdsk /r tries to repair files but does nothing about files in bad sectors.

 

Chkdks /r will try to move files in bad sectors...as well as all functions performed via chkdsk /f command.

 

Louis



#10 RandyMarsh

RandyMarsh
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:09:24 PM

Posted 17 July 2013 - 12:50 PM

Chkdsk /r is the best command to use.

 

Chkdsk with nothing else...just runs in read-only mode.

 

Chkdsk /r tries to repair files but does nothing about files in bad sectors.

 

Chkdks /r will try to move files in bad sectors...as well as all functions performed via chkdsk /f command.

 

Louis

chkdsk /r completed without error. However, the next time I ran chkdsk from windows it came up with the original error.



#11 hamluis

hamluis

    Moderator


  • Moderator
  • 56,395 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:24 PM

Posted 17 July 2013 - 01:10 PM

Please download MiniToolBox  , save it to your desktop and run it.

 

Checkmark the following checkboxes:

  List last 10 Event Viewer log

  List Installed Programs

  List Users, Partitions and Memory size.

 

Click Go and paste the content into your next post.

 

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link.

 

Louis



#12 slgrieb

slgrieb

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas Panhandle
  • Local time:08:24 PM

Posted 17 July 2013 - 08:13 PM

 

Chkdsk /r is the best command to use.

 

Chkdsk with nothing else...just runs in read-only mode.

 

Chkdsk /r tries to repair files but does nothing about files in bad sectors.

 

Chkdks /r will try to move files in bad sectors...as well as all functions performed via chkdsk /f command.

 

Louis

chkdsk /r completed without error. However, the next time I ran chkdsk from windows it came up with the original error.

 

You can make a bootable drive diagnostic from your drive manufacturer's support site, and run a full test to evaluate your drive, but I think the evidence is pretty clear that your HDD is bad. Some drive utilities offer to repair the bad sector(s), but they just delete the data there and then mark the area as bad. If you have one or more bad sectors on the drive, it's likely you are going to have more soon, or a sudden failure of the drive. Time to replace it while you can still probably clone the old drive. 


Edited by slgrieb, 17 July 2013 - 08:14 PM.

Yes, Mr. Death... I'll play you a game! But not CHESS !!! BAH... FOOEY! My game is... 
WIFFLEBALL!

 


#13 shariff2030

shariff2030

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:07:54 AM

Posted 21 July 2016 - 02:35 AM

I had a similar problem like this but not the same error code. My error was ‘error in index $i30 for file 12427’. Below link resolved it and u try it too !!!

 

https://support.microsoft.com/en-us/kb/2641432






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users