Your crash report zip file was incomplete.
When you can, upload the complete report, so we can help you.
Blue Screen of Death (BSOD) Posting Instructions
When posting any crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Are you overclocking anything?
Is this your computer?
HP Pavilion Elite m9600t Desktop PC Product Specifications and Configurable Options
If it is, can you verify the components?
We need more details on your system.
Do you still have the original PSU?
OEM PSUs are not the best quality and do go out frequently.
HP diagnostics may be ok for some things but, you need to run other tests. These tests are more thorough and will give us a better idea of where to start.
This test will be ran from a CD/USB stick and doesn't need W7 to be running.
Run
Data Lifeguard Tools 11 for DOS on your hard drive.
How to create a Data Lifeguard diagnostics bootable CD.
Run the QUICK TEST and the EXTENDED TEST.
Do you have the W7 installation disks?
If you don't follow this tutorial to make a System Repair Disc.
How to Create a Windows 7 System Repair Disc
If you are unable to boot your Windows 7 to create a Windows 7 System Repair Disc, then you could create it on another computer to use on your computer.
From 19, Jan 2011
Code:
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
ERROR_CODE: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.
DEFAULT_BUCKET_ID: CODE_CORRUPTION
MODULE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
This was after you got the new WD hard drive.
Have you ran memtest86+ again since 24 Jan 2011?
Run memtest86+ for 7 full passes, with all RAM cards installed.
Best to run overnight as depending on the amount of RAM you have may take several hours.
If you get any errors you can stop the test.
RAM - Test with Memtest86+
From 22, April 2011 and 3, May 2011
Code:
STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CPU issue.
From 25, June 2011
Code:
STOP 0x0000009C: MACHINE_CHECK_EXCEPTION
Usual causes: Hardware error (similar to STOP 0x124)
BUGCHECK_STR: 0x9C_GenuineIntel
FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c
Another CPU issue
From 3, Dec 2012
Code:
STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
Probably caused by : GenuineIntel
BUGCHECK_STR: 0x124_GenuineIntel
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
CPU again.
This indicating a CPU problem for a long time.
These will have to wait until you can boot W7.
Have you checked the CPU core temps?
Use
Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Have you remove the CPU, or the CPU cooler?
These kind of errors can be caused by bent CPU pins, bad motherboard or bad PSU, and of coarse a bad CPU, which is rare.
From your System Event Logs:
Code:
Event[32654]:
Log Name: System
Source: Disk
Date: 2012-09-20T15:17:07.116
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: HomeOffice-PC
Description:
The driver detected a controller error on \Device\Harddisk8\DR9.
This is indicating a hard drive error.
Your System Event Logs stop on 1, Oct '12
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.
If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.
