Hi, I keep receiving a blue screen error. It happens frequently, but not all the time, and it happens under different circumstances. I have just re-installed Windows XP and done all of the updates. I am also running microsoft office 2007 and microsoft outlook. All of them have been updated with all the latest updates via Windows Update.This is what appears on the blue screen error:KERNAL_DATA_INPAGE_ERROR(then the info telling you what to do if this is the first time you are receiving the blue screen error, then...)*** Stop: 0x0000007A (0xC07B9E40, 0xC000000E, 0xF73C850C, 0x332BD860)*** atapi.sys - address F73C850C Base at F73BB000 datestamp 4802539d(Then after it finishes dumping the memory it comes up with the following message, but gets stuck in a loop and keeps repeating it)Intel UNDI, PXE-2.0 (Build 082)Copyright (C) 1997-2000 Intel CorporationFor Realtek RTL8139(X)/8130/810X PCI Fast Ethernet Controller v2.13 (020326)PXE-E61 Media test failure, check cablePXE-M0F: Exiting PXE ROMOperating System: Windows XP1 person needs an answerI do too

You might try checking the sata connection between hard drive and motherboard. The connectors can be problematic so replacing the sata cable may resolve the problem.Download and run HD Tune (freeware version)http://www.hdtune.com/download.htmlPlease post a copy of the Health Report.Update your Realtek drivershttp://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=6&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=falseHope this helps, Gerry Cornell

If you reinstalled Windows, you should also check with the manufacurer of your hardware (motherboard, video, sound, network) to see if there are any newer drivers for your system. The ones you would get with a new/fresh reinstall are usually generic drivers and you need ones to match your system.Here are some things to do to help you figure it out.Do the best you can with the directions (especially the msinfo32 part) and we can help you find the drivers you need so you can download them and get your system up to date.Please provide additional information about your system:What is your system make and model?What is your XP Version and Service Pack?Describe your current antivirus and anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc.Does the afflicted system have a working CD/DVD drive?Now provide more information about your system and information from the most recent crashes.Click Start, Run and in the box enter:msinfo32Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information back here.There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.This will minimize back and forth Q&A and eliminate guesswork.Download BlueScreenView from here:http://www.nirsoft.net/utils/blue_screen_view.htmlUnzip and run it (BSV installs nothing) and let it finish scanning all your crash dump files. If you double click on of the dumps, you will get some information about it (including the Caused By Driver field) and you may be able to spot the problem right away - especially if you see a pattern in the dumps where the Caused by Driver field is the same (start with that driver).Select (highlight) one or more of the most recent dump files by clicking them and holding down the Ctrl key to select multiples files. Try to select just the most recent ones that relate to your issue (maybe five or so dump files to get started).Click File, Save Selected Items and save the information from the dumps to a text file on your desktop called BSOD.txt. Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.Here is an example of the BSV report from a single BSOD that I initiated on purpose that shows the cause of the crash as the i8042prt.sys driver belonging to Microsoft Corporation:==================================================Dump File : Mini062110-01.dmpCrash Time : 6/21/2010 11:51:31 AMBug Check String : MANUALLY_INITIATED_CRASHBug Check Code : 0x000000e2Parameter 1 : 0x00000000Parameter 2 : 0x00000000Parameter 3 : 0x00000000Parameter 4 : 0x00000000Caused By Driver : i8042prt.sysCaused By Address : i8042prt.sys+27fbFile Description : i8042 Port DriverProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 5.1.2600.5512 (xpsp.080413-2108)Processor : 32-bitComputer Name : Full Path : C:\WINDOWS\minidump\Mini062110-01.dmp==================================================Send the information from the last 5 memory dumps (if you don't have 5 memory dumps yet, send the most recent ones you have).While you are waiting, please do this:Perform some scans for malicious software, then fix any remaining issues:Download, install, update and do a full scan with these free malware detection programs:Malwarebytes (MBAM): http://malwarebytes.org/SUPERAntiSpyware: (SAS): http://www.superantispyware.com/They can be uninstalled later if desired.Reboot your computer and troubleshoot remaining issues.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

The second parameter in the bugcheck error message is the I/O status code:0x0000007a (<var>Parameter1</var> ,0xC000000E, <var>Parameter3</var> , <var>Parameter4</var> )0xC000000E means "STATUS_NO_SUCH_DEVICE", this is usually indicative of failing hardware. This I/O status code can also be caused by improper or incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives this can be caused by incorrect Master/Slave drive configuration.John

Thanks will check into the cable.All my drivers are up to date.

Thanks for the help. Below is the info you requested: I am running Microsoft Windows XP Home addition, with service pack 3 installed. The problem started before I re-installed my system and then I was running Avast, Spyware Doctor and ZoneAlarm.I am now only running Avast and Spyware Doctor and the windows firewall. I have installed all the updates available on the windows update site. I have also run the HP update, and it says that i am running the most up to date versions of everything. The original bluescreen error (before the re-install) started after a windows update. I had also recently switched from using Avira to Avast. Yes I have a working CD/DVD drive. Here is the system summary from msinfo32:OS Name Microsoft Windows XP Home EditionVersion 5.1.2600 Service Pack 3 Build 2600OS Manufacturer Microsoft CorporationSystem Name DAVIDSystem Manufacturer Hewlett-PackardSystem Model Presario V5000 (ES271EA#ABU)System Type X86-based PCProcessor x86 Family 15 Model 44 Stepping 2 AuthenticAMD ~1790 MhzBIOS Version/Date Hewlett-Packard F.22, 07/11/2005SMBIOS Version 2.31Windows Directory C:\WINDOWSSystem Directory C:\WINDOWS\system32Boot Device \Device\HarddiskVolume1Locale United KingdomHardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"User Name DAVID\David de BeerTime Zone South Africa Standard TimeTotal Physical Memory 1,280.00 MBAvailable Physical Memory 298.41 MBTotal Virtual Memory 2.00 GBAvailable Virtual Memory 1.96 GBPage File Space2.69 GBPage File C:\pagefile.sys MY computer is not creating a dump file. I have double checked all the settings, but when the blue screen error occurs it does not succeed in creating a dumpfile. So I cannot check it with BlueScreenView... The BSOD occurs every second time I restart my computer (without fail), and takes approximately 5-10minutes before it occurs.On the times when the BSOD does not occur the computer runs perfectly. The following are the three most common error messages at the top of the BSOD:1.) DRIVER_IRQL_NOT_LESS_OR_EQUAL2.) KERNAL_DATA_INPAGE_ERROR3.) (no error message just the BSOD) 1 & 2 occur if i am running programs (IE, Chrom, microsoft office, outlook, and everything else).3 if i just let the laptop boot but do nothing on it. when the first two error messages occur the info next the "*** stop:" is different except for they always include "0xF73C850C" and the error below "*** stop:" is always: "atapi.sys - Address F73C850C Base at F73BB000 DateStamp 4802539d" When the 3rd BSOD occurs only the "*** stop:" line appears with info in it and it still contains the 0xF73C850C part of the error message. The atapi.sys line does not appear. If under the system settings: startup and recovery: i have the Automatically restart option checked then after the BSOD (approximately 20minuts) the computer always gets stuck in a loop saying: "Intel UNDI, PXE-2.0 (Build 082)Copyright (C) 1997-2000 Intel CorporationFor Realtek RTL8139(X)/8130/810X PCI Fast Ethernet Controller v2.13 (020326)PXE-E61 Media test failure, check cablePXE-M0F: Exiting PXE ROMOperating System: Windows XP" If I do not have the Automatically restart option checked, then the computer remains on the BSOD saying that it is "beginning the memory dump", but nothing changes. Left the computer for 5 hours and it remained like that. haven't yet had a chance to do the malware scans as i have been very busy. but will do them next. (though as i said i just re-installed windows and the only website i visited was the windows update site before the BSOD occured... So unless the malware was included in the windows updates i doubt it is that. But i will run the scans anyway.) I am thinking that i should try disabling the realtek driver to see if that changes anything, and if that does nothing then to try removing avast (as the first BSOD occured after i had switched from Avira to Avast though not immediately)?

the second parameter in the bugcheck message is different almost every single time that i have had the BSOD the 3rd parameter however is always the same: 0xF73C850C...The BSOD also occurs every second time i boot my machine (without fail). On the other times the machine runs perfectly with no problems.

Well, I would review your setup about the dump files:Configure your system to not automatically restart on system failure (that is what it wants to do):Right click My Computer, Properties, Advanced, Startup and Recovery Settings.In the System failure section:Put a check mark in the "Write an event to the system log" boxPut a check mark in the "Send an administrative alert" boxUncheck the "Automatically restart" boxIn the Write debugging information section, choose:Small memory dump (64 KB)Set the Small dump directory to:%SystemRoot%\MinidumpClick OK, OK.Restart your computer.That means the dumps will go in this folder:c:\windows\minidumpSo take a look out there and see if there are any files. That is where BSV will look by default.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

Well, I would review your setup about the dump files:Configure your system to not automatically restart on system failure (that is what it wants to do):Right click My Computer, Properties, Advanced, Startup and Recovery Settings.In the System failure section:Put a check mark in the "Write an event to the system log" boxPut a check mark in the "Send an administrative alert" boxUncheck the "Automatically restart" boxIn the Write debugging information section, choose:Small memory dump (64 KB)Set the Small dump directory to:%SystemRoot%\MinidumpClick OK, OK.Restart your computer.That means the dumps will go in this folder:c:\windows\MinidumpSo take a look out there and see if there are any files. That is where BSV will look by default.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!

I did that with all the settings, but no files were written to that directory. The directory minidump does not even exist on my computer.

Then I would create a Minidump folder.Do, or do not. There is no try.I decided to save up points for a new puppy instead of a pony!