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: Multiple BSOD in Windows 7

24 Feb 2010   #21
usasma
Microsoft MVP

 
 

_rtm, _gdr, and _ldr are all valid build numbers. When the code comes out (from Microsoft) it'll be _rtm.
Then general releases from Windows Update will sometimes cause it to go to _gdr.
Special fixes (such as hotfixes) that are limited in their scope (only for certain systems) will go to _ldr
Then, when Service Packs get released, it'll return the build to _rtm - and the cycle starts over again :)

Try fixing your symbols using this:
Quote:
Symbol File Path:
FYI - Open WinDbg, go to File...Symbol File Path
Delete anything in the box.
Then copy the stuff in the Code box below and paste it into the box.
Code:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Then click on OK to exit the dialog.
Then close WinDbg and answer Yes when it asks you if you want to "Save information for workspace"
Try this to fix the Norton issue:
Quote:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's



My System SpecsSystem Spec
.
03 Mar 2010   #22
hulagirl

Windows 7
 
 

I've been crashing again. Here are my latest dumps.

usasma - tried those things. No help...
My System SpecsSystem Spec
03 Mar 2010   #23
hulagirl

Windows 7
 
 

and my symbols still appear to be wrong, even though I've posted the correct symbol path:


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


Loading Dump File [C:\Windows\Minidump\030310-17986-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x83217000 PsLoadedModuleList = 0x8335f810
Debug session time: Wed Mar 3 09:34:09.205 2010 (GMT-8)
System Uptime: 0 days 16:44:22.844
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 A, {4, 2, 1, 83282aa6}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ( nt+6baa6 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
.

Reply

 Multiple BSOD in Windows 7




Thread Tools




Similar help and support threads
Thread Forum
BSOD Multiple types multiple times a day, can't pin down the problem
Hello everyone, I came here once before for assistance, but the issue was unable to be resolved. Here is the link to the previous thread. https://www.sevenforums.com/bsod-help-support/342840-several-bsod-no-singular-triggers.html There is no singular trigger to set this off. Sometimes I can...
BSOD Help and Support
Multiple BSOD Multiple Drivers - Fresh Install (atikmdag.sys = main)
Hi, i had been having issues with bluescreens once every week or so. I took action by updating my drivers etc but this did not fix the issue. I re-installed windows and got all my drivers on and such yet the problem persists with more bluescreens, more often and with more driver causes. Before the...
BSOD Help and Support
Multiple BSOD's with multiple errors occuring randomly
Just realized I uploaded the wrong zip folder, It doesn't have everything in it. Fixed that now though! Sorry about the hassle! So I built my own PC a a good few months back, and within a month I experienced a BSOD, and now they are very frequent. They can happen three or four times a day, or...
BSOD Help and Support
BSOD errors. multiple times during multiple programs
windows 7 x64 - original install on system but i don't have my disks. they are somewhere... - full retail version installed - age of the system is approximately 3 years - age of the install is approximately 2 years it seems to happen at random but i get BSODs. approximately 2-3 times a day...
BSOD Help and Support
Multiple BSOD at Random Times with Multiple Drivers Identified
I am trying to get my wife's new computer up and running without any BSOD or program failures. Note that the system was not initially set up to capture the dmp files so all the earliest ones are missing. I presented the initial problems to the original seller who recommended sticking with MSE and...
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 19:42.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App