[Rollin' Rog]

This is an exact copy/paste from the most recent dump you uploaded

Debug session time: Thu Sep 10 14:04:50.859 2009 (GMT-8)



BugCheck 10000050, {ffffffe8, 1, 805266aa, 0}

Probably caused by : HPZid412.sys ( HPZid412+3743 )

Try running services.msc and look for the HP drivers there. You can double click to read their properties and change the startup mode to "disabled". You probably won't see that driver name -- but you are looking for HP startup services that will have their own names and their should be a description adequate to confirm -- possibly this:

IEEE-1284.4 Driver HPZid412: System32\DRIVERS\HPZid412.sys (manual start)
Print Class Driver for IEEE-1284.4 HPZipr12: System32\DRIVERS\HPZipr12.sys (manual start)

---------------------------------

Have you tried the Windows Installer Cleanup Utility on your HP printer install?

[ritzbits]

September 10? I started the topic on October 18, soon after it happened, a minimum of 2 weeks or so, but not 38 days. I sometimes have printer problems when I turn off/on the printer, it goes to a blue screen

This blue screen of death problem started when a game was loading, around 7-10 PM US Central

Could it just be the RAM then or just another problem?

[Rollin' Rog]

If you do not see any NEW minidumps, be sure you are not using any cache cleaner such as CCleaner. Also run sysdm.cpl and select Advanced > Startup and Recovery. Make sure "small memory dump" is the one chosen under "write debugging information" and the location should be %systemroot%\minidump

If you want to test ram, try memtest86 >>

Beginners Guides: Diagnosing Bad Memory

Memtest86 - A Stand-alone Memory Diagnostic

Also try testing using Clean Boot Troubleshooting:

Run msconfig and select the "Services" tab. Check "Hide Microsoft Services" and then disable the rest. Also uncheck "load startup items" on the general page.


Now restart and test the issue at hand

If no problems, run msconfig and recheck half the disabled items on the Services tab. Test again. If the problem recurs, UNcheck half the items you just checked to narrow down the culprit.

If the problem didn't occur, check the other half, so all the Services are enabled -- proceed to do this on the startup tab as well.

Get the idea? You want to isolate the problem to a specific startup if possible.

Note: if you already have items unchecked under msconfig > startups and are in “selective” startup mode – you should note what these are before beginning. They will need to be de-selected again.


http://support.microsoft.com/kb/929135/en-us >> writen for Vista but applies just as well to XP

[ritzbits]

Already have CCleaner installed, ran it
tried unchecking everything except for required services and startup items, and diagnostic startup, didn't work.

I'm pretty sure it's the RAM that's the problem, as I get some errors when I run the test.

[ritzbits]

Do you think I could use a USB flash drive or some sort with windows XP for a temporary RAM solution to see if it works or not?

[DaveBurnett]

Do you think I could use a USB flash drive or some sort with windows XP for a temporary RAM solution to see if it works or not?

Np you cannot.

[Rollin' Rog]

I am saying do NOT run CCleaner, or at least make sure it is not deleting the minidump folder.

If you are running it, it is deleting any new dumps.

Also do NOT use Diagnostic startup on XP -- as it will not start the SR (System Restore Service) and therefore all restore points will be lost, should you need one.