bsod problem

wilson1980 · Jan 12, 2010

wonderin if anyone can help. guy in my work keeps having a problem with his 64 bit computer. he's changed everything apart from mother board and processor but keeps gettin a bsod and thats even changing os xp 32bit /vista 64bit and memory. he's just got win 7 upgrade but doesnt want to put it on till he finds out why he keeps gettin this bsod. i got him to find the minidump it leaves which he gave to me this morning so i run it on windbg and this is what it came back. ive never used this windbg before but the error at the bottom its sayin could be the cause. when i get home im going to run the mini dump again on my 64bit computer as i used windbg 32 bit to read this in work so just incase it say problem is different.

ive google this ntoskrnl.exe but has anyone had aproblem with this before or know anything else about it. cheers

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

Loading Dump File [C:\Documents and Settings\office1\Desktop\Mini011110-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 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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02dcddb0
Debug session time: Mon Jan 11 23:19:27.298 2010 (GMT+0)
System Uptime: 0 days 0:26:56.139
*********************************************************************
* 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 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, fffffa60005ec180, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe

Followup: MachineOwner
---------

techquest · Jan 12, 2010

Just a quick suggestion. Why not put W7 on another partiton or spare drive and just proove the point that it just might be vista that is causing the problem. Nothing to loose and everything to gain as W7 is by far a better os than vista will ever be and your m8 will see that instantly when he can see it with hopefully a quick solution.

wilson1980 · Jan 12, 2010

techquest said:
Just a quick suggestion. Why not put W7 on another partiton or spare drive and just proove the point that it just might be vista that is causing the problem. Nothing to loose and everything to gain as W7 is by far a better os than vista will ever be and your m8 will see that instantly when he can see it with hopefully a quick solution.

cheers for reply bud.. ive said for him to give that a try as he's put off upgradin the win 7 upgrade incase it keeps doin it as it has with xp and vista but like u said no harm tryin.

another part off the message in the program i run it says

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

DEBUG_FLR_IMAGE_TIMESTAMP: 4a796b09

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

i clicked another option in it and it came up that..ive said for him if he does get another processor id go with intel as its an athlon one he has just now. ive had both and prefered intel for some reason. never had any bother with it unlike my athlon i had ages ago..

Bally12345 · Jan 12, 2010

Is it a ready built computer or self build which has been overclocked etc? Just read hes changed everything except mobo and cpu... Could be a problem with voltages if its a overclocked machine...

Give PC specs... eg cpu, ram, mobo, psu.

Try going to bios and save current settings then loading optimised defaults. If that dont work then you can just load the saved settings again.

techquest · Jan 13, 2010

wilson1980 said:
cheers for reply bud.. ive said for him to give that a try as he's put off upgradin the win 7 upgrade incase it keeps doin it as it has with xp and vista but like u said no harm tryin.

another part off the message in the program i run it says

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

DEBUG_FLR_IMAGE_TIMESTAMP: 4a796b09

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

i clicked another option in it and it came up that..ive said for him if he does get another processor id go with intel as its an athlon one he has just now. ive had both and prefered intel for some reason. never had any bother with it unlike my athlon i had ages ago..

looks to me that he does not have the debug tools set up properly in that you need to set the symbols file path correctly otherwise it won't have the symbols to debug with and thats why his log reads the way it does.

To make sure he needs to do the following

Once you have downloaded and installed the tools, go to start, all programs, Debugging Tools For Windows, Windbg. Once you open Windbg, you will presented with a blank screen. Click on File, Symbol File Path. Here you will enter the symbols path. Symbols are needed to effectively debug.

The path will be:

SRV*c:\symbols*Symbol information

Enter in this path and click OK. Now, go to File, Save Workspace so that your symbols path is saved for future use.

bsod problem

wilson1980

Premium Member

techquest

DW Regular

wilson1980

Premium Member

Bally12345

VIP Member

techquest

DW Regular

Similar threads

We value your privacy