Hello,I am having a problem with an HP Pavilion ZT3000 notebook. I started having random stop errors (STOP 0A, STOP 4E, STOP C1) or the computer simply freezing up. I did a through check of the memory with Microsoft's Memory Diagnostic, as well as MemTest86+. No errors were found after vigourous testing.I also checked the hard drive for errors. After significant testing, no errors were found. I cannot measure the CPU temperature with software as many of the downloadable programs do not read the CPU temperature of this HP Pavilion chipset platform.I have completely wiped the computer and started WinXP installation from scratch. Eventually the STOP errors re-manifest themselves.I even tried to install Windows 7 on this system, but that was unsuccessful as there are no drivers for many of the onboard functions (WiFi, sound, etc).What else can I do to try to ressurect the WinXP OS for this laptop? I'd hate to junk it because of these stop errors. In Safe mode the computer doesn't crash to the same extent, but safe mode is not as usable as Normal XP mode. Thanks,Mike 1 person needs an answerI do too

Please provide additional information about your system and let's see what your BSODs have to say for themselves.What is your XP version and Service Pack?Describe your current antivirus and anti malware situation: McAfee, Norton, Spybot, AVG, Avira!, MSE, Defender, ZoneAlarm, PC Tools, Comodo, etc.Does the afflicted system have a working CD/DVD drive?Do you have a genuine bootable XP installation CD (this is not the same as any Recovery CDs that came with your system)?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.Don't guess what the problem might be - figure it out and fix it. I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!