XP SP3 crashing with Event Category: (102), Event ID: 1003

Blast. Another IRQL_NOT_LESS_OR_EQUAL, again referencing ATAPI.sys. Note I did disable the installed NIC card. Dump file download link.

Both errors are 0xD1 which are usually caused by faulty drivers. Both cite the Windows OS driver atapi.sys which IDE/AEPI Port Driver - Standard Harddisk controller. It can also be used for CD-ROM drives.

In my research it cited possible memory issues, harddrive issues, or CD-ROM.

Also, there was a lot about rootkits and this driver being corrupted but I am not saying this is your issue.

Have you done any system scans with your security software?

Yep ran AVG from safe mode, full scan, clean. Beyond frustrated...

Download the free versions of Malwarebytes and Superantispyware and run both.

Sorry, but I can't remember if you did or stated the following:

1. Run a harddrive diagnostics.

2. Check your cables to your harddrive and ROM drives. Make sure they are securly attached to both components and the motherboard.

3. When do the BSODs occur, i.e. what are you doing?

Have run Malwarebytes previously; clean.

1) HD diagnostics passes multiple times
2) check all good.
3) Sometimes nothing, sometimes browsing with IE or Safari.

Lets back up a step. When you updated your onboard NIC drivers from where did you update?

Update: Are you running Avira? The reason for my asking is because in one of your latest minidumps the avipbb.sys driver was cited as not being able to load because it was being blocked. This is an Avira driver that I had written down to research but I forgot to. What security software besides Avira do you have installed running as real time protection, i.e. firewall, anitspyware/malware, etc.? Which ones, if any, are installed but not in real time protection?

Well I disabled the NIC card and put in an old one, but for the installed, hard wired NIC I used the HP support page.

Yes only AVG Free 9.0 is installed. I uninstalled SAV a whilst back. No other real time running. Should I uninstall AVG? MalwareBytes is installed but not real time.

Another minidump attached.

First, since you uninstalled Avira the avipbb.sys driver should not be present. Different antivirus drivers will conflict causing system crashes. it appears there is at least one old Avira driver still present in your system.

Second, I read your minidump file and it is error 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues.

It simply cited hardware as the problem. However, within the minidump this information was cited: IP_MISALIGNED and this is often due to memory. In my research I came across the following from a 2005 TechSpot post by cpc2004 who, in my estimation, was the best I have ever come across to read minidumps. He now only checks in on the rare occasion. Here is what he wrote to someone else concerning IP_MISALIGNED:

This is hardware problem. IP_Misaligned (Instruction Misaligned) is usually caused by faulty memory.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram

I've done 1-5 already. Note that I still had AVG installed; I just UNinstalled it now. Just before uninstalling yet another crash of:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xbff6a931, 0xee346830, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

And a link to download the dumps..

Both errors are 0x8E and both pointed to the Windows driver rdpdd.dll as the cause of your crashes. This driver is for video display. keep in mind that OS drivers generally are not the issue but point to the fact that there is an issue. From research the latest video card drivers correct this issue. However, you already did this if I am not mistaking, correct?

Another interesting thing in your dump is the following: PEB is paged out. This can be due to memory leakage and here is one definition that, honestly, I can't fully explain but perhaps it might help you:

"PEB is paged out." This error indicates that the process environment block (PEB) is not accessible.

To load symbols, the debugger looks at the list of modules loaded by the operating system. The pointer to the user-mode module list is one of the items stored in the PEB.

In order to reclaim memory, the Memory Manager may page out user-mode data to make space for other process or kernel mode components.

When this error occurs, it means that the debugger has detected that the PEB data structure for this process is no longer readable. Most likely, is has been paged out to disk.

Without this data structure, the debugger cannot determine what images the symbols should be loaded for.

* I'll take a guess but a module or two could not be loaded for your video card.

So even after uninstalling AVG, there's a crash. And yes I updated the video driver and made sure it was for the specific monitor. Now Windows Explorer is crashing with:
Faulting application explorer.exe, version 6.0.2900.5512, faulting module duser.dll, version 5.1.2600.5512, fault address 0x00036e8d.

And another BSOD:
Error code 00000050, parameter1 f805a030, parameter2 00000000, parameter3 804ed4ee, parameter4 00000000.

Minidump attached.

Has the be a motherboard. The memtest passed 19 times in a row!

This is going to be hard to believe but your error is 0x50 and it specifically cites corrupted memory as your issue.

Refresh my memory (no pun intended) please: You already accessed the BIOS and the memory voltage was set at the manufacture's correct voltage specs, correct?

I checked the BIOS several times and could not even find a way to change it so yes.

The make of your system? Never mind, I remember. it is an HP but I forget how old.

HP D530, about 4 years old.

I went back through the posts and re-read them. I could be mistaken but have you run a harddrive diagnostics yet?

Yes a few times, always clean, no errors.

The problem with HP and Dell, etc. is that they prevent the customer from accessing the BIOS and this is a hinderance because two things I really want to know is a) how the BIOS recognizes your RAM and b) at what voltage it has it set at. I am not saying the voltage is your issue but for information sake it would settle a few things.

In most computers the way you access the BIOS is at boot-up you keep hitting the Delete key (in some cases the Escape key). Have you tried either key?

Delete not Escape do nothing; F10 brings me in to Setup but again I could not find voltage setting.

That is what I was afraid of. Okay, sorry to be repeating myself but what is your present memory configuration and what RAM is installed? What slots?

I went back and looked at your Kingston. How many sticks of 512 did your purchase?

* Also, just for you to know I went back through your PC manual to check memory information.