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
Having Multiple BSOD's and Windows FTS.
Having Multiple BSOD's while running any program. Multiple instances of Windows Failed to Start, as well, especially when first starting up in the morning. A system restore works for 1-3 hours, then it's back to BSOD's. I tried reinstalling Windows, but the problem is never gone for more than a day...
BSOD Help and Support
Multiple BSOD Windows 7 32
Hi I have recently upgrade pretty much everything(motherboard, RAM, PSU). I did a clean install of Windows 7 Pro 32 bit and updated all drivers. Since the installation I have seen regular crashes each time a different error I duno why but I tried running the system on one RAM module and I don't...
BSOD Help and Support
multiple BSOD Windows 7 x64
Ok so where to start? I bought a custom built computer on ebay with following specs. (yes i know.. this is the part where most people already ask why in the world i would buy a computer of ebay..:o) -Mainboard: ASRock 890GX Extreme 3 -AMD Phenom II X6 1055T AM3 2,6Ghz -4 GB OCZ3P1333LV4GK...
BSOD Help and Support
multiple BSOD on windows 7 OS please help.
Just bought my pc a couple of weeks ago, and it's been giving me multiple BSODs quite often. AMD Phenom II x455 3.2gHz Asus M4A87TD/USB3 motherboard Radeon HD 5850 1gig memory OCZ 2x2gig memory 550w true power supply I've attached the minidumps here in this zip file.
BSOD Help and Support
Windows 7 HP Multiple BSOD (Pt 2)
Hi everyone. New to the forum so I'm not sure how it's done, but I'm having a bunch of problems with Windows 7 HP and I need some advice. I upgraded from Vista 64 to Windows 7 64-bit and the same problems still exist. It used to happen once a month but now its happening everyday. It just...
BSOD Help and Support
Windows 7 Pro x64 Multiple BSOD
Hello, I have just recently installed Windows 7 Pro x64 on my machine and it has been giving me seemingly random blue screens, about once or twice a day and it does not seem to matter what the computer is doing when it crashes. It seems to run perfectly and then randomly crash. I am attaching my...
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 07:09.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App