According to your dump, you most certainly did not install SP1, and binaries are still all at RTM levels:
Code:
0: kd> vertarget
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a89e50
Debug session time: Thu Apr 9 10:05:28.063 2015 (UTC - 7:00)
System Uptime: 0 days 0:44:25.343
0: kd> lmvm hal
start end module name
fffff800`02803000 fffff800`0284c000 hal (deferred)
Mapped memory image file: C:\ProgramData\dbg\sym\hal.dll\4A5BDF0849000\hal.dll
Image path: hal.dll
Image name: hal.dll
Timestamp: Mon Jul 13 18:27:36 2009 (4A5BDF08)
CheckSum: 0004BD36
ImageSize: 00049000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: hal.dll
OriginalFilename: hal.dll
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: Hardware Abstraction Layer DLL
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> lmvm ntfs
start end module name
fffff880`0120e000 fffff880`013b1000 Ntfs (deferred)
Mapped memory image file: C:\ProgramData\dbg\sym\Ntfs.sys\4A5BC14F1a3000\Ntfs.sys
Image path: \SystemRoot\System32\Drivers\Ntfs.sys
Image name: Ntfs.sys
Timestamp: Mon Jul 13 16:20:47 2009 (4A5BC14F)
CheckSum: 00195F88
ImageSize: 001A3000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NT File System Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> lmvm nt
start end module name
fffff800`0284c000 fffff800`02e28000 nt (pdb symbols) C:\ProgramData\dbg\sym\ntkrnlmp.pdb\DE7B3DD8AC5343B3B4874BAB3F4599DD2\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\dbg\sym\ntoskrnl.exe\4D9FDD345dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Fri Apr 08 21:14:44 2011 (4D9FDD34)
CheckSum: 00547734
ImageSize: 005DC000
File version: 6.1.7600.16792
Product version: 6.1.7600.16792
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16792
FileVersion: 6.1.7600.16792 (win7_gdr.110408-1633)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> !chkimg !nt
3563 errors : !nt (fffff80002b28000-fffff80002b28fff)
I asked that you install SP1, and then fully patch via Windows or Microsoft update. According to this dump file, you most certainly have failed to do so, and corruption in the kernel binary is still causing issues. Until you get SP1 and subsequent patches on here, it will potentially continue to fail. Since there are so many bugs fixed with SP1 and subsequent patches, I don't think it's wise to troubleshoot anything without these patches. Get SP1 on that system, and then patch please. After that, if you're still seeing issues, you probably want to test your hardware, specifically memory (RAM) and disk, for potential issues.