Hello, sorry if this post is supposed to be SOMEWHERE else.

I have a hand-me-down hp pavilion a1328x, upgraded to 2gb ram, came with integrated ati radeon xpress 200 graphics, and windows xp mce 2005. I replaced the hard drive and instead of using the manufactures restore disks, i used a plain windows xp mce 2005 disk. I went straight to the hp website and installed all the drivers: video, firmware, bios, everything they listed. I installed all the microsoft updates including sp3. I installed ff3, openoffice, livestation (an internet streaming tv app), and itunes. NOTHING CRAZY.

The crashes (blue screen and restarts) happen at SEEMINGLY meaningless times, like when i click on a different tab in my browser, or sometimes when i click on any other program to open it. At times it is so bad that I cannot open a second tab in a browser - this is in both ie8 and ff3.

I repeated the complete reinstall of the os MORE THAN SEVERAL times and finally ordered the hp recovery disks. The same thing happened again. I repeated the hp recovery but this time i chose the option where it was supposed to leave my personal data and just return the system to factory conditions. Then i just did the Microsoft updates and installed no other apps. i noticed that ff3 was still there and didn't get removed. Made it a whole day without a crash, then just now i clicked on ff3 to open it - and it crashed

Now i am wondering if next i should do another hp recovery, but wipe the drive completely to get rid of ff3, then wait another week before installing each app??? My gut tells me that nothing this bad could be happening because of ff3. Do you think i could have some hardware problem? bad ram? bad video card? monitor problem?? I did the hardware test that came with the recovery. I think it was pc doctor 5 or something like that. It tested the ram, and a couple other things (sorry cant remember). Could some of the ms updates be doing this? should I try without sp3?

Any suggestions??

Thanks so much!
JohnDownload BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.I see i have 7 crashes in there. It did have a bumpy install of all the MS stuff. Some of those were crashes that I thought "didn't count" haha... The only crash that occurred when i didn't think anything was going on was that 6-25-2010 3:12 one.

==================================================
Dump File : Mini062510-01.dmp
Crash Time : 6/25/2010 3:12:16 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041284
Parameter 2 : 0x105d9001
Parameter 3 : 0x00002035
Parameter 4 : 0xc0883000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062310-03.dmp
Crash Time : 6/23/2010 8:43:31 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xc03e0018
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x80511918
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3a918
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062310-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062310-02.dmp
Crash Time : 6/23/2010 8:38:47 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052b282
Parameter 3 : 0xb17d7ccc
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+a18d
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5976 (xpsp_sp3_gdr.100501-1623)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062310-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062310-01.dmp
Crash Time : 6/23/2010 1:17:05 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x0002f002
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062210-02.dmp
Crash Time : 6/22/2010 9:46:25 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xba277190
Parameter 3 : 0xba276e8c
Parameter 4 : 0xb9d48981
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+43981
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062210-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062210-01.dmp
Crash Time : 6/22/2010 6:04:17 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xe2dd6dc0
Parameter 3 : 0xe2dd6dc0
Parameter 4 : 0x0c000202
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22f43
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062210-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini062110-01.dmp
Crash Time : 6/21/2010 6:30:01 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xba51399c
Parameter 3 : 0xba513698
Parameter 4 : 0xb9d0b36e
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+636e
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini062110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

It looks to me, you have RAM issues.

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

Thank you so much!! I will try that tonight... have to make dinner for the kids right now. I will post BACK and let you know how it goes.

I do remember now, that when i put the two new ram sticks in, it wouldn't boot, the screen came up techno-color. I pulled them out and re-inserted them and the problem went away. I thought i just didn't get them in all the way but maybe one is bad.... This was over a year ago, I have been running Ubuntu since then and never had the crashes. but recently i switched back to xp and the problem started.

JohnCool
Let me know...OK so I ran it for a bit longer than they recommended.

stick one: 11 passes, 1 error
Stick two: 15 passes, 6 errors (all on pass 12)

The instructions said even one error means I have bad ram, but is it possible that if you run the test long enough an error will eventually occur?

What do you think, should I buy new ram?Try running computer on 1 RAM stick at a time, for a day, or so and see, if it'll BSOD.