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

Please help,my PC crashing


  • Please log in to reply
5 replies to this topic

#1 Manny2009

Manny2009

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 06 July 2009 - 01:39 PM

Everytime I use muxing and demuxing video,my PC shut down and blue screen appearance.

Here is mini dump report of crash.I hope there is solution for this.Thanks in advance.


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


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Jul 5 19:43:43.531 2009 (GMT+2)
System Uptime: 0 days 0:42:58.110
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 804e13b2, f78bac3c, f78ba938}

Probably caused by : ntoskrnl.exe ( nt!KiTrap0D+46c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 804e13b2, The address that the exception occurred at
Arg3: f78bac3c, Exception Record Address
Arg4: f78ba938, Context Record Address

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


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

FAULTING_IP:
nt!KiTrap0D+46c
804e13b2 fe4a23 dec byte ptr [edx+23h]

EXCEPTION_RECORD: f78bac3c -- (.exr 0xfffffffff78bac3c)
ExceptionAddress: 804e13b2 (nt!KiTrap0D+0x0000046c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000023
Attempt to write to address 00000023

CONTEXT: f78ba938 -- (.cxr 0xfffffffff78ba938)
eax=00000000 ebx=00000000 ecx=89467c50 edx=00000000 esi=00000000 edi=892d0000
eip=804e13b2 esp=f78bad04 ebp=f78bad28 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiTrap0D+0x46c:
804e13b2 fe4a23 dec byte ptr [edx+23h] ds:0023:00000023=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

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

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 00000023

WRITE_ADDRESS: 00000023

FOLLOWUP_IP:
nt!KiTrap0D+46c
804e13b2 fe4a23 dec byte ptr [edx+23h]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from 00000000 to 804e13b2

STACK_TEXT:
f78bad28 00000000 892d0000 892d0000 89e9e638 nt!KiTrap0D+0x46c
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x0


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0D+46c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c19b5

STACK_COMMAND: .cxr 0xfffffffff78ba938 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!KiTrap0D+46c

BUCKET_ID: 0x7E_nt!KiTrap0D+46c

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

BC AdBot (Login to Remove)

 


m

#2 hamluis

hamluis

    Moderator


  • Moderator
  • 54,830 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:46 PM

Posted 06 July 2009 - 02:01 PM

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for possible additional information.

How To Use Event Viewer - http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/

My best guess would be either video drivers need to be removed, then updated/replaced...or some sort of RAM problem (either video card/chip or system RAM).

I would try uninstalling the current video drivers and installing fresh drivers first, with emphasis on uninstalling the current ones first.

http://www.optimizingpc.com/install/hardwaredrivers.html

How to update a Windows hardware driver - http://www.bleepingcomputer.com/tutorials/how-to-update-a-windows-hardware-driver/

Louis

#3 Manny2009

Manny2009
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 07 July 2009 - 10:56 AM

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for possible additional information.

How To Use Event Viewer - http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/

My best guess would be either video drivers need to be removed, then updated/replaced...or some sort of RAM problem (either video card/chip or system RAM).

I would try uninstalling the current video drivers and installing fresh drivers first, with emphasis on uninstalling the current ones first.

http://www.optimizingpc.com/install/hardwaredrivers.html

How to update a Windows hardware driver - http://www.bleepingcomputer.com/tutorials/how-to-update-a-windows-hardware-driver/


Louis


Ok.I will try this if that would help.Thank you.

Edited by Manny2009, 07 July 2009 - 10:56 AM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 54,830 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:46 PM

Posted 07 July 2009 - 03:03 PM

It may not help...but it won't hurt :thumbsup:.

Louis

#5 Manny2009

Manny2009
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:46 AM

Posted 08 July 2009 - 11:42 AM

It may not help...but it won't hurt :thumbsup:.

Louis


I tried your suggests,but that doesn't help.I don't know what other to do to fix that.My PC crashes only when I using demuxing and muxing tools for making DVD,like example, SubtitleCreator,IfoEdit,MuxMan,thx anyway.

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 54,830 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:46 PM

Posted 08 July 2009 - 01:44 PM

Those tools (and any video-editor) have their own drivers.

Perhaps you need to try a different program or an updated version, since your system crashes when those tools are used.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users