Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: blue screen error

27 Jun 2010   #1
joshaundia

windows 7 ultimate
 
 
blue screen error

every once and a while my computer will shut down giving me the blue screen of death i have attatched my .dmp files please any help would be great\


Code:
 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Windows\Minidump\062710-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c95e50
Debug session time: Sat Jun 26 19:58:24.240 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:46.378
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
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, {61, 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: 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:
------------------
***** 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: fffff80002a58000 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: 
fffff800`00b9bfd8 fffff800`02a76443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e7180 : nt+0x70600
fffff800`00b9bfe0 00000000`00000101 : 00000000`00000061 00000000`00000000 fffff880`009e7180 00000000`00000001 : nt+0x1e443
fffff800`00b9bfe8 00000000`00000061 : 00000000`00000000 fffff880`009e7180 00000000`00000001 fffffa80`036de000 : 0x101
fffff800`00b9bff0 00000000`00000000 : fffff880`009e7180 00000000`00000001 fffffa80`036de000 00000001`00000000 : 0x61
 
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------



My System SpecsSystem Spec
.
27 Jun 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.

https://www.sevenforums.com/crash-loc...-what-try.html

Thanks


Ken
My System SpecsSystem Spec
27 Jun 2010   #3
joshaundia

windows 7 ultimate
 
 

thanks ken I have updated all drivers and bios for mobo still get blue screen error and unexpected shutdowns with no bluescreen error I have already done a mem test and cpu test but i will try removing ram and cleaning case and see what happens I will post the good or bad.
My System SpecsSystem Spec
.

09 Jul 2010   #4
joshaundia

windows 7 ultimate
 
 
Blue screen errors

My computer keeps giving me a blue screen error or it will just shut down I've tested the ram 22 passes with memtest, I also bought a new harddrive, updated drivers and bios on mobo, uninstalled avg, removed ram one at a time, removed dvd rom/and all usbs, and installed new graphics card! STILL NO LUCK! any help would be appreciated I'am about to go broke buying parts.....


Thanks in advance, Shaundia.

P.S. I also attached the latest mini dumps.
My System SpecsSystem Spec
09 Jul 2010   #5
merkat106

Windows 7 Enterprise x64 SP1
 
 

My System SpecsSystem Spec
Reply

 blue screen error




Thread Tools




Similar help and support threads
Thread Forum
Blue Screen Error but no actual blue screen pops up
While using my laptop, usually when trying to open some "windows" application such as task manager, wireless networks, documents, media player, windows updater etc. my laptop freezes or doesn't allow me to click on anything except the minus button on all my windows and the start button. I'll try to...
BSOD Help and Support
Windows 7 x64 Blue Screen error, memory corruption/dll error
I have absolutely no idea what is causing this but I can provide all of the blue screen error text (blue screen viewer is awesome). I can say that the first time it happened I was just playing World of Warcraft when the game crashed to windows which soon after crashed and went to a blue screen...
BSOD Help and Support
Help with blue screen auto reboot, Stop: 0x0000007B error screen
Hello, I have an HP Pavilion g series laptop (running win7) that is in a continuous restarting loop. This happened after the computer auto updated (windows update). I do not know what was updated, but now every time the laptop starts up it seems to be in a continuous rebooting loop after the...
BSOD Help and Support
BSOD error dump files (blue screen error) please help
https://www.sevenforums.com/attachment.php?attachmentid=188494&stc=1&d=1324019702 dump file attachment I am getting the blue screen error. but it is not significant. happens anytime. sometims pc works 24 hours without error. somtimes it comes. please help.
BSOD Help and Support
Blue Screen Error and Change of Screen Resolution
I have a Lenovo ThinkPad Edge 15. The problem I am facing now is The screen resolution changes by itself and after this, a blue screen error comes and computer restarts again. Please Help me on this.. Operating System: Windows 7 Ultimate N (32 Bit) Processor: Core i3
BSOD Help and Support
Blue screen error: With various Error Code (Help pls)
Hi folks, Recently I built a new system and installed with Win7 64bit. Since then, I have been encountering various blue screen errors, after installing various software. However, at the basic (without installing any programs) it work fine. PC Configuration: Processor: AMD Phenom (TM) II...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:56.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App