BSOD and reboots

[BlackHawk1]

Hi. I am trying to diagnose and fix an issue with a desktop computer for a friend of mine. I have never had so much difficulty until now, this thing has me stumped. It's a HP Pavilion Slimline s5-1050z running Windows 7. It would continuously reboot no matter what I did. I even went and unchecked the option for Automatically restart under the System failure section in Startup And Recovery without success. I was also getting a 1 beep error so I replaced the MB battery which fixed that. Then I was getting a "BAD POOL HEADER" error. I ran diagnostics on the memory, MB, graphics card, etc. and all the tests came back as OK. So I decided to format it. I first formatted it using the recovery partition that HP provides. I then formatted it using a bloatware free Windows 7 iso. BOTH methods didn't provide a fix as it's still having issues. This is very frustrating and I am hoping that someone here can look at the zip file I attached and figure the problem out. I would greatly appreciate that! Thank you!

 

[axe0]

Hi BlackHawk1,

The crashes, especially the 0x24, are possibly pointing to hard drive problems.
There is a lot of NTFS activity.
NTFS is the file system.

Please test your hard drive

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

 

[BlackHawk1]

Thank you very much for the reply axe0!

I ran a test of the HD before (even using a Hiren's boot cd) and it passed, but I will do it again to be sure. The HD is a Hitachi. UPDATE: I ran the Seagate test again, both short and long, and it passed.

There are so many things going on with this desktop. At times I don't have a display even when trying to boot to the Hiren's Boot CD. I replaced the video card and that doesn't fix the issue... sometimes I have a display and some times I don't, it's hit or miss. Various problems and messages I have received when dealing with this mess...

A reboot loop which has been fixed with a new MB battery, APC Index Mismatch, Bad Pool Header, IRQL Not Less or Equal, various BSOD, No PXE stack commands message when booting to the Hiren's Boot CD, etc.

I admit I am not qualified to evaluate the logs I uploaded in the zip file however I am leaning towards a power supply or motherboard issue with this computer. What do you think? Update...

I ran Memtest86+ from the Hiren's Boot CD and the memory checked out ok, but I ran it again today and it came up with errors the second time around which puzzles me. I then pulled one of the sticks and tested them singly and one stick is bad this time around. I even ran the Windows 7 memory test before (mdsched ) and it said it was ok. This is very odd? I am providing screen shots below. I am going to cross my fingers at this point and hope this memory issue is the TRUE problem because as of now things are "ok." Man this has been so frustrating and time consuming! I have troubleshooted memory issues before, but none like this... one time it was good and the next it was bad. If anything changes I will update this thread. I thank you very much!

 

[axe0]

Hi BlackHawk1,

I couldn't provide troubleshooting steps for other crashes you mention as they aren't in the zip file.

MemTest86+ is proven a better program to test your memory with, the main reason why we recommend MemTest86+ to test the memory with.

From what is the system tests picture exactly? It doesn't look familiair to me.

If you get another (few) BSOD('s), please use the tool again and upload the new zip.
I'll gladly check the files to help you.

EDIT: I don't know either why MemTest86+ gave errors at the 2nd test, but you have now progress

 

[BlackHawk1]

That systems test picture is from a diagnostics program that HP has built in to it.

Yeah I don't know why Memtest86+ didn't report it as bad the first time around. The first time I even let it run over night and it came up with nothing. The second time it took just a few seconds to report the memory as bad... very odd in my opinion. Like I said I just hope that was the problem, the ONLY problem, and I hope this issue is fixed.

I thank you again and will report if any thing changes. Have a good one!