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

Can't Load Windows


  • Please log in to reply
3 replies to this topic

#1 bigdog1100

bigdog1100

  • Members
  • 308 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 13 February 2010 - 08:57 PM

Hello. So I am a victim as so many others apparently. Here is what happened. I did Windows XP update. After it took about 30 minutes installing updates before turning PC off, next time I turned PC on the issues started.

Here is what you should know. This is Windows XP, SP2.

1.) As step #1 I did http://pcsupport.about.com/od/fixtheproble...pairbootini.htm

2.) As step #2, thanks to people on live chat, I did try to fix it with

http://social.answers.microsoft.com/Forums...24-817bf39c207b

From the offered list of KB's I got invalid directory with KB978037, KB975713 and KB977165. Apparently latter is the issue.... Neither helped.

3.) Also, I tried the http://social.answers.microsoft.com/Forums...73-0eea8dfd0211 But as mentioned before KB977165 is nowhere near there.

I have two installations of windows. One I haven't used and wasn't planning on. So I can, in fact log on to that one. And I can have access to folders in both Windows if necessary.

However, the other one that I use as my main, I get this blue screen.

Please help me. We can arrange chat session if necessary. This is my business PC and I must have access to is ASAP. I really hope you can help me. Thank you in advance. :thumbsup:

Edited by bigdog1100, 13 February 2010 - 09:18 PM.

Motherboard: ASUS P8Z68-V LX; Processor: Intel i5 2500k; RAM 24GB: CORSAIR XMS3 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800); CORSAIR Vengeance 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800); Video Card: MSI AMD Radeon RX 470 Gaming X 4G GDDR5; Storage: HDD 2TB Seagate ST2000DM001-9YN164; SSD 500GB Samsung 860 EVO 500GB;Power Supply:  OCZ ZS Series 650W 80PLUS Bronze High Performance Power Supply; Multi-card reader: Nippon Labs Delux 3.5" Internal All In One Card Reader/Writer with USB2.0 & eSATA Ports Model ICR-BB. Optical 1: LG GH22NS90; Optical 2:  ASUS BW-12B1ST; Fans: 3x80mm, CPU Cooling: XIGMATEK LOKI SD963. So there are total of 6 fans.
 


BC AdBot (Login to Remove)

 


#2 Plasmatic

Plasmatic

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:01:23 PM

Posted 15 February 2010 - 11:12 PM

Is this an AMD machine? I've had some choke on sp3, Dell and HP both have a fix that must be ran before sp3.

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,564 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:23 PM

Posted 16 February 2010 - 06:49 AM

You did not post the error message.

There are a wide variety of typical BSOD errors, can be found at http://www.aumha.org/a/stop.htm.

In addition to these...there are STOP errors which are not so typical.

Posting the error message received...at least provides a starting point.

<<next time I turned PC on the issues started>>

What issues might those be?

Louis

#4 bigdog1100

bigdog1100
  • Topic Starter

  • Members
  • 308 posts
  • OFFLINE
  •  
  • Local time:02:23 PM

Posted 16 February 2010 - 10:25 AM

Problem solved. A big thank you to @Leurgy in live chat, here. Thank God for live chat and people like @Leurgy

The problem was 0x000007E error. Turned out it was malware. We replaced Atapi.sys infected file with the file from another windows directory (I have two installations). Once I did that, I was able to get to almost starting the windows. At that point I got lsass.exe error "When trying to update a password the return status indicates that the value provided as the current password is not correct". Someone else in chat suggested that this was registry issue. And it was. So I followed thsese instructions in steps 1 and 2. http://support.microsoft.com/kb/307545
Windows started. I also followed instructions on how to reverse to original restore point through DOS using instructions from another message board. Then I followed step 3 and what I got was brand new windows. So, I reversed back to the state as it was with the Lsass.exe error, and repeated step 1. Then I scanned my pc for viruses and malware. I found a few, cleaned, installed service pack 3 from internet, given I was taken back to SP1, since my system restore was off except this one time in April 09 (time of my other crash) and recent RP after the issue was resolved to some degree. So now my PC is up and purring...running. Thank you very much. I now replaced Zone Labs with more aggressive Comodo with Defense+, and Avast. I have scanned with Full scan of Avast, Malwarebytes, Some other Anti spyware Software and Updated Spyware Blaster.

P.S. This is not AMD machine.

Edited by bigdog1100, 16 February 2010 - 10:34 AM.

Motherboard: ASUS P8Z68-V LX; Processor: Intel i5 2500k; RAM 24GB: CORSAIR XMS3 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800); CORSAIR Vengeance 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800); Video Card: MSI AMD Radeon RX 470 Gaming X 4G GDDR5; Storage: HDD 2TB Seagate ST2000DM001-9YN164; SSD 500GB Samsung 860 EVO 500GB;Power Supply:  OCZ ZS Series 650W 80PLUS Bronze High Performance Power Supply; Multi-card reader: Nippon Labs Delux 3.5" Internal All In One Card Reader/Writer with USB2.0 & eSATA Ports Model ICR-BB. Optical 1: LG GH22NS90; Optical 2:  ASUS BW-12B1ST; Fans: 3x80mm, CPU Cooling: XIGMATEK LOKI SD963. So there are total of 6 fans.
 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users