BSOD - On Random Startup, please help.

Hello, I have been having this BSOD issue lately and I dont know what has casued this to start, but I do suspect it is the video card. The card is a MSI Hawk 460 and its brand new but the issues if I recall correctly didnt start happening till it was installed.

So the problem is randomly I will boot up the PC and it will get to the black windows logo screen then crash and reboot. It has done it now in the last couple of days on id say 20 bootup's, it would crash half the time.

I did a fresh install of the OS Win7 64 with updated drivers but I used nvidia drivers that were older 260 I believe and not 266. I thought maybe the drivers were the problem.

Anyways please any help would be nice b/c I dont know if its a software thing or a hardware and I dont want to waste money on replacing parts that are not the problem . I dont understand these dump files or anything but I did record and follow the posting FAQ so I could get the correct help.

Thank you for your time.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88003DFAB20
BCP3: 0000000000000000
BCP4: 00000000000001BC
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\021111-21777-01.dmp
C:\Users\Jason\AppData\Local\Temp\WER-24585-0.sysdata.xml

Hello and welcome to Seven Forums,
- Boot into safe mode with networking
- Uninstall the nVidia Drivers
- Use driver sweeper to remove leftover nVidia display driver files Guru3D - Driver Sweeper
- Install the latest drivers Drivers - Download NVIDIA Drivers
- Reboot into normal mode

Also, update this most cause driver.

Code:

ASACPI.sys Mon Mar 28 15:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 11th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Also, update this driver.

yk62x64.sys Tue Feb 24 04:02:27 2009 - Marvell Yukon Networking
http://www.marvell.com/support.html

Thank you for taking the time to help.

So I went and downloaded the ASACPI.sys file "ATK0110 driver for Windows 7"
It now shows...
Created: Thursday, ‎May ‎14, ‎2009, ‏‎10:26:24 AM
Modified: ‎Today, ‎February ‎11, ‎2011, ‏‎2 minutes ago
What is this file for? Im curious.

I also downloaded the Marvel file "yk62x64.sys" and its says...
Created: ‎‎Thursday, ‎September ‎23, ‎2010, ‏‎2:11:28 AM
Modified: ‎‎Thursday, ‎September ‎23, ‎2010, ‏‎2:11:28 AM
Again, is this for the ethernet? Im curious and want to learn more.

Ill try to see if I can get it to BSOD and ill report back.

Also, I am curious if there was anything in those files I uploaded that would lead to any type of error on the video card or the drivers? B/C this problem if I recall right started when I had installed this MSI Hawk. I did a fresh install of windows when I installed it to minimize any conflicts.

Those two files are fine, you just updated them. The graphic drivers could be corrupted and needed to be re install.

The Marvell is for your Ethernet.

Ok I hope I updated the Marvel correctly. I downloaded the setup and ran the the setup and it did some stuff and rebooted. It was the 2nd option they gave me out of the 3 Windows Setup Installer (32- and 64-bit) for Yukon Controllers.

How could I tell if its a hardware issue with the video card? I can the MSI Kombuster benchmark program over night awhile ago and it did not crash or anything, it did what it was suppose to do I guess. But, when I boot into windows at the startup screen sometimes the graphics get corrupt. It did it also when I was doing a fresh install of Win7 2 weeks ago, thats why I thought it is the video card causing the BSOD.

(edit - Kinda like this but not to as bad http://www.pchelpforum.com/graphics/41714-graphic-card-problems-advice-please.html)

I would test the graphics card with Fumark: Video Card - Stress Test with Furmark

Ok so I am running the program and have now for an hour now and I havent noticed anything bad or artifacts.
All I have left to run is Prime95 and I plan to over night when im sleeping.

Any other conclusions? im willing to try anything.

Run Prime95.

   Tip

Run the Blend, Small FFTs, and Large FFTs Prime95 tests: CPU - Stress Test with Prime95

Well, It BSOD again on me today booting up form a cold state.
I also ran memtest and prime95 yesterday for 7hours each and nothing came back with errors.

Details from EventViewer...

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2/12/2011 3:23:39 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Jason-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2011-02-12T23:23:39.112813300Z" />
<EventRecordID>10001</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Jason-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">278</Data>
<Data Name="BugcheckParameter1">0xfffffa80061a4010</Data>
<Data Name="BugcheckParameter2">0xfffff88003b34e64</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x2</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Also, attached the other files.

I wonder if this is coming from your graphics card - the dump blames them.
Test the graphics card with Furmark: Video Card - Stress Test with Furmark

If any errors occur in Furmark (such as artifacts), replace your graphics card or use onboard graphics.

Understanding STOP 0x116: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80061a4010, fffff88003b34e64, 0, 2}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+12ee64 )

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

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

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

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


FAULTING_IP: 
nvlddmkm+12ee64
fffff880`03b34e64 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031829c8 fffff880`04887ef8 : 00000000`00000116 fffffa80`061a4010 fffff880`03b34e64 00000000`00000000 : nt!KeBugCheckEx
fffff880`031829d0 fffff880`04887c02 : fffff880`03b34e64 fffffa80`061a4010 fffffa80`05ef5d50 fffffa80`05e98320 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03182a10 fffff880`0492ef07 : fffffa80`061a4010 00000000`00000000 fffffa80`05ef5d50 fffffa80`05e98320 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03182a40 fffff880`04958b75 : 00000000`ffffffff 00000000`000003c3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03182b20 fffff880`049572bb : 00000000`00000102 00000000`00000000 00000000`000003c3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03182b50 fffff880`0492a2c6 : ffffffff`ff676980 fffffa80`05e98320 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03182bf0 fffff880`04956e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`049cb168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03182d00 fffff800`02f787c6 : 00000000`027a36c0 fffffa80`05eb8360 fffffa80`0396db30 fffffa80`05eb8360 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03182d40 fffff800`02cb3c26 : fffff880`009e9180 fffffa80`05eb8360 fffff880`009f3f40 fffff880`01233534 : nt!PspSystemThreadStartup+0x5a
fffff880`03182d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+12ee64
fffff880`03b34e64 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+12ee64

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dd0e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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