Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue screen


  • Please log in to reply

#1
Tom Schlichting

Tom Schlichting

    Member

  • Member
  • PipPip
  • 47 posts
when trying to setup hauppage hvr-1800 tv card in media center i get a blue screen and system reboots, this is a fresh install with new mother board.windows,video and tv card drivers are up to date. couldn't zip mini dump,output of windbg is below.
vista 64 bit
ga-ep45-ud3p
core2quad 6700
nvidia 9800gtx
hauppage hvr-1800
4gb kingston hyperx

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini052509-01.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 \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 Vista Kernel Version 6000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02000000 PsLoadedModuleList = 0xfffff800`0219af70
Debug session time: Mon May 25 08:18:59.697 2009 (GMT-5)
System Uptime: 0 days 0:10:17.432
*********************************************************************
* 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 \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
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff800024e05fc}

***** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+4dd90 )

Followup: MachineOwner
---------
  • 0

Advertisements


#2
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
We can't get anything meaninful out of the dump file because the symbols aren't correct. Follow the steps in this article for the symbols (paragraph E): http://usasma.vox.co...ed-02oct08.html

You must enter the correct symbol path ( SRV*c:\symbols*http://msdl.microsoft.com/download/symbols ) and you must be connected to the internet for this to work.

Also, please read the Additional Commands section of paragraph G
Alternatively, you can zip up the minidump(s) and upload them with your next post.
  • 0

#3
Tom Schlichting

Tom Schlichting

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
have ran norton 360,malwarebytes and superantispyware all returned nothing found.here is the output of wndbg.


Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini052509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16830.amd64fre.vista_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`02000000 PsLoadedModuleList = 0xfffff800`0219af70
Debug session time: Mon May 25 08:18:59.697 2009 (GMT-5)
System Uptime: 0 days 0:10:17.432
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff800024e05fc}

Unable to load image \SystemRoot\system32\drivers\HCW85BDA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HCW85BDA.sys
*** ERROR: Module load completed but symbols could not be loaded for HCW85BDA.sys
Probably caused by : ks.sys ( ks!CKsQueue::DeleteMappingsTable+62 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800024e05fc, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800021fa0b0
0000000000000008

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalPutScatterGatherList+1c
fffff800`024e05fc 488b5a08 mov rbx,qword ptr [rdx+8]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

TRAP_FRAME: fffff98001397940 -- (.trap 0xfffff98001397940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800024fa800 rbx=0000000000000000 rcx=fffffa8008305580
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800024e05fc rsp=fffff98001397ad0 rbp=fffffa80047585a0
r8=0000000000000000 r9=0000000000000000 r10=50008a4991340001
r11=00000000000007ff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!HalPutScatterGatherList+0x1c:
fffff800`024e05fc 488b5a08 mov rbx,qword ptr [rdx+8] ds:8284:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000204db33 to fffff8000204dd90

STACK_TEXT:
fffff980`013977f8 fffff800`0204db33 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff980`01397800 fffff800`0204ca0b : 00000000`00000000 00000000`00000000 fffffa80`04d04200 fffffa80`0496a000 : nt!KiBugCheckDispatch+0x73
fffff980`01397940 fffff800`024e05fc : fffffa80`058d8790 00000000`00000014 fffffa80`082c9500 00000000`00000000 : nt!KiPageFault+0x20b
fffff980`01397ad0 fffff980`03e64f52 : fffffa80`059fc440 fffffa80`047585a0 00000000`00000000 fffff980`013b0900 : hal!HalPutScatterGatherList+0x1c
fffff980`01397b30 fffff980`03e5e195 : fffffa80`058d8790 fffffa80`04524d20 00000002`0e7cee05 fffff980`01397be0 : ks!CKsQueue::DeleteMappingsTable+0x62
fffff980`01397b60 fffff980`03e5e113 : 00000000`00000000 fffffa80`082c92c0 fffff980`013ad102 00000000`00000001 : ks!CKsQueue::PutAvailableFrameHeader+0x25
fffff980`01397b90 fffff980`03e5dfbf : fffffa80`047585a0 fffff980`03e5f747 00000000`00000000 00000000`00000000 : ks!CKsQueue::ForwardIrp+0x123
fffff980`01397be0 fffff980`03e5ddd6 : fffffa80`04524c80 00000000`00000000 00000000`00000000 fffffa80`082c92c0 : ks!CKsQueue::ForwardWaitingIrps+0x3f
fffff980`01397c10 fffff980`058a764e : 00000191`be347f50 00000191`be347f50 00000000`00000000 fffffa80`04962540 : ks!CKsQueue::DeleteStreamPointer+0x146
fffff980`01397c50 00000191`be347f50 : 00000191`be347f50 00000000`00000000 fffffa80`04962540 fffffa80`04524ce0 : HCW85BDA+0x4564e
fffff980`01397c58 00000191`be347f50 : 00000000`00000000 fffffa80`04962540 fffffa80`04524ce0 fffff980`013b0480 : 0x191`be347f50
fffff980`01397c60 00000000`00000000 : fffffa80`04962540 fffffa80`04524ce0 fffff980`013b0480 fffff980`013ad180 : 0x191`be347f50


STACK_COMMAND: kb

FOLLOWUP_IP:
ks!CKsQueue::DeleteMappingsTable+62
fffff980`03e64f52 83630c00 and dword ptr [rbx+0Ch],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ks!CKsQueue::DeleteMappingsTable+62

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4549bc67

FAILURE_BUCKET_ID: X64_0xA_ks!CKsQueue::DeleteMappingsTable+62

BUCKET_ID: X64_0xA_ks!CKsQueue::DeleteMappingsTable+62

Followup: MachineOwner
---------
  • 0

#4
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
It looks like ks.sys (a Microsoft driver) is crashing soon after it's accessed by HCW85BDA.sys
But, it appears that you haven't installed SP1 on your Vista system.

Install this patch first: https://www.microsof...f6-f722d0d42a61
Then install Vista Service Pack 1.

If the BSOD's still occur after that, then update your Hauppage TV card drivers.
  • 0

#5
Tom Schlichting

Tom Schlichting

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
Hauppage TV card drivers are up to date, windows update just installed service pack 1, when running the patch it say's that it doesn't apply to this system, going to try and setup tv card again, will let you know how it go's.will reply back soon.

thanks for the help.
  • 0

#6
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
http://support.microsoft.com/kb/812035
Ks.sys may crash if you repeatedly start and stop a Hauppauge playback graph on a computer with an Intel CPU that uses Hyper-Threading technology.
  • 0

#7
Tom Schlichting

Tom Schlichting

    Member

  • Topic Starter
  • Member
  • PipPip
  • 47 posts
it looks like it was due to sp1 not being installed, is working right now, the link is for winxp.

thanks to all for the help again, you people are great.

best regards
Tom
  • 0

#8
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Cool :)
  • 0

#9
usasma

usasma

    Member

  • Member
  • PipPipPip
  • 636 posts
  • MVP
Updated drivers are listed as updated - even if they are corrupted. It's always advisable (in a situation such as this) to uninstall the old drivers - then install a fresh copy.

FWIW - I have a Hauppage TV card in my Vista system that I can't use. It was incompatible with Vista so it just sits there doing nothing since Vista came out.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP