My system keeps crashing!

I had to try five NVidia drivers before I got my system stable. The latest drivers nor the beta driver worked for me. I think I finally used the third driver down on the list. Go the NVidia website and search for drivers for your model of card.

What exactly is happening when the BSOD occur? Is the system idle? Screen saver? Gaming? Browsing? Watching videos? Rendering?.... etc etc

OK! I tried the drivers that came with the GPU and this is the first day that system did not crash on bootup! I will hopefully report back in a few days without anymore crashes. Thanks for all the help.

Thanks for the report! I'm glad it looks good so far.

That is good to hear. I hope your problems are over.

First of all, please run system file check:
SFC /SCANNOW Command - System File Checker

It looks like you all get BSODs at boot, please perform a clean boot:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Error code 19 BAD_POOL_HEADER - device driver, BSOD Index

Error code 3B SYSTEM_SERVICE_EXCEPTION - system service, Device driver, graphics driver, ?memory, BSOD Index

Both dumps show c0000005 which indicates memory corruption or a memory problem. Neither dump specifically shows the cause.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a00121c620, fffff8a000f12110, fffff8a00121c620}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )

Followup: Pool_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8a00121c620, the pool entry being checked.
Arg3: fffff8a000f12110, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a00121c620, 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:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800029fd10b to fffff800028ca740

STACK_TEXT:  
fffff880`043e6918 fffff800`029fd10b : 00000000`00000019 00000000`00000003 fffff8a0`0121c620 fffff8a0`00f12110 : nt!KeBugCheckEx
fffff880`043e6920 fffff800`029ff4c1 : fffff8a0`00f6c140 fffff8a0`00f6c130 00000000`00000006 fffff800`02bc1f96 : nt!ExDeferredFreePool+0xc7b
fffff880`043e69b0 fffff800`02b9f822 : 00000000`00c4f478 00000000`00000001 00000000`20206553 00000000`00000001 : nt!ExFreePoolWithTag+0x411
fffff880`043e6a60 fffff800`02b9f6ac : 00000000`00000000 00000000`00020001 00000000`00003d42 fffffa80`057e2bd0 : nt!AlpcpQueryTokenModifiedIdMessage+0x82
fffff880`043e6b30 fffff800`028c9993 : fffffa80`05733060 00000000`00c4f3e8 fffff880`043e6bc8 00000000`00c4f4a8 : nt!NtAlpcQueryInformationMessage+0x224
fffff880`043e6bb0 00000000`777d06ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c4f3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777d06ea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+c7b
fffff800`029fd10b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+c7b

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+c7b

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b

Followup: Pool_corruption
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002bb8a4a, fffff88003ddafe0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002bb8a4a, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003ddafe0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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!ObpLookupDirectoryEntry+16a
fffff800`02bb8a4a 396b10          cmp     dword ptr [rbx+10h],ebp

CONTEXT:  fffff88003ddafe0 -- (.cxr 0xfffff88003ddafe0)
rax=0000000000000200 rbx=0000000000000100 rcx=fffff80002a70d80
rdx=fffff8a003a95c60 rsi=fffff8a003a95c20 rdi=fffffa8004ff8cc8
rip=fffff80002bb8a4a rsp=fffff88003ddb9b0 rbp=00000000ca664a1b
 r8=0000000000000050  r9=fffff8a000123300 r10=0000000000000150
r11=fffff8a000123308 r12=fffff88003ddbab0 r13=0000000000000001
r14=fffff8a003a95ed8 r15=fffff8a003a95eb0
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObpLookupDirectoryEntry+0x16a:
fffff800`02bb8a4a 396b10          cmp     dword ptr [rbx+10h],ebp ds:002b:00000000`00000110=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002bb8a4a

STACK_TEXT:  
fffff880`03ddb9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupDirectoryEntry+0x16a


FOLLOWUP_IP: 
nt!ObpLookupDirectoryEntry+16a
fffff800`02bb8a4a 396b10          cmp     dword ptr [rbx+10h],ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpLookupDirectoryEntry+16a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88003ddafe0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpLookupDirectoryEntry+16a

BUCKET_ID:  X64_0x3B_nt!ObpLookupDirectoryEntry+16a

Followup: MachineOwner
---------

Something is causing a memory problems. As Ttran pointed out, both crashes occurred during bootup - 00:55.551 and 00:10.890 seconds. Your problem is in the initial loading. Have you tried booting in the safe mode? If so, do you get the same results?

Open your case. Check all of your connections, particularly your electrical connections from your PSU to your graphics card. Reseat your RAM sticks, graphics card and audio card.

You said you have run Driver Verifier. I suggest that you enable it again on the chance that it may point to an offending driver. Keep in mind that Driver Verifier will cause a crash and a BSOD. If your system crashes during booting, let Driver Verifier run for another bootup. Then, if your system crashes during the boot, turn it off and upload the Driver Verifier enabled dumps. If your system does not crash, let Driver Verifier run.

You said you have tested your RAM. Specifically, did you test it using Memtest 86+ and did you let it run for at least seven cycles? If not, please test your RAM again.

RAM - Test with Memtest86+

I know this is sounding redundant; but you have a hardware or driver problem that is causing memory corruption and this is occurring at boot up. I know of no other way to discover the source of the problem.

Have you tried another power supply?

Have you tried removing all of your RAM except for one stick and running your system?