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

windows failed to start


  • Please log in to reply
10 replies to this topic

#1 dimmi1

dimmi1

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 29 September 2014 - 08:20 AM

Hi, computer was working ok until I restarted it. Now I get a black screen: WINDOWS BOOT manager
file: ataport.sys
status:0x0000098

I have win7 premium 64 bit. I have the upgrade win7 disk. Startup repair did not work, tests show 0 issues found.
restore point and disk image are not available. I have rkill, slimcleaner and malewarebytes on the computer but not used.

Thank you for any help

Dimmi

BC AdBot (Login to Remove)

 


m

#2 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 29 September 2014 - 08:37 AM

Actually startup repair shows: problem signature:
Problem event name:Startuprepairoffline
Problem signature 01: 6.1.7600.16385
PS02: 6.1.7600.16385
PS03: Unknown
PS04: 21201077
PS05: Autofailover
PS06: 40
PS07: Corruptfile
Os version: 6.1.7600.2.0.0.256.1
Locale id: 1033

#3 rockysosua

rockysosua

  • Members
  • 772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Caribbean
  • Local time:02:12 PM

Posted 29 September 2014 - 08:41 AM

As you're showing a corrupt file in the list, you might want to boot back up with your Win 7 disc, go to repairs and open the Command Prompt and paste in the following.

 

chkdsk /r c:

then hit Enter, then hit Y for yes and hit Enter again.

After the checkdisk has run, hopefully it will have repaired your problem.


All is well in Paradise.

#4 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 29 September 2014 - 09:35 AM

Thanks for the reply. Tried that already and tried scannow also. Hasn't worked.

#5 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 29 September 2014 - 01:31 PM

Now says ataport.sys missing

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 54,832 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:12 PM

Posted 29 September 2014 - 02:45 PM

You might want to run a hard drive diagnostic.

 

Louis



#7 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 02 October 2014 - 09:47 PM

Ok. Running Western Digital Data Lifeguard diagnostic.



#8 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 03 October 2014 - 01:14 AM

passed

 

However, I had to connect the drive as a second drive on a another computer. The original computer, all of the sudden, showed  a I/O error. I tried to boot with the  drive on the new computer but it still shows a atapi.sys corrupted message. I do have access to all the files on the drive once I boot up with the new computer's own drive. (win 7)



#9 hamluis

hamluis

    Moderator


  • Moderator
  • 54,832 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:12 PM

Posted 03 October 2014 - 11:49 AM

For I/O errors...my first step is to disconnect the drive and then reattach the cables.  Loose cables will create I/O errors which will be false indicators of possible hard  drive problems.

 

A drive from System A...should not boot in System B, the drivers, components, settings are not the same.

 

Louis



#10 dimmi1

dimmi1
  • Topic Starter

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:12 PM

Posted 03 October 2014 - 03:19 PM

I ran the ms repair 3-4 times and I reattached the drive to the original computer. It now works! I'm more inclined to believe  that the act of reattaching everything is the more likely reason it now works. Your 1st assessment that it was more of a physical issue and not software was apparently correct.  



#11 hamluis

hamluis

    Moderator


  • Moderator
  • 54,832 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:12 PM

Posted 03 October 2014 - 06:33 PM

Well...even losers get lucky guesses at times :).

 

Let's hope that you have no further adventures with this drive...if you do, just post and we'll try to solve it.

 

Happy computing :).

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users