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 when playing any videofile


  • Please log in to reply

#1
ed_ua

ed_ua

    New Member

  • Member
  • Pip
  • 2 posts
Hi there,
Help me out please. I've got laptop toshiba Satellite a25-s307.
I just did clean intsall of Windows XP.
Seemed to install all the drivers, dx9, updates.
Every time i try to play videofile, computer crashes with blue screen. Here's dump file.
Thanks. Any suggestions? I think i have to update something, maybe even BIOS.

Loading Dump File [C:\WINDOWS\Minidump\Mini060305-04.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 ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c850
Debug session time: Fri Jun 3 22:03:46.845 2005 (GMT-3)
System Uptime: 0 days 0:02:57.445
*********************************************************************
* 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 ntoskrnl.exe, Win32 error 2
*** 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 unloaded module list
.............
Loading User Symbols
Unable to load image tridxp.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for tridxp.dll
*** ERROR: Module load completed but symbols could not be loaded for tridxp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfa08c82, f0aa7b40, 0}

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

Unable to load image dxg.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
Probably caused by : tridxp.dll ( tridxp+51c82 )

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

  • 0

Advertisements


#2
ed_ua

ed_ua

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
ok obviously it was caused by video adapter drivers.
i uninstalled and installed again. it worked.
thx everyone
  • 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