Help please, random freezes and bsod

[dsapper]

Hello everyone, this is becoming very annoying. My computer has a couple of problems that I think are related. I reinstalled windows 7 but it hasnt solved my problems. Also there is no error code to google on the bsod.

Basically its random, sometimes 30 seconds after starting, sometimes Ill be in a cycle of it not getting to windows, others it will go a week. These are the logs from the minidump files attached.

I have a core 2 extreme x9650, quad sli 9800gx2, 4 sticks of 2gb ram and two raptors in sli with a 1tb storage drive. The computer itself isnt overheating from what I can see (temp gauge on computer).

I've updated the video card drivers.... I'm at a loss. I'm guessing its a hardware issue since a reinstall of windows 7 didnt help but am not sure where to start....

Any help would be greatly appriciated!!!

 

[ttran]

These crashes were caused by hardware. Please use these instructions to find out what that means and to figure out what to try.

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

Download hard drive diagnostic from manufacture's site and test your hard drive please:
HD Diagnostic

BUGCHECK SUMMARY:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.337\072910-19312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Fri Jul 30 06:39:42.570 2010 (UTC + 7:00)
System Uptime: 0 days 0:04:59.256
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80086fd028, b2000008, 6000e0f}

Probably caused by : hardware

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff880098cd808, fffff880098cd070, fffff80002c9df5a}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanupOnNewStack+42 )

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

 

[Jonathan_King]

Welcome!

These appear to be caused by hardware. See this article: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

I am suspicious of hard drive in particular. Please test it: HD Diagnostic

Also test other components. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

[font=lucida console]
BugCheck 124, {0, fffffa80087e1028, b2000040, 800}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa80086fd028, b2000008, 6000e0f}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa80087de028, b2000000, 175}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa8008a63028, b2000008, 6000e0f}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa800876c028, b2000000, 175}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa80087e7028, b2000000, 125}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa8008a29028, b2000000, 175}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff880098cd808, fffff880098cd070, fffff80002c9df5a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanupOnNewStack+42 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 124, {0, fffffa8008a3b028, b2000000, 125}
Probably caused by : hardware
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[cluberti]

Uh-oh - the dreaded WHEA 124 STOP error:

Proc. Info 0  @ fffffa8008a3b240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008a3b138
Section       @ fffffa8008a3b2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_WR_ERR (Proc 3 Bank 1)
  Status      : 0xb200000000000125

3: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 3  6,23,6 GenuineIntel 4025 0000060b00000000                   011b3ffe
                      Cached Update Signature 0000060c00000000
                     Initial Update Signature 0000060b00000000
3: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4025
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 23 Stepping 6
ProcessorNameString = REG_SZ Intel(R) Core(TM)2 Extreme CPU X9650  @ 3.00GHz
Update Signature = REG_BINARY 0,0,0,0,c,6,0,0
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 60c00000000

  Processor may be overclocked!
  Expected Frequency: 3000
  Actual Frequency:     4025
  Overclock Ratio:      1.34

There was one NTFS error, but it was inconclusive (could have been a hardware error as well), but the rest are all STOP 0x124 WHEA hardware errors. Specifically, all of them point to either L1 cache write or evict errors on CPU core 3, or bus errors on CPU core 2. Given your CPU is overclocked, the overclock itself could be causing this (that's a pretty large overclock), the CPU could really actually be damaged, or you're having cache miss events where the write back to main memory is failing (although this is the least likely of the 3 options). Since testing RAM is easy, I'd still start with that (to rule that out if possible), and after that you're looking at putting your CPU back to it's stock or underclocking it to see if it still fails, and if so, replacing it.

As I mentioned previously, I'm not as worried as the others about the HDD because the call to NtfsCommonCleanupOnNewStack would cause a filter driver lookup, which would cause an IRP, which would cause a DPC, which would hit the CPU - given there's only one (and all the rest are basically the same CPU failure), I'm fairly convinced the oddball NTFS failure dump is actually a CPU issue as well. I can't prove it without at least a kernel dump, of course, but empirical evidence is overwhelmingly bad for your CPU.

 

[cluberti]

hehehe - seems we all were writing at the same time!

 

[dsapper]

ok, I did the memory test and let it run all night, after 7 passes there wasnt one error so I assume thats ok. I also did a full checkdisk on my raid, also passed with no errors. I couldnt get the recommended hard drive check in the previous threads working so I havent done that.

Ok, so I bought this computer overclocked. I'm no expert here at all but I know how to get into the bios etc. How do I reset it to factory settings, what do I need to record to change it back to the overclock if thats not the culprit?

Thanks for the help so far guys!

 

[ttran]

Turn on your computer and press the key on your keyboard to enter the BIOS. then Go to the last tab or page of your BIOS, Select an option similar to "restore factory settings", finally Save your changes and confirm your selection if necessary. This will often be combined with the process of exiting a BIOS. Some BIOS types may have this as a separate option such as "F10: Save Changes".