[getownse]

Asus Rampage II Extreme
Corsair Dominator 12GB (6 x 2GB)
Thermaltake Toughpower W0156RU
Evga GTX 285 x2 (SLI)
Vista Ultimate 64 (SP1)

While running Warhammer Online (DirectX10) in SLI and Windowed Mode, I will get a BSOD before I can even log in my character (maybe 30 seconds to 1 minute in)

If I run in single card mode, I can usually play for a few hours before a crash.

It only seems to crash on this one game.

Prime95 = ~8 hours no crash.
3DMark = No crash (in SLI and Single)
MemTest = Overnight = No errors

Blue Screen
-------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800D6498AC
BCP3: 00000000BE000000
BCP4: 0000000000800400
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini030109-01.dmp
C:\Users\Gary\AppData\Local\Temp\WER-28891-0.sysdata.xml
C:\Users\Gary\AppData\Local\Temp\WER79B1.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

-----------------------------------------------------------------

[rainforest123]

Hello & Welcome to Tech Guy Forum.

Good job including the mini dumps. 1 of us will analyze them.

How's ventilation inside the PC?

Do your video cards have GPU fans? Are they in good condition?

Can you relate the onset to installation / removal of hardware / software or updates to Windows, drivers, AV program?

Has the system ever functioned as desired? If so, what changed?

Did you read this?
http://forums.techarena.in/windows-v...nce/734708.htm

Source:
http://www.google.com/search?num=100...24&btnG=Search

I suggest that while waiting for the mini dump analysis, that you download, but NOT install drivers for:
motherboard chipset
video cards
sound cards

Think about using Acronis True Image, www.acronis.com to clone your HDD, or make an image of your HDD. Previously, they had a fully functional 14 day trial program.

RF123

[getownse]

Wanted to also add that my processors is a Core i7 965 Extreme and my Ram is DDR3-1600.

Now to your questions:

** How's ventilation inside the PC?

Ventilation is really good. Have a Cooler Master 932 HAF. The CPU during heavy burn in maxes at 68c. (Hot CPU Tester Pro). Normal run is around 42c. Playing the game (when it isn't crashing) is about 48c. (Using Real Temp 3.00 for measuring)

My GPU cards (GTX 285) never went over 68c. (Using RivaTuner v2.24) Most the time hovers at 55c-60c

I am not over clocking anything, and all components are using stock fan/heat sink.

** Do your video cards have GPU fans? Are they in good condition?

My entire system is brand new, about 3 days old. Fresh out of the package, all stock, no over clocking.

** Can you relate the onset to installation / removal of hardware / software or updates to Windows, drivers, AV program?

Wish I could. The computer has a fresh windows vista 64 installed, and all of the drivers are up to date. Including the ASUS Rampage II Extreme BIOS (v1104) All downloaded from official sites. Except for my nVidia drivers, they are newer then the RC. I'm using the 185.20 drivers. However, I had this issue when I had the 182.06 drivers. I'm attaching my DXDIAG file as well.

I have also disabled in the BIOS all motherboard devices except for the lan port. This includes onboard sound, firewire, 2nd lan port, etc.

** Has the system ever functioned as desired? If so, what changed?

I was impressed by all the benchmarks and burn in applications I ran: very good scores, and not once did my computer fault. Including: Hot CPU Tester Pro, MemTest86+, Prime95, 3DMark, Sandra, Everest Benches, etc. In most cases (MemTest86+, Hot CPU, ..) I ran the application for hours.

I played a few other directx games (Neverwinter Nights, Call of Duty, Crysis, Farcry 2) and had no issues at all. It wasn't till I tried Warhammer that I saw a problem.

* Did you read this?
* http://forums.techarena.in/windows-v...nce/734708.htm

Yes, it was my introduction to this website =)

* Source:
* http://www.google.com/search?num=100...24&btnG=Search

I have been searching a lot, because I have only a week to find out which parts are bad to RMA without shipping costs/worry.

* I suggest that while waiting for the mini dump analysis, that you download, but NOT install drivers for:
* motherboard chipset
* video cards
* sound cards

I have already installed the latest versions =( I have also downloaded the MS diag tool and vista symbols and debugged the files myself. But the problem seems to be very random, from audio drivers (before I disabled them in bios), to network, to core thread interrupts.

* Think about using Acronis True Image, www.acronis.com to clone your HDD, or make an image of your HDD. Previously, they had a fully functional 14 day trial program.

Since this computer is only a few days old, I have no worries about losing data, but thanks for bringing it up

RF123

[Rollin' Rog]

I've taken a brief look at the minidumps -- many of them indicate a "hardware" error without specifics; others point to memory management drivers, Yukon ethernet driver, Nvidia, and intel chipset drivers -- quite a list.

You might want to give the ram some thorough testing. You can try Vista's built-in tester for starters. (run mdsched.exe). When the sytem reboots and you reach the user interface, press F1 for the advanced menu and run the extended tests.

I notice that this is 64 bit Windows -- and I have seen many issues with the 64 bit version when folks have SLI enabled. Approaches to this include disabling SLI, and/or updating chipset, bios and graphics drivers to the latest versions.


You might want to review the latter part of this thread for what I believe was a similar issue that took some time to resolve >>

http://forums.techguy.org/windows-vi...-screen-2.html

[getownse]

I followed your instructions, 5 hours later the machine rebooted and when I logged in I got a messenger-like pop up that said:

"No memory errors were detected"

Which doesn't surprise me with the number of MemTest86+ and Prime95s I have ran (Including Prime95 with 3DMark at the same time overnight) in hopes something will error out and help me find the root of the problem.

Now that I have all the newest drivers, updated my bios, and turned all mobo devices off... I have narrowed it down to 1 reoccurring error I have copy/pasted at the bottom of this post.

Also, while playing WAR, there are many times that I freeze with no blue screen, and no reboot. It just locks indefinitely. I have let it sit there for 30 minutes to 45 minutes and it will not recover. It even locks before the game engine even begins, during the initial introduction videos. From startup on a cold machine, to 5-10 seconds after launching the game.

The locks ups only seems to happen reliably with SLI active and running in windowed mode.

Thanks for your help! Any advice for next steps?

Gary

----------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000019
BCP2: 0000000000000000
BCP3: FFFFFA6001843180
BCP4: 0000000000000004
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini030109-03.dmp
C:\Users\Gary\AppData\Local\Temp\WER-28329-0.sysdata.xml
C:\Users\Gary\AppData\Local\Temp\WER73C8.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

------------------

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa6001843180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: winss.exe

CURRENT_IRQL: d

STACK_TEXT:
fffffa60`0d2c3188 fffff800`01cc0321 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`01843180 : nt!KeBugCheckEx
fffffa60`0d2c3190 fffff800`01c6ae7a : fffff800`021613c0 fffffa60`0d2c32b0 fffffa60`0d2c3300 fffff800`021613c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`0d2c31d0 fffff800`0213ed74 : 00000000`00000000 00000001`3090eaf3 00000000`00000000 00000001`309122e2 : nt!KeUpdateSystemTime+0xea
fffffa60`0d2c3200 fffff800`01c72aed : 00000000`2abb6a00 fffff980`02911408 00000000`00000000 fffff6fc`c0014811 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`0d2c3230 fffff800`01cb9644 : fffffa60`00000000 fffff980`02911408 00000000`00000000 00000000`00000004 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`0d2c33c0 fffff800`01c7ffe7 : fffff800`01de2220 fffffa80`0e273bb0 38500000`8d9a6921 fffffa80`0e273bb0 : nt!KeFlushSingleTb+0xf4
fffffa60`0d2c33f0 fffff800`01c6fed9 : 00000000`00000001 00000000`00000007 00000000`00001000 fffff980`02911400 : nt!MmAccessFault+0xff7
fffffa60`0d2c34e0 fffffa60`010da2be : 00000000`00000000 fffffa60`0d2c3758 fffffa80`00000400 fffffa80`00000001 : nt!KiPageFault+0x119
fffffa60`0d2c3670 fffffa60`010dbcd0 : fffff880`00bb9aa0 fffffa80`0bcd6010 fffffa60`0c1b92b0 fffff880`00196bd0 : Ntfs!NtfsChangeAttributeValue+0x28e
fffffa60`0d2c3810 fffffa60`010d5e50 : fffffa60`0c1b92b0 fffff880`00bb9aa0 fffff880`00bb9bd0 fffff880`00196bd0 : Ntfs!NtfsUpdateStandardInformation+0x26e
fffffa60`0d2c3920 fffffa60`01023999 : fffffa80`09d5ad20 fffffa80`0b651450 fffffa60`0c1b9210 fffffa80`0e273bb0 : Ntfs!NtfsCommonCleanup+0xa00
fffffa60`0d2c3d30 fffff800`01c6b637 : fffffa60`0c1b9210 f8e9e9e9`c32b2b2b b8040404`d0595959 d0595959`b8040404 : Ntfs!NtfsCommonCleanupCallout+0x19
fffffa60`0d2c3d60 fffff800`01c6b5ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffffa60`0c1b9130 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa6001843180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffffa60`005af9a8 fffff800`01cfe321 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`01843180 : nt!KeBugCheckEx
fffffa60`005af9b0 fffff800`01ca8e7a : fffff800`01c413c0 fffffa60`005afad0 fffffa60`005afb20 fffff800`01c413c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`005af9f0 fffff800`01c1ed74 : 00000000`00000000 00000000`7573d23a 00000000`00000000 00000000`75740a28 : nt!KeUpdateSystemTime+0xea
fffffa60`005afa20 fffff800`01cb0aed : 00000000`1fb41769 fffffa80`0687b580 00000000`00000000 00000000`714e8959 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`005afa50 fffff800`01cd0665 : fffff800`01e20b40 fffff800`01dd3b00 00000000`00000000 fffffa80`09d23060 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`005afbe0 fffff800`01cd085c : 00000000`00000000 fffff6fd`30002308 00000000`00000006 fffff800`01ca39b1 : nt!KxFlushEntireTb+0xc5
fffffa60`005afc10 fffff800`01ca3b8a : 00000000`00005000 00000000`00000080 fffff6fd`30002308 00000000`00005000 : nt!KeFlushTb+0x30
fffffa60`005afc40 fffff800`01ca3442 : 00000000`00000049 00000000`0000007f 00000000`00000080 fffff800`00820550 : nt!MiMapPagesForZeroPageThread+0x13a
fffffa60`005afc80 fffff800`0209bb1e : 01c6fe48`00000000 fffffa80`00000000 00000000`00000000 fffff800`020ea000 : nt!MmZeroPageThread+0x362
fffffa60`005afd20 fffff800`01ed1ff3 : 00000000`00000020 fffff800`01ce9539 00000000`00000010 00000000`00000286 : nt!Phase1Initialization+0xe
fffffa60`005afd50 fffff800`01ce9546 : fffff800`01dce680 fffffa80`09d23060 fffff800`01dd3b80 fffff800`00820550 : nt!PspSystemThreadStartup+0x57
fffffa60`005afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

[rainforest123]

RR is the expert in this thread.

You could:
run your PC with only 2 sticks of ram. Try to determine if the problem happens with 4 of the 6 sticks removed. If no problem with sticks 1 & 2, you can narrow it down from there.

I prefer www.memtest86.com , run for > 8 hrs , but I can't provide you with a side by side comparison of Memtest86 and Microsoft's ram diag.

Keep us posted.

RF123

[getownse]

I was finally able to recreate the issue with OCCT.

http://www.ocbase.com/perestroika_en/index.php?Download

After running the OCCT:GPU test for 9 minutes, I got the following BSOD error (I have attached the dump)

After running the OCCT:CPU test for 3 minutes, my CPU is overheating. The test stops with 'CPU is too hot'. It is only at a 4% OC. (I have attached the images)

EDIT: http://picasaweb.google.com/getownse/Computer#

Here are pictures of my PC. To view for air flow. Yes, I know I have 3x Evga GTX 285 Tri-Sli however, the card does not fit in the Rampage II Extreme (it wont' allow the card to seat with the power/reset cable. It will also not fit between the gap left by the Power Supply and the motherboard. I am thinking about moving the Power above the MOBO and bending the power/reset pins, but right now I have to get the PC to run with 2 cards =(
------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800D002C6E
BCP3: 00000000BE000000
BCP4: 0000000000800400
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini030109-04.dmp
C:\Users\Gary\AppData\Local\Temp\WER-29655-0.sysdata.xml
C:\Users\Gary\AppData\Local\Temp\WER7B85.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409

[rainforest123]

Try removing your over clocking and improving the cooling of the GPUs and CPU.

RF123

[getownse]

I'm sorry, I did not explain well enough =)

My PC is not overclocked, everything in the bios is set to AUTO.

The OCCT software is designed to stress your CPU, GPU, Power Supply etc. It does this both logically and by slowly overclocking the device until the temperature hits max or an error occurs. My CPU overclocked to 4% until it overheated at MAX (100% cpu processing on all 4 cores/8 threads). During this time, the CPU did NOT error.

However, the OCCT stressing the graphics card did error out but never maxed out the temperature. The max temp was at 71 when the error occurred.

To demonstrate that my computer is running cool enough, I downloaded software to save a screenshot every few seconds. I ran this software until I crashed. I attached the last screenshot that was taken.

The CPU temperatures were: 56, 55, 65 and 54.
The GPU temperatures were: 71 and 63.

[rainforest123]

g:
Thanks for educating me!

Your images depict a lot of cooling potential from the fans. Perhaps the hardware sub forum gurus can provide advice for cooling your system.

RF123

[getownse]

Few things I have done, with no success.

1) Dropped to 2 sticks of ram. Fail. Replaced those 2 with 2 more. Fail. Replaced those 2 with 2 more. Fail. Tried all combinations. All Fails.
2) I have 4 GTX 285 cards. 3 of mine, and my friend let me borrow his. I tried all combinations in sli mode. All Failed.
3) I have reset my CMOS and reinstalled Windows Vista 64 with vendor drivers for all parts. Fail.
4) I flashed my BIOS with the latest and downloaded all the latest drivers. Fail.
5) Disabled all Motherboard Devices (Firewire, 1 Lan port, USB, Audio) Fail.
6) Fixed my BIOS to 3.2mhz and DDR3-1600 and turned off Turbo Mode (slightly OCs when needed) Failed.
7) Fixed BIOS to 3.2mhz and DDR3-1333/1066. Failed.
8) Reseated the CPU. Failed.

Knowns:

- Heating is not an issue, Application hangs with very cool temperatures. 48 CPU and 55 GPU was lowest temps on hang.
- Not the Video Cards or RAM
- Not the on board Audio
- The error that is plaguing me is Bug Error 0x101. CLOCK_WATCH_TIMEOUT.
* General consensus on this bug is
a) HARDWARE: one of the CPU cores is bad
b) SOFTWARE: one of the CPU threads deadlocks (driver)
c) OTHER: lots of other speculations

Things not tested:

- Replaced CPU
- Replaced Motherboard
- Replaced SLI Bridge (The cable that binds the 2 cards)
- Replaced Power Supply
- Used a Different Operating System

----------------------

I'm going to try and RMA the CPU tomorrow. Please let me know if you guys can think of anything else.

Thank you for all your feedback and help

[Rollin' Rog]

Most of these minidumps are similar in that they do suggest a hardware problem leading to a system hang.

How are you monitoring the temps -- are you doing it under load or just looking at the BIOS or other monitor when no heavy processing is taking place? Waiting until after a hang has taken place may be too late if there is much delay in viewing the temps.

In the dumpcheck you posted the active process was winss.exe which belongs to Windows OneCare Live -- but I think this is probably coincidental.

I don't think you have tested with SLI turned completly off at the BIOS level have you? If it's the SLI configuration having a problem in 64 bit Vista -- you need to determine that.

Still I would probably RMA the CPU as well if everything you've tried up to now has failed.

After running the OCCT:CPU test for 3 minutes, my CPU is overheating. The test stops with 'CPU is too hot'. It is only at a 4% OC. (I have attached the images)

The above would certainly make me suspicious that the CPU is not properly heatsinked or otherwise being cooled.

[getownse]

Most of these minidumps are similar in that they do suggest a hardware problem leading to a system hang.

I agree. This is the only erorr I am getting now, and it is very easy to reproduce with both the video game, and also OCCT.

http://msdn.microsoft.com/en-us/library/aa469194.aspx

How are you monitoring the temps -- are you doing it under load or just looking at the BIOS or other monitor when no heavy processing is taking place? Waiting until after a hang has taken place may be too late if there is much delay in viewing the temps.

I have dual monitors. On the monitor without the game I am running 'RivaTuner, GPU-z, Real Temp, CPU-z and AsusProbe'. When my computer freezes, I can see the temperature that was registered by these programs. I also downloaded software to take a screenshot of the entire desktop every second, so I could capture the temps to post to the forum (see above).

In the dumpcheck you posted the active process was winss.exe which belongs to Windows OneCare Live -- but I think this is probably coincidental.

I also noticed this. It was one of the only minidumps where the process was not system or WAR.exe. (The game file). I didn't know if that would give more meaning to the CPU core locking.

I don't think you have tested with SLI turned completly off at the BIOS level have you? If it's the SLI configuration having a problem in 64 bit Vista -- you need to determine that.

SLI is deffinately making this issue happen quicker. I played the game with a single card for about an hour before a crash occured. My guess is that not all of the cores are being utilized as much in a single card situation.

Thanks again for your help, I'll keep you posted when I get my replacement CPU.

[Rollin' Rog]

Good luck, this is certainly a messy area with a lot of possible variables. But it's definitely a hardware issue that may be complicated by SLI and 64 bit Vista.

[rainforest123]

g:
Biting the RMA bullet can be difficult, but I think this is the correct decision.

If you are going to return only the CPU, be careful when you remove the heat sink. It is possible to pull the CPU right out of the socket, WITH the ZIF lever still down.
:0

I know you have an Intel CPU, but this might be helpful.
http://www.amd.com/us-en/Processors/...5E6678,00.html

RF123