big bsod problem

hi im having a problem with a bsod that has occured for along time.
THis can happen when ever. It can take weeks before it happen or just minutes after
eachother.
But i guess its happening when i play games mostly i think.

Im getting memory dump fail from windows xp,vista and 7.
Iv run memtest on my ram and gotten NEW ram but same fault.

I have NO heating problem since i can see the temp on my display card,cpu and case temp and all of thos are low/normal.

I sure its a hardware problem,but i need to know WITCH item thats making the problem.

Iv uploaded the memdump file. plz help me

Im using a itel core 2 quad 9300
Asus p5e3 motherbord
Asus nvidia geforce 9800 gtx
6gig ocz ram

Hello and welcome to SF.

The fact that you're getting it from all of your operating system does "ensure" that it's a hardware problem. Especially because that minidump that you enclosed is bugcheck 0x124 - UNCORRECTABLE_HARDWARE_ERROR:

Code:

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


Loading Dump File [C:\Users\Devin\AppData\Local\Temp\Rar$DI00.591\022310-21902-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7100 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e88e90
Debug session time: Tue Feb 23 14:14:42.942 2010 (GMT-5)
System Uptime: 0 days 0:00:07.956
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800623b8f8, 0, 0}

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: fffffa800623b8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031bd6f0 fffff800`02f05a99 : fffffa80`0623b8d0 fffffa80`05215680 00000000`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`02de6ba7 : fffffa80`0623b8d0 fffff800`02e60638 fffffa80`05215680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`02d50b85 : fffff800`02ec23a0 00000000`00000001 fffff880`00dde080 fffffa80`05215680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`02cd3744 : fffffa80`061eee00 fffff800`02ec2400 fffffa80`05215600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`02f53e66 : 0c50938b`48cd7cfd 00000000`00000001 fffffa80`05215680 89147b38`4008e9c1 : nt!ExpWorkerThread+0x11a
fffff880`031bdd40 fffff800`02c80a86 : fffff880`02f64180 fffffa80`05215680 fffff880`02f6efc0 89c1b60f`820c8b3c : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d37580 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

1: kd> r
rax=fffffa80065b4000 rbx=fffffa800623b8f8 rcx=fffff880031bd730
rdx=fffff88002f00000 rsi=0000000000000000 rdi=fffffa80065b4000
rip=fffff800030f32bc rsp=fffff880031bd6f0 rbp=0000000000000001
 r8=000000000000f1e0  r9=00000000000007ff r10=000000000000060c
r11=0000000000000000 r12=fffff80002ec23a0 r13=0000000000000001
r14=0000000000000000 r15=fffff88002f68f40
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`030f32bc 48897c2438      mov     qword ptr [rsp+38h],rdi ss:0018:fffff880`031bd728=fffffa8000000910
1: kd> k
Child-SP          RetAddr           Call Site
fffff880`031bd6f0 fffff800`02f05a99 nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`02de6ba7 nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`02d50b85 nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`02cd3744 nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`02f53e66 nt!ExpWorkerThread+0x11a
fffff880`031bdd40 fffff800`02c80a86 nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 nt!KxStartSystemThread+0x16
1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`031bd6f0 fffff800`02f05a99 : fffffa80`0623b8d0 fffffa80`05215680 00000000`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`02de6ba7 : fffffa80`0623b8d0 fffff800`02e60638 fffffa80`05215680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`02d50b85 : fffff800`02ec23a0 00000000`00000001 fffff880`00dde080 fffffa80`05215680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`02cd3744 : fffffa80`061eee00 fffff800`02ec2400 fffffa80`05215600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`02f53e66 : 0c50938b`48cd7cfd 00000000`00000001 fffffa80`05215680 89147b38`4008e9c1 : nt!ExpWorkerThread+0x11a
fffff880`031bdd40 fffff800`02c80a86 : fffff880`02f64180 fffffa80`05215680 fffff880`02f6efc0 89c1b60f`820c8b3c : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d37580 00000000`00000000 : nt!KxStartSystemThread+0x16
1: kd> lmnts,m
           ^ Syntax error in 'lmnts,m'
1: kd> lmntsm
start             end                 module name
fffff880`01038000 fffff880`0108f000   ACPI     ACPI.sys     Tue Apr 21 23:23:23 2009 (49EE8DAB)
fffff880`00fe3000 fffff880`00fee000   amdxata  amdxata.sys  Tue Mar 10 19:22:44 2009 (49B6F644)
fffff880`00e92000 fffff880`00e9b000   atapi    atapi.sys    Tue Apr 21 23:23:18 2009 (49EE8DA6)
fffff880`00fb9000 fffff880`00fe3000   ataport  ataport.SYS  Tue Apr 21 23:23:22 2009 (49EE8DAA)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Wed Apr 22 01:28:26 2009 (49EEAAFA)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Tue Apr 21 23:23:28 2009 (49EE8DB0)
fffff880`00d50000 fffff880`00dae000   CLFS     CLFS.SYS     Tue Apr 21 23:23:24 2009 (49EE8DAC)
fffff880`01531000 fffff880`015a3000   cng      cng.sys      Tue Apr 21 23:56:45 2009 (49EE957D)
fffff880`0149c000 fffff880`014aa000   crashdmp crashdmp.sys Wed Apr 22 00:10:01 2009 (49EE9899)
fffff880`01486000 fffff880`0149c000   disk     disk.sys     Tue Apr 21 23:23:30 2009 (49EE8DB2)
fffff880`013dc000 fffff880`013e5000   dump_atapi dump_atapi.sys Tue Apr 21 23:23:18 2009 (49EE8DA6)
fffff880`014aa000 fffff880`014b6000   dump_ataport dump_ataport.sys Tue Apr 21 23:23:18 2009 (49EE8DA6)
fffff880`013e5000 fffff880`013f8000   dump_dumpfve dump_dumpfve.sys Tue Apr 21 23:25:16 2009 (49EE8E1C)
fffff880`00e9b000 fffff880`00eaf000   fileinfo fileinfo.sys Tue Apr 21 23:39:41 2009 (49EE917D)
fffff880`00dae000 fffff880`00df9000   fltmgr   fltmgr.sys   Tue Apr 21 23:23:28 2009 (49EE8DB0)
fffff880`015b4000 fffff880`015be000   Fs_Rec   Fs_Rec.sys   Tue Apr 21 23:23:17 2009 (49EE8DA5)
fffff880`015be000 fffff880`015f8000   fvevol   fvevol.sys   Tue Apr 21 23:25:27 2009 (49EE8E27)
fffff880`017af000 fffff880`017f9000   fwpkclnt fwpkclnt.sys Tue Apr 21 23:24:33 2009 (49EE8DF1)
fffff800`02c06000 fffff800`02c4f000   hal      hal.dll      Wed Apr 22 01:23:51 2009 (49EEA9E7)
fffff880`016ad000 fffff880`016b6000   hwpolicy hwpolicy.sys Tue Apr 21 23:23:11 2009 (49EE8D9F)
fffff800`00bd3000 fffff800`00bdd000   kdcom    kdcom.dll    Wed Apr 22 01:27:31 2009 (49EEAAC3)
fffff880`01517000 fffff880`01531000   ksecdd   ksecdd.sys   Tue Apr 21 23:24:14 2009 (49EE8DDE)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Tue Apr 21 23:57:47 2009 (49EE95BB)
fffff880`00cff000 fffff880`00d3c000   mcupdate mcupdate.dll Wed Apr 22 01:25:27 2009 (49EEAA47)
fffff880`00e78000 fffff880`00e92000   mountmgr mountmgr.sys Tue Apr 21 23:23:27 2009 (49EE8DAF)
fffff880`0108f000 fffff880`01099000   msisadrv msisadrv.sys Tue Apr 21 23:23:13 2009 (49EE8DA1)
fffff880`014b9000 fffff880`01517000   msrpc    msrpc.sys    Tue Apr 21 23:24:51 2009 (49EE8E03)
fffff880`0169b000 fffff880`016ad000   mup      mup.sys      Tue Apr 21 23:26:49 2009 (49EE8E79)
fffff880`016be000 fffff880`017af000   ndis     ndis.sys     Tue May 12 22:51:22 2009 (4A0A35AA)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Tue Apr 21 23:25:37 2009 (49EE8E31)
fffff800`02c4f000 fffff800`03229000   nt       ntkrnlmp.exe Tue Apr 21 23:51:21 2009 (49EE9439)
fffff880`01231000 fffff880`013dc000   Ntfs     Ntfs.sys     Tue Apr 21 23:24:23 2009 (49EE8DE7)
fffff880`010a6000 fffff880`010bc000   partmgr  partmgr.sys  Tue Apr 21 23:23:32 2009 (49EE8DB4)
fffff880`00f71000 fffff880`00fa4000   pci      pci.sys      Tue Apr 21 23:23:19 2009 (49EE8DA7)
fffff880`010bc000 fffff880`010c3000   pciide   pciide.sys   Tue Apr 21 23:23:21 2009 (49EE8DA9)
fffff880`00e68000 fffff880`00e78000   PCIIDEX  PCIIDEX.SYS  Tue Apr 21 23:23:19 2009 (49EE8DA7)
fffff880`015a3000 fffff880`015b4000   pcw      pcw.sys      Tue Apr 21 23:23:14 2009 (49EE8DA2)
fffff880`00d3c000 fffff880`00d50000   PSHED    PSHED.dll    Wed Apr 22 01:28:36 2009 (49EEAB04)
fffff880`0144c000 fffff880`01486000   rdyboost rdyboost.sys Tue Apr 21 23:40:07 2009 (49EE9197)
fffff880`01009000 fffff880`01038000   SCSIPORT SCSIPORT.SYS Wed Apr 22 00:10:02 2009 (49EE989A)
fffff880`010ca000 fffff880`011fe000   spkg     spkg.sys     Sun Jul 26 16:13:14 2009 (4A6CB8DA)
fffff880`01800000 fffff880`01808000   spldr    spldr.sys    Wed Mar 25 15:59:44 2009 (49CA8D30)
fffff880`0180e000 fffff880`019fe000   tcpip    tcpip.sys    Tue May 12 22:52:38 2009 (4A0A35F6)
fffff880`01099000 fffff880`010a6000   vdrvroot vdrvroot.sys Wed Apr 22 00:10:21 2009 (49EE98AD)
fffff880`0168b000 fffff880`0169b000   vmstorfl vmstorfl.sys Tue Apr 21 23:49:30 2009 (49EE93CA)
fffff880`00fa4000 fffff880`00fb9000   volmgr   volmgr.sys   Tue Apr 21 23:23:30 2009 (49EE8DB2)
fffff880`00e00000 fffff880`00e68000   volmgrx  volmgrx.sys  Tue Apr 21 23:24:00 2009 (49EE8DD0)
fffff880`01400000 fffff880`0144c000   volsnap  volsnap.sys  Tue Apr 21 23:23:40 2009 (49EE8DBC)
fffff880`00ebe000 fffff880`00f62000   Wdf01000 Wdf01000.sys Tue Apr 21 23:25:47 2009 (49EE8E3B)
fffff880`00f62000 fffff880`00f71000   WDFLDR   WDFLDR.SYS   Tue Apr 21 23:23:28 2009 (49EE8DB0)
fffff880`01000000 fffff880`01009000   WMILIB   WMILIB.SYS   Tue Apr 21 23:23:25 2009 (49EE8DAD)
Mini Kernel Dump does not contain unloaded driver list

Follow the instructions here for step #2: System Information Collection - Windows Live

i dowloaded the seagate program but cant see any faults yet.
Can a harddrive give a mem dump error?

done and uploaded the file

Unfortunately, it looks like you chose the wrong number (4 instead of 2?), but this will produce the same outcome.

Open an elevated command prompt (Start>type cmd>right-click>Run as administrator) and copy/paste the following commands, one after the other:

Code:

wevtutil qe Application /c:50000 /rd:true /f:text > "%userprofile%\Desktop\ApplicationLog.txt"
wevtutil qe System /c:35000 /rd:true /f:text > "%fuserprofile%\Desktop\SystemLog.txt"

These will make two files on your Desktop, ApplicationLog.txt and SystemLog.txt. Zip them together and attach them to your next post. I'll still look at what you posted; it's just more minidump files. Can't hurt.

I could not find the systemlog.txt when i pasted the command you wrote.
But i did run the 2nd step from the program and uploaded that to you in the application1 zipp.

I also zipped and uploaded the ApplicationLog.txt i found from your command line.
Dont know if they are the same but i would think so :P

I really hope you can find out whats wrong. Iv worked as a computer tech a few years but thos memory dump problems are hateful.

The logs aren't very helpful because they're in a foreign language...

There isn't much debugging to do with 0x124. All that it tells us is that you're having a hardware issues. Make sure that your BIOS is up-to-date as well. Finally, follow the steps here: https://www.sevenforums.com/crash-loc...-what-try.html

Also, have you ever changed any voltage settings in the BIOS?