NP5792 BSOD on startup?

Anyone else had this problem. Happened only once to me just now - just wanted to check with you guys.

Switched on my NP5972 lappy this morning (Vista 64 home prem. T7250, 2GB RAM, 100GB HD, 8800M GTX,) and had a blue screen of death. Too fast for me to read the error code.

The laptop started, I think the sager bios loaded (can't remember) but then the screen stayed black (no vista orb) and the mouse pointer showed up. after about 2 mins of that the screen just flicked (there was a weird green pattern in the top left corner) and the BSOD came up. Memory dumped and the laptop restarted.

Anyone else had this problem? Windows error reporting found it was a problem with nVidia and sent off a report (not sure if drivers or card). It recommended to download the latest drivers but I'm still using 167.43 (don't other drivers halve 8800m performance?)

Any help/info on this would be appreciated. Am I looking at a hardware problem? The last thing I'd want to do at this stage is have to send off the laptop to be repaired/replaced.

Thanks
Adam

-EDIT-
Here's the info that came up:

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
WD-20080213-1030.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: FFFFFA800282C010
BCP2: FFFFF98003C56CC0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: 3ee54579-9a55-4e97-b2e3-cd120e70d638

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
WD-20080213-1030-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: 117
BCP1: FFFFFA8001E0D4E0
BCP2: FFFFF98003C56CC0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1
Server information: ffe5d7e1-5965-4ad8-9698-5f1dff6c04ef

 

You can analyze the minidump log to determine what caused it.

To see the BSOD without restart:
- go to System Properties > Advanced tab > Start & Recovery settings > UNCHECK Automatic Restart

Usually BSODs (in a new system) can happen by:
- usually software... what did you last install or update to cause this?
---- drivers, utilities, anti-viruses, etc...
- HDD errors... do a CHKDSK C: /F in Safe Mode
- RAM errors... get MemTest86+ iso, burn image onto a black CD, let it autoboot and do a memory scan (if any errors are listed, then its the RAM)

 

Thanks for the reply.
Unchecked automatic restart.

I'll post the minidump and run the memory/hd test. Shoulda done that when it arrived

 

Your dump seems to be attributed to the videocard drivers or config.... software issue more than anything.

Download a good and stable driver, go into safe mode and uninstall the previous driver, and then restart, then install the new one.

You can ask which drivers that other 579x owners are using.

 

Here's the minidump.
Figure it must be driver related: nvlddmkm.sys is nVidia. I'll try reinstalling my current drivers - they seem to be the only ones where the 8800M GTX runs at full clock speed (according to other threads).
I'm happier with nVidia than I ever was with ATI, but they do seem to have issues. On my desktop they tend to just cut out when running in 3D and the drivers has to restart.

Thanks very much for your help. Think I'll still go ahead with the hd and ram checks.

Kind Regards,
Adam


Microsoft (R) Windows Debugger Version 6.8.0004.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*C:\Program Files\Debugging tools for Windows 64-bit\symbols* http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.amd64fre.vista_gdr.071009-1548
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70
Debug session time: Wed Feb 13 10:30:11.910 2008 (GMT+3)
System Uptime: 0 days 0:02:19.754
Loading Kernel Symbols
..............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8001e0d4e0, fffff98003c56cc0, 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+9cc0 )

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: fffffa8001e0d4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff98003c56cc0, 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+9cc0
fffff980`03c56cc0 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff980`06243a08 fffff980`03b192d0 : 00000000`00000116 fffffa80`01e0d4e0 fffff980`03c56cc0 00000000`00000000 : nt!KeBugCheckEx
fffff980`06243a10 fffff980`03b19103 : fffff980`03c56cc0 fffffa80`01e0d4e0 fffffa80`08fd1c50 fffffa80`08fcb730 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff980`06243a50 fffff980`03ad4c1f : fffff980`ffffe464 00000000`00000000 00000000`00000000 fffffa80`08fcb730 : dxgkrnl!TdrIsRecoveryRequired+0x16f
fffff980`06243a90 fffff980`03b938a7 : 00000000`00000000 00000000`00000002 00000000`ffffffff 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x2f7
fffff980`06243b40 fffff980`03b924a9 : fffffa80`08fcb730 00000000`00000000 00000000`000021fc 00000000`00000000 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffff980`06243b70 fffff980`03ad8c94 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffff980`06243bf0 fffff980`03b922c9 : 00000000`00000000 fffffa80`08fe8990 00000000`00000080 fffffa80`08fcb730 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffff980`06243d10 fffff800`01ee196b : fffffa80`08ffe200 fffff800`01c383b7 fffff980`00c56a10 00000000`00272201 : dxgkrnl!VidSchiWorkerThread+0x95
fffff980`06243d50 fffff800`01c34656 : fffff980`00a21180 fffffa80`08ffe200 fffff980`00a2ac40 fffff980`00bd9290 : nt!PspSystemThreadStartup+0x5b
fffff980`06243d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+9cc0
fffff980`03c56cc0 ?? ???

SYMBOL_NAME: nvlddmkm+9cc0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 473183a1

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

 

Major Major problems.
Microsoft update just updated a load of stuff and now the system won't start at all, it just BSODs and tells me to remove hardware and check the hard disk etc.

Tech info is:

*** STOP: 0x0000007B (0xFFFFF980006079C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

This is even more frustrating as I have some render work for a client which I need to send off today.

Thanks,
Adam

 

There definitely seems to be a software conflict that is causing your BSODs...

So you are using Vista x64? Which drivers are you using?

Did you do a clean uninstall of the old drivers (in Safe Mode)?

Then installed newer drivers?

... if you have time.
Then I might recommend to switch to XP or Vista 32-bit to see if the problem is the same.

 

Apologies for the late reply (had all my wisdom teeth out) but just a quick update:

I was using Vista 64-bit (mainly for my 3D, so don't think I'll be installing 32-bit).

I had cleaned out the system but probably not enough.

Couldn't get the laptop started at all so reinstalled Vista 64-bit and everything seems to be working fine (recovered work files from windows.old luckily).

Gonna see how things go from here.

I was on the phone with tech support and sent them all the details.

Thanks for all your help Gophn!
Adam