problema ar windows 7 ultimate x64

[voldis]

pa laikam paradas zils ekrans...es dabuju to dump failu un tur ne ko nesaprotu...varbut kads sapratis un izskaidros man ko jadara, lai zilais ekrans vairs nelektu ara

 

CPU tips QuadCore AMD Phenom X4 Black Edition 9600, 2300 MHz (11.5 x 200)

Sistēmas plates nosaukums Asus M2N-SLI Deluxe (3 PCI, 2 PCI-E x1, 2 PCI-E x16, 4 DDR2 DIMM, Audio, Dual Gigabit LAN, IEEE-1394)

Sistēmas plates mikroshēmu komplekts nVIDIA nForce 570 SLI, AMD K10

Sistēmas atmiņa 4096 MB (DDR2-800 DDR2 SDRAM)

Videoadapteris NVIDIA GeForce 8800 GT (512 MB)

 

 

Loading Dump File [C:\Windows\Minidump\020610-15678-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: C:\Symbols

Executable search path is:

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

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

Machine Name:

Kernel base = 0xfffff800`0285b000 PsLoadedModuleList = 0xfffff800`02a98e50

Debug session time: Sat Feb 6 08:22:22.729 2010 (GMT+2)

System Uptime: 0 days 0:17:32.523

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

...................

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 101, {31, 0, fffff880009e7180, 1}

 

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

Probably caused by : ntoskrnl.exe

 

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: fffff880009e7180, The PRCB address of the hung processor.

Arg4: 0000000000000001, 0.

 

Debugging Details:

------------------

 

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

 

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: fffff8000285b000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

 

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

CURRENT_IRQL: 0

 

STACK_TEXT:

fffff880`050a9478 fffff800`02879443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e7180 : nt+0x71f00

fffff880`050a9480 00000000`00000101 : 00000000`00000031 00000000`00000000 fffff880`009e7180 00000000`00000001 : nt+0x1e443

fffff880`050a9488 00000000`00000031 : 00000000`00000000 fffff880`009e7180 00000000`00000001 fffff800`02b03900 : 0x101

fffff880`050a9490 00000000`00000000 : fffff880`009e7180 00000000`00000001 fffff800`02b03900 00000001`00000000 : 0x31

 

 

STACK_COMMAND: .bugcheck ; kb

 

FOLLOWUP_NAME: MachineOwner

 

IMAGE_NAME: ntoskrnl.exe

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------