BSOD in new samsung laptop

[bmori]

I was hoping this laptop would be immune to BSODs but after 1 week I got my first.

The pc is a Samsung RV511 - M480 64bit core i5 running at 2.67GHz, with 500gb hard drive and 4gb RAM. Operating system is windows 7 home premium.

The crash happened when I tried to turn on Cyberlink Power Director which seems to be pre-installed on a segment of the hard drive.

attached is the mini dmp and JCgriff2 zip files.

any thoughts

cheers
Bill

 

[theog]

AS your notebook is new, have the Retailer check it out.
Use the warranty to the full.

 

[bmori]

back to retailer will probably be my last resort option. Generally retailers do not warrant software problems. They reset the pc to factory defaults and run it for a week if no fault shows it is returned. If a fault does show they return it to the manufacturer. At least that has been my experience in the past.

however many thanks for your suggestion

cheers
Bill

 

[MvdB]

Hello Bmori, welcome to SF... I saw from your post in another thread last night that you were also waiting for help.... well, here goes:

Some of your uploaded files are empty which is a bummer, I'll have to figure out why that is... but I was able to look at your dump. It claims you have problems with your Graphics driver. I can't tell you what new drivers to get because of that missing info and you've not filled out your CP stuff...http://www.sevenforums.com/general-discussion/8-forum-rules-info-please-read.html#post23230 see "fill out system spec's" in there...

Anyway... if you don't want to go back to the retailer... find the manufacturer of your videocard/chip and download latest drivers from there. Be sure to de-install old drivers first and do that not only in the standard manner of removing /de-installing software but also by using something like Driversweeper in safemode.

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

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

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


FAULTING_IP:
nvlddmkm+1597d8
fffff880`0f4537d8 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`0308f9c8 fffff880`0f25d000 : 00000000`00000116 fffffa80`0a19a4e0 fffff880`0f4537d8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`0308f9d0 fffff880`0f25cddb : fffff880`0f4537d8 fffffa80`0a19a4e0 fffffa80`087c9c90 fffffa80`07b83100 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0308fa10 fffff880`0ff7cf07 : fffffa80`0a19a4e0 00000000`c00000b5 fffffa80`087c9c90 fffffa80`07b83100 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`0308fa40 fffff880`0ffa6b75 : 00000000`ffffffff 00000000`0011e93d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0308fb20 fffff880`0ffa52bb : 00000000`00000102 00000000`00000000 00000000`0011e93d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0308fb50 fffff880`0ff782c6 : ffffffff`ff676980 fffffa80`07b83100 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0308fbf0 fffff880`0ffa4e7a : 00000000`00000000 fffffa80`087c9c90 00000000`00000080 fffffa80`07b83100 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0308fd00 fffff800`0336d32e : 00000000`0230509b fffffa80`07b24b60 fffffa80`036ca9e0 fffffa80`07b24b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0308fd40 fffff800`030c2666 : fffff880`031d3180 fffffa80`07b24b60 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0308fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+1597d8
fffff880`0f4537d8 4883ec28 sub rsp,28h

SYMBOL_NAME: nvlddmkm+1597d8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d7376ce

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

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

 

[bmori]

many thanks MVdb, much appreciated, I didn't fill out the profile 'cause I have more than 1 laptop and I thought the jcgriff file captured the sys info.

So far that has been the only glitch I've had - NVIDIA has a more recent driver but Samsung says all the drivers are up to date. If it happens again I'll download the new drver

thanks again

Cheers bill

 

[MvdB]

My pleasure. I'd go to nvidia.com and download the latest for your card an OS version there. BUT be sure to first deinstall with Driversweeper in Safemode....