Win 7 BSOD when playing video files

[apex2000]

In the beginning, I had no problems with Win 7 build 7000. I could play whatever video file I wanted and it would work perfectly. Since checking out the various builds after 7000, right up to the latest RC build 7100, I have nothing but problems when playing video files. No matter which player I use, be it WMP, KMPlayer, VLC or Media Player Classic, I get a BSOD after trying to open a video file, including DVD. (Actually, that is not strictly true as I can open *.mpg files for some strange reason.) This problem is so frustrating as I cannot find any answer. This is my machine: Mainboard - ASUS P5VD2-X CPU - Dual Core Intel Pentium D 925, 3000 MHz (15 x 200) RAM - DIMM1: Kingbox Tech. KINGBOX 2GB; DIMM3: Kingbox Tech. KINGBOX 2GB Display - ASUS ATI Radeon HD 3650 (ATI Catalyst 9.4 Driver) OS - Win 7; any build after 7000. I have tried changing my video card for an older ASUS ATI card but got the same result - BSOD. So, my question to you folks is: Can anyone give me a clue as to what might be wrong?

 

[chev65]

I had similar stability problems at first. I just bumped up my SPP voltage a notch and the problems went away. Not a single bsod after that.

 

[Chappy]

Can you post the BSOD info please?
These often contain offending module names or error codes that can be researched.

 

[apex2000]

Can you post the BSOD info please?
These often contain offending module names or error codes that can be researched.

Could you explain how to do that? The BSOD screen flashes on for a second or two then the machine reboots as you know. How do I get the information to post here? Thanks for your help.

 

[apex2000]

I had similar stability problems at first. I just bumped up my SPP voltage a notch and the problems went away. Not a single bsod after that.

Sorry, could you tell me how to do that? Thanks for your reply.

 

[Delphin]

Sorry, could you tell me how to do that? Thanks for your reply.

While bsod, the dump file which contains the information about the bsod will be copied to C:\Windows\minidump folder. Upload the latest one it will help us to look into that.

 

[apex2000]

While bsod, the dump file which contains the information about the bsod will be copied to C:\Windows\minidump folder. Upload the latest one it will help us to look into that.

How can I upload it? The file will not let me do anything; all I get is 'Access denied'. Which application is able to read files with the extension .dmp? Can anyone help please?

 

[RustyNutz]

I'm getting the same BSOD when I try to do anything that involves playing media.

I have a selection of these, but I'll attach the most recent!

Any help would be great.

I have a Dell XPS M1710 Laptop, I could list the hardware I remember, but W7 seems to have made a lot of it up, which is probably the major problems!

The Sound and Video cards have had the original drivers installed, but with Video (Nvidia 7950 Go) the updated drivers wont install because I'm not running XP or Vista on it's OS check!

 

[RustyNutz]

Grrrr, .dmp wouldn't upload, and .txt messes with the format.

It's in the zip file.

Ta
John

 

[torrentg]

The Sound and Video cards have had the original drivers installed, but with Video (Nvidia 7950 Go) the updated drivers wont install because I'm not running XP or Vista on it's OS check!

Did you try to install the the following driver in Vista compatibility mode? Or from the device manager itself?

http://www.nvidia.com/object/geforce_notebook_winvista_179.48_beta.html

Anyway, this is from the dump:

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


Loading Dump File [C:\052109-42120-01 - Copy.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82816000 PsLoadedModuleList = 0x8295e810
Debug session time: Thu May 21 07:40:06.801 2009 (GMT-4)
System Uptime: 0 days 0:05:03.939
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......

You could try from an elevated command prompt, to see if it fixes any corrupt files:

sfc /scannow