BSOD playing + streaming

[DigiCZ]

Windows 7 x64 Ultimate
CPU: Core i7 2600k 3.4GHz
MB: Asus p8p67-m pro
RAM: Kingston KHX1600C9D3B1K2/8GX (2x 4gb)
psu: Corsair GS 700
gpu: nvidia geforce gtx570

Just installed new mothermoard, RAMs and CPU (+ hydro cooling system for CPU - H60)
Had some problems with starting windows (BDOS) so I reinstalled whole W7. Then it worked. But now when I play a game (ex. League of Legends) and I turn on my Stream (I capture my game while playing) after like 1 min i get BSOD.

It tells: A clock interrupt was not recieved on a secondary processor within the allocated time interval.

Vcore is at that time at like 1.3 - 1.4 V. Temperature of CPU is 40-50°C. I updated my windows, BIOS is at version 1002, IDK WHAT TO DO. Just spent so much money on smthing that is not working properly Hope you can tell me what is wrong from dumps. THX !

Edit: Doing Prime95 test at the moment. Temperatures are at 65°C~. Vcore 1.28V. Core speed 3800MHz.

Here are my dumps:

 

[DigiCZ]

bump

 

[DigiCZ]

New dumps

Also I have a problem that I cant change my settings in BIOS. I changed a few things then hit F10 for save. The systen retarted but nothing changed... I also updated my BIOS to newest ver. Sometimes when I do this the PC turns off, then on, then after 2 secs back off and then again on. And evey single time it says that I dont have a HDD (but then loads like normal)
I tried Prime95 for 2 hours - nothing happened. Then when I tried to stream and play, after like 20 min BSOD (I had like 30% usage of CPU and 50°C temp.)

Edit: Added new dump -> BSOD by just installing some Win7 updates (BTW I cant install SP1, I just cant...)

 

[DigiCZ]

I'd be really happy if someone looked at it... Please?
Bump.

 

[writhziden]

Sorry to see you were missed... The more you reply in your thread to your own posts, the less likely you are to obtain help. Many of us see the number of replies in the thread and assume someone has already started to assist you. Also, the forum rules ask that you do not bump your thread... http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html


Security Software:??? Recommend either of these two:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

Install all Windows Updates!!! You currently only have a few installed before Service Pack 1; you have 150-200 to install still.

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


Loading Dump File [D:\Kingston\BSODDmpFiles\DigiCZ\newDump\032312-17643-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03098e70
Debug session time: Fri Mar 23 11:35:55.424 2012 (UTC - 6:00)
System Uptime: 0 days 3:04:40.844
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 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: 0000000000000031, 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_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`06ef5e88 fffff800`02e7a423 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`06ef5e90 fffff800`02ed4b67 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff880`010c723f : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`06ef5f20 fffff800`02e1d895 : fffff800`02e42460 fffff880`06ef60d0 fffff800`02e42460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`06ef6020 fffff800`02ec8a33 : 00000000`8a28ea74 fffff800`03045e80 fffff800`03045e80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`06ef6050 fffff800`02eda388 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06ef61e0 fffff800`02ebb76c : fffffa80`01a22060 00000000`00000000 00000000`00000000 fffff800`02eb9813 : nt!KeFlushMultipleRangeTb+0x258
fffff880`06ef62b0 fffff800`02eb8011 : fffffa80`07634b60 00000000`00000000 fffff880`06ef6500 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`06ef63b0 fffff880`012e48ad : fffffa80`1285b0c8 00000000`00000000 fffffa80`00000000 fffffa80`00001000 : nt!CcFlushCache+0x561
fffff880`06ef64b0 fffff880`012a9131 : fffff880`06ef6a70 00000000`00000000 fffff800`03070500 fffff880`06ef6601 : Ntfs!NtfsFlushLsnStreams+0x295
fffff880`06ef6550 fffff880`012aa7eb : fffff880`06ef6a70 fffffa80`1251d180 00000000`00000000 fffff880`06ef6c00 : Ntfs!NtfsCheckpointVolume+0x1391
fffff880`06ef6950 fffff880`012aa9ab : fffff880`06ef6a70 fffffa80`1251d180 fffffa80`1251d188 fffffa80`06d61188 : Ntfs!NtfsCheckpointAllVolumesWorker+0x4b
fffff880`06ef69a0 fffff880`012a9a38 : fffff880`06ef6a70 00000000`00000000 fffff880`012aa7a0 fffff880`06ef6c78 : Ntfs!NtfsForEachVcb+0x167
fffff880`06ef6a40 fffff800`02ed96e1 : fffff800`03070500 fffff800`031c4401 fffffa80`07634b60 00000000`00002000 : Ntfs!NtfsCheckpointAllVolumes+0xb8
fffff880`06ef6c70 fffff800`0316b726 : fffffa80`0c9f0870 fffffa80`07634b60 00000000`00000080 fffffa80`066f0040 : nt!ExpWorkerThread+0x111
fffff880`06ef6d00 fffff800`02eaaac6 : fffff880`02fd5180 fffffa80`07634b60 fffffa80`06703040 fffff880`012222b4 : nt!PspSystemThreadStartup+0x5a
fffff880`06ef6d40 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_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

All the same. Proceed through the steps given in http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html and post back if you need anything further.

 

[DigiCZ]

Ok, so I installed all the updates I could, but I still cannot install the SP1 update. Next, I looked up that link about WATCHDOG and I think I dont understand what to do to fix my problem.

I started with the Driver Verifier - set it up and then waited for BSOD. There was written "Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post."
Does that mean normal dump from Windows/minidump/ ?

Why should I do the stress tests? How will that help me? And I checked for any dust or smthing like that, and my parts are brand new (except for MoBo)
BTW I got the BSOD during the FurMark stability test.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\DigiCZ\032412-19936-01\032412-19936-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e56000 PsLoadedModuleList = 0xfffff800`03092e70
Debug session time: Fri Mar 23 18:17:44.440 2012 (UTC - 6:00)
System Uptime: 0 days 1:01:32.876
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009ea180, 1}

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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009ea180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`031bd638 fffff800`02e74423 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ea180 : nt!KeBugCheckEx
fffff880`031bd640 fffff800`02eceb67 : 00000000`00000000 fffff800`00000001 00000000`000186a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4d8e
fffff880`031bd6d0 fffff800`02e17895 : fffff800`02e3c460 fffff880`031bd880 fffff800`02e3c460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`031bd7d0 fffff800`02ec2a33 : 00000000`a3216926 fffff800`0303fe80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`031bd800 fffff800`02ed9aaa : 00000000`00000000 fffff800`00000001 00000000`00000000 fffff800`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`031bd990 fffff800`02f75ed6 : 00000000`00000000 fffff800`0303fe80 fffff980`1f8c8fc0 fffff800`02ef2ef4 : nt!KiIpiSendRequestEx+0xaa
fffff880`031bd9d0 fffff800`02fccb9d : 00000000`00000001 fffff880`031bda90 fffff6fc`c00fc640 fffff980`1f8c8fc0 : nt!KeFlushSingleTb+0x126
fffff880`031bda50 fffff800`02ff8356 : fffff800`02e56000 00000000`20206f49 00000000`0030329c fffff980`1f8c8fc0 : nt!MmFreeSpecialPool+0x34d
fffff880`031bdb90 fffff800`031be493 : fffffa80`090dd050 fffffa80`06735040 fffff980`199d2fc0 fffffa80`06735040 : nt!ExDeferredFreePool+0xf13
fffff880`031bdc40 fffff800`02ed36e1 : fffff800`0306a500 fffff800`031be470 fffffa80`06735040 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031bdc70 fffff800`03165726 : 00000000`00000000 fffffa80`06735040 00000000`00000080 fffffa80`066afb30 : nt!ExpWorkerThread+0x111
fffff880`031bdd00 fffff800`02ea4ac6 : fffff880`02f64180 fffffa80`06735040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd40 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_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE

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

Another 0x101 crash.

Stress tests will check whether there is a hardware problem and/or whether you have proper cooling for the system. And yes, the memory dump file is the minidump folder in the Windows directory.

 

[DigiCZ]

I think I may have misunderstood. When I turn on the Driver Verifier, it tests the drivers by itself? Or do I have to run a stress test? Or should I just leave the PC like that and wait till some BSOD?
Then, what do you suggest I should do? Try the prime95 stress test for a long period of time?

 

[writhziden]

I would not recommend running the stress tests while running Verifier. They will probably cause erroneous crash results that will point to the wrong culprits. Run the stress tests first (Prime95, furmark, video memory, etc.). Then when you are ready to start Verifier, I will give the updated steps for doing so.

 

[DigiCZ]

So I did the prime95 stress test again, and after 2 hours I got BSOD.
Then I did FurMark and Video memory tests -> nothing happened, all passed.
Lastly I did CPU Stress Test and after 5 min -> BSOD.

Everytime the BSOD said that clock-interrupt something with 0x101.

 

[writhziden]

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: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[DigiCZ]

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?

 

[writhziden]

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.

 

[DigiCZ]

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.

 

[writhziden]

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.

 

[DigiCZ]

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?

 

[writhziden]

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.

 

[DigiCZ]

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:

 

[writhziden]

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.

 

[DigiCZ]

EDIT: OK nevermind, crashed again :3


Hello again, I haven't tested the new MoBo yet, but I was wondering... In BIOS there is option called Hyperthreading, and it says it should be enabled only when using Windows XP or Linux, but I have it enabled on Win7 for "8 CPU cores" (instead of just 4).

But when I checked some websites, a lot of people are using it even with Win7.

Memtest 30% done, no BSOD yet (never crossed 25% line before).