BSOD playing + streaming

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\DigiCZ\prime95bsod\032412-16926-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03296e70
Debug session time: Fri Mar 23 20:52:36.690 2012 (UTC - 6:00)
System Uptime: 0 days 1:49:34.736
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007d99028, be200000, 5110a}

Probably caused by : hardware

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

6: 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: fffffa8007d99028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, 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:  prime95.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`03101b58 fffff800`03023903 : 00000000`00000124 00000000`00000000 fffffa80`07d99028 00000000`be200000 : nt!KeBugCheckEx
fffff880`03101b60 fffff800`031df923 : 00000000`00000001 fffffa80`07705a60 00000000`00000000 fffffa80`07705ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`03101ba0 fffff800`030235c8 : 00000000`00000728 fffffa80`07705a60 fffff880`03101f30 fffff880`03101f00 : nt!WheaReportHwError+0x263
fffff880`03101c00 fffff800`03022f1a : fffffa80`07705a60 fffff880`03101f30 fffffa80`07705a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03101d50 fffff800`03022dd5 : 00000000`00000008 00000000`00000001 fffff880`03101fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03101d90 fffff800`03016e88 : 00000000`00000000 00000000`43d4ac80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03101dc0 fffff800`030c8dec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03101df0 fffff800`030c8c53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03101f30 00000001`409d3466 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`04dfe420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`409d3466


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

One of those crashes mentions your Ethernet driver (CPU STAB TEST). See if updating it helps: Realtek


The Prime95 test: Stop 0x124 - what it means and what to try

Ok, so I updated that driver and run the CPU STRESS TEST again, and everything was fine /no BSOD), then I run prime95 for 5 hours and nothing happened (no BSOD).

5 mind ago I tried to play an online game but after 5 min i got BSOD... I am really sad right now, wish I never bought the new parts...

Dont know what to do anymore...

How about that Driver Verifier you talkem about?

Did you run all three tests for Prime95 for a few hours each? I'd like to find out about this before proceeding to Verifier.

Also, one other quick test to run (this one does not take long at all):

• Use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

So I did |MG| Video Memory Stress Test for 10 passes and I got 0 errors. Then I did the second Prime95 test for 6 hours -> nothing. Now I've been running the first test for 2 hours and still no error. By the way, earlier today I got BSOD while playing and streaming game with Xsplit (streaming program) like always. Sadly I was too quick that no dump was created, but I think there would be only info about that 0x101 error like usual.

I still think this has somethink to do with CPU, but I am not sure. Also I checked, and my RAMs are not listed in my MoBo's "supported RAMs". But I dont think that this could be the cause of my problem, right? And why is it that my CPUTIN (?? what is it) temperature is around 60-70°C when I do NOTHING on the PC, and now when I am running the tests it is only at 25°C? My CPU's temperatures are now around 70°C, kinda high with my h60 CPU cooler.

Not all sensors are accurate, so I would recommend ignoring any that give readings that do not make logical sense. The two to watch are CPU and GPU and see if you get behavior you would expect as they are stressed. The stress temperatures are more accurate than the idle temperatures for those two components.

RAM that is not included in the Motherboard QVL is not necessarily going to cause problems. It can sometimes, though. The QVL contains the RAM that was diligently tested by the motherboard manufacturer, but it will not contain all compatible RAM. The best place to find out if the RAM is compatible is to ask Kingston whether they guarantee it for your motherboard and processor.

You could also try running with one RAM module at a time and see if you still get the same behavior. Sometimes bad RAM can cause crashes that blame the CPU. A 101 error, if everything else checks out, usually does mean a CPU failure. We need to narrow things down first, though. Avoid Static Damage to Your PC when swapping out system components, such as RAM modules.

So I tried running with only 1 RAM and still the same (got BSOD during gameplay + streaming). Then I completly dismantled all PC pieces and put them together, changed the heat-stuff pasta on CPU and hoped for the best. Sadly, that didnt work either.

When did I get BSOD:

-When playing + streaming ( only playing is OK)
-When I installed random software (.NET framework, ...)
-When I watched video
-During some stress tests

Also, my MoBo is not brand new, I bought it at a auction site, so is there a possibility that the MoBo could be source of this problems?

Quite possible. If the motherboard is interfering with the processor, it could result in these crashes. I would also recommend that you check the CPU itself for any bent pins. Remember, Avoid Static Damage to Your PC when handling the CPU.

Huh, so I guess I know where the problem is now. I just downladed and tested another RAM Memtest and everytime i get 0x101 BSOD. Guess I will try to change to RAMs listed on my MoBo's supported RAM's list. (duh)

Edit: Now that I think about it, it can still be MoBo error colliding with RAMs... I guess I will have to switch to my old MoBo that has 2x DDR3 and 2x DDR2 slots and try my new RAMs there...

This is the dump file from Memtest BSOD:

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\DigiCZ\032712-17019-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`0328fe70
Debug session time: Tue Mar 27 09:22:14.701 2012 (UTC - 6:00)
System Uptime: 0 days 0:06:13.747
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( 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: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  memtest.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`093eda18 fffff800`03071423 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`093eda20 fffff800`030cbb67 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffff880`10097365 : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`093edab0 fffff800`03014895 : fffff800`03039460 fffff880`093edc60 fffff800`03039460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`093edbb0 fffff800`030bfa33 : 00000000`0124ef51 fffff880`093edc01 00000000`fffd8000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`093edbe0 00000000`00401ae3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`025efe7c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x401ae3


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
---------

It was another 0x101 crash.

Let us know how the memory testing goes with the other board.