BSOD The bugcheck was: 0x00000257

[cyla]

Hi guys

This is a different error than the one I had before. I can't find any info on what it might be, so any help is really appreciated.

thanks
Cyla

 

[zigzag3143]

Hi guys

This is a different error than the one I had before. I can't find any info on what it might be, so any help is really appreciated.

thanks
Cyla

Hi Cyla and welcome

This crash was probalby caused by one of the following.



Usual causes: Device driver, BIOS bug, hardware defect (see Significant Posts section below)


I would
run a system file check (type cmd in search>right click and run as admin>sfc /scannow)

Update BIOS

Let us know the results


Ken

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


Loading Dump File [C:\Users\K\Desktop\030910-23906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Mon Mar  8 19:00:50.890 2010 (GMT-5)
System Uptime: 10 days 1:21:54.937
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {18, 0, fffff880009b2180, 4}

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

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0333f528 fffff800`02c6d443 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff880`0333f530 fffff800`02cc95f7 : fffffa80`00000000 fffff800`00000004 00000000`0002625a fffff880`00d8223f : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0333f5c0 fffff800`02c1a090 : 00000000`00000000 fffff880`0333f770 fffff800`02c35460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0333f6c0 fffff800`02cbd3f3 : 00000000`5b66be1b fffff800`02c35460 fffff800`02e39e80 00000000`00000001 : hal!HalpRtcClockInterrupt+0x130
fffff880`0333f6f0 fffff800`02ccee06 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0333f880 fffff800`02cb016c : fffffa80`04479a20 00000000`00000000 00000000`00000000 fffff880`0333faa8 : nt!KeFlushMultipleRangeTb+0x266
fffff880`0333f950 fffff800`02caca11 : fffffa80`05517b60 00000000`00000000 fffff880`0333fc58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`0333fa50 fffff800`02cb418b : fffffa80`07da0558 fffff800`00000001 00000000`00000001 00000000`00001000 : nt!CcFlushCache+0x561
fffff880`0333fb50 fffff800`02cb4d60 : fffff880`041ced00 fffff880`0333fc58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
fffff880`0333fc00 fffff800`02cce161 : fffffa80`0550b800 fffff800`02fba504 fffff800`02ec6140 fffffa80`00000003 : nt!CcWorkerThread+0x1c8
fffff880`0333fcb0 fffff800`02f64166 : 01c9c194`9473f91e fffffa80`05517b60 00000000`00000080 fffffa80`054ed040 : nt!ExpWorkerThread+0x111
fffff880`0333fd40 fffff800`02c9f486 : fffff880`03186180 fffffa80`05517b60 fffff880`031910c0 00010000`00000725 : nt!PspSystemThreadStartup+0x5a
fffff880`0333fd80 00000000`00000000 : fffff880`03340000 fffff880`0333a000 fffff880`0333f9f0 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
---------