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: Windows 7 crashing

28 Mar 2010   #1
rcblythe

Windows XP
 
 
Windows 7 crashing

Hi, I am hoping someone can help me with my problem. I downloaded the SF Diagnosis tool so I will attach it and hopefully that will telll you why. Thanks, Rob


My System SpecsSystem Spec
.
28 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by rcblythe View Post
Hi, I am hoping someone can help me with my problem. I downloaded the SF Diagnosis tool so I will attach it and hopefully that will telll you why. Thanks, Rob
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

My best guess is your video driver.

let us know if you need help

Ken



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\Seven Forums\Minidumps\032810-13010-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\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 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 = 0x82856000 PsLoadedModuleList = 0x82995570
Debug session time: Sat Mar 27 21:11:16.543 2010 (GMT-4)
System Uptime: 0 days 0:45:33.229
Unable to load image \SystemRoot\system32\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
......
0: kd> !ANALYZE -V

Unknown option '-V'
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, c000009d, 8577d044, 0}

***** 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                                     ***
***                                                                   ***
*************************************************************************
OLD DRIVERS THAT NEED TO BE UPDATED
Code:
mohfilt.sys        0x91792000    0x91797ba0    0x00005ba0    0x427b57a3    5/6/2005 7:40:19 AM                        
IntelC53.sys        0x91786000    0x91791900    0x0000b900    0x427b57c1    5/6/2005 7:40:49 AM                        
IntelC51.sys        0x904e2000    0x90629180    0x00147180    0x427b581e    5/6/2005 7:42:22 AM                        
IntelC52.sys        0x9062a000    0x906c1180    0x00097180    0x4406209b    3/1/2006 6:30:51 PM                        
secdrv.SYS        0x945f1000    0x945fb000    0x0000a000    0x45080528    9/13/2006 9:18:32 AM                        
emupia2k.sys        0x95d39000    0x95d68000    0x0002f000    0x461a2fd7    4/9/2007 8:21:43 AM                        
ctsfm2k.sys        0x95d68000    0x95d91000    0x00029000    0x461a2fd8    4/9/2007 8:21:44 AM                        
ctoss2k.sys        0x9171e000    0x91752000    0x00034000    0x461a2fdc    4/9/2007 8:21:48 AM                        
ha10kx2k.sys        0x95c2f000    0x95d39000    0x0010a000    0x461a2fde    4/9/2007 8:21:50 AM                        
hap16v2k.sys        0x907c3000    0x907ee000    0x0002b000    0x461a2fe0    4/9/2007 8:21:52 AM                        
ctaud2k.sys        0x91624000    0x916a1600    0x0007d600    0x461a2fec    4/9/2007 8:22:04 AM                        
ctprxy2k.sys        0x91752000    0x9175a000    0x00008000    0x461a2fed    4/9/2007 8:22:05 AM                        
COMMONFX.DLL        0x95e2d000    0x95e48000    0x0001b000    0x461a3043    4/9/2007 8:23:31 AM                        
CTAUDFX.DLL        0x95e48000    0x95ed3000    0x0008b000    0x461a304d    4/9/2007 8:23:41 AM                        
CTSBLFX.DLL        0x95ed3000    0x95f61000    0x0008e000    0x461a3059    4/9/2007 8:23:53 AM
My System SpecsSystem Spec
Reply

 Windows 7 crashing




Thread Tools




Similar help and support threads
Thread Forum
Windows explorer crashing randomly. Windows logs not showing anything
I have attached a copy of he dumpfile. Please let me know if you require any other information. The user cannot replicate the issue, it happens at random times and she isnt starting or stopping any programs around the time of the crash.
General Discussion
Windows 7 keeps crashing blue screen C:\Windows\Minidump\101912-39795-
Hi please can you help me, I have a windows 7 Home premium 64 bit, and the problem is my computer keeps crashing to blue screen and restarting. I've checked my drive for errors and checked my memory and have found nothing!!! I've done a restore system to an earlier point in time and the...
BSOD Help and Support
Windows Explorer crashing, adobe plug in crashing.
Im running windows 7 ultimate 64 ... I dont know totally system specs. It's a custom rig that I purchased about 6 months ago. I dont think the specs matter anyway because I don't believe this is a hadware problem, but a windows problem. Ok, So about a month ago I was unlucky enough to pick up...
General Discussion
crashing windows help plz
windows 7 keeps on crashing while playing games on my pc.when ever i started to play the game,after some time suddenly the system shutdowns itself and no error pops up.previously it never happened,i freshly installed new operating system but the problem remains same.i used to play ea cricket and...
BSOD Help and Support
Windows 7 Crashing... Please Help!
So I'm normally a tomshardware.com user, but the *******s there were not very helpful and quite irritating, so I was told to try seven forums by a friend. Here's my situation: I have just upgraded from Windows 7 RC to Win 7 32 bit Enterprise Edition with no problems. Did a fresh install and...
BSOD Help and Support
Windows 7 crashing
Hi, didn't know where to put this but I have a problem, Windows 7 tends to crash at the moment I think it's something to do with winamp and the automatic scans with AVG but I'm not entirely sure. I have had times before when I've had winamp running and tried initiating a scan on a portable drive...
Performance & Maintenance


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 17:49.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App