Bug Check 0×1000008E When Turning TV On

[nsainfreek]

Bug Check 0×1000008E When Turning TV On

I have an HTCP running Windows 7 Ultimate. No issues when I was running via VGA/DVI to my computer monitor but I have moved it into my entertainment room and connected to my Samsung Plasma via HDMI. When I just need to run computer processes or downloads, I turn off the TV and Receiver and just let the computer run. When I turn the TV back on later I get the Bug Check BSOD.

I am uncertain how long I need to leave the TV off because if I turn it off and back on five minutes later there is no issue. But I have left it running over night and came back to turn it on and I get the BSOD.

The crash seems to happen the instant I turn the TV back on. I checked the logs, and the crash time stamps reflect the time that I turn the TV on.

I followed the instructions for the memory dump but the file came out to over 200MB and around 69MB zipped. Not sure if that is need but I've attached just one of the minidumps to this post and have a megaupload link for the entire memory dump.

If anyone can help, I would be very grateful. Thanks.

Here's a link to the complete memory dump:
MEGAUPLOAD - The leading online storage and file delivery service

 

[zigzag3143]

I have an HTCP running Windows 7 Ultimate. No issues when I was running via VGA/DVI to my computer monitor but I have moved it into my entertainment room and connected to my Samsung Plasma via HDMI. When I just need to run computer processes or downloads, I turn off the TV and Receiver and just let the computer run. When I turn the TV back on later I get the Bug Check BSOD.

I am uncertain how long I need to leave the TV off because if I turn it off and back on five minutes later there is no issue. But I have left it running over night and came back to turn it on and I get the BSOD.

The crash seems to happen the instant I turn the TV back on. I checked the logs, and the crash time stamps reflect the time that I turn the TV on.

I followed the instructions for the memory dump but the file came out to over 200MB and around 69MB zipped. Not sure if that is need but I've attached just one of the minidumps to this post and have a megaupload link for the entire memory dump.

If anyone can help, I would be very grateful. Thanks.

Here's a link to the complete memory dump:
MEGAUPLOAD - The leading online storage and file delivery service

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 this crash was caused by ks.sys

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


Loading Dump File [C:\Users\K\Desktop\032110-37440-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 = 0x82c39000 PsLoadedModuleList = 0x82d81810
Debug session time: Sun Mar 21 14:06:06.976 2010 (GMT-4)
System Uptime: 0 days 17:30:53.443
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 1000008E, {c0000005, 83a13772, 922979d0, 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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : ks.sys ( ks!KspPinPropertyHandler+10b )

Followup: MachineOwner
---------

 

[nsainfreek]

Sorry, but I'm not completely clear on everything you recommend me to do. I'm not sure what the "symbols" are.

My Windows is already activated and it is a legit copy, not a torrent or pirated. Nonetheless, I went to the website and ran the validation. I also ran the sfc.exe/scannow. With the Microsoft incident, I'm not sure what I should be asking them. I know you listed those exe files that Windows Debugging Tools can't access but I'm not clear on what I'm supposed to access Microsoft.

How will I know if any of this has resolved the issue? Should I post another dump?

Also, what is ks.sys?

Thanks for your prompt reply and taking the time to help me!

 

[nsainfreek]

Also, for my scan I got the following error...

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log."

Does that explain anything?

If I need to reinstall windows do I really need to wipe by hard drive or can I just install?

 

[zigzag3143]

Sorry, but I'm not completely clear on everything you recommend me to do. I'm not sure what the "symbols" are.

My Windows is already activated and it is a legit copy, not a torrent or pirated. Nonetheless, I went to the website and ran the validation. I also ran the sfc.exe/scannow. With the Microsoft incident, I'm not sure what I should be asking them. I know you listed those exe files that Windows Debugging Tools can't access but I'm not clear on what I'm supposed to access Microsoft.

How will I know if any of this has resolved the issue? Should I post another dump?

Also, what is ks.sys?

Thanks for your prompt reply and taking the time to help me!

Lets start with the symbol issue. the latest release from MS is RTM, yours however is marked GDR. they have different files for the core os files. We dont have a way to translate them in to english (symbols)
Built by: 7600.16481.x86fre.win7_gdr.091207-1941

This is the bit that isw giving us fits.

It may be something as simple as an update that has changed
some of the core OS files.

As far as the results of SFC /scannow if you upload the CBS.LOG file I can tell you which files are bad and if you need to re-install. It may be as simple as a repair install

Ken

 

[zigzag3143]

Also, for my scan I got the following error...

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log."

Does that explain anything?

If I need to reinstall windows do I really need to wipe by hard drive or can I just install?

Dont re-install till we look at sbs.log, it may be as easy as a repair install.

ken

 

[nsainfreek]

Ok, here's the CBS.log file.

So what do you recommend I do about GDR vs RTM?

 

[nsainfreek]

Hi, did you manage to figure anything out? Any help would be appreciated.