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: getting many bsods, cant find the cause

31 Mar 2010   #1
fighter

Windows 7
 
 
getting many bsods, cant find the cause

hi
i knew how to find the problem in windows xp but in windows 7 the windbg always says i have the wrong symbols
could you guys help me to find what causes so many bsods? this one is a very recent one

thanks


My System SpecsSystem Spec
.
31 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by fighter View Post
hi
i knew how to find the problem in windows xp but in windows 7 the windbg always says i have the wrong symbols
could you guys help me to find what causes so many bsods? this one is a very recent one

thanks
You were getting the wrong symbols as I was because there has been a modification to some of the core OS files

The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds


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


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

Symbol search path is: SRV*F:\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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x83017000 PsLoadedModuleList = 0x8315f810
Debug session time: Wed Mar 31 19:27:15.887 2010 (GMT-4)
System Uptime: 0 days 0:01:24.447
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
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 001904fb
Arg2: 807a1614
Arg3: 807a11f0
Arg4: 830ad03d

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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
My System SpecsSystem Spec
31 Mar 2010   #3
fighter

Windows 7
 
 

my windoes core files had been modified? weird, well i'll follow the steps
My System SpecsSystem Spec
.

Reply

 getting many bsods, cant find the cause




Thread Tools




Similar help and support threads
Thread Forum
Different BSODs cannot find the problem
Hello, I need help figuring out the problem here. It started out of the sudden while playing and never got over it since then. I can't even tell if it's an hardware or software problem because for my mainboard and also for my w-lan card no proper Win7 drivers exist. But I have never had such...
BSOD Help and Support
Random BSODs, Can't Find a Pattern
Hi all, I've been getting intermittent BSODs with various messages - 13 in the last 2 months according to Blue Screen Viewer. The crashes seem to happen fairly randomly, although when I get MEMORY_MANAGEMENT it does at least seem to be when the computer is in use. Also (no idea if related)...
BSOD Help and Support
Regular BSODs, unable to find specific trigger/cause
I'm not sure what to write here, I included the diagnostics zip but I'll fill this out anyway: I'm running Windows 7 Home Premium 64 bit, ATI Radeon HD 4800 series video card, and I've had problems on a pretty regular basis since around late January, when someone attempted to change my system...
BSOD Help and Support
BSODs about twice a week. Can't find cause.
Been having random BSODs lately and it seems only when I leave Chrome open with a few tabs for an extended period of time. I know nothing about the error report when Windows boots up. So that's why I am asking for help here. Random Info: - I had to replace my PSU in December. The new one...
BSOD Help and Support
BSODs while gaming, cannot find cause
Hi everyone I've been having some problems with BSODs while gaming. No one has been able to solve my problem on various forums I've been posting on, so hopefully someone over here is a ninja and knows whats up. Here's my story, hopefully it's not to long Built a new system about a month...
BSOD Help and Support
Keep getting BSODs, can't find the cause
Just recently I've switched from Win7 32bit to 64bit. Never had any problems under 32bit, but with 64bit I keep getting BSODs. I've tried to change some components (new processor, new video card, new RAM), checked to make sure that all drivers are up to date - didn't help. I've unplugged any...
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 02:31.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App