Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD could be video card error?

02 Apr 2010   #1

Windows 7
 
 
BSOD could be video card error?

Hi everyone,

I recently had two BSOD's within a short time period. I was surfing the internet on a site that I frequently go to and had the screen randomly go black and then after about 30 seconds I got a flashing BSOD with purple stripes running through it which was followed by an automatic restart and video driver problems (did not have proper resolution and could not change resolution to proper resolution... was not in safe mode though). After restarting again the computer worked fine, resolution and everything, however I had the exact set of events that I previously described happen once more when I started my browser. After my second manual restart I had no problems. The error I got the second time was:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105

Additional information about the problem:
BCCode: 116
BCP1: 87134148
BCP2: 8EE2A700
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040210-25162-01.dmp
C:\Users\Leo\AppData\Local\Temp\WER-51246-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I've attached my minidump folder so if anyone could check it out and let me know if they have any idea's as to the origin of the issue that would be highly appreciated. Thanks in advance.

P.S: I'm running a Dell XPS M1210 and am out of warranty in a couple months so if it is a hardware issue I suppose I should get it dealt with asap. Previously about a year ago I had the MOBO/video card replaced through warranty due to issues with them and the fan on my computer.

My System SpecsSystem Spec
.

03 Apr 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by LeoM View Post
Hi everyone,

I recently had two BSOD's within a short time period. I was surfing the internet on a site that I frequently go to and had the screen randomly go black and then after about 30 seconds I got a flashing BSOD with purple stripes running through it which was followed by an automatic restart and video driver problems (did not have proper resolution and could not change resolution to proper resolution... was not in safe mode though). After restarting again the computer worked fine, resolution and everything, however I had the exact set of events that I previously described happen once more when I started my browser. After my second manual restart I had no problems. The error I got the second time was:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105

Additional information about the problem:
BCCode: 116
BCP1: 87134148
BCP2: 8EE2A700
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040210-25162-01.dmp
C:\Users\Leo\AppData\Local\Temp\WER-51246-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I've attached my minidump folder so if anyone could check it out and let me know if they have any idea's as to the origin of the issue that would be highly appreciated. Thanks in advance.

P.S: I'm running a Dell XPS M1210 and am out of warranty in a couple months so if it is a hardware issue I suppose I should get it dealt with asap. Previously about a year ago I had the MOBO/video card replaced through warranty due to issues with them and the fan on my computer.
The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

best guess on probable cause YOUR VIDEO DRIVER


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


Loading Dump File [C:\Users\K\Desktop\New folder (4)\040210-35927-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a48000 PsLoadedModuleList = 0x82b90810
Debug session time: Fri Apr  2 23:10:49.732 2010 (GMT-4)
System Uptime: 0 days 23:09:01.839
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
...................................
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 87186510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8ee24700, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
My System SpecsSystem Spec
26 Apr 2010   #3

Windows 7 Ultimate x64 SP1
 
 

Hi man.
You'd must read this Softpedia's article:

Windows 7 Blue and Black Screens for Graphics Driver Installs - On hybrid graphics laptops that are rebooted improperly - Softpedia

Hope it helps you!!!


"PLEASE REP ANYONE WHO HELPS YOU"


My System SpecsSystem Spec
.


Reply

 BSOD could be video card error?




Thread Tools



Similar help and support threads for2: BSOD could be video card error?
Thread Forum
BSOD after adding an external video card error 0x000000124 BSOD Help and Support
BSOD New Hardware (MB, CPU, RAM, Video Card), error 0x000000C4 BSOD Help and Support
Video Card Error while playing MMO Graphic Cards
Video Card artifacts, Memory error, BSOD = all in one BSOD Help and Support
Solved bsod video scheduler and attempt to reset video card BSOD Help and Support
Video hardware error -- but independent of video card BSOD Help and Support
Video card error Virtualization

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:13 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33