 | |
| |
| 22 Mar 2010 | #1 |
| | 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 Specs | |
| 22 Mar 2010 | #2 |
| | 
Quote: Originally Posted by kristianc  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 Specs |
 |
Crashes in stand-by mode problems?
| Thread Tools | |
| Similar help and support threads for: Crashes in stand-by mode | ||||
| Thread | Forum | |||
 Windows Normal Mode Crashes to BSOD and Safe Mode doesn't load | BSOD Help and Support | |||
| Need help: video crashes in XP Mode | Virtualization | |||
| Stand alone version of MS Word has disappeared from WinXP Mode | Microsoft Office | |||
| Crashes in Sleep mode | BSOD Help and Support | |||
| Sleep mode crashes PC | BSOD Help and Support | |||
All times are GMT -5. The time now is 02:55 PM.
