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.
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.
