Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing + streaming

22 Mar 2012   #1

Windows 7 x64
 
 
BSOD playing + streaming

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 Windows 7. 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-50C. 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 65C~. Vcore 1.28V. Core speed 3800MHz.

Here are my dumps:

My System SpecsSystem Spec
.

23 Mar 2012   #2

Windows 7 x64
 
 

bump
My System SpecsSystem Spec
23 Mar 2012   #3

Windows 7 x64
 
 

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 50C temp.)

Edit: Added new dump -> BSOD by just installing some Windows 7 updates (BTW I cant install SP1, I just cant...)
My System SpecsSystem Spec
.


23 Mar 2012   #4

Windows 7 x64
 
 

I'd be really happy if someone looked at it... Please?
Bump.
My System SpecsSystem Spec
23 Mar 2012   #5

Windows 7 Home Premium 64 Bit
 
 

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-d...ease-read.html


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

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


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\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 STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg and post back if you need anything further.
My System SpecsSystem Spec
23 Mar 2012   #6

Windows 7 x64
 
 

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.
My System SpecsSystem Spec
23 Mar 2012   #7

Windows 7 Home Premium 64 Bit
 
 

Code:
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.
My System SpecsSystem Spec
23 Mar 2012   #8

Windows 7 x64
 
 

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?
My System SpecsSystem Spec
23 Mar 2012   #9

Windows 7 Home Premium 64 Bit
 
 

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.
My System SpecsSystem Spec
24 Mar 2012   #10

Windows 7 x64
 
 

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.
My System SpecsSystem Spec
Reply

 BSOD playing + streaming




Thread Tools



Similar help and support threads for2: BSOD playing + streaming
Thread Forum
Solved BSOD 101 while playing AND streaming after new PSU BSOD Help and Support
BSOD Playing Diablo 3, Twitch Streaming BSOD Help and Support
Solved BSOD playing Sims Medieval and when streaming TV or dl win updates BSOD Help and Support
BSOD Randomly when playing games/streaming BSOD Help and Support
BSOD while playing games or streaming BSOD Help and Support
BSOD when streaming videos and playing games BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:26 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33