Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows 8 Won't boot after BSOD Corrupt ataport.sys pcmcia.sys


  • Please log in to reply

#1
blakeje

blakeje

    New Member

  • Member
  • Pip
  • 3 posts

Hi, 

 

I will start from the beginning. 

 

I was tweaking some setting in my Webcam software and clicked the reset settings option then Windows BSOD with error FN_LIST_CORRUPT.   After the computer restarted i would hang on boot with an error atapi.sys .  I tried booting into safemode and it just loops back to the atapi.sys error screen regardless of what I pick between 1- 9.    I got my windows 8 usb drive and booted into the installation and went to start up repair that also could not complete and created  a SrtTrail file.  I plugged my boot drive into my laptop using an enclosure to retrieve said file and I will post the log below.   I also ran Malwarebytes on drive and nothing was found. 

 

My theory is that  I had a pending windows update installation restart  and maybe that messed something up when the system crashed.  

 

Any help would be much appreciated.  I would rather not have to reinstall windows and all my applications. 

 

SrtTrail Log

 

 

 

Startup Repair diagnosis and repair log

---------------------------
Last successful boot time: ‎3/‎16/‎2015 12:51:44 PM (GMT)
Number of repair attempts: 2
 
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 2
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 110 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 46 ms
 
Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 610 ms
 
Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
Boot critical file c:\windows\system32\drivers\atapi.sys is corrupt.
 
Repair action: File repair
Result: Failed. Error code =  0xc1
Time taken = 375 ms
 
Repair action: System files integrity check and repair
Result: Failed. Error code =  0xc1
Time taken = 0 ms
 
Root cause found: 
---------------------------
Boot critical file C:\ataport.SYS is corrupt.
 
---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1
 
Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms
 
Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 93 ms
 
Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 94 ms
 
Test Performed: 
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Test Performed: 
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 63 ms
 
Test Performed: 
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 593 ms
 
Test Performed: 
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
 
Root cause found: 
---------------------------
Boot critical file c:\windows\system32\drivers\pcmcia.sys is corrupt.
 
Repair action: File repair
Result: Failed. Error code =  0xc1
Time taken = 406 ms
 
Repair action: System files integrity check and repair
Result: Failed. Error code =  0xc1
Time taken = 0 ms
 
---------------------------
---------------------------
 

 

 


Edited by blakeje, 18 March 2015 - 05:49 PM.

  • 0

Advertisements


#2
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,356 posts

Boot your computer using Windows 8 USB Flash Drive and from System Recovery Options start Command Prompt and type bcdedit | find "osdevice" command press enter key to find out which driver letter is assign to Windows OS installed partition. Type chkdsk C: /f command to repair C: partition file system replace C: drive letter with Windows OS partition drive letter. Also Type Sfc   /scannow  /offbootdir=C:\  /offwindir=C:\windows command to repair Windows OS system files. After all command finish executing restart your computer to find out problem has been resolved.


  • 0

#3
blakeje

blakeje

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts

Tried to run the Sfc command from the Recovery Options Command Prompt but kept getting ''Windows Resource Protection Could Not Start the Repair Service''. I tried running net start trustedinstaller which I found elsewhere but still getting the same message.

 

Thanks


Edited by blakeje, 19 March 2015 - 05:52 AM.

  • 0

#4
blakeje

blakeje

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts

Gave up and did a reinstall :-/ All fixed now. 


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP