Windows 7 BSOD

Hi, I have a the debug info of my memory.dmp with me here but I don't know how to analyze it, can you help me? Thanks.. Here it is:


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Sat Aug 1 08:40:20.646 2009 (GMT+8)
System Uptime: 0 days 14:32:13.441
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005a37038, b2000000, 14}

*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005a37038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000014, Low order 32-bits of the MCi_STATUS value.

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

PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd9018). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: f

IRP_ADDRESS: ffffffffffffff88

STACK_TEXT:
fffff880`009f29d8 fffff800`031f9903 : 00000000`00000124 00000000`00000000 fffffa80`05a37038 00000000`b2000000 : nt!KeBugCheckEx
fffff880`009f29e0 fffff800`02d90513 : 00000000`00000001 fffffa80`05a30650 00000000`00000000 fffffa80`05a306a0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f2a20 fffff800`031f95c8 : 00000000`00000728 fffffa80`05a30650 fffff880`009f2db0 fffff880`009f2d00 : nt!WheaReportHwError+0x263
fffff880`009f2a80 fffff800`031f8f1a : fffffa80`05a30650 fffff880`009f2db0 fffffa80`05a30650 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f2bd0 fffff800`031f8dd5 : 00000000`00000002 00000000`00000001 fffff880`009f2e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f2c10 fffff800`031ece88 : fffffa80`09d00010 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f2c40 fffff800`02c7a7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f2c70 fffff800`02c7a613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f2db0 fffff800`02c9b0bd : fffff880`0d792818 fffff880`0d792850 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0d7927b0 fffff800`02c7e8cd : 00000000`00000000 fffffa80`093e6760 fffffa80`093e6701 fffffa80`00000000 : nt!IopCompleteRequest+0x11d
fffff880`0d792880 fffff880`04354a44 : fffff800`02df2e68 fffff800`02f7a902 fffa8005`b7e0b000 00000000`00000000 : nt!IopfCompleteRequest+0x75d
fffff880`0d792960 fffff880`03c39bb9 : 00000000`0012001b 00000000`00000000 00000000`0012001b 00000000`c0000001 : nsiproxy!NsippDispatch+0xb4
fffff880`0d792990 fffff800`02f943a7 : fffffa80`0972c6a0 fffff880`0d792ca0 fffffa80`0972c6a0 fffffa80`09d00010 : kl1+0x2bb9
fffff880`0d792a10 fffff800`02f94c06 : 00000000`01f5e6e0 00000000`000010e8 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0d792b40 fffff800`02c7b153 : fffffa80`045ff8d0 00000000`01f5e6c8 fffff880`0d792bc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0d792bb0 00000000`7717ff2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01f5e758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7717ff2a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_TLB

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_TLB

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

 

Looks like something is up with your GPU. I'm PM'ing you some basic instructions.

 

what version of Win 7 are you using?

 

10char10char

 

oh wasn't look carefully...geez....i'm using the same build and now problem.

 

Did you OC your GPU or undervolt your CPU?

And what AV do you use?