debugging a minidump

I am trying to debug my minidumps using the instructions given here on this website using the microsoft debugging tools. I set the symbols path to microsofts symbol server as suggested. when I open the minidump here is what I get. Any help would be greatly appreciated.


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


Loading Dump File [C:\Users\user\Desktop\Mini052809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x81c4d000 PsLoadedModuleList = 0x81d64c70
Debug session time: Thu May 28 06:23:42.906 2009 (GMT-5)
System Uptime: 0 days 8:41:42.291
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.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, 803d1120, 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 ***
*** ***
*************************************************************************
Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

Unable to open image file: C:\Windows\Symbols\ntkrnlpa.exe\49AC8FB43b9000\ntkrnlpa.exe
The system cannot find the file specified.

*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe

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

 

Hi, you drew the short straw, but I will try to help, looks like the path is wrong and you will not get the needed info you need.

From: http://forums.majorgeeks.com/showthread.php?t=35246

Correct path:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

SRV*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols < your path

Hope this helps.

 

I had thought that at first as well. I originally had the path set to

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

and was getting the same error. So, in my thinking, since I had downloaded the symbols and stored them in

C:\windows\symbols

I thought maybe I should change the path to

SRV*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols

but still get the same error. It seems like its not finding the ntkrnlpa.exe file, which is nowhere on my pc for it to find anyway.

I have copied down the error I'm getting in the blue screen finally.

"A clock interrupt was not received on a secondary processor within the allocated time interval."

"Stop:0X00000101"

I have been doing a lot of research on this and seems like maybe the cpu may be bad or unstable for some reason. I have updated the bios to the latest version, 610. I have reset the board to the default settings, so no overclocking going on, everything was set to auto anyway. I am now in the process of making sure all my hardware drivers are updated as per amd's website on that error. I have installed pc probe to watch the cpu voltage and temps, so far nothing over 51 deg c and no more than 1.33 volts. So far I cannot duplicate the problem, seems just happen intermitently. I have opened the case up and checked all connections. I swapped the 2 sticks of ram around, dont have any other to try at this time.

Here is the system info I have

win vista home premium
6.0.6001 service pack 1 build 6001
AMD Athlon 64 X2 Dual Core Processor 5000+, 2600 Mhz
ASUS M4A78 PLUS motherboard
BIOS is American Megatrends, 0602
SMBIOS versio is 2.5
2 GB DDR2 ram
NVIDIA GeForce 8400 GS

 

I tried the debugger again with the path set correctly, again.

Here are the results:

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


Loading Dump File [C:\Users\user\Desktop\Mini053009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81c39000 PsLoadedModuleList = 0x81d50c70
Debug session time: Sat May 30 09:38:50.874 2009 (GMT-5)
System Uptime: 0 days 1:10:06.755
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, 803d1120, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

 

Here is the results of the !analyze -v command

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: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
99ae08dc 81cf1271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
99ae0910 81cf0f7d 99ae091b 000000d1 99ae09a8 nt!KeUpdateRunTime+0xd5
99ae0910 81c58f48 99ae091b 000000d1 99ae09a8 nt!KeUpdateSystemTime+0xed
99ae09a8 81e721ec 00000001 1624b911 00000053 nt!KeFlushProcessWriteBuffers+0x7f
99ae0d4c 81c90a1a 00000053 0035adc8 00000002 nt!NtQuerySystemInformation+0x2254
99ae0d4c 77569a94 00000053 0035adc8 00000002 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0087f9f8 00000000 00000000 00000000 00000000 0x77569a94


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: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

 

Hi again,

Good job, you're making progress. Did you check your memory, if not do so.

http://majorgeeks.com/Memtest86_d1247.html


Also found this and might be your problem, but check your memory and wait for a major geek to look at this link and see if ok to try, I don't want to make matters worse.

http://support.microsoft.com/kb/955076

 

First off I want to thank you for your help, and everyone elses on here.

I ran the memtest, first on single cpu cause I didn't tell it otherwise in time, to busy reading which one to pick. I went ahead and let it finish on cpu0.
It passed with no errors. I rebooted and ran it on both cpu's and it went for over 2 hours, got 4 passes in with no errors. I think the memory is ok.

Let me know what the major geeks think about the windows hotfix that relates to this problem.

The only hardware driver that I can find outdated is the one for my realtek high definition audeo, according to uniblue driverscanner. If I go to the asus website and check the drivers there, it says they are the latest ones. I dont think it is an issue but if you think I should try and update it let me know.

 

I was digging around on ASUS's website this afternoon and seen another update for the bios, released today from what I could tell. I went ahead and updated it and have not seen the bsod since then. It did it twice this morning, once at 9:40 and again at 10:45. I think I updated right after lunch, proabably around 1 or 2. So far so good, maybe that fixed it. I'm keeping my fingers crossed for now, still dont trust it.

 

Well, no such luck. I got up this AM and it had blue screened. I rebooted it and was working on another computer when I glanced over and seen it had done it again. I rebooted it again and looked at the minidump folder to see that the first time it blue screened was at 8:16. Then again at 8:29 and 8:37.
I am using it to reply here. There is an update that was not installed correctly due to not being able to restart the machine, SP2. I wonder if it was trying to restart when it blue screened the first time or something.

 

Hi again,

Did you check the dump file again and see if it's the same error?

Sorry, thought you were a home user with one PC and was being very cautious.

Check and see if the HotFix was installed on the PC, it's included in SP2, so no harm. Not sure if you installed SP2 by your post about the restart in update.

You've updated drivers, bios and maybe SPs so things have changed, looks like your crashes are happening more often now.

Sorry I don't work on PCs just a little geeky and help out here. Looking at the fix the elusive Ntoskrnl.exe is involved. The original issue had to do with the processor racing due to a permission not being set, think you should be able to monitor and see if the processor is racing... if it's still the same issue and not another one or a combo of things now.

Maybe look at the dump again, compare files in fix to what's on the PC and see where you stand.

 

Yes all the dump files are for the same error.

I have 3 pc's going and all networked together, just a home user and geeky.

The hotfix is not installed but I am currently dl SP2 now, dont have much to loose.

The processor does not seem to be racing when it crashes, at least when I've been here. Like I said it can crash when nothing is happening or when I've got a few different things going on. I never did crash when I was running
Orthos on it or during the memtest.

 

Hi If it were me, I would install the HotFix, prior to installing SP2, you're crashing too much to make it through the install of SP2 IMO.

 

I tried installing the hotfix and I kept getting the error "failed to install"
It says to run the update readiness tool and try again. That did no good.
I have not tried since I reinstalled windows. I talked with the company that built the pc today and they want me to try and reseat the processor and double check the thermal paste on the heat sink. I told them the hotest I've seen it is 55C. Guess it wont hurt anything to check it. I am going to try that tonite after work and then try installing the hotfix again. If this dont work I think I will request an RMA from them tomm. I hate not being able to figure it out though.

 

I removed the heat sink and fan from the processor last night and it had good coverage of the thermal paste. I removed the processor and made sure all the pins were ok, they were. I then reinstalled the cpu, heat sink and fan, with new thermal paste. After I rebooted it up I messed around a little bit and sure enough, bsod again, same error code.
Then I dl and installed the hotfix, which installed ok this time. And I'm still getting the bsod. I'm about to the point of thinking it's time to start changing hardware. I guess I'll call the company back today and see what they want to do with it.
Thanks for all your help. I will let you all know what they do or find out.