Welcome to Seven Forums.
Let's do some hardware checks first.
D/L
CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use
Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.
Install SP1:
Learn how to install Windows 7 Service Pack 1 (SP1)
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a0122e9e60, the pool entry being checked.
Arg3: fffff8a0122e9e60, the read back flink freelist value (should be the same as 2).
Arg4: 0000000000000000, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: TrustedInstall
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002dbd130 to fffff80002c8a700
STACK_TEXT:
fffff880`03bc1998 fffff800`02dbd130 : 00000000`00000019 00000000`00000003 fffff8a0`122e9e60 fffff8a0`122e9e60 : nt!KeBugCheckEx
fffff880`03bc19a0 fffff800`02dbf4c1 : 00000000`00000000 fffff8a0`12364a00 fffff880`03bc1a40 fffff880`03bc1a40 : nt!ExDeferredFreePool+0xca0
fffff880`03bc1a30 fffff800`02c8f8bc : fffff8a0`12364a30 00000000`00000000 fffffa80`2079654b fffffa80`06a4f510 : nt!ExFreePoolWithTag+0x411
fffff880`03bc1ae0 fffff800`02f9f264 : fffffa80`06d79670 00000000`00000000 fffffa80`0a9f45d0 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`03bc1b40 fffff800`02f9f164 : 00000000`0000b484 fffffa80`06d79670 fffff8a0`0bc64b60 00000000`0000b484 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`03bc1bd0 fffff800`02c89953 : fffffa80`0a9f45d0 fffff880`03bc1ca0 00000000`00000000 00000000`08ddc158 : nt!ObpCloseHandle+0x94
fffff880`03bc1c20 00000000`7768f7aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0624cb18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7768f7aa
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+ca0
fffff800`02dbd130 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+ca0
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+ca0
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+ca0
Followup: Pool_corruption
---------
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
This indicates a RAM issue.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030dcd05, The address that the exception occurred at
Arg3: fffff88009601938, Exception Record Address
Arg4: fffff880096011a0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!PfpFlushBuffers+255
fffff800`030dcd05 4883bd8001000000 cmp qword ptr [rbp+180h],0
EXCEPTION_RECORD: fffff88009601938 -- (.exr 0xfffff88009601938)
Cannot read Exception record @ fffff88009601938
CONTEXT: fffff880096011a0 -- (.cxr 0xfffff880096011a0)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88003fd072d to fffff88003fd06e4
STACK_TEXT:
fffff800`03f9fc68 fffff880`03fd072d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`03fd06e4
fffff800`03f9fc70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffff880`03fd072d
FOLLOWUP_IP:
nt!PfpFlushBuffers+255
fffff800`030dcd05 4883bd8001000000 cmp qword ptr [rbp+180h],0
SYMBOL_NAME: nt!PfpFlushBuffers+255
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
STACK_COMMAND: .cxr 0xfffff880096011a0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!PfpFlushBuffers+255
BUCKET_ID: X64_0x7E_nt!PfpFlushBuffers+255
Followup: MachineOwner
---------
STOP 0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
Usual causes: Device driver(s)
Cause: A driver has called IoCompleteRequest to ask that an IRP be completed, but the packet has already been completed.
This is blaming a device driver.
Go to your motherboard website and make sure all your drivers are up to date.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8006e5c410, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
IRP_ADDRESS: fffffa8006e5c410
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+3ec3e
fffff800`02cb2355 cc int 3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: Wow.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cb2355 to fffff80002cc8700
STACK_TEXT:
fffff880`080a53e8 fffff800`02cb2355 : 00000000`00000044 fffffa80`06e5c410 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`080a53f0 fffff880`0126d6d3 : fffff880`080a56a0 00000000`00000001 fffff880`080a57f0 fffffa80`06e5c410 : nt! ?? ::FNODOBFM::`string'+0x3ec3e
fffff880`080a54d0 fffff880`0126ecf8 : fffff880`080a56a0 fffffa80`06e5c410 fffff880`080a5701 fffffa80`0797b801 : Ntfs!NtfsCommonRead+0x1bc7
fffff880`080a5670 fffff880`00e3823f : fffffa80`06e5c7b0 fffffa80`06e5c410 fffffa80`0797b8f0 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`080a5870 fffff880`00e366df : fffffa80`079ef8e0 fffffa80`06e5c410 fffffa80`079ef800 fffffa80`06e5c410 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`080a5900 fffff800`02cba212 : fffffa80`06e5c430 fffffa80`07a11f20 00000000`00000043 fffff680`003bcb60 : fltmgr!FltpDispatch+0xcf
fffff880`080a5960 fffff800`02cba515 : 00000000`00000001 00000000`00000001 fffff880`080a5a60 fffffa80`09590b60 : nt!IoPageRead+0x252
fffff880`080a59f0 fffff800`02ce38bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x255
fffff880`080a5ac0 fffff800`02cc67ee : 00000000`00000000 00000000`003bf8ec fffff880`00000001 fffffa80`06b82d10 : nt!MmAccessFault+0x14bb
fffff880`080a5c20 00000000`779b0afc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`003bded8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779b0afc
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3ec3e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x44_nt!_??_::FNODOBFM::_string_+3ec3e
BUCKET_ID: X64_0x44_nt!_??_::FNODOBFM::_string_+3ec3e
Followup: MachineOwner
---------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Cause: This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Code:
Event[144]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T15:55:47.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002cc2905, 0xfffff880097befa0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
Event[145]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T15:55:47.000
Event ID: 1005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
Unable to produce a minidump file from the full dump file.
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Code:
Event[343]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T15:37:15.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000008886, 0xfffffa8004d778f0, 0xfffffa8004c27950, 0x0000000000000503). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
Event[344]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T15:37:14.000
Event ID: 1005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
Unable to produce a minidump file from the full dump file.
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Code:
Event[453]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T14:13:40.000
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80002ccb7ae). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
Event[454]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2011-07-30T14:13:40.000
Event ID: 1005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alan-PC
Description:
Unable to produce a minidump file from the full dump file.
There is a lot of update errors, install SP1.
