BSOD problem

[h4x]

Hi,

About week ago my comp started to freeze while playing COD4 for 10-20 minutes. When Win booted up a got error: "Windows recovered from unexpected Shutdown"
Type: Blue Screen, even though I don't get any, game just freezes.
I got really annoyed so I reinstalled game then OS. Now with new OS problem still occurs.
My specs(everything stock no oc)
E8400
ASUS P5Q PRO
GTX280
Corsair Dominator 2x4gb
Corsair psu 650w

Any help would be appreciated.

 

[richc46]

According to your dump report, this is due to a hardware error. The specific nature cannot be determined with this type of analsis. For your information and action
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\N5BQNVW9\minidump[1]\060710-19671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0281f000 PsLoadedModuleList = 0xfffff800`02a5ce50
Debug session time: Mon Jun  7 14:45:37.833 2010 (GMT-4)
System Uptime: 0 days 0:00:07.425
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, fffffa8004d92038, 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: fffffa8004d92038, 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`02fe76f0 fffff800`02ad9a79 : fffffa80`04d92010 fffffa80`039fe680 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fe7c10 fffff800`029bb5a7 : fffffa80`04d92010 fffff800`02a345f8 fffffa80`039fe680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fe7c40 fffff800`02923b85 : fffff800`02a96360 fffffa80`0527d6a8 fffffa80`0527d6a0 fffffa80`039fe680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fe7c80 fffff800`0289c861 : fffff880`00e98e00 fffff800`02923b60 fffffa80`039fe680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fe7cb0 fffff800`02b34a86 : 8901893f`8b044e8b fffffa80`039fe680 00000000`00000080 fffffa80`039e8040 : nt!ExpWorkerThread+0x111
fffff880`02fe7d40 fffff800`0286db06 : fffff880`009ea180 fffffa80`039fe680 fffff880`009f4f40 5e5fffff`6949e808 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe7d80 00000000`00000000 : fffff880`02fe8000 fffff880`02fe2000 fffff880`037c15a0 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> !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: fffffa8004d92038, 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`02fe76f0 fffff800`02ad9a79 : fffffa80`04d92010 fffffa80`039fe680 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fe7c10 fffff800`029bb5a7 : fffffa80`04d92010 fffff800`02a345f8 fffffa80`039fe680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fe7c40 fffff800`02923b85 : fffff800`02a96360 fffffa80`0527d6a8 fffffa80`0527d6a0 fffffa80`039fe680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fe7c80 fffff800`0289c861 : fffff880`00e98e00 fffff800`02923b60 fffffa80`039fe680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fe7cb0 fffff800`02b34a86 : 8901893f`8b044e8b fffffa80`039fe680 00000000`00000080 fffffa80`039e8040 : nt!ExpWorkerThread+0x111
fffff880`02fe7d40 fffff800`0286db06 : fffff880`009ea180 fffffa80`039fe680 fffff880`009f4f40 5e5fffff`6949e808 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe7d80 00000000`00000000 : fffff880`02fe8000 fffff880`02fe2000 fffff880`037c15a0 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> lmtsmn
start             end                 module name
fffff880`0102f000 fffff880`01086000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00e5d000 fffff880`00e68000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e2a000 fffff880`00e33000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e33000 fffff880`00e5d000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01400000 fffff880`01430000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d40000 fffff880`00d9e000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0148a000 fffff880`014fd000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01430000 fffff880`0143e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`015e1000 fffff880`015f7000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0144a000 fffff880`01453000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0143e000 fffff880`0144a000   dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01453000 fffff880`01466000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`00cc0000 fffff880`00cd4000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00e68000 fffff880`00eb4000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0150e000 fffff880`01518000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015a7000 fffff880`015e1000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`017a6000 fffff880`017f0000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02dfb000 fffff800`02e44000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0159e000 fffff880`015a7000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff800`00bbb000 fffff800`00bc5000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0177b000 fffff880`017a6000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00ce8000 fffff880`00d2c000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00e10000 fffff880`00e2a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01086000 fffff880`01090000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`00d9e000 fffff880`00dfc000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`0160f000 fffff880`01621000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01629000 fffff880`0171b000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0171b000 fffff880`0177b000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`0281f000 fffff800`02dfb000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01249000 fffff880`013ec000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`0109d000 fffff880`010b2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f6d000 fffff880`00fa0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011f8000 fffff880`011ff000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e00000 fffff880`00e10000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`014fd000 fffff880`0150e000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00d2c000 fffff880`00d40000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01564000 fffff880`0159e000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01000000 fffff880`0102f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`01608000 fffff880`0160f000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
fffff880`01600000 fffff880`01608000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`010c9000 fffff880`011ef000   spmw     spmw.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`01090000 fffff880`0109d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`017f0000 fffff880`01800000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`010b2000 fffff880`010c7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00fa0000 fffff880`00ffc000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01518000 fffff880`01564000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00eba000 fffff880`00f5e000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f5e000 fffff880`00f6d000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`011ef000 fffff880`011f8000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list

 

[Jonathan_King]

Richard is correct, the cause is hardware. If you upload a few more dmps, we can be even more certain.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Try this free stress test: http://www.mersenne.org/freesoft/

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Test hard drive: HD Diagnostic

 

[h4x]

Ok here's my second dump since I only have two of them(fresh install).
Edit: For memtest can I use USB stick ver ?

 

[richc46]

The results of the last dump test revealed stop error 124.

For further inormation read below.
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Please run a system files check.
Open an elevated command prompt and enter sfc /scannow.
Stop error 0x124 is a hardware error.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.Try this free stress test: Free Software - GIMPS

se !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004d5f038, 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: fffffa8004d5f038, 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`02fda6f0 fffff800`02ac3a79 : fffffa80`04d5f010 fffffa80`03a14040 00000000`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fdac10 fffff800`029a55a7 : fffffa80`04d5f010 fffff800`02a1e5f8 fffffa80`03a14040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fdac40 fffff800`0290db85 : fffff800`02a80360 fffffa80`04d53a58 fffffa80`04d53a50 fffffa80`03a14040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fdac80 fffff800`02886861 : fffff880`00dbce00 fffff800`0290db60 fffffa80`03a14040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fdacb0 fffff800`02b1ea86 : 00000000`00000000 fffffa80`03a14040 00000000`00000080 fffffa80`039ff040 : nt!ExpWorkerThread+0x111
fffff880`02fdad40 fffff800`02857b06 : fffff880`009ea180 fffffa80`03a14040 fffff880`009f4f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fdad80 00000000`00000000 : fffff880`02fdb000 fffff880`02fd5000 fffff880`037d6560 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
---------

 

[Jonathan_King]

Sure, you can use the USB stick version. Just don't use the built-in Windows memory diagnostic. Memtestx86 is the best..

 

[h4x]

I've used sfc command and it says that windows found some problems that could not be fixed and rescanned after restart and get same thing over and over.
I ran prime95 for almost 12 hours and everything is fine. Ran memtest86 for 10 passes - everything is fine.

 

[richc46]

If the computer is working properly, I would not worry about the report from SFC. If you are still having problems, you can try a repair install.

http://www.sevenforums.com/tutorials/3413-repair-install.html?filter[2]=General Tips

 

[Jonathan_King]

Time for a repair install: http://www.sevenforums.com/tutorials/3413-repair-install.html