BSOD (Again)

This crash occurred after only 25 seconds of uptime. This means it is most likely either a hard issue or a driver issue. Can you boot in the Safe mode without a BSOD? If you can, that points to a likely driver issue. If you get a BSOD in the Safe mode, it is likely a hardware issue. I see this BSOD occurred during a cold boot. A failing power supply can cause this.

Your dump blames wininit.exe for the crash. This file is a Windows system startup file. There are some viruses that disguise themselves as wininit.exe. I suggest you download and install Malwarebytes. Update it and then run a scan to make sure you don't have a nasty lurking about on your system.

I find two outdated drivers loaded on your system. The rest of your drivers look good. Update these two drivers and see if they make a difference.

LHidFilt.Sys Wed Jun 17 12:49:39 2009 - Logitech SetPoint HID Filter Driver. Downloads.

LMouFilt.Sys Wed Jun 17 12:49:43 2009 - Logitech SetPoint HID Filter Driver. Downloads.

Let me know if you can cold boot in the Safe mode without a BSOD. That will tell us what we should try next. If you can boot in the Safe mode, enable Driver Verifier. Driver Verifier will cause a BSOD if it encounters a problem driver. Upload any and all Driver Verifier enabled dumps. Follow the instructions in this tutorial precisely: Driver Verifier - Enable and Disable. If you get a BSOD in the Safe mode, run Memtest again from a cold boot after your computer has been off for a while. RAM - Test with Memtest86+

I see that you successfully updated the Logitech drivers. Very good. Your RTKVHD64.sys driver is up to date. The 0.0000005 error code means memory corruption. One of the two Driver Verifier enabled dumps contained no data; it is corrupt. Make sure Driver Verifier is turned off for now.

Run Memtest again from a cold boot after your computer has been off for at least two hours. RAM - Test with Memtest86+. I want to be as certain as we can be (Memtest is not perfect) that RAM is not causing the problem. Post your results.

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`03296e50
Debug session time: Sat Dec 11 14:10:18.711 2010 (GMT-5)
System Uptime: 0 days 0:00:25.428
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98002e08d60, 0, fffff8800691cef6, 0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

Could not read faulting driver name
Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98002e08d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8800691cef6, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033010e0
 fffff98002e08d60 

FAULTING_IP: 
RTKVHD64+d9ef6
fffff880`0691cef6 8b4630          mov     eax,dword ptr [rsi+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003cc82b0 -- (.trap 0xfffff88003cc82b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003cc84d8
rdx=fffff88003cc8440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800691cef6 rsp=fffff88003cc8440 rbp=0000000000000002
 r8=0000000000000000  r9=fffff8800691cef6 r10=0000000000000000
r11=fffff80003243e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
RTKVHD64+0xd9ef6:
fffff880`0691cef6 8b4630          mov     eax,dword ptr [rsi+30h] ds:3e80:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003149f14 to fffff800030c9740

STACK_TEXT:  
fffff880`03cc8148 fffff800`03149f14 : 00000000`00000050 fffff980`02e08d60 00000000`00000000 fffff880`03cc82b0 : nt!KeBugCheckEx
fffff880`03cc8150 fffff800`030c782e : 00000000`00000000 fffff8a0`0140910c fffffa80`07038000 fffff800`030fc33f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`03cc82b0 fffff880`0691cef6 : fffff880`03cc84d8 00000000`00000000 fffff8a0`0140910c fffffa80`06d0ef40 : nt!KiPageFault+0x16e
fffff880`03cc8440 fffff880`03cc84d8 : 00000000`00000000 fffff8a0`0140910c fffffa80`06d0ef40 00000000`00000000 : RTKVHD64+0xd9ef6
fffff880`03cc8448 00000000`00000000 : fffff8a0`0140910c fffffa80`06d0ef40 00000000`00000000 fffff800`00000000 : 0xfffff880`03cc84d8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+d9ef6
fffff880`0691cef6 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+d9ef6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c80ab93

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+d9ef6

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+d9ef6

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

Yes it is weird and it really sounds like a power supply problem.

Odd thing is, that wasn't how it happened before! It would BSOD in the middle of running Firefox or watching a movie!

*Sorry, ignore this. I actually had a bad RAM stick when I first had errors (it's being RMA's at the moment).

Run Check Disk

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).

Copy/paste the results into your next post.

I also suggest that your run an SFC (System File Checker) scan. SFC /SCANNOW Command - System File Checker.