TechSpot

System reboots while playing video files.

By AustinK
Jun 7, 2006
  1. System reboots while playing WMV video files.

    Hello, I wanted to see if someone could help me out. We're experiencing a random blue screen STOP error 0x0000008E while playing WMVs after some hours. It is a seemingly random crash as we've had it occur after anywhere from 30 minutes to 40 hours of playing videos before the system crashes.

    We have each hard drive (Western Digital) cloned on different machines, specs are as follows:

    Dell Optiplex 620
    Pentium 4 Prescott 430 3.0 GHZ
    2 512 DDR2 Ram Sticks
    2 SATA 80BG and 160GB
    PNY Geforce 6800 GT graphics card

    We have 6 machines with all of the same specs running the videos and each crash randomly throughout the day. I've used other models of computer and hardware configuration and it seems to be no result. We've tried the following:

    1. Replaced the power supply to 375W
    2. Swapped hard drives into an earlier computer GX 280 -- got same crash
    3. Installed latest Nvidia Drivers 84.21
    4. Installed DirectX 9.0c drivers
    5. Removed external usb devices
    6. Reinstalled computer
    7. Installed chipset drivers from Intel

    Still no result. We've then looked at the error logs and we're getting the same error which is it points to the kernel:

    *******************************************************************************
    * *
    * 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: 80000004, The exception code that was not handled
    Arg2: 8053103c, The address that the exception occurred at
    Arg3: bab7e324, Trap Frame
    Arg4: 00000000

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

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


    MODULE_NAME: nt

    FAULTING_MODULE: 804d4000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 3d6dd59c

    EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

    FAULTING_IP:
    nt+5d03c
    8053103c 6a00 push 0x0

    TRAP_FRAME: bab7e324 -- (.trap ffffffffbab7e324)
    ErrCode = 00000000
    eax=01010101 ebx=00000000 ecx=01010101 edx=bab7e648 esi=7ffde000 edi=00030000
    eip=8053103c esp=bab7e398 ebp=bab7e344 iopl=0 nv up di pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000002
    nt+0x5d03c:
    8053103c 6a00 push 0x0
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from f7743724 to 8053103c

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bab7e344 f7743724 e13816e8 00000030 00000000 nt+0x5d03c
    bab7e358 00000000 bab7e648 01010101 01010101 Ntfs+0x23724


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nt+5d03c
    8053103c 6a00 push 0x0

    FAULTING_SOURCE_CODE:


    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt+5d03c

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner

    ----------------------

    Note, each following minidump is pretty much the same thing -- it does not point to a specific error such as a system file, etc. It's identical to the above in the last times, each giving an 0x0000008E.

    If someone can shed some light, this would be great. I'm trying to launch about 200+ of these and this random error is very odd.

    Thanks.
     
  2. IBN

    IBN TS Maniac Posts: 487

    375w PSU is not enough!!! YOu guys need more power from a good brand too.
     
  3. AustinK

    AustinK TS Rookie Topic Starter

    Ok. What kind of power supply do you recommend? Why is there not enough power? I've looked at different options and there is no problem with the power usage.
     
  4. tipstir

    tipstir TS Ambassador Posts: 2,385   +105

    Brand, doesn't matter today! What matters is that you get 430W to 500Ws. Depending on what you have inside. 375 more like 325Ws. Also check your memory with MEM386. It's a dos boot CD and see if your have problems there?

    Is this a home built PC or just you have picked up?
     
  5. AustinK

    AustinK TS Rookie Topic Starter

    Ok, well I did a memtest in windows and the RAM passed. This is a dell optiplex 620 straight off from DELL. The power supply recommended for the graphics card is 350 -- have you seen this happen before where the card takes up more?
     
  6. AustinK

    AustinK TS Rookie Topic Starter

    It just crashed again, here's another dump this time mentioning win32k.sys:


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


    Loading Dump File [C:\memory2.dmp]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: c:\symbols\;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp1.020828-1920
    Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a130
    Debug session time: Thu Jun 8 18:42:30.625 2006 (GMT-7)
    System Uptime: 0 days 20:06:00.407
    Loading Kernel Symbols
    ................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 8E, {80000004, 805304fd, f7903cf0, 0}

    Probably caused by : win32k.sys ( win32k!LeaveCrit+c )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    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: 80000004, The exception code that was not handled
    Arg2: 805304fd, The address that the exception occurred at
    Arg3: f7903cf0, Trap Frame
    Arg4: 00000000

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


    EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

    FAULTING_IP:
    nt!KiSystemCallExit3+2c
    805304fd 0f23fb mov dr7,ebx

    TRAP_FRAME: f7903cf0 -- (.trap fffffffff7903cf0)
    ErrCode = 00000000
    eax=00000001 ebx=00000000 ecx=01010101 edx=ffffffff esi=00c0d3fb edi=00c0d3fb
    eip=805304fd esp=f7903d64 ebp=f7903d64 iopl=0 nv up di pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000002
    nt!KiSystemCallExit3+0x2c:
    805304fd 0f23fb mov dr7,ebx
    Resetting default scope

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from 804f9467 to 804f52af

    STACK_TEXT:
    f79038c4 804f9467 0000008e 80000004 805304fd nt!KeBugCheckEx+0x19
    f7903c80 80530dcd f7903c9c 00000000 f7903cf0 nt!KiDispatchException+0x307
    f7903ce8 80530d66 867863ac 00002500 86786378 nt!CommonDispatchException+0x4d
    f7903cfc bf879588 bf87a93e f7903d64 00ebfecc nt!Kei386EoiHelper+0x176
    f7903d00 bf87a93e f7903d64 00ebfecc bf87a8f6 win32k!LeaveCrit+0xc
    f7903d48 00000000 f7903d64 00000000 805304fd win32k!NtUserPeekMessage+0x83


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!LeaveCrit+c
    bf879588 ff259cff97bf jmp dword ptr [win32k!_imp__KeLeaveCriticalRegion (bf97ff9c)]

    FAULTING_SOURCE_CODE:


    SYMBOL_STACK_INDEX: 4

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: win32k!LeaveCrit+c

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de5e5

    FAILURE_BUCKET_ID: 0x8E_win32k!LeaveCrit+c

    BUCKET_ID: 0x8E_win32k!LeaveCrit+c

    Followup: MachineOwner
    ---------
     
  7. danisvoranu

    danisvoranu TS Rookie

    Too complex. Problem is somewhere, simple, little

    (my english is poor)
    You have a good hardware system(s) and the problem coming from another side.
    I thing is software (player, mostly) and something happen in memeorii (eq stack overflow) depending by another active programs wich rule in this time.
    I hope to usefull.
    dan I
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...