Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

help diagnosing blue screen stop error


  • Please log in to reply
4 replies to this topic

#1 dru482

dru482

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:14 PM

Posted 30 December 2008 - 03:54 AM

i have been having a reocurring issue trying to edit some video and been getting stop errors at the same point along the process. i have used a debugger to obtain a description of the minidump that occurs with the stop error and have copied it below. i have also been reading about disabling caching and shadowing features which are mentioned in the stop error desctiption screen.

cpu information:

dell dimension 8300
windows xp professional 2002 (32-bit)
service pack 3
pentium 4 2.6 GHz
2.59 GHz, 3.25 GB of RAM
NVIDIA GeForce 6200 vid card

this is my first post and any information would really really be appreciated.


* * * *


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini122908-04.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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Dec 29 22:56:43.446 2008 (GMT-8)
System Uptime: 0 days 0:03:26.071
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b9a77f24, b63fb8f0, 0}

Unable to load image P16X.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for P16X.sys
*** ERROR: Module load completed but symbols could not be loaded for P16X.sys
Probably caused by : portcls.sys ( portcls!CPortPinWaveCyclic::SetDeviceState+44 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b9a77f24, The address that the exception occurred at
Arg3: b63fb8f0, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
portcls!CPortPinWaveCyclic::SetDeviceState+44
b9a77f24 ff5114 call dword ptr [ecx+14h]

TRAP_FRAME: b63fb8f0 -- (.trap 0xffffffffb63fb8f0)
ErrCode = 00000000
eax=89e0e000 ebx=00000000 ecx=00000000 edx=00000001 esi=89e71a6c edi=00000001
eip=b9a77f24 esp=b63fb964 ebp=b63fb97c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
portcls!CPortPinWaveCyclic::SetDeviceState+0x44:
b9a77f24 ff5114 call dword ptr [ecx+14h] ds:0023:00000014=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: VideoWave11.exe

LAST_CONTROL_TRANSFER: from b9a8d2b2 to b9a77f24

STACK_TEXT:
b63fb97c b9a8d2b2 89e71a6c 00000001 00000002 portcls!CPortPinWaveCyclic::SetDeviceState+0x44
b63fb9b4 b9a8d91d 89e34290 00000002 8ac23ce0 portcls!CPortPinWaveCyclic::DistributeDeviceState+0x4f
b63fb9d0 b9bd8f5c 8ab9041c 89ebd440 89ebd438 portcls!PinPropertyDeviceState+0x93
b63fba34 b9bd8ed9 8ac23ce0 0000000b e1d8b204 ks!KspPropertyHandler+0x616
b63fba58 b9a806a9 8ac23ce0 0000000b e1d8b1f0 ks!KsPropertyHandler+0x19
b63fba6c b9a8d70f 8ac23ce0 0000000b e1d8b1f0 portcls!PcHandlePropertyWithTable+0x1b
b63fbaa4 b9a8074d 89e71a60 8ae44030 8ac23ce0 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
b63fbac0 b9bd8f1f 8ae44030 8ac23ce0 b63fbae8 portcls!DispatchDeviceIoControl+0x49
b63fbad0 b9a808c0 8ae44030 8ac23ce0 89f2de70 ks!KsDispatchIrp+0x126
b63fbae8 b9a80881 8ae44030 8ac23ce0 b63fbb44 portcls!KsoDispatchIrp+0x43
b63fbaf8 b9a9a4c0 8ae44030 8ac23ce0 8aeeaf38 portcls!PcDispatchIrp+0x5f
WARNING: Stack unwind information not available. Following frames may be wrong.
b63fbb44 b6e8ab33 89f2de70 00000000 002f0003 P16X+0x64c0
b63fbb8c b6e8d095 89f2de70 00000000 00000002 sysaudio!PinConnectionProperty+0x42
b63fbbb8 b6e8d1bb 00000001 00000001 00000007 sysaudio!CPinNodeInstance::SetState+0x101
b63fbbd4 b6e8cc92 00000001 00000002 00000007 sysaudio!CConnectNodeInstance::SetStateBottomUp+0x26
b63fbbf4 b6e8ceb6 00000001 00000002 00000007 sysaudio!CStartNodeInstance::SetStateBottomUp+0x29
b63fbc14 b6e8ce23 00000000 00000007 e413d450 sysaudio!CStartNodeInstance::SetState+0x6b
b63fbc24 b6e8863d e2520f00 b63fbc48 b6e8abea sysaudio!CStartNodeInstance::~CStartNodeInstance+0x21
b63fbc30 b6e8abea 00000001 e2520f00 b6e8aba2 sysaudio!CStartNodeInstance::`scalar deleting destructor'+0xd
b63fbc3c b6e8aba2 8ac56e70 b63fbc58 b6e8b35c sysaudio!CPinInstance::~CPinInstance+0x2f
b63fbc48 b6e8b35c 00000001 8ac8c268 b63fbc68 sysaudio!CPinInstance::`scalar deleting destructor'+0xd
b63fbc58 b9bd9695 8a7472c8 8ac56e70 b63fbcb0 sysaudio!CPinInstance::PinDispatchClose+0x26
b63fbc68 804e13d9 8a7472c8 8ac56e70 8ac56e70 ks!DispatchClose+0x32
b63fbc78 8057b199 89f248c8 00000000 00000000 nt!IopfCallDriver+0x31
b63fbcb0 8056d73d 00f248e0 00000000 89f248c8 nt!IopDeleteFile+0x132
b63fbccc 804e1957 89f248e0 00000000 000017ac nt!ObpRemoveObjectRoutine+0xe0
b63fbce4 8056fafd 89f1cbe0 e1904748 89f0b838 nt!ObfDereferenceObject+0x4c
b63fbcfc 8056fa1b e1904748 89f248e0 000017ac nt!ObpCloseHandleTableEntry+0x155
b63fbd44 8056fa65 000017ac 00000001 00000000 nt!ObpCloseHandle+0x87
b63fbd58 804dd99f 000017ac 0012d650 7c90e4f4 nt!NtClose+0x1d
b63fbd58 7c90e4f4 000017ac 0012d650 7c90e4f4 nt!KiFastCallEntry+0xfc
0012d650 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
portcls!CPortPinWaveCyclic::SetDeviceState+44
b9a77f24 ff5114 call dword ptr [ecx+14h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: portcls!CPortPinWaveCyclic::SetDeviceState+44

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: portcls

IMAGE_NAME: portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025ccc

FAILURE_BUCKET_ID: 0x8E_portcls!CPortPinWaveCyclic::SetDeviceState+44

BUCKET_ID: 0x8E_portcls!CPortPinWaveCyclic::SetDeviceState+44

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,264 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:14 AM

Posted 30 December 2008 - 08:52 AM

My guess would be that it's your VideoWave program...possible corruption/damage in either the program itself or the drivers it employs.

http://kb.roxio.com/content/kb/General%20I...mation/000071GN

I would suggest uninstalling/reinstalling the program and updating same...along with a defrag of the partitions which you are using for storage of outputs/inputs you edit.

Louis

#3 dru482

dru482
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:14 PM

Posted 30 December 2008 - 02:17 PM

to hamluis:

firstly...thank you for your reply...

i initially thought along the same lines; i uninstalled the entire program and its affiliated package contents, defragged the partitions, reinstalled the video drivers for the card from disk. still having the same stop screen issue. i will try to download a newer driver for the GeForce vid card i have installed. perhaps that will help. i am wondering what the "portcls.sys" module reference is in the minidump report message is; does anybody know?

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,264 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:14 AM

Posted 30 December 2008 - 03:02 PM

Seems to be an audio driver, description at http://www.dynamiclink.nl/htmfiles/rframes...s/info_p/48.htm

http://msdn.microsoft.com/en-us/library/ms790577.aspx

Louis

Edited by hamluis, 30 December 2008 - 03:04 PM.


#5 dru482

dru482
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:14 PM

Posted 30 December 2008 - 08:56 PM

im not exactly sure how to read that flow chart on the above posted link. it seems the problem only occurs when editing a specific type of media file, namely mpeg2. im wondering if this is a roxio glitch or perhaps a source problem.

i am getting a different error message set after reinstalling audio drivers; each step i take seems to open more problems.

the blue screen stop message is IRQL_NOT_LESS_OR_EQUAL and STOP: 0x0000000a

there are so many variations listed on this message or ones similar to it. i have been wading through all this information and its starting to get confusing.




*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 1c, 1, 804e2056}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+86 )

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

0: 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: 00000000, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, 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: 804e2056, address which referenced memory

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


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiTimerExpiration+86
804e2056 893b mov dword ptr [ebx],edi

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: VideoWave11.exe

LAST_CONTROL_TRANSFER: from 804dcd22 to 804e2056

STACK_TEXT:
f78a2fcc 804dcd22 80562320 00000000 0004c0cb nt!KiTimerExpiration+0x86
f78a2ff4 804dc88d f7896914 00000000 00000000 nt!KiRetireDpcList+0x61
f78a2ff8 f7896914 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
804dc88d 00000000 00000009 0081850f bb830000 0xf7896914


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+86
804e2056 893b mov dword ptr [ebx],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerExpiration+86

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a4044a

FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+86

BUCKET_ID: 0xA_nt!KiTimerExpiration+86

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




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users