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

BSOD 0x0000007E after updating patches XP sp2


  • This topic is locked This topic is locked
7 replies to this topic

#1 lukewoolfson

lukewoolfson

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:12:32 PM

Posted 06 March 2010 - 06:51 AM

Hi,

I recently had cleaned my windows XP (sp2) pc (Abit Ic7G intel P4 2.4ghz) using the following guide (http://forums.majorgeeks.com/showthread.php?t=139313) as it was hanging after logging in.
After I fixed that problem and then went through this guide (http://forums.majorgeeks.com/showthread.php?t=44525) to keep my pc free from rubbish. Still booting fine so I made a restore point.
Next I Installed the XP updates/patches...which I hadn't done for a while. After installing 70 odd updates/patches (including sp3) the machine rebooted only to come back with a BSOD with the following error:

*** STOP: 0x0000007E (0xC0000005, 0x805ED9A7, 0xF78C93B0, 0xF78C90AC)

I then tried booting in to safe mode and it produced the same BSOD...it came up after or during loading 'agp440.sys.

So I googled the fault an tried the following fixes (note: I can only get in to the recovery console now from boot off my windows CD)

1. Turned off the agp440.sys service from loading (http://support.microsoft.com/kb/324764)

2. Removed some suspect patches: (http://en.community.dell.com/forums/p/19321239/19663986.aspx)

KB971468

KB975560

KB977165 (note: this wasn't installed on my machine but does seem to cause a the same error)

KB977914

KB978037

KB978251

KB978262

KB978706

3. Removed sp3 (http://support.microsoft.com/kb/950249)

4. copied a old system restore point...which I made before downloading the updates (http://www.myfixes.com/articles/system)

Now I'm stuck and its still producing the same fault...please help.

BC AdBot (Login to Remove)

 


#2 lukewoolfson

lukewoolfson
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:12:32 PM

Posted 06 March 2010 - 08:20 AM

I appear to have fixed it...down to a corrupted iastor.sys file

I copied the .dmp file located here: C:\windows\minidump to a floppy

note: if you get a access denied trying to do this in windows recovery mode you need to allow the permission to write files to the floppy type in the following line:

set AllowRemovableMedia = TRUE

I then installed blue screen view (http://www.nirsoft.net/utils/blue_screen_view.html) on a working pc to look and the error...which was related to iastor.sys

I then copied an original iastor.sys file off my installation disk to c:\windows\system32\drivers\

appears to be booting ok now.

does anyone know how iastor.sys can get corrupted...do you think ti was the fault of the updates or some prior bug?

Edited by lukewoolfson, 06 March 2010 - 08:23 AM.


#3 hamluis

hamluis

    Moderator


  • Moderator
  • 55,247 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:32 AM

Posted 06 March 2010 - 09:27 AM

"Corrupted" is just another word for "damaged."

Any file on a system can becme damaged at any time, for any number of reasons.

Causes of Data Corruption - http://ezinearticles.com/?Causes-of-Data-C...n&id=817785

Data corruption and loss causes and avoidance - http://www.thexlab.com/faqs/datacorruption.html

Louis

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:11:32 AM

Posted 06 March 2010 - 12:02 PM

iastor.sys sounds like Intel related Drivers.

#5 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,613 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:04:32 AM

Posted 06 March 2010 - 12:26 PM

I appear to have fixed it...down to a corrupted iastor.sys file

Some rootkits will do exactly that.
I suggest, you create new topic at "Am I Infected?" forum.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#6 lukewoolfson

lukewoolfson
  • Topic Starter

  • Members
  • 16 posts
  • OFFLINE
  •  
  • Local time:12:32 PM

Posted 28 March 2010 - 12:29 PM

cheers broni, looks like I have some kind of root kit on my machine. I've posted my logs over here: http://www.bleepingcomputer.com/forums/t/305469/rootkit-infection/

#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,613 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:04:32 AM

Posted 28 March 2010 - 01:25 PM

Cool :thumbsup:
Thanks for posting back :flowers:

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#8 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,804 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:07:32 AM

Posted 28 March 2010 - 05:56 PM

Hello,

Now that you have posted a log here: http://www.bleepingcomputer.com/forums/t/305469/rootkit-infection/ you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a MRT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the MRT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the MRT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the MRT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses as the e-mail notification system is unreliable.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :thumbsup:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users