Two BSODs while idle and away from computer, stop 19 and F4

[MBD]

I had an issue a few months ago that seemingly pointed to my HDD, but after running all diagnostics available, my HDD came back clean, so I thought nothing of it, and I got no additional blue screens. However, I recently formatted that HDD and installed Windows 7 fresh (did a full format, not a refresh). No issues until last night, apparently, when the computer had two blue screens, one with stop 19 and another with stop F4. WinDbg isn't insanely helpful.

WinDbg analyze dump for the stop F4 error (occurred first, chronologically):

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008bdd5b0, Terminating object
Arg3: fffffa8008bdd890, Process image file name
Arg4: fffff80002fdbe70, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8008bdd5b0

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`047fa9c8 fffff800`0306dcb2 : 00000000`000000f4 00000000`00000003 fffffa80`08bdd5b0 fffffa80`08bdd890 : nt!KeBugCheckEx
fffff880`047fa9d0 fffff800`03024d8b : ffffffff`ffffffff fffffa80`08dcd5c0 fffffa80`08bdd5b0 fffffa80`08bdd5b0 : nt!PspCatchCriticalBreak+0x92
fffff880`047faa10 fffff800`02f8f484 : ffffffff`ffffffff 00000000`00000001 fffffa80`08bdd5b0 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29ce6
fffff880`047faa60 fffff800`02cd6853 : fffffa80`08bdd5b0 fffff880`c0000005 fffffa80`08dcd5c0 fffffa80`08a00260 : nt!NtTerminateProcess+0xf4
fffff880`047faae0 00000000`779edc7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01c7ecd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779edc7a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe

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

WinDbg analyze dump for the stop 19:

6: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8009c4b7d0, The pool entry we were looking for within the page.
Arg3: fffffa8009c4b800, The next pool entry.
Arg4: 000000000403007d, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec2100
 fffffa8009c4b7d0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dbbcae to fffff80002c845c0

STACK_TEXT:  
fffff880`02e1e1d8 fffff800`02dbbcae : 00000000`00000019 00000000`00000020 fffffa80`09c4b7d0 fffffa80`09c4b800 : nt!KeBugCheckEx
fffff880`02e1e1e0 fffff880`04974b3b : 00000000`00000000 00000000`00000002 fffffa80`414c764e fffffa80`0880e1d8 : nt!ExDeferredFreePool+0x12da
fffff880`02e1e290 00000000`00000000 : 00000000`00000002 fffffa80`414c764e fffffa80`0880e1d8 fffffa80`09c4b700 : nvlddmkm+0x7db3b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+7db3b
fffff880`04974b3b ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvlddmkm+7db3b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55dc6eed

FAILURE_BUCKET_ID:  X64_0x19_20_nvlddmkm+7db3b

BUCKET_ID:  X64_0x19_20_nvlddmkm+7db3b

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

Attached are the DM Logs results (.zip)

 

[axe0]

Hi MBD,

The 0x19 says that the cause is the Nvidia Video driver.
Unfortunately I cannot look in the dumps to determine any possible causes for the 0xf4, because I get symbol errors (likely due to corruption).

Please use the tool again and upload the zip file.

 

[Laith]

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

There's some 0xF4's. This could mean that there's a virus, a failing harddrive, failing RAM stick/s. Run SeaTools(DO NOT RUN FOR SSDS) http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html Also run MemTest86+ for 8 passes. It must be MemTest86+. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html Scan your computer for viruses using Malwarebytes. http://www.sevenforums.com/tutorials/338716-malwarebytes-anti-malware-free.html