Blue Screen!Help!

Question

Blue Screen!Help!

Anonymous

Hi,

My system crashed several times in one day.

Here is my log, help me! thanks!

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_5f390000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_5f390000

Debugger can not determine kernel base address

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7600.16385.x86fre.win7_rtm.090713-1255

Machine Name:

Kernel base = 0x83c14000 PsLoadedModuleList = 0x83d5c810

Debug session time: Sun Aug 15 11:06:32.732 2010 (GMT+8)

System Uptime: 0 days 1:06:04.669

WARNING: Unable to reset page directories

Missing image name, possible paged-out or corrupt data.

*** WARNING: Unable to verify timestamp for Unknown_Module_5f390000

*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_5f390000

Debugger can not determine kernel base address

Loading Kernel Symbols

Missing image name, possible paged-out or corrupt data.

.Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

Loading unloaded module list

.Image path too long, possible corrupt data.

....Image path too long, possible corrupt data.

...Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

...Image path too long, possible corrupt data.

....Image path too long, possible corrupt data.

..Image path too long, possible corrupt data.

.Missing image name, possible paged-out or corrupt data.

.Image path too long, possible corrupt data.

...Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

..Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

....Image path too long, possible corrupt data.

.Image path too long, possible corrupt data.

..

WARNING: .reload failed, module list may be incomplete

0: kd> !analyze v

Page b65657 too large to be in the dump file.

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, 807c5120, 1}

Page b65657 too large to be in the dump file.

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Page b65657 too large to be in the dump file.

Page 1311a43 too large to be in the dump file.

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 1

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

0: kd> !analyze -v

Page b65657 too large to be in the dump file.

*******************************************************************************

* *

* 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: 00000061, Clock interrupt time out interval in nominal clock ticks.

Arg2: 00000000, 0.

Arg3: 807c5120, The PRCB address of the hung processor.

Arg4: 00000001, 0.

Debugging Details:

Page b65657 too large to be in the dump file.

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Page b65657 too large to be in the dump file.

Page 1311a43 too large to be in the dump file.

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 1

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

Missing image name, possible paged-out or corrupt data.

Unable to read KLDR_DATA_TABLE_ENTRY at 5303f46d - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:

8d10f57c 00000000 00000000 00000000 00000000 0x83cf0d10

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

0 additional answers

Answer 1

Hi,

When exactly do you get the Blue screen?
Was it working fine earlier?

If it was working fine you may perform System Restore to an earlier point of time when everything was working fine else load BIOS [Basic Input Output System] defaults.

Step 1:

System Restore:

Before you start System Restore, save any open files and close all programs. Once you confirm your restore point, System Restore restarts your computer.

To open System Restore, follow the steps below:

a. Open System Restore by clicking the Start button. In the search box, type System Restore, and then, in the list of results, click System Restore.‍

b. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

Access the link below to know more about System Restore:

http://windows.microsoft.com/en-us/windows7/System-Restore-frequently-asked-questions

**Step 2:**If you are using the computer for the first time, then I suggest you to load BIOS defaults.

BIOS DISCLAIMER:

Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can e solved. Modifications of the settings are at your own risk.

Also make sure you update the all drivers like chipset, network card and sound card.

Regards, Manasa P – Microsoft Support.

Share via

Blue Screen!Help!

0 additional answers