Windows 7: BSOD help!

kewljoe · 31 Jul 2010

Hi keep getting BSODs when in games, I have latest drivers of my video card and sound card could use some help please. I uploaded my dmp file to skydrive here:
073110-19047-01.dmp - Windows Live

Custom Built PC
OS is Windows 7 64bit
4GB Ram

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

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000061
BCP2: 0000000000000000
BCP3: FFFFF880009E7180
BCP4: 0000000000000001
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\073110-19047-01.dmp
C:\Users\kewljoe\AppData\Local\Temp\WER-40170-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

CarlTR6 · 31 Jul 2010

We prefer that you upload your dumps here to the forum.

[1 - Novice] How to ask for help with a BSOD problem

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

This dump is an error code 101. Please read these two threads and then post any questions you might have.

http://www.sevenforums.com/crash-loc...tml#post567135

http://www.sevenforums.com/crashes-debugging/35427-win-7-clock-interrupt-bsod-101-error.html#post356791

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\073110-19047-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Sat Jul 31 11:18:44.475 2010 (GMT-4)
System Uptime: 1 days 13:33:16.254
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0c1de478 fffff800`02a6c443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e7180 : nt!KeBugCheckEx
fffff880`0c1de480 fffff800`02ac6cf7 : 00000000`00000000 fffff800`00000001 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`0c1de510 fffff800`02a0f895 : fffff800`02a34460 fffff880`0c1de6c0 fffff800`02a34460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0c1de610 fffff800`02abaaf3 : fffff800`02c38e80 00000000`00000001 fffff880`0c1de730 fffff800`02aba207 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0c1de640 fffff800`02a7d999 : fffffa80`06e06000 fffffa80`06ac1000 fffff880`0c1de9b0 fffff880`1289a13f : nt!KiInterruptDispatchNoLock+0x163
fffff880`0c1de7d0 fffff800`02dbd158 : 00000000`00000000 fffff880`0c1deca0 fffff800`02a4e000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`0c1de840 fffff800`02dbe149 : 00000000`0918e950 fffff800`02db9cee 00000000`00000000 00000000`00000040 : nt!ExpQuerySystemInformation+0x1368
fffff880`0c1debe0 fffff800`02abd853 : fffffa80`04a00000 000007fe`f9d80b98 ffffffff`fffec780 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`0c1dec20 00000000`775e00ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a8f148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e00ba


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_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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

merkat106 · 31 Jul 2010

you don't have to repost your dmp

from what I can tell, your bsod is hardware related: CLOCK_WATCHDOG_TIMEOUT.

try this:
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

CarlTR6 · 31 Jul 2010

Refresh your page, I have added information to my post.

merkat106 · 31 Jul 2010

This is the output of my debugging:

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002a4e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0c1de478 fffff800`02a6c443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e7180 : nt+0x70600
fffff880`0c1de480 00000000`00000101 : 00000000`00000061 00000000`00000000 fffff880`009e7180 00000000`00000001 : nt+0x1e443
fffff880`0c1de488 00000000`00000061 : 00000000`00000000 fffff880`009e7180 00000000`00000001 fffff800`02b1739f : 0x101
fffff880`0c1de490 00000000`00000000 : fffff880`009e7180 00000000`00000001 fffff800`02b1739f 00000001`00000000 : 0x61

STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner

CarlTR6 · 31 Jul 2010

I find some obsolete drivers on your system. Win 7 does not like older drivers. They can and do cause conflicts and crashes. Older software and hardware can create problems. The following drivers should be updated:

AnyDVD.sys Thu Mar 20 13:41:59 2008 - AnyDVD Filter Driver or Watch & copy any DVD! belongs to the software AnyDVD by SlySoft, Inc (www.slysoft.com). I recommed that you uninstall this software.

ctac32k.sys Wed Jul 02 04:38:22 2008 - Creative AC3 SW Decoder Device Driver (WDM) belongs to the software Creative AC3 Software Decoder or Creative Audio Product by Creative Technology Ltd (www.creative.com). Update this driver or uninstall the software.

ElbyCDIO.sys Tue Aug 07 15:48:36 2007 - ElbyCD Windows NT/2000/XP I/O driver or ElbyCD Windows NT/2000 I/O driver belongs to the software CDRTools or ElbyCDIO Driver or DVD Region Killer or VirtualCloneDrive by Elaborate Bytes AG (www.elby.ch). Update this software or uninstall.

ElbyDelay.sys Wed Dec 13 14:14:48 2006 - See above

emBDA64.sys Fri Aug 31 20:34:08 2007 - I think this one is an MSI (Microstar) or TM TV tuner. Update this driver if you can or upgrade your TV tuner to one that is compatible with Win 7.

emOEM64.sys Fri Aug 31 17:13:47 2007 - See above

mcdbus.sys Tue Feb 24 05:34:07 2009 - s MagicISO SCSI Host Controller belongs to the software MagicDisc or Driver for MagicISO SCSI Host Controller by MagicISO, Inc. See if you can update this driver.

Here is how we recommend updating drivers:

Quote:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Let us know if we can help you.

kewljoe · 31 Jul 2010

thanks for the quick responses, be back w/ my results in a few.

CarlTR6 · 31 Jul 2010

We will be here.

kewljoe · 31 Jul 2010

Ok so I checked the bios and I have latest, I started uninstalling drivers and everything points to my TV Tuner I dont know how the hell thats supposed to link in to when I play but whatever, dont know why it would cause a conflict if it still works just fine. Anyways thanks for the help!!

CarlTR6 · 01 Aug 2010

You are very welcome; it is a pleasure to help.

The drivers for the TV tuner are obsolete and are conflicting with Win 7 corrupting the memory. You may not be using the TV tuner at the time; but the drivers are loaded into memory and interfering with other things in the memory - thus memory corruption. I suggest you completely uninstall the TV tuner and replace it with one compatible with win 7.

Windows 7: BSOD help!

BSOD help! problems?