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: Crashes in stand-by mode

22 Mar 2010   #1
kristianc

Windows 7 professionel
 
 
Crashes in stand-by mode

Hey

I have a Windows 7 professionel version that I use as a Media Center.
I have installed a Anysee tv tuner and suspects the driver for causing som issus. My media center goes into stand-by after 20 minutes of idle time. And that has worked for many months, but after I installed the tv tuner often it is turned off when I have to use it. In the logs I can read I can only se: The previes shutdown was unexpected. Can you help me find the problem? I have attached a minidump file


My System SpecsSystem Spec
.
22 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by kristianc View Post
Hey

I have a Windows 7 professionel version that I use as a Media Center.
I have installed a Anysee tv tuner and suspects the driver for causing som issus. My media center goes into stand-by after 20 minutes of idle time. And that has worked for many months, but after I installed the tv tuner often it is turned off when I have to use it. In the logs I can read I can only se: The previes shutdown was unexpected. Can you help me find the problem? I have attached a minidump file


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\032210-16816-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 = 0x81815000 PsLoadedModuleList = 0x8195d810
Debug session time: Sun Mar 21 21:28:10.827 2010 (GMT-4)
System Uptime: 0 days 17:37:37.732
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
..................
Unable to load image \SystemRoot\system32\DRIVERS\anyseeTU.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for anyseeTU.SYS
*** ERROR: Module load completed but symbols could not be loaded for anyseeTU.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 0, a462b968, 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                                     ***
***                                                                   ***
*************************************************************************
My System SpecsSystem Spec
Reply

 Crashes in stand-by mode




Thread Tools




Similar help and support threads
Thread Forum
PC crashes after 2nd use of sleep mode
Hi all, MY PC won't wake up after the second instance of sleep mode. I have to toggle power to reboot my PC. When this happen, i get a safe boot message indicating the PC did not shutdown correctly. I also receive the following message once the PC boots back up: Problem signature: ...
BSOD Help and Support
Windows Normal Mode Crashes to BSOD and Safe Mode doesn't load
I need some help please as I do not know where to start. I installed a Windows Update a few days ago and then got a BSOD the next time I turned my PC on. So I did a system recovery and this seemed to work. Now, it's happened again without me doing a Windows Update and I cannot get into...
BSOD Help and Support
Need help: video crashes in XP Mode
I would like to run a program that uses video. It's an old program that won't run in Windows 7, but ran well in XP. I just upgraded to Windows 7, but still really need this software, so I was hoping it would run in XP Mode. The installation went well. However, it works only up until the point...
Virtualization
Safe mode crashes
I am in a very unussual situation. When I start my Laptop for a safe mode I hold the F8 key as it reboots, it brings me to the Choice screen. With an arrow Key, I direct it to SAFE MODE hit the enter key and neccessary drivers list is displayed in black, no problems. Then it goes straight to...
Installation & Setup
XP Mode Desktop crashes
I loade XP Mode onto Win 7 HP 64 and the desk top crashes 98% of the time when loading. I press "Restore My Active Desktop" and nothing happens - always have to restore manually. I have deactivated the active destop and tried sevral things. Thanks....
Virtualization
Crashes in Sleep mode
Hey guys, My computer went dead so I had to format and reinstall windows 7 ultimate 32 bit. Everything is working fine when i actually use the computer. But there is an issue when i put it to sleep mode. The computer always successfully enters sleep mode, but it has issues starting back up after...
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 01:49.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App