PC Crashes (blue screen) when trying to watch TV

ssubo · 2007-03-05, 18:23

I installed a clean Media Center 2005, the latest MP and I have 2 Tuner Cards: ATI AIW 128 Pro (I use this one to output to TV) and ATI eHome Wonder. Both have the latest drivers and I deleted the ATI AIW 128 Pro from MP configuration, as it has a lot of problems.

Now when I scan the channels it detects them all and shows them with no problem, but when I open MP and try to watch TV, the TV is extremely slow (like flashing the whole MP) and after less than a minute I get the blue screen and my PC is restarted.

I tried using both the MPA and DSCALER. Any ideas on how to solve this issue?

Thanks for your help,

Ssubo

grandalf · 2007-03-05, 21:16

I had similar problems using mce. Went back to standard XP install, and all is OK now. Must be something to do with the media extensions I guess.

ssubo · 2007-03-05, 21:26

I checked the minidump and it looks like the atinewp2.sys is causing the problem... I tried versions 1.17.24.231 and 1.17.24.200 and still get the same BSOD... Any help will be greatly appreciated!

Ssubo

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

Loading Dump File [D:\Mini030507-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Mar 5 16:49:52.390 2007 (GMT-5)
System Uptime: 0 days 0:16:03.981
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** 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
............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 96, {820cf16c, 8056147c, 80561440, f7cbc8b8}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image atinewp2.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for atinewp2.sys
*** ERROR: Module load completed but symbols could not be loaded for atinewp2.sys
************************************************** ***********************
*** ***
*** ***
*** 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 : atinewp2.sys ( atinewp2+d8b8 )

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

ssubo · 2007-03-08, 05:38

I was using two tuner cards: ATI AIW 128 Pro (to output to TV) and the eHome Wonder (tuner). When I unplugged the AIW 128 Pro I didn't get the BSOD, however I get it when both cards are plugged in at the same time... Does anyone know how to solve this issue? I still need both cards because I want to output to my TV and use the eHome Wonder's tuner which is compatible with the latest MPs...

Thanks a lot for your help!

Ssubo

2007-03-05, 18:23	#1 (permalink)
ssubo Portal Member Join Date: Jan 2005 Posts: 37 Thanks: 0 Thanked 0 Times in 0 Posts	PC Crashes (blue screen) when trying to watch TV I installed a clean Media Center 2005, the latest MP and I have 2 Tuner Cards: ATI AIW 128 Pro (I use this one to output to TV) and ATI eHome Wonder. Both have the latest drivers and I deleted the ATI AIW 128 Pro from MP configuration, as it has a lot of problems. Now when I scan the channels it detects them all and shows them with no problem, but when I open MP and try to watch TV, the TV is extremely slow (like flashing the whole MP) and after less than a minute I get the blue screen and my PC is restarted. I tried using both the MPA and DSCALER. Any ideas on how to solve this issue? Thanks for your help, Ssubo

2007-03-05, 21:26	#3 (permalink)
ssubo Portal Member Join Date: Jan 2005 Posts: 37 Thanks: 0 Thanked 0 Times in 0 Posts	Some additional information... I checked the minidump and it looks like the atinewp2.sys is causing the problem... I tried versions 1.17.24.231 and 1.17.24.200 and still get the same BSOD... Any help will be greatly appreciated! Ssubo Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Mini030507-03.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: * Invalid * ************************************************ ************************ * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * ************************************************ ********************** Executable search path is: ********************************************** ***************** * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ************************************************ *************** Unable to load image ntoskrnl.exe, Win32 error 2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Mon Mar 5 16:49:52.390 2007 (GMT-5) System Uptime: 0 days 0:16:03.981 ********************************************** ***************** * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ************************************************ *************** Unable to load image ntoskrnl.exe, Win32 error 2 * 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 ............ ********************************************** *************************** * * * Bugcheck Analysis * * * ************************************************ ************************* Use !analyze -v to get detailed debugging information. BugCheck 96, {820cf16c, 8056147c, 80561440, f7cbc8b8} ANALYSIS: Kernel with unknown size. Will force reload symbols with known size. ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9 * Kernel symbols are WRONG. Please fix symbols to do analysis. * Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image atinewp2.sys, Win32 error 2 * WARNING: Unable to verify timestamp for atinewp2.sys * ERROR: Module load completed but symbols could not be loaded for atinewp2.sys ********************************************** ******************* * * * * * 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 : atinewp2.sys ( atinewp2+d8b8 ) Followup: MachineOwner ---------

2007-03-08, 05:38	#4 (permalink)
ssubo Portal Member Join Date: Jan 2005 Posts: 37 Thanks: 0 Thanked 0 Times in 0 Posts	Some additional information: multiple cards I was using two tuner cards: ATI AIW 128 Pro (to output to TV) and the eHome Wonder (tuner). When I unplugged the AIW 128 Pro I didn't get the BSOD, however I get it when both cards are plugged in at the same time... Does anyone know how to solve this issue? I still need both cards because I want to output to my TV and use the eHome Wonder's tuner which is compatible with the latest MPs... Thanks a lot for your help! Ssubo

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Windows Blue Screen Of Death !!!	Geon106	General Support	4	2007-01-28 10:31
MP crashes when i watch SAT1	airfranse	General Support	5	2006-10-16 19:05
Blue Screen Total Restart	Bistromaths	General Support	8	2006-08-12 07:42
Blue Screen	Blutarsky	The old Bugreport Forum	2	2006-06-28 10:26
Blue screen when recording changes from 2 channels to 1	Brocklander	General Support	15	2006-01-15 23:26

2007-03-05, 21:16	#2 (permalink)
grandalf Portal Member Join Date: Jan 2007 Posts: 31 Thanks: 0 Thanked 0 Times in 0 Posts Country:	I had similar problems using mce. Went back to standard XP install, and all is OK now. Must be something to do with the media extensions I guess.