New
#1
BSOD please help!
Here is my minidump file. Please help!
BSOD just after restart of the comp
win 7 64 bit...
Here is my minidump file. Please help!
BSOD just after restart of the comp
win 7 64 bit...
Sorry results inconclusive.
I would do the following anyway
run a system file check
(type cmd in search>right click and run as admin>efc /scannow)
If you are overclocking stop.
Let us know the results.
Ken
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\031210-29078-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa4e50 Debug session time: Fri Mar 12 13:25:51.408 2010 (GMT-5) System Uptime: 0 days 0:02:24.064 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {60, 0, fffff880009e8180, 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: 0000000000000060, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009e8180, 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: explorer.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0793f7f8 fffff800`02885443 : 00000000`00000101 00000000`00000060 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx fffff880`0793f800 fffff800`028e15f7 : 00000000`00000000 fffff800`00000001 00000000`0002625a 00000000`00601aba : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0793f890 fffff800`02832090 : 00000000`00000000 fffff880`0793fa40 fffff800`0284d460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0793f990 fffff800`028d53f3 : 00000000`7d229b8a fffff800`0284d460 fffff900`c339b000 00000000`ffffffff : hal!HalpRtcClockInterrupt+0x130 fffff880`0793f9c0 fffff800`028ec502 : 00000000`00000000 fffff800`00000001 00000000`00000000 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0793fb50 fffff800`028e6f21 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiIpiSendRequestEx+0xb2 fffff880`0793fb90 fffff800`028f1061 : fffff900`c339b062 00000000`00000064 00000000`00000001 fffff960`00134c16 : nt!KeFlushMultipleRangeTb+0x381 fffff880`0793fc60 fffff800`029040fb : 00000000`00000064 fffff880`0793fdc0 fffff900`c339b000 00000000`00000001 : nt!MiFlushTbAsNeeded+0x1d1 fffff880`0793fd70 fffff800`02a08ceb : 00000000`00064000 00000000`00064000 00000000`00000021 fffffa80`05bf6060 : nt!MiAllocatePagedPoolPages+0x4bb fffff880`0793fe90 fffff800`028eb860 : 00000000`00064000 fffff880`030d4cc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePoolPages+0x8e2 fffff880`0793ffe0 fffff800`02a0bbfe : 00000000`00000000 fffff800`028e504b 00000000`00000020 fffff880`030d4cc0 : nt!ExpAllocateBigPool+0xb0 fffff880`079400d0 fffff960`001228ed : fffff900`c2098630 00000000`00000000 00000000`00781370 00000000`025217d8 : nt!ExAllocatePoolWithTag+0x82e fffff880`079401c0 fffff960`00123e0f : 00000000`00000000 fffff880`07940360 00000000`00000001 00000000`76db5dc0 : win32k!AllocateObject+0xdd fffff880`07940200 fffff960`000fb48c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb fffff880`079402f0 fffff960`000fb006 : 00000289`0000009c 00000000`00000289 00000000`01080030 00000000`0000009c : win32k!hsurfCreateCompatibleSurface+0x3bc fffff880`079403c0 fffff800`028d8153 : fffffa80`05bf6060 fffff880`07940520 00000000`0000009c fffff900`c00c0010 : win32k!GreCreateCompatibleBitmap+0x26e fffff880`079404a0 000007fe`fe86290a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`07c2e768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe86290a 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 ---------
here it is.
some file repaired but info was that not all of them.